热门搜索：
您的位置： -&
软件教程分类查找
非常抱歉！2345软件大全没能为您提供完善服务，万分感谢能得到您的指点！
您的建议：
精品软件课程
人气：335503
Cool Edit是一个非常出色的数字音乐编辑器
人气：679373
腾讯QQ支持在线聊天、视频***、点对点断点
人气：101935
After Effects是一款图形视频处理软件,为电
人气：598293
搜狗拼音输入法是网上最流行、功能最强大的
小游戏推荐
网际快车FlashGet常见问题解答
出处：2345软件大全
人气：6178
核心提示：如果不使用FlashGet，怎样使用浏览器的下载功能？
Q.如果不使用FlashGet，怎样使用浏览器的下载功能？
A.点击的时候请按住"Alt"键，FlashGet会忽略该点击，或者在[选项/监视]中设定按住"Alt"键FlashGet才会监视浏览器点击，也可以在悬浮窗上按右键弹出菜单选择"禁止监视浏览器点击"。
Q.如何使用代理服务器？
A.FlashGet支持代理服务器列表,对于不同的任务可以使用不同的代理服务器,比如下载国内的文件可使用一个代理服务器,下载国外的文件可使用另外一个代理服务器。所以除了要在选项中设定代理服务器的信息之外,还要在下载任务中指明使用代理服务器。
Q."Download All By FlashGet"和"Download using FlashGet"不起作用?
A.1.重新***,***完毕后运行一次网际快车，并且要重新启动浏览器。如果依然没有效果请确定不要***网际快车到一个中文名字的目录下。　2.重新***IE浏览器
Q.无法监视IE的点击?
A. 在"选项/监视"中点击"缺省下载程序".如果还有问题,首先确定“Download All by FlashGet”和"Download using FlashGet"是否有效，如果无效重新***,注意不要***到中文目录下。其次也许由于现在监视浏览器点击的软件比较多，常常会有冲突，FlashGet提供了两种不同的机制实现的监视点击方法，如果一种方式无效可以换成另外一种方式。注意设置完毕后最好重新启动机器。如果只是部分的点击无法监视到，主要是因为IE根本没有传送该URL到监视模块，以后的版本会尽量考虑以其他方法捕获这种点击。目前可以考虑***Opera和FlashGet Opera plug-in,就能正确的监视到点击。
Q.两种的监视方式有何不同?
A.实现的机理式不同的。由于现在监视浏览器点击的软件比较多，常常会有冲突，FlashGet提供了两种不同的机制实现的监视点击方法，如果一种方式无效可以换成另外一种方式。注意设置完毕后最好重新启动机器。
Q.使用IE5.5,FlashGet监视点击后IE跳到一个提示错误的页面?
A.这是由于监视IE点击的方式1与IE5.5兼容的问题，请切换到方式2，注意切换后最好重新启动机器。
Q.提示"Socket Error 100xx"?
A.如果所有的站点均是如此,请确保你与Internet的连接没有问题(如果使用代理服务器请确保在FlashGet中设置的正确，如果使用了防火墙也需要在防火墙软件中设置允许FlashGet访问因特网，具体需要参阅防火墙软件的帮助文件)，另外也有可能是由于创建了过多的连接导致的，请不要同时下载太多的文件。如果只是个别站点如此，应该是该站点临时有点问题或者根本无法连接该站点（比如国内封掉了某些IP),请过些时候再试。 WSAEACCES (10013) Permission denied. An attempt was made to access a socket in a way forbidden by its access permissions. An example is using a broadcast address for sendto without broadcast permission being set using setsockopt(SO_BROADCAST). Another possible reason for the WSAEACCES error is that when the bind function is called (on Windows NT 4 SP4 or later), another application, service, or kernel mode driver is bound to the same address with exclusive access. Such exclusive access is a new feature of Windows NT 4 SP4 and later, and is implemented by using the SO_EXCLUSIVEADDRUSE option.
WSAEADDRINUSE (10048) Address already in use. Typically, only one usage of each socket address (protocol/IP address/port) is permitted. This error occurs if an application attempts to bind a socket to an IP address/port that has already been used for an existing socket, or a socket that wasn't closed properly, or one that is still in the process of closing. For server applications that need to bind multiple sockets to the same port number, consider using setsockopt(SO_REUSEADDR). Client applications usually need not call bind at all—connect chooses an unused port automatically. When bind is called with a wildcard address (involving ADDR_ANY), a WSAEADDRINUSE error could be delayed until the specific address is committed. This could happen with a call to another function later, including connect, listen, WSAConnect, or WSAJoinLeaf. WSAEADDRNOT***AIL (10049) Cannot assign requested address. The requested address is not valid in its context. This normally results from an attempt to bind to an address that is not valid for the local machine. This can also result from connect, sendto, WSAConnect, WSAJoinLeaf, or WSASendTo when the remote address or port is not valid for a remote machine (for example, address or port 0). WSAEAFNOSUPPORT (10047) Address family not supported by protocol family. An address incompatible with the requested protocol was used. All sockets are created with an associated address family (that is, AF_INET for Internet Protocols) and a generic protocol type (that is, SOCK_STREAM). This error is returned if an incorrect protocol is explicitly requested in the socket call, or if an address of the wrong family is used for a socket, for example, in sendto. WSAEALREADY (10037) Operation already in progress. An operation was attempted on a nonblocking socket with an operation already in progress—that is, calling connect a second time on a nonblocking socket that is already connecting, or canceling an asynchronous request (WSAAsyncGetXbyY) that has already been canceled or completed. WSAECONNABORTED (10053) Software caused connection abort. An established connection was aborted by the software in your host machine, possibly due to a data transmission time-out or protocol error. WSAECONNREFUSED (10061) Connection refused. No connection could be made because the target machine actively refused it. This usually results from trying to connect to a service that is inactive on the foreign host—that is, one with no server application running. WSAECONNRESET (10054) Connection reset by peer. An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, or the remote host uses a hard close (see setsockopt for more information on the SO_LINGER option on the remote socket.) This error may also result if a connection was broken due to keep-alive activity detecting a failure while one or more operations are in progress. Operations that were in progress fail with WSAENETRESET. Subsequent operations fail with WSAECONNRESET. WSAEDESTADDRREQ (10039) Destination address required. A required address was omitted from an operation on a socket. For example, this error is returned if sendto is called with the remote address of ADDR_ANY. WSAEFAULT (10014) Bad address. The system detected an invalid pointer address in attempting to use a pointer argument of a call. This error occurs if an application passes an invalid pointer value, or if the length of the buffer is too small. For instance, if the length of an argument, which is a SOCKADDR structure, is smaller than the sizeof(SOCKADDR). WSAEHOSTDOWN (10064) Host is down. A socket operation failed because the destination host is down. A socket operation encountered a dead host. Networking activity on the local host has not been initiated. These conditions are more likely to be indicated by the error WSAETIMEDOUT. WSAEHOSTUNREACH (10065) No route to host. A socket operation was attempted to an unreachable host. See WSAENETUNREACH. WSAEINPROGRESS (10036) Operation now in progress. A blocking operation is currently executing. Windows Sockets only allows a single blocking operation—per- task or thread—to be outstanding, and if any other function call is made (whether or not it references that or any other socket) the function fails with the WSAEINPROGRESS error. WSAEI*** (10004) Interrupted function call. A blocking operation was interrupted by a call to WSACancelBlockingCall. WSAEINVAL (10022) Invalid argument. Some invalid argument was supplied (for example, specifying an invalid level to the setsockopt function). In some instances, it also refers to the current state of the socket—for instance, calling accept on a socket that is not listening. WSAEISCONN (10056) Socket is already connected. A connect request was made on an already-connected socket. Some implementations also return this error if sendto is called on a connected SOCK_DGRAM socket (for SOCK_STREAM sockets, the to parameter in sendto is ignored) although other implementations treat this as a legal occurrence. WSAEMFILE (10024) Too many open files. Too many open sockets. Each implementation may have a maximum number of socket handles available, either globally, per process, or per thread. WSAEMSGSIZE (10040) Message too long. A message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram was smaller than the datagram itself. WSAENETDOWN (10050) Network is down. A socket operation encountered a dead network. This could indicate a serious failure of the network system (that is, the protocol stack that the Windows Sockets DLL runs over), the network interface, or the local network itself. WSAENETRESET (10052) Network dropped connection on reset. The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress. It can also be returned by setsockopt if an attempt is made to set SO_KEEPALIVE on a connection that has already failed. WSAENETUNREACH (10051) Network is unreachable. A socket operation was attempted to an unreachable network. This usually means the local software knows no route to reach the remote host. WSAENOBUFS (10055) No buffer space available. An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full. WSAENOPROTOOPT (10042) Bad protocol option. An unknown, invalid or unsupported option or level was specified in a getsockopt or setsockopt call. WSAENOTCONN (10057) Socket is not connected. A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using sendto) no address was supplied. Any other type of operation might also return this error—for example, setsockopt setting SO_KEEPALIVE if the connection has been reset. WSAENOTSOCK (10038) Socket operation on nonsocket. An operation was attempted on something that is not a socket. Either the socket handle parameter did not reference a valid socket, or for select, a member of an fd_set was not valid. WSAEOPNOTSUPP (10045) Operation not supported. The attempted operation is not supported for the type of object referenced. Usually this occurs when a socket descriptor to a socket that cannot support this operation is trying to accept a connection on a datagram socket. WSAEPFNOSUPPORT (10046) Protocol family not supported. The protocol family has not been configured into the system or no implementation for it exists. This message has a slightly different meaning from WSAEAFNOSUPPORT. However, it is interchangeable in most cases, and all Windows Sockets functions that return one of these messages also specify WSAEAFNOSUPPORT. WSAEPROCLIM (10067) Too many processes. A Windows Sockets implementation may have a limit on the number of applications that can use it simultaneously. WSAStartup may fail with this error if the limit has been reached. WSAEPROTONOSUPPORT (10043) Protocol not supported. The requested protocol has not been configured into the system, or no implementation for it exists. For example, a socket call requests a SOCK_DGRAM socket, but specifies a stream protocol. WSAEPROTOTYPE (10041) Protocol wrong type for socket. A protocol was specified in the socket function call that does not support the semantics of the socket type requested. For example, the ARPA Internet UDP protocol cannot be specified with a socket type of SOCK_STREAM. WSAESHUTDOWN (10058) Cannot send after socket shutdown. A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call. By calling shutdown a partial close of a socket is requested, which is a signal that sending or receiving, or both have been discontinued. WSAESOCKTNOSUPPORT (10044) Socket type not supported. The support for the specified socket type does not exist in this address family. For example, the optional type SOCK_RAW might be selected in a socket call, and the implementation does not support SOCK_RAW sockets at all. WSAETIMEDOUT (10060) Connection timed out. A connection attempt failed because the connected party did not properly respond after a period of time, or the established connection failed because the connected host has failed to respond. WSATYPE_NOT_FOUND (10109) Class type not found. The specified class was not found. WSAEWOULDBLOCK (10035) Resource temporarily unavailable. This error is returned from operations on nonblocking sockets that cannot be completed immediately, for example recv when no data is queued to be read from the socket. It is a nonfatal error, and the operation should be retried later. It is normal for WSAEWOULDBLOCK to be reported as the result from calling connect on a nonblocking SOCK_STREAM socket, since some time must elapse for the connection to be established. WSAHOST_NOT_FOUND (11001) Host not found. No such host is known. The name is not an official host name or alias, or it cannot be found in the database(s) being queried. This error may also be returned for protocol and service queries, and means that the specified name could not be found in the relevant database. WSA_INVALID_HANDLE (OS dependent) Specified event object handle is invalid. An application attempts to use an event object, but the specified handle is not valid. WSA_INVALID_PARAMETER (OS dependent) One or more parameters are invalid. An application used a Windows Sockets function which directly maps to a Win32 function. The Win32 function is indicating a problem with one or more parameters. WSAINVALIDPROCTABLE (OS dependent) Invalid procedure table from service provider. A service provider returned a bogus procedure table to Ws2_32.dll. (Usually caused by one or more of the function pointers being null.) WSAINVALIDPROVIDER (OS dependent) Invalid service provider version number. A service provider returned a version number other than 2.0. WSA_IO_INCOMPLETE (OS dependent) Overlapped I/O event object not in signaled state. The application has tried to determine the status of an overlapped operation which is not yet completed. Applications that use WSAGetOverlappedResult (with the fWait flag set to FALSE) in a polling mode to determine when an overlapped operation has completed, get this error code until the operation is complete. WSA_IO_PENDING (OS dependent) Overlapped operations will complete later. The application has initiated an overlapped operation that cannot be completed immediately. A completion indication will be given later when the operation has been completed. WSA_NOT_ENOUGH_MEMORY (OS dependent) Insufficient memory available. An application used a Windows Sockets function that directly maps to a Win32 function. The Win32 function is indicating a lack of required memory resources. WSANOTINITIALISED (10093) Successful WSAStartup not yet performed. Either the application hasn't called WSAStartup or WSAStartup failed. The application may be accessing a socket that the current active task does not own (that is, trying to share a socket between tasks), or WSACleanup has been called too many times. WSANO_DATA (11004) Valid name, no data record of requested type. The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for. The usual example for this is a host name-to-address translation attempt (using gethostbyname or WSAAsyncGetHostByName) which uses the DNS (Domain Name Server). An MX record is returned but no A record—indicating the host itself exists, but is not directly reachable. WSANO_RECOVERY (11003) This is a nonrecoverable error. This indicates some sort of nonrecoverable error occurred during a database lookup. This may be because the database files (for example, BSD-compatible HOSTS, SERVICES, or PROTOCOLS files) could not be found, or a DNS request was returned by the server with a severe error. WSAPROVIDERFAILEDINIT (OS dependent) Unable to initialize a service provider. Either a service provider's DLL could not be loaded (LoadLibrary failed) or the provider's WSPStartup/NSPStartup function failed. WSASYSCALLFAILURE (OS dependent) System call failure. Returned when a system call that should never fail does. For example, if a call to WaitForMultipleObjects fails or one of the registry functions fails trying to manipulate the protocol/name space catalogs. WSASYSNOTREADY (10091) Network subsystem is unavailable. This error is returned by WSAStartup if the Windows Sockets implementation cannot function at this time because the underlying system it uses to provide network services is currently unavailable. Users should check: That the appropriate Windows Sockets DLL file is in the current path. That they are not trying to use more than one Windows Sockets implementation simultaneously. If there is more than one Winsock DLL on your system, be sure the first one in the path is appropriate for the network subsystem currently loaded. The Windows Sockets implementation documentation to be sure all necessary components are currently installed and configured correctly. WSATRY_AGAIN (11002) Nonauthoritative host not found. This is usually a temporary error during host name resolution and means that the local server did not receive a response from an authoritative server. A retry at some time later may be successful. WS***ERNOTSUPPORTED (10092) Winsock.dll version out of range. The current Windows Sockets implementation does not support the Windows Sockets specification version requested by the application. Check that no old Windows Sockets DLL files are being accessed. WSAEDISCON (10101) Graceful shutdown in progress. Returned by WSARecv and WSARecvFrom to indicate that the remote party has initiated a graceful shutdown sequence. WSA_OPERATION_ABORTED (OS dependent) Overlapped operation aborted. An overlapped operation was canceled due to the closure of the socket, or the execution of the SIO_FLUSH command in WSAIoctl.
Q.提示“无法创建或者打开文件”?
A.首先确定要保存到的目录存在并且是可写的，另外请使用磁盘检查工具检查并修复错误。
Q.点击FlashGet界面右上角的"X"只是最小化?
A.是有意设计为如此的，主要为了防止用户误关闭程序。可以在“选项/其它”中关掉该选项
Q.为什么没有下载像其他下载软件一样的优先级功能?
A.网际快车的下载优先级功能不同一般的下载软件，它是按照显示的顺序依次下载的，这样非常清楚，可以通过工具条的上下箭头来更改下载的顺序，按住“Ctrl”键可以一次移动任务到列表的顶部或者底部。
Q.使用FlashGet无法下载或者下载不对，使用浏览器可以下载为何?
A.有一些站点只允许通过浏览器下载，所以请在设置“选项/协议”中设置 用户代理为“Internet Explore 5.x”可以冒充IE5.x.另外有点站点还有一种限制必须通过特定的引用页，请在下载任务的属性中引用页字段添入从哪下载的页面连接，比如从下载FlashGet, 引用页属性添,还有一种很特殊的情况，如果发送引用页就无法正确下载，可以在“选项/协议”中去掉发送引用页的选项。
Q.速度限制选项是何意义？
A.由于FlashGet的下载速度较快，通常下载时FlashGet会占用几乎所有的带宽，这时基本无法浏览，使用该功能可限制FlashGet使用的带宽，留出一部分带宽供浏览器使用。
Q.条目的速度为什么和主界面右下角的速度为何不同?
A.每个条目的速度是该文件本次下载的平均速度,而右下角的速度是FlashGet下载文件的即时速度
Q.为何把文件分成的最大块数限制为10？
A.近来发现有的用户对于以为分成的块数愈多速度就愈快，其实不然经过我和其他一些用户的测试，有时更多的快数反而会使得速度下降，较多的快数只是对非常慢的连接有效。并且分成的快数越多，整个网络的负担也越重，有可能导致网络（下载服务器）崩溃。对于较慢的连接建议使用计划下载的功能避开高峰时间（白天不能连接的站点，凌晨确能高速下载）
Q.如何使用微软的ISA代理服务器？
A.ISA的确省***只允许一个组"BackOffice Internet Users"使用.会拒绝FlashGet的连接请求。请设置为"Any request"FlashGet就可正常使用，具体步骤: From the SBS console:Expand ISA in the treeExpand Servers and ArraysExpand the server nameExpand Access PolicyLeft click on Protocol RulesRight click on the rule shown in the list view and click PropertiesClick the Applies To tabChange setting to "Any Request"
Q.出现"无法解析域名"的提示如何处理？
A.应该是通过代理服务器上网,参见问题"如何使用代理服务器".
Q.我使用微软的代理服务器软件上网，为什么即使用户名、口令设定正确依然无法下载？
A.网际快车只支持基本的验证方式，想要通过微软的MS Proxy使用网际快车可以使用以下的任何一种方法: 配置Ms Proxy使用基本的验证方式（您要有网络管理员的权限） 在您的机器上***MS Proxy Winsock客户端软件，***完毕后可以直接使用网际快车就象没有使用代理服务器访问Internet一样（在网际快车中设定直接相连）。 通常该客户端软件放在\代理服务器机器名mspclnt 下。
Q.为什么下载到99%会速度会减慢甚至会暂停一段时间?
A.下载接近完成的时候一般只剩下一两个连接，由于其他连接的关闭，导致下载速度较慢，如果这一两个连接再出现连接和下载线路不通畅，就会导致长时间的停顿，在FlashGet中已就该情况进行了一些特殊处理，不过有时依然会有问题，可以设置超时时间为一个较小的值，可以改进一些，不过对正常的下载又有一些影响。最好不要理它，等一段时间就会下载完成。如果着急，可以手动停止再启动。
Q.为什么我的FlashGet是英文界面的?
A.FlashGet中英文可随便切换,从菜单[View/Language]中选择Chinese(Simp)即可转为中文界面.
Q.运行时提示"缺少DLL"或者"连接的设备不能正常运行"(特别是在Win95环境)?
A.这是由于FlashGet需要的一些Dll不存在或者是版本的问题,请*** DCOM98 for Windows98 or DCOM95 for Windows95
Q.运行时都出现错误提示" Failed to create empty document"?
A.1.请***微软最新版的Common Control　2.*** DCOM98 for Windows98 or DCOM95 for Windows95 3.也有可能是下载数据库损坏
Q.运行时都出现错误提示" Unexpect file format"?
A.使用的下载数据库损坏，请使用备份数据库恢复，备份数据库为同目录下的与下载数据库同名后缀名为bk1,bk2,bk3的文件，如果使用缺省下载数据库default.jcd,备份数据库为default.bk1,default.bk2,default,bk3。具体过程：先备份这几个文件到其他目录，然后删除default.jcd,更改default.bk0为default.jcd然后启动flashget
Q.我下载的页面文件为何没有包含连接的图片？
A.请注意下载软件与浏览器的"另存为"的功能不同，下载软件只是对于单个文件下载，如果想要下载页面中连接的图片可以在FlashGet中显示该文件所有连接的窗口中选定添加到下载列表中。如果想要一次下载所有的内容，需要***离线浏览器工具软件。
Q.如何使用FlashGet的管理功能,如何设置缺省下载目录?
A.FlashGet可以把下载的软件分门别类存放,每种类别可以指定不同的磁盘目录,比如可新建一个类别名字为"MP3",磁盘目录为"c:downloadmp3",当下载一个mp3文件时可以指定下载到类别"MP3"中,文件就会保留到"c:downloadmp3"下,下载的条目可移动到任何类别中,同时下载的文件也可移动到该类别指定的磁盘目录中.缺省的下载类别为"已下载",更改它的磁盘目录即改变了缺省下载目录.推荐做法时下载时不必指定存放的类别,下载完成后移动到相应的类别中去
Q.如何一个接着一个下载文件
A.请在“选项/连接”中设定“最多同时进行的任务数”为1，然后开始下载所有的任务，文件就会一个接着一个下载完成。
Q.发现问题如何报告？
A.报告Bug请包含以下信息：　操作系统（务必包含具体的版本号)　FlashGet(JetCar)版本号　错误的简单描述　URL　日志窗口内容,日志窗口就是显示一条一条彩色文字的窗口　如果是“非法操作”包括寄存器内容
Q.下载后的文件无法打开，提示“没有关联的程序”或者提示要用打开方式？
A.有三种可能性：1.由于一些网站的限制或者用户提交给FlashGet下载的地址的错误，FlashGet不能正确下载文件，只是下载了一些页面文件，有时这些页面是服务器动态生成的，文件后缀为php,asp等等，请参照常见问题解答中的相关问题***确保FlashGet可以下载到正确的文件
2.没有***处理下载的文件的相关程序，比如后缀为zip的文件，需要***程序(WinZip等)
3.FlashGet会给未下载完成的文件添加.jc!的后缀，下载完成后会去掉该后缀，可能由于一些特殊的情况(***了某些实时病毒监测软件)造成无法自动完成该工作，请手动去掉已下载文件的.jc!后缀。另外在选项/常规中去掉设置"添加后缀jc!直到文件下载完成"以后就不会有该问题。
Q.为何已经下载完的任务仍留在“正在下载”类别中，而并没有自动移动到“已下载”类别中?
A.请在菜单/工具/默认下载属性中修改类别属性为"已下载",以后添加的任务下载完毕后会自动移动到“已下载”类别，当前已下载完毕而仍在“正在下载”类别中的任务可以托拽到“已下载”类别中。
Q.***了FlashGet的Opera插件后，无法使用IE自身的下载?
A.某些版本的IE会自动导入Opera的插件设置，请卸载FlashGet的Opera插件并且删除机器上的npfgc1.dll,npfgc2.dll,npfgc3.dll和注册表条目HKEY_LOCAL_MACHINESOFTWAREMicrosoftPluginsExtension(run regedit.exe)下相关的内容
Q.FlashGet提示30秒后挂断或者关机？
A.在工具菜单下去掉“完成后关机”和“完成后挂断”的选项。
Q.如何下载Ftp站点的整个目录？
A.任务属性对话框中输入的URL不好包含任何统配符，比如要从下载public目录下的所有文件，可以输入，然后在任务属性的高级设置中适当选择以下三个选项：从Ftp站点下载子目录：可以下载Ftp站点目录中的所有文件和子目录 在本地创建子目录：创建与Ftp站点相同的目录结构。 创建类别：在FlashGet中依照Ftp站点的目录结构创建类别。
Q.如何使用多代理功能
A.首先需要在“选项/代理服务器”中添加一系列代理服务器并且选中多代理功能时使用其中的几个或者全部的代理服务器，在下载任务的站点属性中必须限定为1，选中使用多代理选项。如果在任务的属性中分成5快下载，如果同时已设定了5个合适的代理服务器那么就会使用不同的代理服务器建立5个连接。不过这些设置限制的站点是为了为更多的人服务所以不推荐使用该功能。
Q.如何下载Flash动画？
A.如果使用IE可以通过鼠标右键菜单“使用网际快车下载全部连接”，然后选定swf 后缀的文件下载即可。如果使用其它的浏览器可以用FlashGet的站点资源探索器打开包含 FlashGet动画的网页，选取swf后缀的下载即可。
Q.工具条显示不正确
A.这是显示卡驱动程序的问题，请更新显示卡的驱动程序
Q.获得文件大小后开始下载有明显停顿
A.FlashGet缺省获得文件大小后申请磁盘空间，有的时候文件较大并且用户的硬盘性能不佳（硬盘本身的性能或者磁盘碎片比较多）。第一可以整理硬盘减少碎片，第二可以在“选项/其它”中关闭申请磁盘空间的选项。
相关软件推荐
资源统计：无插件软件：96423个 无病毒软件：96719个 昨日已处理108个带插件、病毒的软件
本站总软件：96719个 软件总下载次数：22.41亿次
软件教程文章：100386篇 总浏览次数：3.219亿次