Registry errors with fresh install...

[Timbob505]

Hey guys, I'm trying to repair our Associate Pastor's computer, but it is not playing along! First, here are the system specs that I am sure of:
Win98 se
Novell Netware 4.1
Cel 400A
Intel 440bx AGP
Intel 740 AGP graphics card
256MB PC100
6GB HD

When I first looked at it, the computer would not boot to a usable state. There were various registry and startup errors that would flash, Novell would crash and the system wouldn't do anything. I tried to re-install Windows, but it took way too long - time remaining was around 92 minutes - longer than it takes on a 300Mhz system with 32MB of ram! I quit the installation and decided to format. I saved what files I could and then did a good ole' fdisk and format, then I proceeded to install win98se again. This time, the install went fine with no problems. I got the network card installed and I got the drivers for the video working and after a reboot, I installed the Netware Client. The first install came up with errors, so I was forced to re-install. Everything worked - once. Now, everytime I reboot, I get this error

Quote:

Windows encountered an error accessing the system registry.

Windows will now restart and repair the registry for you.

It resets and then says the same thing...everytime. I restarted in dos mode and ran scanreg /fix and it said that the registry was repaired and to restart the computer. I did that and again I got the same above error message. Any ideas? Could it be bad memory or a bad Hard drive? Unfortunately, I don't have an extra HD to test it with. I am going to try one more format and re-install before I suggest the church invest in another HD. Any help is greatly appreciated!

Timbob

[DaveLewis]

Have you considered exorcism?

I'm not a Netware expert but you might want to try to backtrack and get some of the history of the machine. Did it work okay on the network and then "all of a sudden" blow up? I've worked on a few church systems and while I have the highest respect for men and women of the cloth, I also find that their computers are usually the most messed up systems imaginable.

I'd verify that the system is totally functional before I installed Netware. Start it up and let it run as a stand alone for a day or two to satisfy yourself that the system is okay. If you've got a copy of Norton Utilities it would be a good time to do some diagnostics. That way you know that you've got a good Windows install and good drivers, etc.

Then if the Netware messes the system up again you can nail your problem down. Given that the system runs okay off the network you have to suspect the Netware. What are you installing Netware from? I've seen a couple of cases where the distribution CD's that are still sitting next to the computer are five or six generations out of date and you really should be on the net looking for and installing the latest and greatest drivers.

If that doesn't work I'd throw a couple of extra bucks in the collection plate and spring for a new hard drive. I personally don't think that's your problem but 6 gig doesn't hold a lot of sermons anyway.

Good luck

Dave

[Richard Cranium]

I suggest doing the FDISK thingy then FORMAT C: to start from scratch.

HD's that are past the MTBF or close sometimes do very odd things.

I have a dozen or more here that some will almooooost work, then let you down after lengthy efforts.

Staples.com has some deals using a coupon from www.jumpondeals.com on Quantum HD's , stay away from Maxtor if possible.

DrVette

[MaxVal]

Try swapping out the memory with known good stuff.
Windows checks the registry after it's loaded into memory at every boot. If there are memory errors, it sees them as registry errors and tries to repair them.
Memory issues may well be the root problem.
MAX

[iosubsys]

I agree with maxval, try changing the memory. I've also seen problems like that when a HD is full or failing.

[Timbob505]

Thanks everyone! I'll try to swap out some memory today and post back later. Hopefully it is memory....its a lot cheaper than a new HD! Have a great day everyone.

Timbob

[Timbob505]

Thanks everyone for your ideas. It turns out that some of the memory was bad. It had 2 64MB sticks and 1 128MB stick in it and I've got it up and running with just 64MB. I'll mix and match to see which other stick was causing problems and throw the other one out. I hope everyone has a great day!

Timbob

[Michael Chiew]

Timbob505

Chances are I'm repeating here what you fellas already know. But bear with me, let me have my say. So lend me thy ears. I come not to bury Tombob505's computer but to resusitate it, if I can.

I guess you all know that there are 2 versions of Scanreg - Scanreg.exe and Scanregw.exe. The former is a real-mode item, the latter being protected-mode, a Windows 32-bit item. What's the big deal, you might say. Only this.

Scanreg.exe does not detect registry damage in memory contrary to popular belief. Scanreg /Fix isn't the perfect fix for registry problems. It does have its drawbacks. When you activate the command, Scanreg assesses the structure of the Registry. If it is sound, Scanreg returns the "fix" message. Scanreg /Fix does allow you to choose from a list of the latest 5 backups of the Registry, from which you select to restore a working copy. When this fails, you have to do the other thing, RUN Scanregw.exe (Windows 32-bit protected-mode item).

When backing up a known good copy fails from Scanreg.exe fails, you've got to contend yourself with possible defective memory. For example, a defective memory chip can damage the registry in memory. Scanregw.exe scans the Registry in memory for damage (Scanreg.exe doesn't do that). When Scanregw.exe finds a damaged Registry in memory, it marks the Registry as damaged and Scanreg.exe is activated the next time your computer starts, hence the message WINDOWS WILL NOW RESTART AND REPAIR THE REGISTRY FOR YOU. Scanreg.exe, however, may not detect any damage if the defective memory is not used in real-mode, i.e., within the 1MB memory line. Windows will start as usual but your Registry problem ain't fixed. Do I make sense so far.

The Registry is kept in C:\Windows above the 1MB memory line. It's logical to assume that Scanreg.exe will never be able to detect defective memory because the Registry resides above the 1MB memory line (in protected-mode territory). So what's the solution. How do you establish the presence of defective memory.

Two ways to determine whether defective memory chips are the troublemakers. The first is very simple. Change ram.

The second is where the excitement begins, where Windows comes into its own and becomes your big brother for a day ... or two, perhaps. You limit the range of memory Windows uses. In other words, you confine Windows to working within a certain memory range to isolate the defective memory chip, if it exists at all (really just part of the troubleshooting process). Here's how you do it -

Start Windows in SAFE MODE.

Click START|PROGRAMS|ACCESSORIES|SYSTEM TOOLS and select
SYSTEM INFORMATION.

In the TOOLS menu, click SYSTEM CONFIGURATION UTILITY. Click GENERAL tab, click ADVANCED button. In the ADVANCED TROUBLESETTING SETTINGS box, check the LIMIT MEMORY TO <N> MB box. Set the value to 32MB. Click OK, click OK and restart your computer.

If the Registry problem disappears, you know you're dealing with defective ram.

There are no failures in the world; there are only those who didn't know they could succeed!

Michael Chiew

[Richard Cranium]

Good info Michael, I've copied it.

Thanks
Doc

Excellent, Michael, as always. Your posts are extremely informative and insightful. Keep up.