G
Guest
Guest
Archived from groups: microsoft.public.win2000.file_system,microsoft.public.win2000.registry (More info?)
Hi folks.
i've got one here that is confusing the hell out of me. The machine is a
standard box with an AMD Athlon 1800 in the middle. The rest is mainstream
hardware, nothing unusual in it. It's running W2K professional.
Now, this is an intermittent fault but incredibly annoying. You power the
machine on and it goes through POST and starts booting 2K as normal. Then...
BLUE SCREEN... the registry is corrupt or not writeable or just plain gone!
This has happened twice since installing 2K a week ago. Repair with an
emergency disk sorta works but not completely. After repair, if you try to
create a dial-up connection, when you go to give the connection a name, e.g.
"Xtra", you get a message that the name must contain a non-blank and mustn't
start with a period. Dunno about you but "Xtra" is within those rules.
Anyone seen this behaviour before and found a cure for it? I'm tearing my
hair out here!
Thanks folks!
Simon.
Hi folks.
i've got one here that is confusing the hell out of me. The machine is a
standard box with an AMD Athlon 1800 in the middle. The rest is mainstream
hardware, nothing unusual in it. It's running W2K professional.
Now, this is an intermittent fault but incredibly annoying. You power the
machine on and it goes through POST and starts booting 2K as normal. Then...
BLUE SCREEN... the registry is corrupt or not writeable or just plain gone!
This has happened twice since installing 2K a week ago. Repair with an
emergency disk sorta works but not completely. After repair, if you try to
create a dial-up connection, when you go to give the connection a name, e.g.
"Xtra", you get a message that the name must contain a non-blank and mustn't
start with a period. Dunno about you but "Xtra" is within those rules.
Anyone seen this behaviour before and found a cure for it? I'm tearing my
hair out here!
Thanks folks!
Simon.