Eyes.....heavy......must.....sleep......

Thanks a million for the help - I'll dig in tomorrow and get back with some specifics.

Best Regards - B.B.S.

You thanked me 4 times already .
Stop thanking me !

I didn't got your LW running so I don't deserve it .

Hey, I didn't mean to "gush", it's just that I'm so thrilled to have a real person willing to help I almost didn't know how to act.....

Wow, do I feel stupid. I was running LW version 1.8 and it worked like a million. Now, not only did the upgrade poop its pants, but I can get the 1.8 installer to run. I'm dorked.....

I've actually gone through this exercise six times or so, and I'm convinced that it's real and very repeatable.

Also, I normally run a software firewall (Zone Alarm) and I've turned it off for all the "experements" listed below. It shoulden't be an issue.

So, here's where I'm at;

- Uninstall Java. Scan the registry for any "remnants". None found. Reboot.

- Download a fresh copy of the Java VM. It runs and installs fine. The version is 1.3.1_02 and installs in a subdirectory of that name. Reboot

- Attempt to run the LimeWire installer. Both 2.X and 1.X installers crash at the same point; I get to the point where it tries to retreive:

http://www.installengine.com/Msiengine20/instmsia.exe

...and the install won't go any further. I'm offerd the choices of "Retry" or "Cancel" and many, many retries yeild nothing. I again check the registry for any "fragments" find none, and reboot.

- I've downloaded both the packages you recommended. I get identical results with both. I unzip them into a directory I want. It's path is:

c:\Internet Tools\LimeWire

Double clicking on the RunLime.jar file gets me the splash screen, the program seems to 'try' to start, and then I get the following error message:

JAVAW.EXE
Assertion failed: (lock & JAWT_LOCK_ERROR) == 0, file CBanner.cpp line 36

...pressing "OK" gets me the following:

JAVAW.EXE
Abnormal program termination

...pressing "OK" closes the whole show up.

I actually had it work right once. The next time I tried it, it went back to this behaviour. I've rebooted multiple times, so it's not like an environmental variable is getting toggled incorrectly.

If I use the runlime.bat file, the program actually starts and runs....with Java in a DOS window. The only problem with this is that the program won't exit. I'm not confusing minimizing the program to the taskbar with a real exit request. The only way that I can get the program to quit is to force the closure of the DOS box, and when I do that, any changes I've made in the program (like the directories I want to share or number of connections to keep alive) is lost.

Other info that may be of interest - OS here is WME. Every other hardware / software I've tried is very fast and very stable. Internet connection is a cable modem (ethernet, not USB), but every and I do mean every other internet aware application has no problems. It's not like the TCP/IP stack is not installed correctly or otherwise hosed.

Man, I wish I'd have stayed with V1.8........

Regards - B.B.S.

CBanner and JAWT ??

Bingo !

Check your Java JRE dirs (it's main dir and all subdirs)
Also check your windows dir and windows/system dir
Look for this file : jawt.dll
If it's not there I'll attach it to my next post .
One you get a copy of jawt.dll somehow , drop it into LW's main dir .
Problem shoud be fixed then .
If the problem is still there after adding the file , I give up .

OK , you have 2 options , drop this either into :

\JavaSoft\JRE\1.3.1_02\bin\

Or into LimeWire's dir .

Attached Files

jawt.zip (1.2 KB, 55 views)

Well, it was a good try.......good news / bad news;

I found the file in the following directory:

c:\Program Files\JavaSoft\JRE\1.3.1_02\bin

....and copied it to the LimeWire directory. Bad news is that....double clicking on the runlime.jar file produces the same result; I get the "lock error" message......

BUT -

Running the runlime.bat file now seems to work and exit as it should. So, I'm thinking that If I could somehow create an appropriate shortcut that would "start" in the right directories....i'd be all set???

B.B.S.

Is the file you sent me the link to any different than the one I found in the Java directory.....??

instmsia.exe (for WinNT/2000/XP) or instmisaw.exe(for Wi***/98/SE/ME) is the installer program for the Microsoft Windows Installer (compatible with the newest XP behavior).
It seems that this Windows component has been damaged, so this causes the error you have.
If the LimeWire installer cannot get it to work, than you should visit the Microsoft Windows Update web site, to reinstall some components (such as Internet Explorer or any new tool from Microsoft that uses this installer).
Note that the Windows Installer, opposed to most installer programs for Windows applications, is un updatable component. Its advantage is that each installed application can reuse the same installer program to register itself correctly on the system, so it saves megabytes of space on your disk, and it benefits from updated rules that make it work on many different situations, where as many installation programs have only be tested on much less types of configurations.
This installer is a licensed software from a commercial non-Microsoft installer, which has greater install functionalities than the limited Microsoft version: these functionalities only allow more scriptable actions within the installation script for specific applications, but the core components are the same.

I know that that file is from MS installer wich is now up to version 2.0 .
But on my system it still tries to download that file even if i have the latest one installed .

So that's useless info .

We need an LW developer inhere .

LimeWire, by itself, does not need MSINSTIA, the Windows Installer.
Only the installation program needs it, because it is based on the InstallShield install engine, which is now compatible makes uses of the Microsoft Windows Installer core libraries.

I think that you may have a corrupted installation of the InstallShield engine, and it fails upgrading itself automatically.
You should visit the InstallShield support web site to find solutions to your problem.

You may also use the latest version of the Microsoft Registry Cleaner to detect and clean up corrupted Windows components registration. (Warning! don't forget the backup of cleaned entries). One spossible source of problems is that your registry references a component (such as an OCX or shared DLL) which is no more in the registered directory, or that has been renamed or erased.

Check the presence of the VER32.DLL file in the System directory. This file is absolutely required by ALL installation engines on Win32. This file is now part of the core Windows system, but using an outdated version of this file may render some newer versions of installation engines completely inoperable (the Ver32 system library contains functions used to get version information about installed files). Some bogous software come with their own copy of this system file, and overwrite it with an outdated version. This file is most often unused from outside of an installation procedure.

If you have installed Microsoft Office, you may check its components (because Office installs its own installer based on the Windows Installer core engine): click on Help, System Information, then use one of the proposed tools.

This also applies if you have Windows 98SE or ME or XP, because they also provide a version of the MSINFO32.EXE tool used to perform these checks. Then you can run "msinfo32.exe" directly from the Start Menu, Execute command...