Troubleshooting
If you encounter a problem other than any mentioned here, please don't hesitate to contact us via our support email address or web form, both to be found on the Support page.
1. Installation
2. General
3. HTTP Search
1. [Windows NT 4.0 ONLY] When I run the fURI Setup file, the following message is displayed:
Why is Internet Explorer 6 (or later) required, and from where is it available?
Internet Explorer (IE) is closely tied to the Windows operating system. While it exists as a stand-alone application, it adds a host of files and extra functionality to the core platform. fURI hooks into these expanded capabilities on Windows NT 4.0 and above during the course of its normal operation (specifically through the library files URLMon.dll, WinInet.dll, SHLWAPI.dll, MSHTML.dll and MSXML3.dll - on Windows 95 bespoke DOM, XSL Transformation and Rendering tools are used which have no dependencies on these files. Windows 98 and later include each of the library files by default, so this requirement is automatically satisfied).
Windows NT 4.0 came supplied with version 2.0 of the Internet Explorer web browser (circa 1996). In its second iteration, the browser was missing several of the key technologies that underpin contemporary versions (significantly MSXML for working with XML files and a far leaner, less feature-complete set of library files). The arrival of Internet Explorer 6.0 marked a maturation of the browser and related components, with better support for web standards and up-to-date XML handling courtesy of MSXML3.
fURI interfaces with the MSXML3 component during the manipulation of XML documents - several of these operations are not implemented fully in MSXML prior to product release 3. MSXML3 can be downloaded independently from Internet Explorer, and other required library files are available with version 4.0 of the web browser. However, Microsoft no longer provides support and security updates for versions before 6.0. For this reason, and because Internet Explorer 6 bundles all necessary library files together with MSXML3, Windows NT 4.0 users must install IE 6 in order to use fURI (Microsoft has announced that IE 7, 8 and beyond will not be made available to customers using Windows NT 4.0).
At the time of writing, Internet Explorer 6 with Service Pack 1 may be downloaded from the Microsoft website.
fURI requires additional functionality added to the Windows operating system with Internet Explorer version 6 or later. The installer detected an older version, or could not find a valid installation of Internet Explorer so cannot continue at this time. For more information and additional instructions please see the FAQ section of the Teign Valley Software website at: http://www.teignvalleysoftware.com/furi.html.
Why is Internet Explorer 6 (or later) required, and from where is it available?
Internet Explorer (IE) is closely tied to the Windows operating system. While it exists as a stand-alone application, it adds a host of files and extra functionality to the core platform. fURI hooks into these expanded capabilities on Windows NT 4.0 and above during the course of its normal operation (specifically through the library files URLMon.dll, WinInet.dll, SHLWAPI.dll, MSHTML.dll and MSXML3.dll - on Windows 95 bespoke DOM, XSL Transformation and Rendering tools are used which have no dependencies on these files. Windows 98 and later include each of the library files by default, so this requirement is automatically satisfied).
Windows NT 4.0 came supplied with version 2.0 of the Internet Explorer web browser (circa 1996). In its second iteration, the browser was missing several of the key technologies that underpin contemporary versions (significantly MSXML for working with XML files and a far leaner, less feature-complete set of library files). The arrival of Internet Explorer 6.0 marked a maturation of the browser and related components, with better support for web standards and up-to-date XML handling courtesy of MSXML3.
fURI interfaces with the MSXML3 component during the manipulation of XML documents - several of these operations are not implemented fully in MSXML prior to product release 3. MSXML3 can be downloaded independently from Internet Explorer, and other required library files are available with version 4.0 of the web browser. However, Microsoft no longer provides support and security updates for versions before 6.0. For this reason, and because Internet Explorer 6 bundles all necessary library files together with MSXML3, Windows NT 4.0 users must install IE 6 in order to use fURI (Microsoft has announced that IE 7, 8 and beyond will not be made available to customers using Windows NT 4.0).
At the time of writing, Internet Explorer 6 with Service Pack 1 may be downloaded from the Microsoft website.
1. When I right-click a File Search result filename and select Save As, nothing is saved to the location I specify, why?
fURI will not save files from HTTP or FTP servers if the file size is 0 (zero) bytes - in other words, an empty file.
fURI will not save files from HTTP or FTP servers if the file size is 0 (zero) bytes - in other words, an empty file.
2. Does fURI support proxy server access?
Yes. fURI can establish FTP and HTTP connections via conventional or SOCKS proxy servers (see the Help File Proxy Settings page for a description of configuration options). However SSL HTTP (HTTPS) traffic can not presently be routed through a SOCKS proxy, although HTTPS functions correctly via conventional proxy servers.
Yes. fURI can establish FTP and HTTP connections via conventional or SOCKS proxy servers (see the Help File Proxy Settings page for a description of configuration options). However SSL HTTP (HTTPS) traffic can not presently be routed through a SOCKS proxy, although HTTPS functions correctly via conventional proxy servers.
3. Icons appear corrupted or misshapen when I run fURI under VMware Virtual Machine with some versions of Windows. What can I do to improve their appearance?
The reason for this behaviour remains unknown, but may be related to problems with some versions of the VMware Tools package. As a workaround, you can edit your Virtual Machine configuration file (the file with an extension labelled .vmx in the directory containing your virtual machine image). We recommend you make a backup copy of this file before proceeding. Append the following lines to the end of the file:
When the Virtual Machine is next loaded, the icon 'corruption' should no longer occur.
The reason for this behaviour remains unknown, but may be related to problems with some versions of the VMware Tools package. As a workaround, you can edit your Virtual Machine configuration file (the file with an extension labelled .vmx in the directory containing your virtual machine image). We recommend you make a backup copy of this file before proceeding. Append the following lines to the end of the file:
svga.noRectFill = "TRUE"
svga.noRectCopy = "TRUE"
svga.noPatFill = "TRUE"
svga.noOffscreen = "TRUE"
svga.noRasterOp = "TRUE"
svga.noRectCopy = "TRUE"
svga.noPatFill = "TRUE"
svga.noOffscreen = "TRUE"
svga.noRasterOp = "TRUE"
When the Virtual Machine is next loaded, the icon 'corruption' should no longer occur.
4. When my search finishes, no results are shown in the Main Form Display Panel, and a DCB002 error ("File segment missing or in use by another application.") message appears in the Status Panel and Error Log. Why?
This error can occur when several searches are started simultaneously. Search results files are labelled according to the date and time at which they were started. If two (or more) searches are started at exactly the same time (within one second of each other), they will adopt clashing result file names. The first search to finish will process result files for all co-running searches - when other searches subsequently complete they will display this message to indicate that their result files are no longer available.
To minimize the potential for this scenario, structure simultaneously running searches to include a brief (at least one second) delay between the start of each of them. In Batch files this is commonly achieved by adding a line such as:
PING 1.1.1.1 -n 1 -w 3000 >NUL
- between application commands, which directs the host computer to harmlessly attempt to communicate with another PC at a non-existent network address for a period of between one and three seconds.
The error might also be generated if one of the 'sub' files that go to make up the larger search results file has been a) opened, and remains open, at the point when each of those file segments is to be 'combined' into a final consolidated document b) deleted from the Unfinished search files directory prior to file-segment combination - generally, any outside changes to the transient results of an in-progress search (editing/deleting/moving) will very likely lead to errors.
This error can occur when several searches are started simultaneously. Search results files are labelled according to the date and time at which they were started. If two (or more) searches are started at exactly the same time (within one second of each other), they will adopt clashing result file names. The first search to finish will process result files for all co-running searches - when other searches subsequently complete they will display this message to indicate that their result files are no longer available.
To minimize the potential for this scenario, structure simultaneously running searches to include a brief (at least one second) delay between the start of each of them. In Batch files this is commonly achieved by adding a line such as:
PING 1.1.1.1 -n 1 -w 3000 >NUL
- between application commands, which directs the host computer to harmlessly attempt to communicate with another PC at a non-existent network address for a period of between one and three seconds.
The error might also be generated if one of the 'sub' files that go to make up the larger search results file has been a) opened, and remains open, at the point when each of those file segments is to be 'combined' into a final consolidated document b) deleted from the Unfinished search files directory prior to file-segment combination - generally, any outside changes to the transient results of an in-progress search (editing/deleting/moving) will very likely lead to errors.
5. [Windows 95 ONLY] When starting fURI the message:
- is displayed. What does this mean, and what can I do to fix the error indicated?
Early editions of the Windows 95 operating system shipped with an older version of the Windows Socket (WinSock) Library, a collection of files that allow applications to communicate with other networked devices. fURI harnesses WinSock to exchange messages with target FTP and HTTP servers - some messages were not implemented in the earlier WinSock releases. Later iterations of the Windows 95 code base, and from Windows 98 onwards, included the Winsock2 update as standard - this message will only be displayed if your system currently uses the version 1 library.
To upgrade your WinSock files, download the Windows Sockets 2.0 for Windows 95 installer from the Microsoft website. At the time of writing this is available via URL:
Windows Sockets 2.0 for Windows 95 See also the Windows 95 category of the Teign Valley Software File download page where this link will be kept current in line with any changes to the Microsoft website page address.
"Error code (FIO002). Error Operation: Testing availability of required system resources. Error Description: Communications software missing or unavailable. Error Resource: WinSock library"
- is displayed. What does this mean, and what can I do to fix the error indicated?
Early editions of the Windows 95 operating system shipped with an older version of the Windows Socket (WinSock) Library, a collection of files that allow applications to communicate with other networked devices. fURI harnesses WinSock to exchange messages with target FTP and HTTP servers - some messages were not implemented in the earlier WinSock releases. Later iterations of the Windows 95 code base, and from Windows 98 onwards, included the Winsock2 update as standard - this message will only be displayed if your system currently uses the version 1 library.
To upgrade your WinSock files, download the Windows Sockets 2.0 for Windows 95 installer from the Microsoft website. At the time of writing this is available via URL:
Windows Sockets 2.0 for Windows 95 See also the Windows 95 category of the Teign Valley Software File download page where this link will be kept current in line with any changes to the Microsoft website page address.
6. [Windows 95 ONLY] What is 'Stub.exe' in the fURI Program Files directory?
Certain program activities are delegated to smaller 'helper' applications that reside within the fURI Program Files folder (the Path Encoder and File Selection tools, for example). When fURI is first started a smaller 'loader' program runs to check whether it's operating in Graphical or Command Line mode. The loader program is a 'console' application - it has no visual user interface, besides the characteristic black 'DOS' screen. Prior to Windows 98/NT, it was impossible to associate an icon (the image that accompanies a program shortcut) with a console application - Windows 95 always overrides any custom icon with its default black 'command prompt' image:
The fURI Start Menu shortcut 'points' to the loader program, which uses the fURI icon: - under Windows 95, however, the default 'command prompt' image is shown instead.
To avoid confusion, an additional 'helper' application - 'Stub.exe' - is placed in the fURI Program Files folder. 'Stub.exe' is a conventional Windows application, and carries the fURI icon. As a convoluted workaround (in Windows 95 only), the Start Menu shortcut is set to 'point' to the 'Stub.exe' application instead of the 'loader' program, in order that the correct shortcut icon is displayed.
The 'Stub.exe' application has no purpose other than to start the 'loader' program which in turn starts the main fURI executable file.
Certain program activities are delegated to smaller 'helper' applications that reside within the fURI Program Files folder (the Path Encoder and File Selection tools, for example). When fURI is first started a smaller 'loader' program runs to check whether it's operating in Graphical or Command Line mode. The loader program is a 'console' application - it has no visual user interface, besides the characteristic black 'DOS' screen. Prior to Windows 98/NT, it was impossible to associate an icon (the image that accompanies a program shortcut) with a console application - Windows 95 always overrides any custom icon with its default black 'command prompt' image:
The fURI Start Menu shortcut 'points' to the loader program, which uses the fURI icon: - under Windows 95, however, the default 'command prompt' image is shown instead.
To avoid confusion, an additional 'helper' application - 'Stub.exe' - is placed in the fURI Program Files folder. 'Stub.exe' is a conventional Windows application, and carries the fURI icon. As a convoluted workaround (in Windows 95 only), the Start Menu shortcut is set to 'point' to the 'Stub.exe' application instead of the 'loader' program, in order that the correct shortcut icon is displayed.
The 'Stub.exe' application has no purpose other than to start the 'loader' program which in turn starts the main fURI executable file.
7. [Windows 95 ONLY] Why doesn't the application close when I click the 'Exit' item in the File menu, or the 'Close' button in the top-right corner of the Main Form?
There is a brief window of time between the consecutive activities of Transforming a XML Results document into a selected Output Format, and then presenting (Rendering) that converted content in the Main Form Display Panel during which any attempt to close the application might be ignored. This period is relatively short, and in practical terms the contrivance of circumstances is unlikely to be encountered. Should the problem occur, wait briefly then retry a second time.
There is a brief window of time between the consecutive activities of Transforming a XML Results document into a selected Output Format, and then presenting (Rendering) that converted content in the Main Form Display Panel during which any attempt to close the application might be ignored. This period is relatively short, and in practical terms the contrivance of circumstances is unlikely to be encountered. Should the problem occur, wait briefly then retry a second time.
8. [Windows 95 ONLY] The File Selection Tool ignores some of my context-menu settings, and file names flicker excessively as they're added to the main form. What is the cause of this, and how can I fix it?
The File Selection tool uses a component part of the Windows operating System called Rich Edit to display and manipulate file names. The functionality provided by this operating system component is largely implemented by a single file - Riched32.dll (later renamed Riched20.dll). Windows 95 shipped with Version 1.0 of the Rich Edit component - more recent Windows operating system releases included Version 2.0, 3.0 and 4.1 (4.1 actually resides within a new file called Msftedit.dll).
Version 1.0 lacked many of the more advanced features which were available from Version 2.0 onwards, including Unicode support, multi-level Undo, improved display and color selection, and more sophisticated font handling. Without access to these features, the File Selection tool is limited to the reduced capabilities of the Version 1.0 Rich Edit component. These restrictions prevent some of the context-menu options from working correctly (the Prompt Before Exit and Highlight Invalid Files settings, for example), and cause problems when the main form is updated (the display will flicker as new file names are found and added to the list).
Microsoft has issued a software update for Windows 95 users - Windows Installer 2.0 Redistributable - which upgrades the Rich Edit component to Version 2.0. At the time of writing this update is available via the link below:
Windows Installer 2.0 Redistributable.
With this update in place, the File Selection tool will operate as intended, and without any of the problems described.
The File Selection tool uses a component part of the Windows operating System called Rich Edit to display and manipulate file names. The functionality provided by this operating system component is largely implemented by a single file - Riched32.dll (later renamed Riched20.dll). Windows 95 shipped with Version 1.0 of the Rich Edit component - more recent Windows operating system releases included Version 2.0, 3.0 and 4.1 (4.1 actually resides within a new file called Msftedit.dll).
Version 1.0 lacked many of the more advanced features which were available from Version 2.0 onwards, including Unicode support, multi-level Undo, improved display and color selection, and more sophisticated font handling. Without access to these features, the File Selection tool is limited to the reduced capabilities of the Version 1.0 Rich Edit component. These restrictions prevent some of the context-menu options from working correctly (the Prompt Before Exit and Highlight Invalid Files settings, for example), and cause problems when the main form is updated (the display will flicker as new file names are found and added to the list).
Microsoft has issued a software update for Windows 95 users - Windows Installer 2.0 Redistributable - which upgrades the Rich Edit component to Version 2.0. At the time of writing this update is available via the link below:
Windows Installer 2.0 Redistributable.
With this update in place, the File Selection tool will operate as intended, and without any of the problems described.
9. [Windows 95 ONLY] On startup, fURI displays an error message: "Access violation at address 7EB56AB7 in module 'SHELL32.DLL'" (or similar) - how can I prevent this from happening again?
Please install Windows 95 Service Pack 1, which includes an update for file shell32.dll (and other important system file revisions). ONLY install the update if you are running Windows 95 version 4.00.950: the update does not apply and should not be used with later editions. See the Microsoft support article below which details instructions for identifying your version of the Windows 95 operating system.
Windows 95 Service Pack 1
Identifying your version of Windows 95
Please install Windows 95 Service Pack 1, which includes an update for file shell32.dll (and other important system file revisions). ONLY install the update if you are running Windows 95 version 4.00.950: the update does not apply and should not be used with later editions. See the Microsoft support article below which details instructions for identifying your version of the Windows 95 operating system.
Windows 95 Service Pack 1
Identifying your version of Windows 95
10. [Windows 95 ONLY] What are 'ShellExecuteHook.dll' and 'URLViewer.dll' in the fURI Program Files directory?
Internet Explorer - Microsoft's home grown web browser - was not shipped with the initial two releases of the Windows 95 operating system (versions 4.00.950 and 4.00.950a - version 4.00.950A, circa 1996, was supplied with Internet Explorer 2.0). The fURI installer adds an 'Internet shortcut' in the Teign Valley Software Start Menu folder that points to the product web page. With no web browser installed, the shortcut displays no icon, and performs no function. The two additional DLL files (only installed on Windows 95, and only where no web browser can be detected) modify the way that the operating system renders icons for Internet shortcuts (files that end with a .url extension) which point to the fURI homepage, so that they display an image associated with the application rather than an anonymous 'blank' picture.
When the Start Menu Internet shortcut is clicked, a form with information about where and how to download web browser software is shown.
Internet Explorer - Microsoft's home grown web browser - was not shipped with the initial two releases of the Windows 95 operating system (versions 4.00.950 and 4.00.950a - version 4.00.950A, circa 1996, was supplied with Internet Explorer 2.0). The fURI installer adds an 'Internet shortcut' in the Teign Valley Software Start Menu folder that points to the product web page. With no web browser installed, the shortcut displays no icon, and performs no function. The two additional DLL files (only installed on Windows 95, and only where no web browser can be detected) modify the way that the operating system renders icons for Internet shortcuts (files that end with a .url extension) which point to the fURI homepage, so that they display an image associated with the application rather than an anonymous 'blank' picture.
When the Start Menu Internet shortcut is clicked, a form with information about where and how to download web browser software is shown.
11. When I launch two or more instances of fURI simultaneously, a message box appears on-screen with an error which states:
What is the cause and how can I prevent it from occurring?
If fURI is started from the command line in 'Command Line Mode' (with no visible user-interface, other than - optionally - a tray icon in the Notification Area) then a special 'Hot Key' is assigned. Hot Keys are a Windows mechanism for controlling elements of program behaviour with the keyboard (e.g., as a 'shortcut' to navigating through application menu structures).
A Hot Key might involve a single keyboard character or a short sequence of keys that are pressed in combination. Each Hot Key should be 'system-wide unique', that is, specific to an individual program. The program with which a Hot Key is associated does not require 'focus' (i.e., to be the top-most, or currently visible program on the desktop) to receive notification that the Hot Key combination has been issued. The Hot Key combination for fURI consists of a three button sequence involving the keyboard keys labeled Ctrl, Alt and T. When pressed together, starting with Ctrl, then Alt, then the T key, a message is sent to the running fURI Command Line Mode instance which instructs it to Exit (to stop running and perform an automatic Save Progress, then quit).
Because each Hot Key can only be in use by one application at a time, launching two instances of fURI will cause a conflict - and the error message will be displayed. Only the first copy of the application will run, the second will not attempt to continue after the error message dialog box has been dismissed. This behaviour can be controlled by modifying a setting in the fURI AppSettings.ini file. The Configuration Files section of the Undocumented Features topic includes a short description of the line which should be edited. If the value of the JvStoredValAssignHotKey line in the AppSettings.ini file is changed from True (default) to False, fURI will NOT assign a Hot Key at startup, and no conflict will occur.
Unable to assign hot key to application (Ctrl-Alt-T). Close down any software which might be causing a conflict and retry.
What is the cause and how can I prevent it from occurring?
If fURI is started from the command line in 'Command Line Mode' (with no visible user-interface, other than - optionally - a tray icon in the Notification Area) then a special 'Hot Key' is assigned. Hot Keys are a Windows mechanism for controlling elements of program behaviour with the keyboard (e.g., as a 'shortcut' to navigating through application menu structures).
A Hot Key might involve a single keyboard character or a short sequence of keys that are pressed in combination. Each Hot Key should be 'system-wide unique', that is, specific to an individual program. The program with which a Hot Key is associated does not require 'focus' (i.e., to be the top-most, or currently visible program on the desktop) to receive notification that the Hot Key combination has been issued. The Hot Key combination for fURI consists of a three button sequence involving the keyboard keys labeled Ctrl, Alt and T. When pressed together, starting with Ctrl, then Alt, then the T key, a message is sent to the running fURI Command Line Mode instance which instructs it to Exit (to stop running and perform an automatic Save Progress, then quit).
Because each Hot Key can only be in use by one application at a time, launching two instances of fURI will cause a conflict - and the error message will be displayed. Only the first copy of the application will run, the second will not attempt to continue after the error message dialog box has been dismissed. This behaviour can be controlled by modifying a setting in the fURI AppSettings.ini file. The Configuration Files section of the Undocumented Features topic includes a short description of the line which should be edited. If the value of the JvStoredValAssignHotKey line in the AppSettings.ini file is changed from True (default) to False, fURI will NOT assign a Hot Key at startup, and no conflict will occur.
1. fURI ends my search suddenly, or skips web pages from a domain I'd expected it to visit, why?
If a search ends abruptly when you've entered an initial URL and clicked the Start button, or misses pages from certain domains during a search, it's probably because the domain name(s) appear in the Domain Ignore List.
fURI will not visit any web pages that reside within a domain included in the list (a small number of frequently recurring domain names are included in the list by default).
You can remove a domain name from the list on a per-search basis using the List Controls, and optionally make the change permanent by then clicking the Save As Default button at the bottom of the page.
If a search ends abruptly when you've entered an initial URL and clicked the Start button, or misses pages from certain domains during a search, it's probably because the domain name(s) appear in the Domain Ignore List.
fURI will not visit any web pages that reside within a domain included in the list (a small number of frequently recurring domain names are included in the list by default).
You can remove a domain name from the list on a per-search basis using the List Controls, and optionally make the change permanent by then clicking the Save As Default button at the bottom of the page.