Discussion Locked

Windows 98 - Registry Problems

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

Have a new ASUS P3V133 system board that sends Windows 98 SE into a "Registry Problem encounted during startup" infinite loop. Installing W98 SE onto a virgin disk - partition (FAT 32) and format it. Have done it on 3 separate disks - no matter. Have changed video cards, ram, etc - no matter. Have installed the VIA 4 In 1 software that came with the ASUS board and the more recent version from the net - no matter. Trying to work with ASUS Tech Support but I am afraid W98 will no longer be supported by the time WE resolve this problem. Has anyone else out there encountered this problem. By the way, the CD is good. Have installed it on many test platforms to verify such. Maybe it trash can time. Thanks in advance.

Gordon Haas
Network Consultant

5 replies

by woodboss

I have Run into the same thing on an A-Bit Board. It will give you this Registry error or will not install. It was not Win98SE! It was the way I was setting up the CPU Chip. Match you bust speed with your Memory Chip Speed. P3V133 uses the Ulta Fast133Mhz Memory Bus so if you are using PIII Chip and set the chip to run at 133Mhz and you are using a MEM Chip that work at 66Mhz. You will get this problem. If you are using a Celeron Chip they will run at 66Mhz or 100Mhz. Make sure it matches withyour MEM. Change out your Memory or Power down the CPU Chip.

Good Luck
Woodboss

by gordonhaas

Purchased new 128 MB PC133 ram - no difference. If this is the problem then it implies that the new ASUS board is inoperative - GEE imagine that!!

by akdude

Try changing the memory SIMMS. The registry is loaded into RAM when Win9X starts. Bad memory can cause this problem.

by gordonhaas

Purchased new 128 MB PC133 ram - no difference. Perhaps the new ASUS board is inoperative.

by fleas

Here are some suggestions:
1) check you memory timing settings in the BIOS. Verify that all BIOS settings are correct.
2) Check your MB jumper settings, verify that they are all correct.
The most likely cause is bad or overclocked memory. try using a known good memory chip, Fdisk, Format, re-install with known good memory, and it should work.

This discussion is closed to new replies.