Why not become a lifetime supporting member of the site with a one-time donation of any amount? Your donation entitles you to a ton of additional benefits, including access to exclusive discounts and downloads, the ability to enter monthly free software drawings, and a single non-expiring license key for all of our programs.

You must sign up here before you can post and access some areas of the site. Registration is totally free and confidential.

I wanted to try out url snooper about 6 months ago, but never really got it working. I think I managed to get one or two urls, but only while reinstalling or somesuch all the while. I discarded it as extremely flakey (despite the gui and menu making a good impression).

Having forgotten these old problems, I tried again recently, with similar frustration; but this new Borland tip saved the day. I can run the (rather undiscerning) .reg file ____________________________REGEDIT4

Without this preamble all I get is an hourglass for about 10s: no error messages, no window, and task "Urlsnooper" is left running. After lots of such hourglass failures there are lots of "Urlsnooper"s still running.

Ok great!!Now that I have this confirmed to fix the problem I can figure out why and make it a permanent fix that doesnt need the registry hack. Thanks for the info and soon there will be a version that doesn't need this.

However I was able to guess at what you were indicating in this post, re. replacement of "EXE" with "DLL".

I did not understand the issue of the double backslashes. But didn't need to, I guess.

The DLL replacement for EXE in the Data field modifyer worked so nice, I can't help smiling, at a solution after about 30 hours of intermittent and mostly unsuccessful work. I LOVE clicking on the button to tell the machine "English is not found." A human confusing a computer program into doing a mistake, that results in what the human needs, is a very pleasing role reversal.

So now urlsnooper opens and closes reliably on my windows millenium machine, thanks to this rube goldberg misdirect of a dysfunction.

Now I have to figure out how to get urlsnooper to find anything useful in it's packet sniffing.

Thousands of packets eventually mount up, but nothing shows, except for a partial url the very first time packets were sniffed. Now no urls or even partial urls, even from multimedia sites, with streaming audio-video.

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 HKEY_CURRENT_USER\Software\Borland\Locales\"C:\Program Files\URLSnooper2\URLSnooper.exe"

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.

I have recently posted a suggested workaround that avoids error messages and problems when running URLSnooper under Win98 and WinME. This post contains more detailed observations of the program's behavior which may prove useful in finding a permanent solution.

Like the above posters, I find that URLSnooper will start correctly on installation but that subsequent startups produce 3 error messages.

This behavior is determined by the registry valueHKEY_CURRENT_USER\Software\Borland\Locales\"C:\Program Files\URLSnooper2\URLSnooper.exe"and is related to the Localiser.

When the program is first installed this key does not exist. The program will start OK. However, as soon as it starts it writes the data "EXE" to the value. On subsequent startup the program fails and these error messages are generated

Using REGEDIT the data in the value can be altered, as earlier posters have suggested. In fact almost any string can be used and the program will then on startup generate this error message

Localiser Error - Language "English" is not found

but then go on to start correctly.

If the string used in the value is a code for a language - for example "enu" or "fr" or "it" - then the error message changes to

Localiser Error - Language "English(United States)" is not found

or "French" or "Italian" or whatever.

However if the string "en" or "ntv" or an empty string "" is used, the program will start correctly without error message at all, but immediately overwrites the data "EXE" to the value and subsequent restarts fail and generate the 3 error messages detailed above.

This testing was all done on URLSnooper 2.17.01, but a brief test on the previous version, URLSnooper 2.14.02, showed the same behavior.

The Language Manager langmngr.exe also uses the same type of localiser routines, writing the data "EXE" to the value HKEY_CURRENT_USER\Software\Borland\Locales\"C:\[installation dir]\langmngr.exe"but this program works correctly and generates no errors.