A new workaround for Win98 and WinME users.
I am using URLSnooper under Win98SE and finding the same problems as other earlier posters. Whilst the workaround described previously will get URLSnooper working, it generates a Localiser Error message each time the program is started. This new workaround avoids this problem and gives an error-free startup each time.
The problem only arises when the program starts using the "native" english language. If the Translation Pack is downloaded and, say, the french or german language files are placed in the URLSnooper2 directory, then the program will start correctly, albeit in either french or german, provided one of these additional languages is selected from the Languages menu (which will appear automatically when a language file is present).
To get the program to start correctly in english it is neccessary, then, to create an english "translation" file. Download the Translator Kit (link is on URLSnooper homepage) and use this to create a new language file. I chose English(United States) but you could choose any that are on the list. DO NOT simply select English as this will produce confusion with the "native" (english) language file. It it probably not neccessary to actually edit anything (although being a pedant who needs to get a life, I did correct a few typos), simply save the new language file, URLSnooper.ENU.lng, to the URLSnooper2 directory.
Next use REGEDIT to delete the value
Now start URLSnooper. A new menu item - Languages will be present. There should be two options on the drop down menu. English (which will have been automatically selected) and English(United States), the new language. Select this. The registry key will now be set to "enu" and when URLSnooper is started on any subsequent occasion it will automatically start with English(United States) as the language.
I would be glad to post the file "URLSnooper.ENU.lng" on this forum to save you all the bother of going through the above, but as it is a binary file and I am new to boards like this, I have no idea how to do that or even whether it is feasible.
I will also make a separate posting that will detail a series of observations on what is happening when the program starts/refuses to start that may prove useful in diagnosing the cause of the problem and aid in resolving it.