Serious problem/bug with dual boot installation of WinME/XP on aSATA harddisk (with KT600 based main

  • Thread starter Thread starter Peter Smith
  • Start date Start date
P

Peter Smith

Now, after several hours, I have NO HOPE to get a working installation
with my Soyo KT600 Dragon Plus and my Hitachi 160 GB SATA harddisk.

I know I have to press F6 during the first time WinXP installation to
install a scsi/sata driver, and I created a "driver disk" with all
necessary files (txtsetup.oem and the driver files) also.
I already enabled the SATA controller and the BIOS message appears
during bios boot up and shows me that there is a 160 GB hitachi SATA drive.
I 've created 2 partitions, one smaller for the WinME, one bigger for
the WinXP.
I installed Windows Millenium with success on the first partition.
I booted then with the WinXP CD ROM and I've pressed F6 for the third
party driver. This driver was used then and the "choose partition"
dialog was also there. I choosed the second partition and after copying
the SATA driver all files from Windows XP were copied to the second
partition (a blue screen with a yellow progress bar was there and shows
a growing progress).
After reaching 100% it reboots AND NOW THE PROBLEM IS HERE.

The initial black screen with that progress bar which is going from left
to right stays and IT DOES NOT GO ON. Even after 10 minutes nothing
happened except this screen is showing me a non-existing progress.
About 450 mb were copied to the second partition but Windows XP was not
really installed. No further screens with questions about the network
a.s.o. appeared.
I also tried to use the newest VIAArena VT8237 SATA driver 2.20E but the
behaviour did not changed.

I have two CD-ROMs connected to the second parallel IDE channel and the
SATA drive on the first SATA channel.
The board has the newest BIOS. So there's nothing else to consider, or ?

I have no glue what to do except to throw all out of the window.

It seems you can't use a SATA only system (except the parallel IDE
connected CD-ROMs) with a dual boot configuration with Windows ME and
Windows XP ??

PLEASE HELP ME !!!!!!
 
Well, before you throw it out the window you might want to check the list of
newsgroups on this server in your newsreader and look for the Hardware
board, it might be listed as microsoft.public.windowsxp.hardware or some
variation of that, go to that board and try your question there.
 
Michael said:
Well, before you throw it out the window you might want to check the list of
newsgroups on this server in your newsreader and look for the Hardware
board, it might be listed as microsoft.public.windowsxp.hardware or some
variation of that, go to that board and try your question there.
Click to expand...

Oh, thank you for your non-helping answer. Seems you didn't notice that
this question was generic and asks about the (missing) SATA support in
WinXP. But I guess, getting the title "MS-MVP" means that you can only
give answers which I also could get from the KB itself.

Peter
 
SATA support is a motherboard thing, not an XP thing. I have SATA drives with WIN XP and they work very well. I would ditch Win ME and embrace XP
Jef

----- Peter Smith wrote: ----

Michael Solomon (MS-MVP Windows Shell/User) schrieb
Well, before you throw it out the window you might want to check the list of
newsgroups on this server in your newsreader and look for the Hardware
board, it might be listed as microsoft.public.windowsxp.hardware or some
variation of that, go to that board and try your question there
Click to expand...

Oh, thank you for your non-helping answer. Seems you didn't notice that
this question was generic and asks about the (missing) SATA support in
WinXP. But I guess, getting the title "MS-MVP" means that you can only
give answers which I also could get from the KB itself

Pete
 
Jeff said:
SATA support is a motherboard thing, not an XP thing. I have SATA drives with WIN XP and they work very well. I would ditch Win ME and embrace XP.
Jeff
Click to expand...
I can't drop WinME (or Win98) because I had several older programs which
do definitely not run under XP, also I have "StarCommander" to transfer
floppy disk images via Parallel-Port cable to a real C64 disk drive,
which runs only in real mode flawless. Because do not advice somebody to
go with XP only until you are a microsoft sales person.
Btw do you have ONLY SATA drives or a mixed system (parallel and serial
ATA) ?

Regards
Peter
 
Whether it was XP or your motherboard, your best bet for an answer is on a
board where people dealing with this type of issue daily post and respond.

I'm sorry you didn't think my response was helpful, I was in fact trying to
help by directing you to a board this type of question is more typically
asked and answered; that's why there is a hardware board as opposed to a
board for more basic questions dealing not so directly related to a hardware
issue.
 
Michael said:
Whether it was XP or your motherboard, your best bet for an answer is on a
board where people dealing with this type of issue daily post and respond.

I'm sorry you didn't think my response was helpful, I was in fact trying to
help by directing you to a board this type of question is more typically
asked and answered; that's why there is a hardware board as opposed to a
board for more basic questions dealing not so directly related to a hardware
issue.
Click to expand...

I'd followed your advice but without success, but the solution for my
problem was related with the way of storing data in the CMOS-RAM which
my motherboard was using. Even after detaching my old Parallel ATA drive
there was still an information about it stored. Loading BIOS defaults
did not solve the problem, but using the "CMOS RAM erase" jumper helped.
So it was in fact related with the hardware, but the way Microsoft
offers or better, does not offer diagnostic tools is a shame.
At the very first time of booting (after the initial copy process from
the CD was finished) it does NOT help to use F8 nor any other offered
choice like SAFE MODE, because there was nothing installed yet, just
copied to my local harddisk.
It makes sense Microsoft would implement a text-only mode for
installation (I mean NOT the safe mode) with some diagnostic messages
but there was only the graphical boot screen.

Peter
 
I won't disagree with you there. However, isn't that a pretty high level
diagnostic and would that not vary depending upon motherboard. In other
words, wouldn't it be more appropriate for such a tool to come from the
hardware manufacturer as opposed to the OS coming with a generic tool to try
to diagnose each setup? There certainly would be limitations on such a tool
and what you are asking for is well beyond the normal user.
 
Back
Top