WINDOW'S SETUP UP WOULDN'T SETUP

[richardj]

Window's XP wouldn't install. I worked -like-2 days on it. It would stop at 34 minuets, which indicates a hardware problem. I tried & tried & searched the web & nothing worked.

THEN my CMOS started to fail to recognize my hard drives-I'd turn the PC off, then it would work for awhile & then it went wacky again.

As I was preparing to repair it with a BFH (big F'n hammer) I removed the CMOS battery & unplugged the PC, went & had dinner, reinstalled the battery & turned the PC back on.

It INSTANTLY found the hard drives , booted into setup & reinstalled XP in record time.

Now that takes the cake.

How does the CMOS become corrupted?

ALL so, the reason I reinstalled was that SOMETHING had added a line to my boot.ini file that read---/MAXMEM=500 MB

When I have 1 GB available!

When I removed this line XP started to freeze up.

I don't get that --either.

Archived topic from Iceteks, old topic ID:4173, old post ID:33991

[Red Squirrel]

XP is weird like that. I use win2k.

Archived topic from Iceteks, old topic ID:4173, old post ID:34000

[Pyr-O-Rgasm]

XP is weird like that. I use win2k.

Win2K rocks hard!

But I want Server 2003 x64.....

I want a 64-bit OS..... So baaadwy.

Archived topic from Iceteks, old topic ID:4173, old post ID:34003

[Red Squirrel]

Yeah server 2003 64 must be nice.

Archived topic from Iceteks, old topic ID:4173, old post ID:34007

[richardj]

XP is weird like that.  I use win2k.

BUT---

What could have added that line?

This is the same line you add if you want to set up a ram drive. You limit the system & use the rest for the ram drive, which I didn't do.

AND how does the CMOS beome corrupted?

Archived topic from Iceteks, old topic ID:4173, old post ID:34011