re: Registry Problems? uhh... yeah... right...
Monday, October 15, 2007 at 9:35 pm
Windows 98 Annoyances Discussion Forum
Posted by Joe Hepperle
(73 messages posted)
Concerning Utopia838's three posts at:
http://www.annoyances.org/exec/forum/win98/1192178189
http://www.annoyances.org/exec/forum/win98/1192178426
http://www.annoyances.org/exec/forum/win98/1192365414
With all respect to James and Keith who attempted to help this "Utopia 838", I don't
believe these are real problems experienced by a real user. I think this post (and
two others) is/are fake. The problems listed in his three posts, and "utopia's" supposed
action don't mesh with what we might expect.
At the time I am posting my message here, this "Utopia" has posted three messages
(this second one here was posted only four minutes after his first one).
In all three he describes scenarios that to me are highly improbable -- even for
a computer on the fritz.
As an example, in his first post he claims an error message keeps popping up and
he can't close it and keep it closed -- it just pops up again, and again, and again
!!
Mysteriously (or by design?), Utopia can't seem to bother telling us what the error
SAID -- even though he's seen it just as many times as he's tried to "close" it
(bunches of times according to him) And if his post is true, the "error message"
is still there! Unable to be closed, and blocking access to his Start Menu. How did
he ever get around that up-popping error message to get on the net, surf to this
site, AND post his message here? Remember, it won't even let him access his Start
Menu.
Uhhh... yeah... right...
Since all three of his posts were submitted in the middle of the night, I highly
doubt that he was over at a friend's house, using a friend's computer to post. I
do realize that it IS possible though. But given the problems he has with Facts in
all three posts, taken together as a whole, my gut tells me he's mad at somebody
and decided to submit these nonsensical "problems" just to watch us squirm and wiggle
trying to answer them.
His next message, here, is posted only four minutes AFTER the first one and describes
a completely different "problem". This other problem, problem #2, he claims is that
when booting a black screen appears and says that his registry is missing.
Well.... hmmmm....
Folks with experience know that if your registry is missing, you don't get a black
screen telling you that. And the message you DO get does NOT mention the 'Registry'.
If your registry is missing, the Windows Registry Checker (a DOS based portion
of Win98) pops up a BLUE screen (not black). On that blue screen is superimposed
a smaller GREY window which says, "Windows found an error in your system files and
was unable to fix the problem..."
But the 'Registry' is NOT mentioned Ever. And of course, if your computer has been
making the secret registry backups (which it does unless you deliberately configure
it Not to) it will automatically replace the 'missing' registry with the last known-good
copy and still pop up that BLUE screen with a smaller grey window superimposed. But
this time the words in the grey window will say, "Windows has found an error in your
system files and restored a recent backup." Again, no mention of the "Registry" whatsoever.
His third message has an equally improbable story to go with it. He claims in his
third post that when he starts to boot the computer, "...it says CMOS error, failure
to load it...". And Joe said that's the biggest crock of sh shellac
I've read in a long time. There is a wording problem here that points this out as
a fake posting. The word is CMOS. Your computer will never say "CMOS error". If his
computer actually had the problem he is trying to fake here, it would have said,
"BIOS error...". The electronics experts and the old timers know what I'm talking
about. I could write a whole chapter here, about CMOS and BIOS but I won't. For those
who are interested, here is a very short version of the explanation why his claim
is fake.
1st -- CMOS (pronounced See-Moss) is an acronym which stands for Complementary Metal
Oxide Semiconductor, which is a type of Integrated Circuit ("chip", "IC chip", "Computer
Chip"). In our casual conversation and casual writing, some folks may colloquially
say or write "CMOS" when they actually are referring to BIOS. Or even more specific
"CMOS" is short for "CMOS Memory" which is the Space on the (CMOS) chip where the
BIOS program is stored. The whole point of all this is that people may incorrectly
refer to the BIOS as "CMOS" but the computer does not. The computer may or may not
load the BIOS but it would never give a message that the "CMOS" didn't load. "CMOS"
is a type of Integrated Circuit Chip and as such it has no ability to load or not
load -- all it can do is stay soldered on the Motherboard where it was installed.
CMOS Memory is a Space on a CMOS chip and so it has no ability to load or not load.
BIOS is a program stored in the CMOS Memory. BIOS is the only thing that can load
or not load.
2nd -- If a computer has Bios loading errors, it does not continue to load windows.
Instead, it halts right there at the POST screen (we haven't even started loading
DOS yet, let alone Windows) and usually says PRESS F1 to enter Setup or PRESS F2
to continue. The machine will just sit there then -- a long ways still from even
STARTING to load DOS or Windows. And it will just sit there, and sit there, and sit
there, and sit there... until you consciously and deliberately press either F1 or
F2. Our faker though would have us believe that Windows went ahead and loaded up
and then gave him another error message about Active Desktop having to be turned
off.
Uhhh... yeah... right...
There is no answer to any of his three posts because he does not describe real events.
Joe Hepperle
- Written in response to:
- Registry Problems (utopia838: Friday, October 12, 2007 at 1:40 am)
There are presently no replies to this message.
|
|
