freeze during installation before press F6 on x86_64

[Flyzone]

Hi,
I have a new laptop (Acer 4920) with Intel Centrino Duo T7300 and a
Intel 965 chipset series with the Bios upgraded yesterday.
During the installation of Windows XP 32bit I got a freeze during
detecting hardware for installation, so I cannot press the F6 key
to read the IDE driver because is in the next windows.
I tried with AHCI setup and IDE setup (from the Bios) with the same
problem.
After the "detecting hardware" sentence, I got a black screen with
the IDE led on fixed.
I tried the windows cd with MSDN/2008 and SP3 installed, and
also some more old (SP2/SP1) with the same result.

No problems with a Windows XP 64bit, Linux (32/64bit) during
installation and execution; I have also made a memtest to check
if was a hardware failure.

There is some way to debug it/bypass the check?
Thanks in advance

 

[Flyzone]

Look familiar?

Google is your friend...

Not all people wrote without googling before....
read again the post with MORE attention about this:
1. in IDE mode already set (so not AHCI)
2. BEFORE press F6 (so no driver issue)

I don't need a driver, I don't need to listen people
telling that I need to google, or solution that I have
already done and wrote in the post.

 

[Paul]

Hi,
I have a new laptop (Acer 4920) with Intel Centrino Duo T7300 and a
Intel 965 chipset series with the Bios upgraded yesterday.
During the installation of Windows XP 32bit I got a freeze during
detecting hardware for installation, so I cannot press the F6 key
to read the IDE driver because is in the next windows.
I tried with AHCI setup and IDE setup (from the Bios) with the same
problem.
After the "detecting hardware" sentence, I got a black screen with
the IDE led on fixed.
I tried the windows cd with MSDN/2008 and SP3 installed, and
also some more old (SP2/SP1) with the same result.

No problems with a Windows XP 64bit, Linux (32/64bit) during
installation and execution; I have also made a memtest to check
if was a hardware failure.

There is some way to debug it/bypass the check?
Thanks in advance

What version of WinXP are you using ? Any chance the
installer is getting stuck on something non-storage
related ?

When the install is happening, it could use one of the
two programs as described here. These programs are
in the i386 directory of the CD. For example, when
I installed WinXP, I booted from a MSDOS floppy and
used winnt.exe. I don't see any debugging options
on the command line here (this info is for Win2K),
to provide feedback as to what is going wrong. I've
linked to this page, to give a general idea as to
what happens with the two programs.

http://www.winsupersite.com/showcase/win2k_cmdline_setup.asp

This WinXP page mentions a debug option for the command
line of winnt32. Whether winnt or winnt32 is being
used, would depend on what environment the installation
CD actually uses (and I don't know what that is).

http://www.informit.com/articles/article.aspx?p=102260&seqNum=6

If your WinXP is an older version, perhaps you could
slipstream up to a later Service Pack.

When set to "IDE" mode, the stock Microsoft I/O space
or PCI space storage driver should work. So I don't
even see pressing F6 as a necessity in IDE mode.
In AHCI mode, then things may be different. It is an
Intel chipset, so IDE should work without assistance
from F6.

You may get more hints about hardware in the computer,
using "dmesg", "lspci", and "lsusb" while booted into
Linux.

What bug was the BIOS update supposed to fix ? Have
you talked to Acer Tech Support, regarding whether
that BIOS works properly ? Any known issues with it ?

Paul

 

[Flyzone]

You may get more hints about hardware in the computer,
using "dmesg", "lspci", and "lsusb" while booted into
Linux.

I'm RHCE I know ;-)

Well...I solved my problems, thanks for that links, was
really useful!

The windows installation lockup while searching for already
installed windows, and the cause was....that I have a
cripted partition LUKS (Linux Uniï¬ed Key Setup) where are
my /home files stored.
Formatting the HD, installing windows, repartitioned, and
recovered all the other partitions solved my troubles

Thanks for the links

P.S: I usually update the Bios cause I saw many times
crashing the installation caused of some bugs, and
passing from 0.11 to 2.10 I saw many bugs removed.

 

[Flyzone]

Sorry, missed that. Too many people ask before Googling...

It's me that need to ask sorry...I think I replied a little hard,
well you'r not the only seeing this, but I prefer to don't reply
instead of giving the easy-reply for them.

Other than that, I got nothin'.

Like me...and that's why I posted here ;-)

So now I have solved, partition-related problem.