20 replies
by thechas
The cards should be adaquete for 3D.
I personally think the Savage 4 is a bit slow.
Anyway, make sure that you have the latest AGP mini-port driver installed for the motherboard / chipset.
I would also check the BIOS settings.
Make sure thatAGP 4X mode is enabled.
The Graphics Aperature should be set to at least double the memory on the card, and up to 1/2 of system RAM.
Make sure that the monitor is detected correctly.
Chas
by clark-hans
by smmurphy
by clark-hans
Hi,
I'm just answering for the moment to let you know I have the same problem with my partner's machine. She doesn't play too many games so I haven't really been worried about it.
But for the others who may read this, my setup is different again, A LeadTek GeForce2 MX 100/200 and the problem happens on both WinXP and Win98.
...so dont close this question for the moment, I'll be looking for a solution and will post it back here as a comment when I find it :-)
Cheers,
Tim.
Hi,
Well, I'm glad TheChas is still looking at this one :-)
For Clark's and TheChas' benefit, I thought I might explain my problem a bit more fully...
I first noticed this problem some months ago when Monique's PC with WinXP blue screened with an infinite loop detected on the video driver. After that the MS Plus aquarium screen saver displayed corrupted fish. Much like the broken glass Clark mentioned.
At that time, I located a "fix" for that crash but was unable to find the actual patch for fixing it. Perhaps TheChas remembers my one and only question ever posted on TechRepublic on this? :-)
So it *was* working but then failed.
It came around again when I tried to run Dungeon Siege on the PC for some of Monique's kid cousins. I was in a hurry to get it working for them so I thought I'd put it up on Win98 (The dual boot on her machine)
But that didn't help. Since then Clark has shown it isn't Video card dependent and I've shown it isn't OS dependent. Consequently,I dont think it'll be driver dependent either.
I liked TheChas' thoughts that it may be memory speed dependent cause one 64Mb bank in Mon's machine is a very old one... but it doesn't have troubles with anything else and I'm running her FSB at 100Mhz which *should* be in spec for it...
I guess its possible its not, though, and I'll try removing that card to see if it makes a difference...
To finish up, here are the specs of the machine.
SocketA Athlon 700Mhz (100Mhz x 7)
abit kt7 motherboard.
384Mb memory in 2x64Mb + 1x256Mb
Leadtek GeForce2 MX 100
+ nic, awe64 sound, and the usual HD, floppy, and CD....
WinXP & Win98 Dual boot (both with the same problem)
Norton Antivirus.
I'll post back here after my test removing the memory.... she's using the PC right now for her Uni assignment right now, though...
Hope this helps,
Cheers,
Tim.
Hi Clark,
FYI, Here's what I've tried so far to get my problem fixed. I'm 95% confident we have the same problem by the way - same results in dxdiag, same problem only with 3d games.
I've removed the older 64Mb boards, leaving 256Mb.
I've Upgraded the BIOS
I've Upgraded the drivers for the video card
I've performed an upgrade installation of WindowsXP (Haven't tried re-installing win98 yet, though)
None of this has helped.
Next I'll try putting the video card in another machine andsee if the problem "follows it".
Cheers,
Tim.
by clark-hans
by thechas
I'm looking over the AZ31 Manual right now.
There is an option to set the AGP Aperature under Advanced Chipset Features.
I believe what you were changing was the Driveing control. Leave this on Auto.
Since this is a Socket A motherboard using PC100/133 SDRAM, double check the CPU speed settings.
Per the manual, you need to use a utility that is on the motherboard CD.
The FSB should be set to 100MHZ, the multiplier must be set appropriately for the CPU. (10X for a 1GHz)
Set the memory clock accordingly in BIOS.
Make sure that the FSB jumper on the MB is set to 100MHz.
I have seen numerous "strange" problems with socket "A" motherboards, when the BIOS auto-detected the CPU frequency settings.
I now manually set the clock speeds on every socket A board I setup.
(many clock a 1GHz at 500MHz even though they detect the CPU as a 1GHz)
(I suspect that htis is a problem since PC100/133 SDRAM based MBs do not support the 200MHz FSB)
Chas
by clark-hans
by thechas
Hello again Clark.
I've got all the parts, I will put a system together, and check out what I can for you.
It will take a day or so to check everything out.
In the meantime, you might try the following;
Remove the video card from device manager.
When you reboot, cancel out of finding the driver.
Re-install DirectX 8.1
After the re-boot, then re-install the S3 video driver.
You may need to perform a search and seak for old revision driver files and registry keys to clear up the problem.
What I hope to do from my test build, is prove that the Savage 4 card does perform to specifications.
Then, I should be able to provide a list of driver files and even registry keys to check.
Chas
by thechas
Hi Clark,
Administer a dope slap to me for not thinking of this sooner. I've had to do the following after changing out video and sound cards before;
1. Go to add/remove programs. Remove any program related to a removed video card. Look through the list carefully, some of the program names may not clearly state the card name.
2. Back up your registry. (see the article at www.aumha.org for details)
3. Open regedit, and remove all keys related to the old video cards. This takes abit of detective work, but should clear up the problems.
Start at HKEY_LOCAL_MACHINE\Enum
Expand the branches for display adapters.
Note the key words used for each of the old video cards.
Then delete the keys for the old video cards.
Using the list of keywords, go back to the top of the registry (My Computer).
Use Edit, Search, and enter a keyword.
Search the registry for the keyword.
As you find keys with the word, expand the branches, and determine if you need to add additionalkeywords to your search list.
Examine the key, most of the time, you can safely delete the key with any information for removed hardware and programs.
If in doubt, leave the key in place, or export the key so that you can restore it if needed.
I have had to perform up to 6 searches on various keywords to clear old hardware from the registry.
You need to go back to the top (home) for each new search.
4. Just in case, run the sysedit command.
Look through the 4 system files (remnants ofWindows 3.1) and either delete, or rem out any lines related to removed hardware.
by thechas
5. Then, if you want / need to free up some disk space, start searching for files from the old drivers.
What I do, is find a file or 2 using the mfg abreviation, (such as ati)
Then, search on the file date.
If in doubt, right click on the file,and select properties. Look at the company and product name.
As in the registry, you should be able to safely delete any files left over from old hardware drivers.
If in doubt, create a folder (junk) and move the file there. If you have any problems, you can replace individual files.
Of course, a fresh install of Windows should clear up all of these driver issues too.
Chas
by clark-hans
by thechas
Hi Clark,
I got the system set up to test the 32MB Savage 4 card that I have.
On a fresh install, it works fine.
I installed Windows 98.
Then, the VIA 4 in 1 version 438 (file name 438(2)v(a).exe )
Followed by DirectX 8.1.
And I finished up with the S3 driver version 82033 (file name 395_win9x_me_82033.exe )
The system passed all Direct 3D tests fine.
I used an ABIT K7A motherboard with a 1GHz Duron.
I only had the S3 card and 1 256MB DIMM installed.
My S3 card is BIOS revision 2.1D.32
Interestingly, all of the S3 files have todays date.
Must be how S3 set up the extraction process.
As I wrote earlier, the culprit likely is a leftover file or registry setting from one of the other cards.
Let me know if you need any further assistance or information.
Chas
by clark-hans
by thechas
Hi Clark,
How goes the project?
I plan to get together some registry information links for you to aid in understanding the registry.
I had another thought.
I have 2 different motherboards that no matter what I did, I could not get an S3 Savage 4 chipset video card to work on them.
I finally ended up installing an Nvidia in one, and and ATI in the other. These are both Intel chipset motherboards, and I have never had a problem with the S3 card on a VIA chipset motherboard.
Chas
by clark-hans
by thechas
Hi Clark,
I'm sending the registry information to the e-mail address that is your user name.
If it gets bounced, I'll come back and place it here.
Best Wishes, Chas
by clark-hans
This discussion is closed to new replies.
Trending Hardware posts
Sort by Trending