Problem during installation... Weird one.

M

Mathieu Paquette

Hi,

This post is lenghty but I've included as much details as possible; please
tell me if you need any other details.

I just bought a new system for my mom. It's a P4SP-MX board, with everything
onboard (she's gonna browse the net and do people's taxes on it, so she
doesn't need much more...)

The machine has a CDBurner-DVD reader combo drive, and that's pretty much
it. For the rest, it's quite standard; no PCI-added cards, nothing. It runs
a Celeron processor with 256megs of RAM.

Well, here's the problem I have. I tried with two different copies of Win2k
(one that I burned with a streamlined SP4 built-in and another original
legit 120-day trial I got at a training that has no SP built-in), and both
sort of "crash" at the same place; at the first part of the graphical part
of the install, when it says "Windows is now detecting devices such as your
keyboard and mouse, you screen might flicker, yada yada yada". What happens
is that the bar goes through halfway, then stop moving. The computer is
still responding (ie. the mouse still moves, the keyboard's light go on and
off when I press cap lock, etc), but nothing more happens. I left the
computer in that state overnight, to no avail.

I've tried different things; I underclocked the CPU, I put PNP OS = Yes
instead of NO in the BIOS, changed keyboard, unplugged the mouse, nothing
works.

Only thing I haven't done is to install the latest BIOS, because I didn't
have a floppy drive anywhere else in the house beside that machine and I had
to get to bed (it was late and I was working this morning) so I didn't want
to unplug the floppy, put it in another machine, etc... But now I'm at work
I'll write a floppy with the latest BIOS, maybe that'll help, but I'm a bit
skeptic.

So, anyone got any idea as to what could solve this issue ?

Oh, last but not least, when I got the system there was a WinXP preinstalled
on the computer (OEM pre-installation, you know where you have to enter the
comp's name and stuff then it boots into Windows); I completed that part,
thinking I might get away with installing Windows on the machine. It worked
perfectly; I proceeded to boot in Windows, uninstalled a few of the crap
that came preinstalled, rebooted, worked, rebooted again, then Windows asked
to be registered; since I did not have a valid key for XP (I own 2k but not
XP, I don't really like XP much, I think 2k does what I need with less
system resources), I popped my 2k CD in and proceeded to install it, and
that's when it crashed. Yes I deleted all partitions, recreated a 20 gig
partition on the 40 gig drive, formatted it ntfs, etc....

I've installed Win2k countless times in my life, but that's the first time
something like this happens to me.

Any idea ?

Thank you.

Mathieu
 
J

John John

Mathieu said:
Oh, last but not least, when I got the system there was a WinXP preinstalled
on the computer (OEM pre-installation, you know where you have to enter the
comp's name and stuff then it boots into Windows... then Windows asked
to be registered; since I did not have a valid key for XP...

The pc manufacturer HAS to send you a COA and key with the pc! Usually
the key is on a Microsoft sticker somewhere on the pc case. None of my
business but I would have kept XP even though I too am not exactly
enamoured with it. Mainstream support for Windows 2000 ends in June of
this year.

John
 
M

Mathieu Paquette

John John said:
The pc manufacturer HAS to send you a COA and key with the pc! Usually
the key is on a Microsoft sticker somewhere on the pc case. None of my
business but I would have kept XP even though I too am not exactly
enamoured with it. Mainstream support for Windows 2000 ends in June of
this year.

John

Nah I didn't pay for a WinXP licence... I asked for a plain PC, I think the
WinXP install went with the HD, and since I didn't ask for the licence well
I wasn't given one.

I wanted to install my old Win2000 licence I no longer use; the machine is a
Celeron with 256megs shared memory with the videocard, so I don't really
want to install XP, which is more system resource hungry than Win2k.. Plus,
my mom is used to using Win2k, not XP, and she's not really tech-savvy, so
I'd rather not have to introduce her to a "new" os. ;-)

Mathieu
 
J

John John

Ok, I see... Makes sense, I would have done the same in a case like
this. But I don't know how to fix your problem... :-(

John
 
A

Andy

I've seen this happen on a fully loaded system. What you can do is
wait for an appropriate time, say one hour. Then reset the computer
and let it continue where it left off. It should get through the
detection phase on the second or third go around.
 
N

none

Did you try to reset the config data in the BIOS? What about
reseating the memory or the processor? How about any other loose
connections like the hard drive?
 
T

Tino Boss

Hi Mathieu,
Maybe try to put another video-card and make the bios-settings to use
this (agp). Then see weather it crashes again.
Or try switching off temporarily not used onboard things like NIC,
Sound, Modem... and try again.

regards
Tino
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top