Sorry for bringing this up again for the five billionth time. Listen in though, this isn't really a "help me!" request, but more of a request to understand exactly what is going on under the hood.
About a month ago, my brother reminded me of that great, old Star Trek RTS game where you fought the Borg and build up space stations and just enjoyed yourself for hours: Star Trek Armada! The nostalgia alone forced me to look up information about the game, and once I learned there was a sequel, I immediately grabbed myself a copy.
Installation proved highly difficult, though. After several attempts, I finally gave up, telling myself that there was no way I could get such an outdated game to work on a computer that was made nine years later. Luckily, a few days later, the installer popped up out of nowhere and I loaded the game on my computer and began the process of enjoying myself. After modding the hell out of it to the point of non-functionality, I uninstalled the game and tried to reinstall it.
And I'm back with the same problems I faced before. And I'm far less patient now. I got a taste of how great the game was, and I'm downright addicted! Now, the obvious answer is--- just wait it out. But why? The 'why' is what is bugging me. Exactly what causes this game to hang? I am using Windows 7 with a 64 bit processor, so there are bound to be issues, but I've tried everything--- all internal windows/virus protection is off, UAC is off, and I've gone into the CD-Rom and set it so literally every executable runs in both Windows 98 compatibility mode, and runs as an admin. Running setup.exe starts the setup.exe*32 process, which hangs for about a day... and after a day, _ISDEL.exe*32 and another similar InstallShield process start up, but they have been hanging for a day too (and are taking up about zero processing power, as if they're waiting for something in the background!). I have no idea what triggered the game to start installing last time, and I have no idea when it will begin now.
Does anyone have some sort of technical understand of why this happens? At this point, I'm more curious. I've looked at older messages, so it looks like this subject has been touched on a thousand times, but there is no real explanation.
Thanks in advance,
A humble Armada junkie!
Edit: A solution! After setting every single file to boot in admin mode/windows 98 compatibility mode, I booted the machine up in safe mode and installed it like that--- it worked instantly! So there is a/are process(es) or services(s) that are causing issues with the installer when running the installer in a normal boot, that are not running in safe boot. Intriguing.
Windows 7 is proving to be one big pain in the arse when it comes to old games (anything more than 4 years old can seem to have issues).
My advice here is to make sure your Armada installation is patched to the latest version and totally unmodded. Then zip the whole thing up. You'll find it a darn site easier to just unzip the whole thing without the pains of reinstalling. Of course you will need the cd though but you can also "install" using this method as many time as you want :D
If you are still having issues, it may be wise to install the Patch Project :)
Thanks for the help guys; I was actually wondering if anyone knew what was the holdup under the hood, not really an actual plea for help.
Running in safe mode helped completely, it installed right away--- meaning there is a process or service (or multiples of both) holding the installer up which doesn't RUN in nominal boot. It's quite interesting.
I loaded A2 in program files(x86)(x86) and set compatibility mode to XPSP2 and never had any problems since. I did the same for A1 and also no problems