Error after exiting Homeworld

[Forward Observe]

I posted this on the Homeworld Universe boards, but thought I would try here also.

I just got the Homeworld game of the year edition that comes with the extra CD that has music and the 1.05 patch.

I have no problem playing the game, but if I exit Homeworld and I try to play any other game, I get an error message that says:

"The (any other game) has caused an undefined error and will now close. Try restarting if you continue to have problems. "

Restarting solves the problem, but it is a bit irritating to have to do that every time I exit Homeworld. Also, if I try to restart Homeworld after exiting, I get a totally locked up black screen, and I have to to a hard reboot to get out of it.

I have contacted the Sierra support via E-mail but have really only gotten stock answers like telling me to check their FAQ.


MY system specs:

P4 1.7 gig
256 RD Ram
Graphics card: G3 Ti200
Sound card: Soundblaster live gamer
DirectX 8.1a
Op system: Windows ME

I tried a complete uninstall, disk scan, defrag, and re-install, but the results are exactly the same. I have all of the latests drivers and my start up file has been gleaned to the minimum. (What die-hard gamer doesn't do all of this stuff, anyway?) Before adding the 1.05 patch, I could not get past the Sierra and Relic splash screens. It would drop me back to the desktop with a resolution so big that only 1/4 of my desktop was visible. After patching, I could play, but once again had the problem as originally stated.

I installed two other games to see if it was related to new installs, and not the game itself. One was Battlecruiser Milinneum and the other was Stronghold. Now this same poblem occurs after exiting BCM, but it does not with Stronghold. This seems to point to a game related problem, but then I think Windows ME has problems in general so I don't have a clue at this point.

It appears that something is not closing when exiting these games, but when I try the old Control-Alt-Delete trick I see nothing other than systray and Explorer.

Anyone have any suggestions short of a complete recovery and reformat or getting rid of Windows ME.

cheers

[CruiserCarrier]

Your in luck, sorta.

I USED TO HAVE THIS SAME EXACT PROBLEM. Cataclysm and other games won't cause this crazy issue.

When I had this problem, I was able to run HW. But after exiting, the DirectX drivers would be disabled or something. I was wondering why I would get a black screen after trying to re-run the game. I tried testing out the DirectX diagnostic tool. It didn't detect DirectX and/or its drivers. In any case playing HW would automatically disable DirectX and/or its drivers. I used to have this problem. Strangely enough, Cataclysm, even though it didn't get enough patches and wasn't even beta tested, didn't display this issue.

Well, to be honest with you, I never truly solved this problem myself. Understand that I tried all sorts of video drivers, sound drivers, chipset drivers, reformatting my hard disk, and everything possible combonation, to no avail.

However, that was on my old computer. Since I tried nearly all combonations of drivers and still got this issue, my assumption is that it lies with your OS, Windwos Me. MY old computer OS is Windows 98. Since Windows 98 and Windwos Me are closely similar, my best guess is that it's the operating system.

My new computer does not display this issue. Of course, it IS running WindowsXP, and I believe that is the reason why. Microsoft has really done an excellent job with this operating system, and I would recommend it, even if you didn't get this reoccuring issue. In fact, I have had this machine for several weeks and it still hasn't acted up once. This amazes me, since I was used to doing a restart every few hours on 98:D

Repeat, I believe it is your OS, Windows Me, because I have tried all sorts of drivers for my hardware. I think it is not a driver problem but a Me problem. So after switching to this new XP machine, I didn't get this problem again.

By the way, I saw your original post on the HWU forums.

[Forward Observe]

Thanks, CruiserCarrier.

I guess that I may just have to bite the bullet and get WinXP.
I know that I have to do my part to keep Billy G. out of the poor house even if it puts me there. Haha!

I have heard that XP is very stable compared to all of the beta operating systems that Mickeysoft put out before it, and it stands to reason that all of the new software (games) coming out will be designed around it anyway. Conversely, I guess with all of the new hardware, XP, and direct X advances (Direct X 9 is in beta now) some older games may just get to be unplayable in the future. Sigh!

I just get a bit anal retentive when everything doesn't work like it should. Thanks again for the info.


Cheers

[ÜberJumper]

Head to the Bug Submission forums here and check the MTL.

Some command line switches you should try are:

/safegl /noswddraw /noglddraw /nodebugint /nofastfe

and /dsoundcoop or alternately /waveout

[Forward Observe]

Originally posted by UberJumper
Head to the Bug Submission forums here and check the MTL.

Some command line switches you should try are:

/safegl /noswddraw /noglddraw /nodebugint /nofastfe

and /dsoundcoop or alternately /waveout



I guess I thought that all of these commands were there to try only if you couldn't get the game to run at all, or simply to make it run better.

Will they help my problem, which is after I exit and try to run another game? Also should I try each one individually or in combination?

Thanks in advance for your help.

[CruiserCarrier]

I suggest you to try them all individually. If that doesn't work, go for combos.

By the way, I have tried the Detonator 3 (12.42) drivers from nVidia's archives before on my old machine. Strangely enough, those drivers were able to have me run the game two times in a row. Any more times after and it'd disable DirectX. Of course, this is useless since the problem still exists. I just thought you'd like to know....

By the way, in no way am I garanteeing results by switching to WindowsXP, as I'm not so sure about this issue myself. Again, I have tried nearly every single combo of diagnostics. Then again, I am using a totally new computer so I am not sure. However, I am just making my best educated guess based on my knowledge to assist you. I truly hope my tips help.

One last thing, the nVdia 28.32 drivers have some texture management issues. This means that it handles the textures in an inefficient way, so performance can drop suddenly for a brief second (entering new area, picking up new weapon, etc). However, this issue is only limited to Unreal Tournament. It is unknown if this also affects Unreal engine games as well. Maybe this is an issue that is affecting HW? I doubt it, since older drivers wouldn't work either, but more information can never hurt....

Good luck.

[Forward Observe]

OK, now I am totally confused.

I right click on my desktop shortcut to Homeworld. I click on properties. A properties box comes up with two tabs. One is general and the other is called shortcut. There are five boxes with changeable data.

1. Target---"C:\Program files\Sierra\Homeworld\Homeworld.exe"
2. Start in---"C:\Program files\Sierra\Homeworld"
3. Shortcut key---none
4. Run---nomal window
5. Comment---This is blank

The first two have a file address in quotes. If I try to insert a command at the end in either one of these inside the quotes, and Click OK or Apply, I get an error message that says that this file name and path does not exist.


Sorry, if I am being dense, but what am I missing here? Does the command go in the comment box? :dunce:

[CruiserCarrier]

You type the commands in the "Target" section. Simply click on the "Target" section, add a space, and type the command in. If you wanna try more than one command simply add another space and type it in.

[Forward Observe]

By Jove, I think I got it. Somewhere I read in the MTL thread about enabling the pilotview and the writer said that the command goes inside the quotation marks. They do not, but instead start after the quotation marks around the file path. Someone should correct that statement, it had me pulling my hair out for a while.

Thanks again.

[HWfreak11]

I don't have that problem with Homeworld, but I do have it with something else.

I have:

Dell Dimension 4100
P3 866mhz
GF3 TI200
PC133 RAM
D815EEA motherboard
WIN98

When I try to run the nVidia "bugs" demo (GF4 demo, but works on the GF3), it works the first time, but if I try to run ANY OPENGL OR DIRECTX program after, it won't work. Just reboot. Its not like it takes 5 minutes... or does it on your machine?

[Forward Observe]

Well, none of the commands solved the problem. I really think that it is graphic related since shutting off my sound card had no effect. Also when I try to restart Homeworld after exiting and have to do the hard reboot, when my system comes back up, my desktop resolution is reset to 640 x 480. I may concentrate on some of the graphics commands, but I really tired of fooling with it, and would rather just play the game.

I thought about going back to old Nvidia drivers, but that seems like buying a new car and putting an old engine in it. I think I am finally resigned to just restarting each time I exit the game.

I hope that my next post is a nothing more than a strategy question or some other fun topic.

Cheers

[CruiserCarrier]

Yeah, I hated that issue from the bottom of my heart. For some queer reason, it simply kills the video drivers after exiting from HW.

HWfreak11, it seems that you are running 98....just like I was when I had the problem. It's strange the computer must be restarted to get the drivers working again.... Now I'm not gonna tell you to get the latest drivers since that's standard operating procedure.

[ÜberJumper]

Are you using the Detonators or the drivers for your card? If you're not using the detonators, try installing them, and also try setting all your graphics options back to the defaults. If you have to switch drivers, don't forget to re-install directx.

Also... can an admin move this thread to bug sub please?

[APOLLO(SLS)]

Moved.