R
Rod Speed
Yes. It is the only OS I have used with DIP.
I restored once before without any problems.
Maybe you booted the copy in between the successful
restore and the one that failed. That can change whats
in the copy when 2K can see both copys at boot time.
Or maybe the restore of the copy doesnt restore everything.
Thats fine when the original isnt corrupted but once it got
corrupted, something that doesnt get restored didnt get fixed.
I just got Everest Home so I will try it out.
I am using the same mouse now and it has
not caused *any* problems whatsoever.
I tried an old mouse that was good and it did
not work when I was having mouse problems.
My son tried my mouse in his machine and it worked fine.
OK, that wasnt clear from your original. Hard to see how a
dust in the power supply could produce that set of symptoms.
And the memory stick list problem too.
I am an old DOS assembly hack from the early days of
computing (like back in the mid 1960s). I did not know what
a mouse was until PARC invented it and Bill Gates stole it.
He didnt steal it, he never claimed he had invented it.
It didnt invent the basic dos command line structures either,
they mostly came from DEC OSs which is hardly surprising
given that he used a PDP10 before he got involved with PCs.
Good to know. I thought I had pushed just
about every possible one to get a right click.
If my speculation about a flaky PS is correct
Unlikely given the mouse detail and the list of memory sticks.
Hard to see how either could be due dust in the power supply.
it is possible that the layoff I made the previous week was
contaminated and when I restored it Win2K got fussy.
Sure.
That was the only thing I did besides running the
a/c that is different - and now the machine runs fine.
Maybe the temp difference is the real effect.
Thats the problem with intermittent faults, they can
be a real bear to pin down whats causing them,
particularly if the fault doesnt show up very often.
I cant see its dirt in the power supply because others in
Houston dont get that problem and I cant see how that
would produce the mouse and memory stick list effects.
I once had an old 286 system that had a flaky
PS. That's what reminded me to clean this one.
I've never had one, likely over a lot more systems than you have used.
I suppose I could try to boot the archive disk to see what
is going on. But until I am convinced the current system
is stable, I do not want to touch that disk because it is
the only "good" archive I have - even if I have to use Win2K
install Upgrade Repair to get it to work after restoring.
Yeah, I wouldnt play around with it until it becomes clearer
that the intermittent fault isnt going to return any time soon.
They hardly ever stay away forever and I would
personally replace the PS because they are so cheap.
I'd replace the ribbon cable to the boot drive too for the same reason.
BTW, as a side question about the Upgrade Repair (aka "In-Place
Upgrade") capability of Win2K Pro Install. Just to make sure I am
communicating this correctly it is referenced in KB article
If I build a completely different machine, can I use Win2K In-Place
Upgrade to make my current disk work on the new machine?
Yes.
From watching the progress screens I got the impression
that Win2K Installation was assessing the hardware and
reinstalling the drivers that were appropriate.
Yes, that is correct.
If so, then it should be able to assess the new
machine and make my current Win2K system work.
Yes.
This is what frustrates me - I do not like smoke and mirrors.
I am an embedded systems developer and I know *everything*
that goes on in any system I design down to the last hiccup.
Trouble is that modern OSs are MUCH
more complex than embedded systems.
Here we are trying to figure out what should be very
simple but thanks to Windows it is being kept from us.
Well, not very well documented, anyway.
Some of that is deliberate, most obviously with NTFS, and some if it aint.
But what is it?
The only real way to prove that is to take a snapshot of the
restored 2K that refuses to boot, repair that using the 2K CD
and then see what that actually changed. Thats not going to be
a trivial exercise tho since 2K changes so much when repairing.
If I didn't value that archive so much - albeit
somewhat broken - I would run CHKDSK on it.
Its unlikely that that would make it bootable.
That was one of the recommendations in the blue screen.
For a different situation, when the drive got corrupted.
I did not boot from it sp I really do not know if
the archive was laid off without any problems.
I do not see how, but I do see that it is possible.
There's a known problem with not all of what is needed to
boot the NT/2K/XP family being restored by stuff like DIP.
Only once before and I had no problems that I can recall.
Maybe you booted the copy, maybe unintentionally.
Thats a known problem with the NT/2K/XP, booting the
copy with both the original and the copy visible to the OS
at boot time on the first boot of the copy. Usually seen
when upgrading the boot drive to a bigger drive.
The trick is to unplug the original drive for the first boot
of the copy and the OS notices that its been moved to
a new drive and fixes the boot detail by itself.
It gets very confused if it can see both the original and the copy.
I will try that. I really do not like DIP - too clunky.
Yeah, and obsolete now that Symantec has bought PowerQuest.
I have never restored an archive more than once, and then
only on two occasions - once in the past and once now.
Yeah, it would be interesting to test carefully.
That's good to know because if true it means my hardware is OK.
No it doesnt, you havent changed any hardware since
the drive got corrupted so that was most likely an
intermittent fault that will almost certainly return.
It could easily be a flakey motherboard. Hard to see
how any PS fault could produce the mouse symptom.
But why would the RAM be reported incorrectly by POST
Has it ever been reported correctly ?
That may just be a wart in the bios.
and why would my mouse act flaky?
Precisely. Thats almost certainly a flakey motherboard.
It was a cheap PS.
I've almost always used cheap PSs. Just recently bought one
a bit up from the cheapest when one of the cheapest cases
happened to have a very quiet PS and I chose to get another
when the test system ended up irritatingly noisey once I moved
to Samsung hard drives which are completely silent, and the
latest intel cpu was so quite that I had to check carefully to see
that the cpu was spinning when I first installed it it was so quiet.
When I finally replaced it with something decent the problem went away.
Sure, PSs certainly can be flakey, just like everything else can be.
Shit happens to the best of us.
It does indeed, in spades with computers.
Yes - and turning on the air conditioner.
I don't either but that's what happened.
I still dont believe that the mouse problem
could be caused by dirt in the PS.
I thought WD had a low-level formatter for their drives.
A few manufacturers do call them that, but they dont actually do
a low level format at all. The drive cant do one with modern drives.
It actually does defect management and they call it a low level
formatter because that has some meaning for some and its too
hard to explain exactly what it does in a simple description of a ute.