Re: SATA Boot drive NOT!

No
It will look where you tell it to look by means of the Bios settings.If you
were silly enough to use default BIOS settings instead of taking the time to
redo your settings(which I hope you write down so you can duplicate them
next time) you deserve to get the *** scared out of you with a boot
failure.
Its just a bloody machine............ if you input *** you will get *** in
return.
peterk

--
It's so much easier to suggest solutions when you don't know too much about
the problem
"Husky" <cbminfo@xxxxxxxxx> wrote in message
news:pib0d155odr0dqnrkhdce1pcup7fh08v30@xxxxxxxxxx
> On Sat, 09 Jul 2005 17:54:34 GMT, milleron <millerdot90@xxxxxxxxxxxxxxx>
> wrote:
>
>>On Sat, 09 Jul 2005 09:37:25 -0400, Husky <cbminfo@xxxxxxxxx> wrote:
>>
>>>SATA Boot drive NOT! Actually that's only half true. As long as there's
>>>no
>>>major malfunction it boots fine from that drive.
>>>
>>>After the floppy disaster I spent the day setting up all the drives
>>>correctly
>>>according to the motherboard directions.
>>>
>>>I now have the Drives as primaries, and the DVD,CD as secondary.
>>>But there's 3 hard Drives the floppy, and the DVD and CD, and HP just
>>>added a
>>>virtual drive.
>>>
>>>I have
>>>A: Floppy
>>>C: SATA 152 gig boot Master
>>>D: Memorex Dual layer DVD Master
>>>E: HP 9300 CD Slave
>>>F: 300 gig Maxtor IDE 10 gig IDE Maxtor data HD Master
>>>G: 10 gig Maxtor IDE Slave
>>>H: HP removable disk 0 bytes ?????
>>>
>>>D and E chained to IDE secondary
>>>F and G chained to IDE primary
>>>
>>>Used to boot and not be able to find any of the drives on the 1st page
>>>boot
>>>screen , but it still booted despite that and never lost a drive till I
>>>had to
>>>install the OS again.
>>>
>>>Now it identifies all the drives and accessories at bootup [takes a bit
>>>longer
>>>now] on the 1st boot page, and the 2nd boot page that shows primary
>>>secondary,
>>>they're missing. This might be interesting to fix also, but doesn't seem
>>>to
>>>affect anything.
>>>
>>>I already found out how to fix it if there's a major crash that screws
>>>the
>>>motherboard settings again. Something that really shouldn't happen, but
>>>it has.
>>>
>>>When it boots and says can't find OS that's when it starts looking for
>>>the OS
>>>on A: Oh yeah, an OS that takes up more than a gig of HD on a 1.44 meg
>>>floppy.
>>>
>>>How Do I get the SATA C: to replace A: the floppy when the next crash
>>>occurs ?
>>>Or is A: just the way the motherboard configures it's defaults ?
>>
>>Well, how do you have the boot order configured in BIOS?
>>
>>And it's NOT looking for an OS that takes up more than a GB on a
>>1.44MB floppy. The BIOS has no idea what OS you want to run or load.
>>It's just looking for any OS on each device you have listed in your
>>"Boot Device Priority" in the "Boot" section of your BIOS setup. If
>>you instruct it to look first at A:, but it finds no OS there, then it
>>will automatically look for an OS on the next device on your list, and
>>so on.
>>A: is the traditional default for the first device. The list usually
>>reads "First Boot Device: Removable; Second Boot Device: Hard disk;
>>Third Boot Device: CDROM."
>>Under "Hard Disks," you can list the order in which you want your hard
>>drives to be queried.
> Well that won't help then, if a major crash occurs again, the asus will
> revert
> to looking for A: every time huh ?
> I have it set to boot correctly. But last major crash screwed up the Asus
> Settings where it asked me to hit F2 to revert to defaults or F1 to
> configure.
> I was in no mood to play so I hit F2.
> And it couldn't find the OS so I had to play.
>
>>
>>Ron
>
> --
> more pix @ http://members.toast.net/cbminfo/index.html


.