When I try to uninstall emplode on my old notebook, it keeps looking for a computer that's no longer on my network. I only drag out this notebook when I need something w. a serial connection. I'm hoping I didn't do something as stupid as install emplode b13 off of a networked drive... Is there a way to manually uninstall emplode or convince my computer that's it's gone?

The new 2.0 final will (for the first time ) properly install over Beta 13 without complaining, so go ahead and do that. I think it'll be OK.

Why the deinstaller is doing that network-drive thingy is beyond me. It's all FM if you ask me. Those newfangled MSI installer packages are a complete PITA, I hate them with a passion. I recently found a bunch of crap left over from those things in my Windows directory, many megs worth of stuff that I just frickin' deleted, made me so mad.

This is what I keep getting...

God, I hate MSI.

Okay...

Dig around your registry searching for some subset of that value, perhaps just the server name. Also do a "containing string" search in the Windows folder to see if one of the MSI package doohickeys has that value squirreled away. Make sure you've got hidden/system files turned on before you do the search...

Anyone know how to deal with:



I've had this error message on 2 systems. First on an old Win95 laptop - I uninstalled beta13 first. And secondly on a Win2k box, I didn't uninstall beta13 (apparently not neccessary anymore).

Net result, I can't install emplode. Help!

Hmm. And it appears that M$ photo editor didn't do a WHYSIWYG on that either
I hate windows.

Why on earth would Windows be looking for the uninstall program in your temp space??? Did you recently upgrade your installer? Try doing a search for that filename on your hard drive (probably \windows \winnt or a system or system32 below it) for that file, and run it directly. Or, failing that, copy it to where it thinks it should be.

You might have something in the registry pointing to that as your uninstaller program location. That can be fixed if you want to search the registry for that filename and adjust it to the proper location.

God, I hate MSI.

Email me and I'll send you the fricking loose EXE file.

God, I hate MSI.

Why on earth would Windows be looking for the uninstall program in your temp space?

Because MSI is a steaming pile of poo.

Just a guess, you might want to check and see if the previous version was completely uninstalled (meaning files and registry entries). I've gotten this type of an error before when an application wasn't completely uninstalled in the registry, (thank you msi) but all the files were deleted. If this turns out to be the case, you have to go in with regedit and delete the msi entries still hanging around. One quick thing to check, is the application still listed in the Add/Remove programs?

God, I hate MSI.

Tony, you can't say that enough times. I can't tell you the number of problems we're having with msi installs right now. Our users are afraid of our product because the install only works about 80% of the time.

God, what a pile of poo.

What is happening is that installshield is looking for instmsiW.exe in the temp directory that winzip created. I found a copy in the old temp directory from beta13, and copied it across to the new directory, and ran setup from there.
So then it complains that it can't find instmsiA.exe. Same process.
Now it complains that Windows Installer cannot install the application and that I need the latest sevice pack.
Here is the dilemma, the old laptop is relatively stable in it's current Win95 configuration. Limited, sure, but it does what I need it too. Even if M$ have released a service pack for it recently, I doubt that I'd want to install it. I managed to reinstall beta13 without any problem.
The Win2k box is SP2 (IIRC). I had no intention of signing up to M$ spyware in order to get SP3 on it.

I'm screwed. I think I'm going to wait for JEmplode to catch up. Unless anyone knows of a Microsoft Installer update that doesn't require signing all of my privacy rights away.

:sigh:

Tony, this is the problem, as posted by GeoffT in the General section, looks like some files were missed from the Zip, I get exactly the same error (except for the path to where I unzipped the files too of course! ):

I get the following error when I try to install Emplode V2.00 to Windows 98.

1155 File C:\My Documents\Empeg Stuff\car-emplode-v2.00\INSTMSIA.EXE not found

The contents of the above downloaded directory are
RIOHD.inf
RIOHD.sys
rioxdrv.inf
RIOXDRV.sys
setup.exe

There is no file named INSTMSIA.EXE

I notice that in the downloaded directory for the previous versions the files
instmsiA.exe
instmsiW.exe
do exist


Am I doing something wrong (again!) or are these files missing? I have ininstalled the previous version of emplode (beta 13)

There's gotta be a Microsoft "Q" article on how to fix problems with the MSI engine somewhere. If anyone has it, I'd love to put it in the FAQ (and perhaps maybe it could also be linked from the empeg download page... if it exists...).

In simple terms (I can understand most things simple) does this mean I can just copy the MSI files from the Beta13 download and run that?

No, using the beta13 versions hasn't worked for me on either Win95 or Win2k.

I get the following error when I try to install Emplode V2.00 to Windows 98.

1155 File C:\My Documents\Empeg Stuff\car-emplode-v2.00\INSTMSIA.EXE not found

INSTMSIA.EXE is the file to install the MSI installer. I do recall someone saying that the new install is utilizing the option in Installshield 8 to get a new version of the installer from the internet. If I were to guess (since I'm not exactly an msi guru here) I'd say that the mechanism for downloading the msi engine isn't working. There must be a way to manually download the msi engine and install it, and this I suspect would fix your problem.

I notice that in the downloaded directory for the previous versions the files
instmsiA.exe
instmsiW.exe
do exist

The "A" and "W" are different version of the MSI install engine for 95 and NT codestreams, though I don't remember which is which.

Here is the download for the "A" version of the installer (95, 98, ME):
http://www.microsoft.com/downloads/details.aspx?FamilyID=cebbacd8-c094-4255-b702-de3bb768148f&DisplayLang=en

And the W Version (NT, 2000):
http://www.microsoft.com/downloads/details.aspx?FamilyID=4b6140f9-2d36-4977-8fa1-6f8a0f5dca8f&DisplayLang=en

You should try downloading and installing these before attempting to install empload. When the empload install comes up it will no longer require these files if the installer is up to date, or at least that's my guess.

Excellent, followed your link FerretBoy and installed the new fangled Microsoft bit and now all is installed OK

Thanks again

Graham

SE_Sport_Driver or Genixia... Did either of those work for you?

To concisely state the bug then: it seems that the installer is not properly downloading a new msi engine if it detects and out of date version on the machine. A workaround is to download the proper engine from the above links and install it before installing empload.

Just finished testing...

Thanks Ferretboy!
Confirmed on both Win2k and Win95

Tony, can you recommend that those 2 links and a brief description get added to the release notes?

I'll put them in the FAQ now, and this thread should serve as the recommendation.

I'm finding references to Host2a-, but they seem to be for MS Explorer mainly... and I'm not sure what to do with them..

SE_Sport_Driver, did you try upgrading your MSI installer engine, using the links that Ferretboy posted?

By the way, thanks for those links, Ferretboy. They're in the FAQ in two places now.

I get that error when trying to uninstall emplode 2.00b13 too. But let me give it a shot... "stand by".

I'm still getting the error... looks like hacking the registry is the only thing that's going to help.

Once I find that entry, do I just delete it? Or change the Host 2a- to something else?

I have no idea at this point.

However... Now that you've upgraded your MSI engine, can you just install atop beta 13 without bothering to do the deinstall?

It appears as though your problem is something else (not the installer problem Tony just added into the FAQ).

To answer your question, I'd say you want to delete the entry, not change it. I'm not sure what it's looking for on Host 2a, but whatever it is I gather it isn't going to find it. If this is true, you're most likely going to have to do the uninstall yourself, which means deleting files and stuff in the registry.

It goes without saying that hacking the registry can do serious damage if you delete the wrong thing.I'm not sitting at a windows machine at the moment, but if you're not in a hurry I can PM you tommorow morning when I get to work with some specifics of where to look for this stuff. If someone else wants to jump in, of course, feel free.

Tony, during the install, it was looking for something in "My Pictures" ?!? NO idea why, but removing that line in my registry fixed it! Flashing the Kernal right now. 2.0 here I come.

Thank you everyone.

(ps, I hated putting this in Bug Reports because even from the beginning, my problem was clearly something on my end.)

IMHO, it is a bug in the Microsoft Installer, so I think it should have been in Bug Reports. Ah well... at least you're up and running.