RE: Adventures in near(?)-futility -- PCTECH

Dan,
Having had this same circumstance on many occasions, the memory error is
probably the culprit. Neither Win95 nor NT nor 2K nor XP will create this
error when memory is, in fact, bad. Win98, Win98SE and ME seem to be the
only ones to create this error.
I would change out the memory, or if it is multiple sticks and the board
will support it, simply remove 1 or 2 if they are paired.

John Brandt
iStudio400.com


-----Original Message-----
From: Dan Bale [mailto:dbale@xxxxxxxxxxxxx]
Sent: Monday, July 12, 2004 9:17 AM
To: pctech@xxxxxxxxxxxx
Subject: [PCTECH] Adventures in near(?)-futility


So anyway, the drive is partitioned and formatted.  I copy the Win98SE
install CD to a partition I created on the end of the HD, do the setup thing
and let it do its thing.  Everything is going perfectly, but... (ya know, I
usually laugh at people who say "it's perfect except...")

Through the course of installing drivers, I make sure that I reboot as
required.  Even installing some stuff that doesn't request a reboot, I
reboot anyway.  Unfortunately, Windows kept biting me with "Windows registry
is damaged. Windows will restart and try to fix the problem" as soon as the
Windows logo came up on the reboot.  This is a result of SCANREG /AUTORUN
sensing some problem and issuing what I call an "idiot light" type of
message.

(BTW, I also got this on the first go-round with the Win98 install.
Fortunately, I learned to use the Reg Checker in the System Information -
Tools, and backup after I had successfully booted up; this saved me from
having to reinstall drivers and re-change the settings I made.)

Microsoft has several KB articles relating to this topic and one, KB 186909,
talks about defective memory as a potential culprit.  Only problem I have
with this is that I've been using this particular memory, 128MB EDO, for
about ten months now, and had no reported problems using Win95.  Does it
seem odd that Win95 had no problems running with it, and now Win98 is
choking on it?  It appears that M$ built this in by design, as the "status"
on this KB article is "This behavior is by design."

I have a few more tests that M$ suggests to help isolate, but if anyone has
comments or advice, I'm all ears.

db


--
This is the PC Technical Discussion for iSeries Users (PcTech) mailing list
To post a message email: PcTech@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/pctech
or email: PcTech-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/pctech.

---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.714 / Virus Database: 470 - Release Date: 7/2/04
 

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.718 / Virus Database: 474 - Release Date: 7/9/04