VOGONS


First post, by athlon-power

User metadata
Rank Member
Rank
Member

I am using Windows 98 FE on my Pentium III build, and all was going full steam ahead until I got to the first bootup. After I entered the Win98 key, it crashed to a BSOD. I formatted the HDDs, and tried again, but now I can't even get to the screen to enter the key in the first place. All it does is this:

20190729_182701.jpg
Filename
20190729_182701.jpg
File size
1.18 MiB
Views
1375 views
File license
Fair use/fair dealing exception

I have removed every single card except the video card, which is a known working one. I am installing Windows 98 from the WIN98 directory copied off of the CD and onto my second HDD (Quantum Bigfoot TX). The RAM has been tested and is good.

Current specs are as follows:

Intel Pentium III Katmai @500MHz (SL35E)
128MB PC100 (2x 64MB 100MHz Sticks)
nVidia TNT2 32MB AGP (non-M64)
OS: Quantum Fireball CR 6.4AT
DATA: Quantum Bigfoot TX 4.0AT
iomega ZIP 100 IDE
Samsung SC-148F CD-ROM
Known Good, Tested 170W Dell PSU
1x 12V 80mm DC Case Fan connected to motherboard via 3-pin fan connector
1x 12V 80mm DC Case Fan connected to PSU via 2-pin Molex
1x 12V DC CPU Fan connected to motherboard via 3-pin fan connector (unknown specific size)

Original specs (before I started jerking things out of it) had the addition of these:

Creative Labs Soundblaster Live! 5.1 PCI SB0100 (stand-in for OG SB Live!)
Compaq OEM Texas Instruments PCI 10/100 Ethernet Card (number on main chip is TNETE100APCM)
US Robotics Model 0727 PCI Dial-Up Modem

Why do I mention everything down to the fans here? I am wondering if I am not overloading the PSU. I am using every available molex connection that the poor thing has. I was concerned about the 170W ceiling after realizing I had a Bigfoot, a Fireball, a ZIP drive, a CD-ROM drive, and a 12V fan connected to the PSU, not withstanding the two other fans connected via the motherboard, the CPU itself, and all those expansion cards I had hooked up.

It still, however, BSODs with all of those cards removed. I have PnP disabled in BIOS. That's all I can think of right now.

Where am I?

Reply 1 of 15, by Mister Xiado

User metadata
Rank Member
Rank
Member

I would check the drive for errors, then try installing from a differently-sourced version of Win98. Perhaps from Winworld or something. I've had failing drives throw all sorts of errors due to minor file corruption. If the drive checks out, before reinstalling, perhaps try the old faithful technique of pulling RAM and expansion cards one at a time with each test boot, to determine if any are causing issues no matter how illogical it may seem.

b_ldnt2.gif - Where it's always 1995.
Icons, wallpapers, and typical Oldternet nonsense.

Reply 2 of 15, by athlon-power

User metadata
Rank Member
Rank
Member
Mister Xiado wrote:

I would check the drive for errors, then try installing from a differently-sourced version of Win98. Perhaps from Winworld or something. I've had failing drives throw all sorts of errors due to minor file corruption. If the drive checks out, before reinstalling, perhaps try the old faithful technique of pulling RAM and expansion cards one at a time with each test boot, to determine if any are causing issues no matter how illogical it may seem.

I'm using a clean, original copy of Windows 98 FE from an actual CD. If I can avoid it, I don't use CDs I've burned for that sort of thing anymore. The only other CD I have is for Windows 98 SE, and I'm hoping I don't have to use that, but if I have to, I will. There may be damage that is just enough to stop it from copying, but I doubt it as it copies to my main PC with no problems.

For now, I will run SeaTools for DOS on both the Quantum Bigfoot and Quantum Fireball drives and see if any errors appear.

Where am I?

Reply 3 of 15, by lost77

User metadata
Rank Member
Rank
Member

Just remove everything possible first, then add one item at a time.

You just need graphics card, one ram stick, cpu+fan and hard drive (with installation files from CD). Just use the one hard drive, you can change the default path for windows 98 installation files later.

Most of the times I have had problems installing windows is was a memory problem.

Reply 4 of 15, by athlon-power

User metadata
Rank Member
Rank
Member
lost77 wrote:

Just remove everything possible first, then add one item at a time.

You just need graphics card, one ram stick, cpu+fan and hard drive (with installation files from CD). Just use the one hard drive, you can change the default path for windows 98 installation files later.

Most of the times I have had problems installing windows is was a memory problem.

That's why I ran MemTest on it, and it didn't show any errors. I would be very confused as to how bad RAM could pass a MemTest test, unless there's some extended test that I can run to double-check. I am using a new 64MB PC100 stick that I got recently, but the fact that MemTest said everything was okay makes me think that it's something other than the memory. If the HDDs pass the SeaTools tests, I will then switch out the dual 64MB sticks for a known good single 128MB stick.

[EDIT]

The Quantum Fireball passed both the short test and long test. The Quantum Bigfoot TX passed the short test, but as soon as the long test starts, it fails due to bad sectors. I'm going to attempt to repair the bad sectors using SeaTools, wish me luck.

Now I hopefully know why Windows 98 setup kept crashing- the installation media, aka the Bigfoot, was bad.

Where am I?

Reply 5 of 15, by athlon-power

User metadata
Rank Member
Rank
Member

Removing the Quantum Bigfoot did nothing. Same as goes with switching to the 128MB memory stick. I even unplugged the IDE ZIP drive.

I'm becoming stupidly tired of these builds failing to function for various different reasons. It gets frustrating after working on the same problem for days without an end to the tunnel in sight.

Where am I?

Reply 7 of 15, by athlon-power

User metadata
Rank Member
Rank
Member
RetroLizard wrote:

Have you tried a different cd-rom/dvd-rom drive? It's possible the board might not like it, or that the drive just might be bad.

I was about to say this system used this CD drive before, but this motherboard didn't. The SE440BX-2 used this CD drive fairly effectively. It's known good with the SE440BX-2, and my main computer used it just fine when I had it hooked up with an IDE to USB adapter. If it's the CD drive conflicting with the motherboard, I'll have to use my other CD-ROM (56x, from 2000 as well, but electric yellow, and the case I'm using is barely yellowed at all 🤣). I had a different CD drive that I was using with the system for a little bit, but it died a few minutes after I started using it. I pulled it from the Dell Dimension V333c I have, seeing as it had a DOM of October 1998, which was older than the June 2000 DOM of the drive I was using before.

CD drive I'm currently using is a Samsung SC-148F.

Where am I?

Reply 9 of 15, by athlon-power

User metadata
Rank Member
Rank
Member
RetroLizard wrote:

Well, even if the colors don't match up, nothing wrong with trying a different drive or two to see what works.

The color part was more of a joke than anything else. I'm about to head to bed, so I'll likely test that drive tomorrow. It should work with this motherboard- it comes out of the case this motherboard used for quite a long while. If it's the CD drive, it won't glitch out with this other one. I may just put it back in the case it was in before- the whole thing is yellowed, so it should match just fine.

Where am I?

Reply 13 of 15, by athlon-power

User metadata
Rank Member
Rank
Member
RetroLizard wrote:

Oof. And you're sure the disc(s) are good? No concerning scratches? (or any at all?)

Sorry for the late-ish reply. I usually take a couple of days to stand back from whatever's going on so I can figure things out. The CD is okay. Works fine on other systems, however, while browsing through other forum posts, I happened to come across this:

Dual-boot 98SE/XP, 98/DOS hangs, XP is fine

I specifically found this:

ShovelKnight wrote:

In early 2000s I had a 440BX machine that was hanging every 5-10 minutes in Windows 98 but worked fine in Windows 2000 and XP. I vaguely remember that the problem was related to the AGP GART driver. I'm not sure it would affect pure DOS though.

The damn video card! I was using a different 16MB TNT2 while I used this motherboard prior, rather than the 32MB TNT2 I was using in my SE440BX-2. This is a 440BX system, alright, and I'm wondering if the video card is somehow incompatible with this specific motherboard. I'm going to try using the 16MB card instead of the 32MB and see what happens.

[EDIT]

Nope, not the video card. But it does work now- I removed the 500MHz Pentium III just to be sure, and put in the processor that the system was using prior, a Pentium III Coppermine 600MHz (100fsb). Sure enough, it went into Windows 98 setup just fine. No BSODs, nothing.

So my question is, is my Pentium III 500MHz dead, dying, or screeching in agony? Just to be safe, I will shut the system off, and re-insert the Pentium III 500MHz, and also make sure I use the configuration jumper this time. I may have not done it the first time, resulting in weirdness regarding the motherboard's configuration. Now that I have pin-pointed the problem, I figure that it's worth a shot.

Where am I?

Reply 14 of 15, by Windows9566

User metadata
Rank Member
Rank
Member

my pentium 3 500 had some weird issues too but at least it let me install Windows 98 though, it was just buggy and caused windows to be unstable, when i put my Pentium II 233 in it, those issues went away.

R5 5600X, 32 GB RAM, RTX 3060 TI, Win11
P3 600, 256 MB RAM, nVidia Riva TNT2 M64, SB Vibra 16S, Win98
PMMX 200, 128 MB RAM, S3 Virge DX, Yamaha YMF719, Win95
486DX2 66, 32 MB RAM, Trident TGUI9440, ESS ES688F, DOS

Reply 15 of 15, by RetroLizard

User metadata
Rank Member
Rank
Member
athlon-power wrote:

So my question is, is my Pentium III 500MHz dead, dying, or screeching in agony? Just to be safe, I will shut the system off, and re-insert the Pentium III 500MHz, and also make sure I use the configuration jumper this time. I may have not done it the first time, resulting in weirdness regarding the motherboard's configuration. Now that I have pin-pointed the problem, I figure that it's worth a shot.

Hmm. Have you updated the bios, by any chance?