Home > Diamond Stealth > Diamond Stealth 64 Mb Dram Video Drivers

Diamond Stealth 64 Mb Dram Video Drivers

jmetal88October 20th, 2014, 08:19 AMSo, I managed to fix my broken motherboard. I also noticed some visible corruption over the past couple of times I've booted, in the form of a dot underneath the ASCII character '7'. I guess I'll try it with the maximum programming time the burner will allow, at this point, and if that doesn't work, maybe I should order a new EPROM. The mode was dropped from the INI file so people wouldn't get segmentation faults by selecting it, but never actually removed from the driver or the README describing the driver (and his comment is here

Funny thing is I could've sworn back when I was trying it that my homemade EPROM eraser had absolutely failed to do anything to this chip, but now I'm thinking it All rights reserved. What caught my eye was that I have just bought a pile of mid 90s PCs, and now have at least two S3 Diamond Stealth 64 video boards, these are PCI It might be worth dumping one of the chips to compare if they have the same chipset (but it has to be a Vision864).

Looks like it just failed to copy any of the 'iffy' data, which is why it matched twice. So I guess now I'll either wait until I can get another dump to compare it with or until I can test it with a known working motherboard and CPU. This thing is really old. Thanks!

I might have just found the chip. Our expert industry analysis and practical solutions help you make better buying decisions and get more from technology.... Magمكتبتيمساعدةبحث متقدم في الكتبالاشتراكتسوق لشراء الكتب على Google Playيمكنك تصفح أكبر متجر للكتب Stealth 3D 2000 Series driver3dnt42031.exe [more] Windows NT viper v550 drivermain550255-9X.exe [more] Windows 95 & 98 WeitekPower P9100 PCI drivervpr95224.exe [more] Windows 95 I've got a blank EPROM of the proper type I can burn the result to in order to test when I'm done.

I don't want to say the burner is bad when I only have one EPROM I can test writing to, anyway. Viper V330 Series drivervprnt223.exe [more] [more] Windows ME Monster Fusion AGP/PCI driverw9xmfu_2.exe [more] Windows ME Viper V330 driverglv33128.exe [more] Next up I need to reattach the PS/2 keyboard connector and replace the DS12887 so I can get into the BIOS and configure things properly. jmetal88October 21st, 2014, 03:39 PMOkay, I think I got the 'real' BIOS dumped, finally.

Search ... smeezekittyOctober 26th, 2014, 02:47 PMIts not that surprising you couldn't run 24 bit color with only 1 MB VRAM. jmetal88October 22nd, 2014, 08:45 AMI hate that I'm just replying to myself here, but I figure even if nobody's interested in what I'm doing now, someone may be in the future. After disabling shadow RAM, I finally got the computer to dump identical files from the VGA BIOS memory locations on two separate cold boots.

jmetal88October 18th, 2014, 07:38 PMOkay, it's the right chip. EDIT: Removed the attachment. Looks like I took the sticker off to see what the part number was, so I'll have to read it back in to see if it's the right one. I just figured out why Diamond removed the 16M color mode from the INI file.

Our expert industry analysis and practical solutions help you make better buying decisions and get more from technology.... Magمكتبتيمساعدةبحث متقدم في الكتبالاشتراكتسوق لشراء الكتب على Google Playيمكنك تصفح أكبر متجر للكتب this content Turns out it just had two chips in the wrong sockets. I just did a visual inspection of the file and it's actually missing a large section. I might be able to fix the files myself.

I can't actually just plug in the card to test it out right now 'cause I don't have a working motherboard I can use it with. But I'll make a couple more dumps of the chip and see which way the bits read back more often, I guess. Forgot your password? weblink I always run my vintage systems that support high color at all at 16 BPP.

I remember setting the EPROM aside somewhere at the time, removing the socket, and then setting the board aside in case I ever wanted to put it back together. Unsubscribe About Us Overview Contact Us Take our Site Survey Testimonials Copyright © 1996 - DriverGuide is an iCentric Corporation Company. But at this point I'm willing to look at a dump of ANY revision of the BIOS if anyone has it to send to me.

Looks like there are only three or four bits reading inconsistently, though.

I'm not sure why I never questioned there there were two chips plugged into sockets that were too long for them before, but after putting them back in their proper sockets jmetal88October 19th, 2014, 07:48 AMI found a generic BIOS here, although it's for a PCI card and not a VLB card: It's not exactly the same, but it did allow I've verified all the settings against what's in the datasheet, except for the 'programming time', which, for whatever reason, isn't specified in the datasheet. Less vram usage = higher resolution and 24 bit color just doesn't gain much on an old system.

Stealth 3D 2000 Series drivervxnt4203.exe [more] Diamond Multimedia Systems, Inc. I did order a couple of the proper DRAM upgrade chips to use with this card off eBay a day or two ago, so hopefully when they come in I won't A dump from a known good chip would probably still help out. check over here For some reason I thought it was at my parents' place, with the board, but instead it was in a box of components I had here at my apartment.