Windows Forum

Ask something
Discussion Locked

Win98 registry and other problems.

0 helpful
7 replies

by reverendzero 2 views

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I apologize in advance because this will be a lengthy question. This has been driving me insane.

Hardware:
Soyo 71WM/L v1.0 with 466mhz Celeron
64MB Generic PC100
4GB Seagate from old IBM PC330 master on IDE1
44x CD-ROM master on IDE2
Linksys LNE100TX NIC
Integrated Audio
Audio, COM 1/2, LPT1, USB are disabled.
DMA is enabled on all drives.

Win98 4.10.2222 from OEM disk.

I can install the OS okay, but it gives me a number of errors, especially whenever I try to install ANYTHING. It always says that the ".EXE is corrupted, try another file." Problem is, it happens on ALL EXEs, even ones I've tested on my other computers. I get illegal operations whenever I try to run Windows Update, install Directx 7.0a and 8, the Soyo VGA drivers even though it let's me install everything else the motherboard needs. The CONFIG.SYS file is also incomplete; I have to repair it myself.

Thoe most worrisome error I get is the registry being corrupted! The rare ocassion when I DO install a program, it fails when I try to run it and gives me a "corrupt registry" problem. It backs it up, and all my work has disappeared off the face of Windows. I can't fix anything because Windows keeps restoring itself to its original setup, which has an inherent problem! I've tried two different 98 disks, one 95 disk, and even NT server. ALL fail. NT Server won't even load; it fails on install. I've even tried to different CD drives.

I think it's a hardware problem, but I don't know where to start. You think it's a HDD problem? This is the same HDD that wouldn't load the OS on the old IBM PC; that's why I bought the SOYO and Celeron. But whenever I put it on a computer at work, it loaded NT Server fine. I could even update it and install software. What is it!?

I hope you can help. I don't mind buying more parts, but I'd like to buy the right one.

Thank you,
Zero

7 replies

by dudad

Did you try scanreg /fix? If so, and no better, it could be the motherboard taking a dump on you. (no pun intended)

Also, was this a clean install? I mean fdisk, format, partition, etc.?

by reverendzero

I did try the scanreg /fix. Nothin' doing. I didn't mention everything I did since I tried a lot of things. All logged, of course.

This was a clean install. About 8 times. I'm afraid I'm frying the HDD.

Why do you think it's the mobo?

(BTW, I hate to reject the answer. Is there any way to comment without accepting?

by skutts

I think your right by saying it sounds like a hardware problem, and the fact that it is the same hard drive puts suspicion on this. Have you tried disabling the 32 bit protected mode? (under troubleshooting in system properties|performance|file system) or turning off the DMA support? (system properties|device manager|hard drive|properties|settings)

hope u find a solution

Rog

by reverendzero

Hmmm. I could disable 32-bit mode tonight if I can't get it licked at work today. Could you clarify what that would do? If you don't have the time, I can look it up...

I've tried it with DMA on/off on both drives, CD/on but HDD/off, and vice versa. Problem still persists.

I'm inclined to think it's a hardware problem too, but the HDD works fine in other systems. I think the problem here is that I'm an impatient boob.

Thanks for the tip, though. I wish there was a "will test" choice rather than outright accepting and rejecting answers.

by simon beck

I suspect either HDD or RAM.

To check this beg, borrow, ste...borrow another known working hard drive, gather the latest drivers for all hardware involed and perform a clean install.

If everything goes OK, install an App that you couldn't install before and run it, if this is OK prob solved HDD.

If it install's but will not run boot to safe mode and try to run it again, if it fails here its RAM.

If the clean install fails with known working HDD its RAM again.

Good luck,

SB

by reverendzero

Right on the mark, Simon. I suspected the memory before, but I put it to the side and forgot about it when I decided to troubleshoot the OS. Maybe I should've taken the few minutes and replace the memory FIRST before beating my head in for two days.

Oh well, hindsight is 20/20. Thanks for the tip; I probably would've gone on and on with the OS.

This discussion is closed to new replies.