I keep getting an error message saying to check if this is valid windows installer program. I have been through all of the troubleshooting things, dowloaded lots of things separately etc. etc yet still keep getting this same message duing installation. PLEASE HELP!!!!!!!!

Please let us know the exact filename of the installer you downloaded as well as the name and version of your operating systems.

So far I have the hunch you downloaded the wrong installer.

Did you already download and install Java, btw.?

Well, I wish I had good news.

I have Win2000Pro with all latest security patches.
I am the administrator.
I do not have Limewire installed.
I downloaded.
I downloaded and installed Java1.3.1 stuff as prescribed.
I already have the MSW...exe program installed from another program (GMAX) so I cannot install another one over it (or at least that is what it says when I try).
I get the 1608 error.
I downloaded the .MSI file just fine manually as you said, installed it, and it installs perfectly.
I rerun LimeWireWin and still it tries to download the .msi file, and sure enough, gives me the 1608 error.

Now I have tried to find this DMC...exe program you refer to but do not have it on my system at all. I to have one with the same front name but the extension is dll but I am sure that is not what you are referring to.

If I do not get this resolved soon...I am going to have to move to another program because it is getting too frustrating.




NealT

NealT-

I unfortunately don't think there's anything we can do to solve this, as we only have limited control over exactly how the installer runs.

That said, we do have an alternate windows installer for LimeWire Pro that will almost definitely work for you. It's not avaiable for the free version basically just because we didn't have the same motivation to make it, but if you buy pro, it's listed at the bottom.

I'm really sorry that this is the only option, and I'm really not trying to extract money from you -- I just thought I would let you know that the option is there.

The thing that pops up for me is it wont download INSTMSIA.EXE. How do i fix that?

Adam and all,

Don't get me wrong...if the alternate installer will work (99% probability at least ) I don't mind shelling out the money. I hate BS and the rest just do not have the features. I just don't like shelling out the $$ not knowing whether or not it will work.

The other installer is the NullSoft installer, which is about as basic as an installer can get. InstallShield can run into problems basically because they're trying to do so much, and the version we're using is the most recent one that is using Microsoft's new Windows Installer Service, which can run into problems. We use it, though, because it allows us to do nice things like dynamically download the JRE installer.

So, anyway, I have not heard of a case of the Nullsoft installer not working. If you choose to buy pro and it doesn't work for you, just send me e-mail at afisk@limepeer.com.com, and I'll refund your money. It also comes with 6 months of free upgrades, which will be nice considering all of the major improvements that we're working on. Plus it comes with e-mail support.

On the INSTMSIA.EXE issue, it's pretty much the same thing -- there's nothing that we can do differently in the installer to get it to work, and there's nothing you can do as a user to get it to work. Again, though the NullSoft one should work. Sorry about this. We're really not trying to force people to buy Pro.

Install Shield gives me this:

1608 Unable to create InstallDriver instance

thanks
linda
blondie@pobox.com

Just a quick suggestion for those who have tried to follow the steps outlined above and have been told that they have the wrong OS when installing instmsiw.exe. I've had similar problems, but managed to solve them by downloading and installing instMsiA.exe (Windows Installer 2.0 I think) from the Microsoft website. I then ran isscript.msi as outlined above and LimeWire installed fine. Hope this helps someone, it worked for me with Windows Me.

InstallShield claims this issue is fixed with their most recent release, at least for the majority of cases. It apparently happens when you're running on a network that doesn't use Microsoft's networking software. The next release will include an updated installer that should solve it.