Reven

I posted again in the tech support forum and it was deleted. If there is still something wrong with my sig, or if there was an issue with the post, can whomever deletes them at least PM me with the issue?

I had a post deleted from the UCSE tech support forum the other day - I guess I missed the big "READ ME NOW" sign for putting my registration in my signature. Anyway, I finally did, but I notice that nothing shows under my "product purchased". I thought at first maybe that didn't show on the public one, but other people's registrations show theirs. If I go to edit my registration, it shows, but not when I view it. I'd rather not have detailed posts deleted, so I'd like to know what I need to do in order to make my registration legit.

This is due to the way the file is packaged. It is stored as a Microsoft Windows Installer package file (.msi). This is embedded inside the .exe with a Windows Installer runtime. InstallShield is doing that nowadays and it's pretty brain dead. When you run the installer, this is what happens: 1) It unpacks the .msi insall package into your temp directory along with an .ini file and the Microsoft Windows Installer runtime. 2) If you already have the Micsosoft Windows Installer on your machine it then immediately tries to run it. If not, then it installs it, and adds an entry in your HKEY_LOCAL_MACHINE/Software/Microsoft/Windows/CurrentVersion/RunOnce registry key that will cause the installer to try and install the package when you reboot. 3) It then creates ANOTHER copy of the package file inside your temp directory. So, you now have the .EXE at 137MB of space and two copies of the package at 131MB each on your system. 4) It then finally processes the install script inside the second copy of the .msi package. I've tried a lot of different ways to try and get it to install under Windows 2000 and no go. But, for the one who is trying on 98 with the small boot drive, what you need to do is edit your AUTOEXEC.BAT and put an entry with TEMP=X:/TEMP where X: is a drive with lots of space. Once you do this and reboot, your Windows temp files will now be on the larger drive (which it should be anyways). Anyone who is developing install scripts, I highly suggest using Wise Installer Pro. It doesn't yet bow to the Microsoft Windows Installer foolishness that InstallShield does.

quote:uhm, it takes 10 engineers to clean an Interceptor? Well, ahem, it was a really intensive date. Lots of repairs needed after they're done.

cruis.in, the person "whining" was me. The situation is this: You have 20 system engineers. 10 of them have been up all night cleaning out Interceptor 3 cuz Lace and Rogue used it for their date the day before (those seats really recline). So you take engineers 1-10 off-duty so that they can get some sleep, and put 11-20 on-duty. You go to assign system engineers to a repair, look at your perscan and see that the system assigned the previously off-duty engineers. Kind of throws a wrench in your crew shift rotations. This way it's simple... if they're off duty, they don't get assigned. If you need them bad enough, then put them (suprise suprise) on-duty, and then assign them. Thanks for the change SC. I don't have to assign people to medibay so much now. ------------------ Cmdr. Tolian Reven GCV Excelsia Ex Turbo Modestum

Ah. So, the part where is says 'Deploy ATV' and it actually doesn't isn't a bug. It's a feature. The Tacops console is playing "Lets make a deal" with us. Was it not a bug when my shiny new 2.09G version ATV (manually launched) as it followed its waypoints tried to do a 'leave planet' maneuver after it's last SEAD order? Some engine in those vehicles now. Point is, planet ops are still hooped. Every time I try a patch I try the same things: 1) Log onto tacops, send a couple shuttles down to deploy two ATV's, and two teams. 2) Have a space battle in an interceptor. 1 is broken, and 2 the AI still cheats (a game play decision I think is what I was told a year or maybe two ago) and moves ships faster than their max speeds. Thinking about it, the tacops code could be cleaned up a lot if the new Shift-E landing code was triggered just before any deploy/extract command. This would make the elevation problems totally irrelevant. If there is a waypoint after, another Shift-E to launch could be triggered, or if not, the current waypoint could be changed to a 'wait for orders'. Trivial - 10 lines of code. Anyways, thanks for the latest patches. Looking forward to the next one. Reven [This message has been edited by Reven (edited 12-28-1999).]

I assume that this same issue is responsible for Extract ATV, Deploy Team, and Extract Team waypoint orders failing as well? ------------------ Cmdr. Tolian Reven GCV Excelsia Ex Turbo Modestum