Win2K Driving Me Crazy

[rn5a]

Sir, can someone please help me overcome my problem?

Win2K Pro (installed in my machine's C: drive was working fine till
today morning but after taking a break for about 3 hours, when I
restarted my machine in the afternoon, I find Win2K restarting by
itself. I can see the Win2K logo (which also shows the progress of the
OS starting) after which the blue screen appears for a short time. At
this point, Win2K restarts by itself. I neither have installed any
hardware or software lately..

Somebody please help me out with this. It's driving me crazy.

I don't do any mischief with my computer but some problem or the other
goes on creeping up now & then.

 

[rn5a]

Forgot to mention that the file system of C:\ was FAT32 but using the
'convert' command, I successfully changed it to NTFS today. I even
restarted my machine after converting C:\ to NTFS (not once but 3-4
times) & it booted without any problems.

So I don't think that the conversion from FAT32 to NTFS is the culprit.

 

[***** charles]

Sounds like the power supply went bad.

later....

 

[rn5a]

Sounds like the power supply went bad.

No Charles, it didn't. I had conventionally switched off my computer by
clicking the 'Start' button & then clicking 'Shut Down'.

There's one thing which I recollected just now. Usually it hardly takes
any time for my PC to switch off but the last time, it took a bit more
time to switch off.

Can you PLEASE give me a solution? It's an earnest request....PLEASE...

I just can't stay without Win2K Pro.

 

[James]

No Charles, it didn't. I had conventionally switched off my computer by
clicking the 'Start' button & then clicking 'Shut Down'.

There's one thing which I recollected just now. Usually it hardly takes
any time for my PC to switch off but the last time, it took a bit more
time to switch off.

Can you PLEASE give me a solution? It's an earnest request....PLEASE...

I just can't stay without Win2K Pro.

This won't be of much help this time but see my note under FAT32 to NTFS
below regarding imaging before a change. Sorry about this problem but
you may only be able to re-install at this point unless there is another
recovery path one of the guru's may be able to suggest.

James

 

[rn5a]

James, even when I am trying to boot using the Win2K Pro CD-ROM (by
going to BIOS & selecting CD-ROM as the first, second & third booting
device), then Windows doesn't even allow me to boot from the CD so that
I can atleast get a chance to repair Win2K.

Why isn't my machine booting from the CD-ROM? Is there any way by which
I can force Windows to boot using the CD-ROM?

I also have the 4 Win2K boot (floppy) disks & on one occasion, Windows
loaded all the necessary files using the 4 floppies but Win2K still
refuses to start!

I beg you....please give me some solution, James, PLEASE....

 

[Tim Judd]

James, even when I am trying to boot using the Win2K Pro CD-ROM (by
going to BIOS & selecting CD-ROM as the first, second & third booting
device), then Windows doesn't even allow me to boot from the CD so that
I can atleast get a chance to repair Win2K.

Why isn't my machine booting from the CD-ROM? Is there any way by which
I can force Windows to boot using the CD-ROM?

I also have the 4 Win2K boot (floppy) disks & on one occasion, Windows
loaded all the necessary files using the 4 floppies but Win2K still
refuses to start!

I beg you....please give me some solution, James, PLEASE....

Test your computer's RAM.

I assume it's a Win32 OS (No x64 support for Win2000 afaik).

http://www.memtest86.com/

burn it to CD or floppy. test for several hours.

It'll quite show you if you have bad memory. If you have >1 stick of
memory in the system, you will need to find which one is bad (try one
stick at a time), and trash the bad one.

if the PC is still under warranty, send the bad stick to the OEM and
demand replacement.

enjoy

 

[walterius]

It definitely sounds like a hardware problem. I am not certain it is, but I
was a software development engineer for over 20 years, usually working to
integrate 'their' new hardware with my new software, and often developing
computers and their diagnostics. I'm not bragging. I'm just saying the
combined weight of my hardware and software experience suggests hardware.
It's just too screwy for software.