There is an other SB Live Control Bar problem
If the bar is up when Homeworld is running. I get a Hw hanup when clicking on the top of the screen.
The problem is solved if i exit the bar before i start Hw.
Asus P2B w/pentium II 266Mhz &4 MB ram
Asus Isdn card
Creative Voodoo 2 w/8MB x2 in sli
Creative DVD 2x w/Mpeg card
ATI all in wonder rage II AGP
13 GB + 3GB harddisks.
Logitech Mouseman w/wheel
Kiss CD burner
RUNDLL32 caused an invalid page fault in
That's a GPF I got when my desktop was in 32-bit mode when I started Homeworld fresh. It cause an assortment of wacky problems if I went in and out of Homeworld with the Alt-Tab key. Try 16-bit mode for your Desktop and see if the problems stop (for any of you who have a lot of GPFs).
*If you have HW set to open gl be sure to leave your desktop at 16bit at startup of the program, most likely rundll32 error is caused when it tried to initialize directx/opengl and change resolution/color depth, best solution is to leave your desktop the resolution you play HW in. Also known problem that HW switches back to software mode if escaped out and temporarily minimized.
Logon Screen Lockup Solution
My machine would lock up after clicking on the internet button. Everything else would run fine and dandy. I found that having an outdated WINSOCK would cause this so I downloaded WINSOCK2 and now it runs flawlessly.
Hope this helps someone!
*it is recommended that you dial up to your isp BEFORE going to multiplayer games in HW because some users have reported that HW seemingly froze at login when in fact if you dont have it set to auto dial it is waiting for you to hit the connect button in windows.
Just thought I'd share this fix for those that have similar video problems.
To wit: HW crashes to desktop at random and reboots the machine when changing video mode or resolution.
Cured this with the switch "/nofastFE" that disables fast front end rendering. Whatever the heck that is....
I was having massive problems switching between video modes (yep even switching from OpenGL to software). Would either crash to the desktop or respond within homeworld with an unable to switch between blah blah error.
Able to change now with running the command line homeworld.exe /disableavi
This has worked for me with all versions of the voodoo video driver.
Interestingly the game falls ass over when in window mode.
I've noticed a couple of other threads indicating that other people are having the same problem I am with HW and a G400, but I cannot find a solution that works ... Grrr
HW crashes to w98 whenever I try to run it in either D3D or OpenGL modes - regardless of resolution or colour depth ... The game seems to last anywhere from 5 secs to about 1-2 min before it crashes.
*Usual caused by out dated drivers etc. Be sure to upgrade to the latest DirectX version and latest drivers.
I experience choppy sound in the movie scenes in btw missions, I now know why.I have a pentium pro, dual I might add box at 200mhz, w/sb pci 64 and Dia.Stealth 3 s540 pci savage 4, just thought it might inform others!
Sound Blaster cards and choppy audio with 3D accelerated games
Creation Date: 29-06-1998
Revision Date: 29-06-1998
The information in this article applies to:
All Creative Audio Cards
PCI 3D Accelerators
When playing a 3D enhanced game, the user may experience choppy audio. The problem gets worse as the graphics detail level, refresh rate and game resolution is increased. The problem does not exist when software rendering mode is enabled or in normal use under Windows
The static or choppy sound being experienced is possibly due to the video card 'hogging the bus'. Some PCI video card manufacturers over utilise the PCI bus to ensure top performance. The card continually writes information to the PCI bus (which is also the master bus) and fills it with information , not allowing other devices to properly transmit or receive data from the CPU. This can actively hinder performance of other devices in the system that rely on the CPU. For more information on this feature, contact the video card vendor - it may be referred to as PCI sharing; automatic bus retries or queue checkin
In order to improve the quality of the audio playback, it is suggested that the user first try various options within the game itself to reduce the amount of data flowing through the PCI bus. Options such as reducing the game resolution, and graphics detail and for 3Dfx Voodoo cards, lowering the refresh rate for the appropriate 3D acclerated resolution may also improve audio quality. Failing this, it is recommeded that the user revert to generic drivers for the graphics chipset in use instead of the optimised driver from the card manufacturer
Internet connection drop outs due to packet resend interval setting error.
TCP/IP fix available at MSN
I went through the threads recently but did not see this one. (Might have missed it
If you get a " Heap file " error , it could be you dont have enough virtual memory , so go into systems and then virtual memory and set it to " Windows automatically blah blah blah.."
I would suggest not to use virtual memory manually unless you have at least 64 ram .
If, like me, you purchased your Voodoo2 from Best Buy, and have long since thrown away the CD that came with it, here's the scoop:
Best Buy, to my knowledge sold mainly Black Magic Voodoo 1000 models (may be wrong, but I'm sure this model was one of the more popular), with 12 megs memory. Well, I got it working *wonderfully* in HW, great frame rates, rich color, wonderful sound...errr...
Anywho, here's what I did:
Downloaded the DX7 reference drivers from www.3dfx.com for the Voodoo2
Got mad cuz the Voodoo2 sucked....
Got madder cuz the Voodoo2 still sucked....
Remembered I still had the original drivers from STB (the wonderful people that manufactured the Voodoo2 Black Magic).
Went to their site http://www.stb.com
Hunted for the drivers...
To find drivers: Click on STB Legacy on the lower right side of the screen.
Click on "Support" in the upper left.
Click on "STB Legacy Product"
Click on "Multimedia Series"
Then dwl the drivers.
Make a folder, extract the files from the driver file.
Go to the control panel-->System.
REMOVE your Voodoo2
Enter logon password...
Rememer to hurt the guy from that made Norton Systemworks.
Windows should say, "OH! Lookie what I found!" and tell you it found your Voodoo2, and it still wants to use the DX7 drivers.
Let it go ahead and use those drivers. Now, go back to Control Panel-->System, click on the Voodoo2 icon-->properties-->Update driver.
Point it to the folder that has the new Voodoo2 drivers...They should be older (duh!).
If you have to restart, restart. Go into HW, and you should notice that Voodoo2 DX7 option is still available. Select that, and viola!
If you look at your drivers under control panel-->system you will notice that windows is still using the DX7 drivers, but the preformance is much much better!
Hope that helps people, and not a random glitch...random glitch...random glitch...
-Nobody N. Particular
Few tips on finding whether problems are being caused by the video or the sound:
1. Be sure you are not running any other application. Terminate all programs through CTRL-ALT-DEL, leaving only Systray and Explorer.
2. Be sure that nothing is set to "always on top", even the taskbar.
3. Try running Homeworld using all the available renderers. If the problem persists even in software rendering mode, chances are, it's not video related. However if in SW the game runs without hitches, it's the video drivers.
4. Disable your sound card through the Windows Device Manager and run the game. If you still get crashes, it's not because of the sound card. If you don't, you probably need to find new sound drivers or lower the number of audio channels in the game.
The above steps are just in order to better isolate the problem.
How to do a clean install of your video card just in case it was futzed up:
If your video card drivers have an uninstall feature:
1. Uninstall it.
2. Install the preferred drivers.
If your video card drivers do not have an uninstall feature:
1. Go into the Windows Device Manager
2. Look for your display adapter settings
3. Change your display adapter to Standard PCI Graphics Adapter (VGA)
*You should boot into Windows at 16 colors*
5. If you know which dll's or files are part of your old video drivers, delete them. Be careful or you might delete a file which is not part of your video drivers. This is often not necessary since the new drivers usually replace all the old driver files. However if they do not replace the old files and by some Windows fluke, they load mismatched versions of the driver files, you have to delete the old files.
6. Install your new drivers, usually by an exe setup that comes with the drivers. If not, extract the driver files into a folder and go into Display Adapter settings again and have windows detect the drivers in the folder. Even if Windows says it has a newer version of the drivers, be sure that you end up with the drivers in the folder since they are the ones you want to install.
For super Socket 7 Motherboards: (K6-2/3 platforms)
Be sure you have the best AGP drivers for your board. If you don't know which is the "best" set, go for the latest set.
Ali chipsets: www.acerlabs.com
VIA chipsets: www.viatech.com
The AGP drivers have to be installed prior to the video drivers in most cases and as I have personally experienced being a previous owner of a ASUS P5A-B.
Install the latest DirectX version (8.1 as of this post) after you've installed your video drivers. It's always best to have the setup exe tucked in a folder somewhere.
While you're at it, you might want to be sure that your DX media drivers are also up to date.
Completely uninstalling Homeworld:
1. Save any files (saved games, recordings, screenshots, etc) by copying them to another folder (ex. C:\Temp)
2. Uninstall Homeworld via the game's uninstall option. Do not use automatic uninstall, use custom uninstall and have the uninstaller remove every trace of Homeworld.
3. Run REGEDIT and check if the following keys are still there:
You might want to delete the keys if you still find them. Be careful about playing with REGEDIT, if you delete something you shouldn't, you might have to reinstall Windows.
4. Delete the entire Homeworld installation target folder.
If anyone is having problems with Homeworld mysteriously quitting right in the middle of a game and throwing you to the desktop, I strongly recommend closing ALL programs except bare essentials. Leave only systray, explorer, and your internet connection if needed. This has fixed my problems.
-->A WAY TO INCREASE HOMEWORLD'S PERFORMANCE ON YOUR COMP, WITHOUT REDUCING GRAPHICAL DETAILS!
Uber Jumper requested that I post this message here, so more people could benefit from it:
The other day I found a way to make Homeworld run faster on my comp. I'm sure many people already know how to do this, but I though maybe there are other newbies just like me who could take advantage of this...
I have a 500 mhz AMD K6-II w/3Dnow! + 128 mb SDRAM + 3DFX Voodoo Banshee.
At first I put all the graphic options of the game on the highest setting possible (with a ressolution of 1024x768), and I didn't get any slow downs. But as I progressed through levels, and the number of units on screen increased, there was so much slow down that it seemed that I was watching a slide show rather than playing a game.
-I could have brought down my resolution and the graphical quality, but the graphix were too good and I didn't want to do that.
So if you are a guy like me, who doesn't want to lose the nice graphics and if you can't stand slow downs, here are some good solutions.
(*note; these solutions are only for those who meet the system recommendations for Homeworld stated by Relic, and still get slow downs - like me
1)--If you have a AMD K6-II or better, you should turn on the 3Dnow! support. Most games automatically detect 3Dnow! if your computer has it, but with Homeworld, you have to turn it on manually.
Creat a shortcut of Homeworld, right click and go to properties. In the target box Add the command:
2)--If you have a Pentium III, add this command instead:
3)--Run the game, and in the menu go to the OPTIONS menu, then click on the VIDEO menu. There is a bar labled "detail treshhold". This bar determines the distance where the game will reduce the units details. For example, when you are zoomed in on a ship, the detail is 100 percent. But if you zoom out, since you can't see the units details from far away anywayz, the game will reduce the units details, to take some load off and increase the game's speed. If you want the best detail, increase the tresh hold detail, ---HOWEVER! do not check the circle labled "full detail". If you check this circle, the game will have 100 percent detail for all units, at any distance, even if you can barely see them. This will reduce the game's performance a LOT! So be usre it is unchecked; it's simply unnecessary to have it on. What's the point of having full detail of a unit, if you can barely see it???
This is very important, and I can gaurantee the game will run a lot faster.
-In addition, try running the game on OpenGL if possible. D3D is famous for being slower than Glide and OpenGL. That's why Quake games have always been on OpenGL
I recommend installing the GLsetup drivers that are included on the Homeworld CD (*note: install at your own risk, but it was fine on my Banshee)
-What is GLsetup? well it's basically the newest compatible drivers for many different cards. The point of including on the CD is that so you won't have to go searching all over the web for the newest compatible drivers for Homeworld. If you already have the newest drivers, then it's ok. But if you are not sure if you do, try GLsetup.
Again, do this at your own risk
Hope this helped all u Homeworld lovers with not so powerful comps. Enjoy!
If you still got questions, e-mail me at email@example.com
When You're Having Graphics Problems
and you're using mods
If you've installed more than one mod (i.e. Kadeshi, Turannic, ST vs. SW, B5) and the graphics are looking wierd, here's what to do:
Go to C:\Sierra\Homeworld\ (or wherever else you installed HW)
Delete all folders like "R1" and "R2"
Reinstall ONE mod.
Also, the /dsound and /dsoundCOOP switches may provide a tiny performance boost as well.