Today I spent my time looking at these beauties 😀
Soon will put it to the test...

I dont have a PS/2 port 🙁

My mouse is serial. I have tried it in 2 machines and same behaviour (with the drivers you posted thankyou)

It could be the IC chip that controls it or the switch is bad.

While Rio de Janeiro is under quarantine thanks to COVID-19, I had my last day of home office on friday and now I am starting a three week vacation... at home. My boss didn't want to postpone my vacations so I could have a nice trip to Spain rescheduled for when the world comes back from the virus spread... I'm pissed... Time to look elsewhere for a new job with a better boss.

Meanwhile, I fired up my Windows 2000 VM and played some matches with Fifa 99. =)

I tried out the new DOS version of HWINFO on my 386 and 486 towers, as well as trying to get the 386 to boot off its hard disk. For some reason despite having the right drive parameters and the hard drive being recognized by HWINFO (it's a Seagate ST3144A, 131MB IDE drive) I would get a "HDD Controller Failure" after putting the parameters in and a DOS 6.22 boot disk couldn't find the hard drive.

Does your 386 retain the settings after saving them in the BIOS? If not, change the clock battery with an external.

EvieSigma wrote on 2020-03-22, 01:45:

I tried out the new DOS version of HWINFO on my 386 and 486 towers, as well as trying to get the 386 to boot off its hard disk. For some reason despite having the right drive parameters and the hard drive being recognized by HWINFO (it's a Seagate ST3144A, 131MB IDE drive) I would get a "HDD Controller Failure" after putting the parameters in and a DOS 6.22 boot disk couldn't find the hard drive.

Some drives (like your Seagate) have native and translated C-H-S. Your tried: 1001-15-17 ?

Horun wrote on 2020-03-22, 01:57:

EvieSigma wrote on 2020-03-22, 01:45:

I tried out the new DOS version of HWINFO on my 386 and 486 towers, as well as trying to get the 386 to boot off its hard disk. For some reason despite having the right drive parameters and the hard drive being recognized by HWINFO (it's a Seagate ST3144A, 131MB IDE drive) I would get a "HDD Controller Failure" after putting the parameters in and a DOS 6.22 boot disk couldn't find the hard drive.

Some drives (like your Seagate) have native and translated C-H-S. Your tried: 1001-15-17 ?

1001 cylinders, 15 heads, 17 sectors? That's what I put in, going off this website here.

https://www.computerhope.com/hdseagat.htm

Yeah it matches the docu by seagate: ftp://ftp.seagate.com/techsuppt/at/st3144a.txt
Does your BIOS also have Precomp and Landing Zone in the HD setting ? Some HDD just do not work well with certain older BIOS. I have a board that a 200Mb works, a 540Mb works but a 320Mb does not like that board....edit: meant 320Mb

Horun wrote on 2020-03-22, 02:07:

Yeah it matches the docu by seagate: ftp://ftp.seagate.com/techsuppt/at/st3144a.txt
Does your BIOS also have Precomp and Landing Zone in the HD setting ? Some HDD just do not work well with certain older BIOS. I have a board that a 200Mb works, a 540Mb works but a 320Mb does not like that board....edit: meant 320Mb

Yeah, it does. I put in 0 for both because that link I have doesn't give a value for those.

This is the hard drive the computer came with so I presume it worked in the past.

Does the BIOS save the settings? Also, check the jumpers on the hard drive and make sure it's not set to AT mode and make sure it's set to single drive (master) mode.

bjwil1991 wrote on 2020-03-22, 02:26:

Does the BIOS save the settings? Also, check the jumpers on the hard drive and make sure it's not set to AT mode and make sure it's set to single drive (master) mode.

HWINFO reports the drive as being in IDE mode but doesn't mention whether it's set as master. I'll have to check that the old fashioned way.

Playing with a Vtech Laser XT/3. The machine came with 640k+512k expanded, a VTCL VGA card and standard VTCL I/O card with 720k 3.5" and 360K 5.25" drives. Plus a DataCannon SCSI adapter (way better than the crappy original RLL card imho) but the Seagate 80Mb SCSI was dead. Installed a 200MB WD SCSI and works well so far. Still need to fix the PSU but am thinking of just swapping in a newer AT PSU board since the paddle switch is a true switch and not some odd lever action thing. Some pics..

A pic of the front and PSU

Ran a patch to Space Quest 1 and 2 for the blond hair on Roger Wilko using my Core2Duo laptop, Raspberry Pi 3B (DHCP server), and a network switch. I then shared the Games directory and the floppy A drive so that I can copy the files in the SQ1 and SQ2 patch directories to the SQ1 and SQ2 directories in the Games folder, installed Visual C++ Redistribution 2010 both x86 and x64 so that the one program could run. It was quick and painless and it looks pretty cool.

Reddit: https://www.reddit.com/r/Sierra/comments/fmfc … _i_and_ii_mods/

I recently bought this Voodoo 3 PCI as part of a scrap lot...was actually the reason to buy. I was rather disappointed as I saw that the card was in a disastrous condition. Difficult to see on the photos, but it was totally bend and did not even fit in the PCI-slot anymore. 2 Caps missing but this is a minor problem.
I bent it straight again and gave it a try. Totally surprised that the cards powers up and works in text mode without problems. In graphics mode there are some minor display errors most likely caused by bad RAM. Maybe it will be fixed after addiding the missing caps.

Predator99 wrote on 2020-03-22, 08:49:

2 Caps missing but this is a minor problem.
I bent it straight again and gave it a try. Totally surprised that the cards powers up and works in text mode without problems. In graphics mode there are some minor display errors most likely caused by bad RAM. Maybe it will be fixed after addiding the missing caps.

I can spot 4:
C10
C49
C140
C129

You are right...C129...didnt see that.
Thanks!

Maybe the reason for the RAM-problem.
Anybody know the value..?

For C10 I dont think its required. If you take a look on other cards its not popoulated there too.

Predator99 wrote on 2020-03-22, 09:30:

You are right...C129...didnt see that. Thanks! […]
Show full quote

You are right...C129...didnt see that.
Thanks!

Maybe the reason for the RAM-problem.
Anybody know the value..?

For C10 I dont think its required. If you take a look on other cards its not popoulated there too.

C129 also not required, see here:
http://www.vgamuseum.info/index.php/cpu/item/ … x-voodoo-3-2000

Predator99 wrote on 2020-03-22, 09:30:

You are right...C129...didnt see that. Thanks! […]
Show full quote

You are right...C129...didnt see that.
Thanks!

Maybe the reason for the RAM-problem.
Anybody know the value..?

For C10 I dont think its required. If you take a look on other cards its not popoulated there too.

On my V3 3500 all the caps of that size are 10uf 16v. But I think, for testing purposes, as long as something is there it should be fine. If the screen corruption persists, check the legs of the ram chips for bad joints, especially since the card is bent.