Jump to content

Need help with very retarded problem.. can't boot off Windows CD?!?!


Recommended Posts

Need help with very retarded problem.. can't boot off Windows CD?!?!

 

Friday, after I got my A64 setup, I formatted and installed Windows XP flawlessly on my Seagate 160GB SATA HDD. Now I have a Raptor 74GB SATA and I want to install Windows XP on it too. So I unplug the data and power cable out of the Seagate and put it into the Raptor (I only have one set of cables thats why ) and load up my computer. It's detected during POST and it's displayed in BIOS so all is well so far. I enter BIOS and set my computer to boot off of CD-ROM as first device, floppy as second, and HDD as third. That's all I touch, everything else is set at optimized defaults. I save settings and exit BIOS. Nothing happens. Can't boot, can't POST, don't hear any beeps, just a blank screen with my CD-ROM drive spinning and reading the Windows Setup CD. I don't understand why this is happening. I followed the exact procedure mentioned above to re-install Windows on my Seagate 160GB SATA HDD 6 days ago - it should work exactly the same way.

 

:

 

I am baffled and I dont know what else to try. The CD isnt bad because I can read it in Windows using my Seagate HDD. My CD-ROM and DVD-ROM works fine too. HDDs are detected too. SATA drivers are installed automatically so there is no need for a floppy driver. EVERYTHING works flawlessly on my Seagate HDD right now. Is the Raptor drive bad? I doubt it, but even if it were, it shouldn't be affecting the way my computer POSTs and boots off CD.

 

Help?

Share this post


Link to post
Share on other sites

Do this:

1) Unplug the power or data cable from the raptor/mobo.

2) Boot up with said cables unplugged and go into the BIOS

3) Change boot order and anything else you wish in the BIOS (Boot Order)

4) Save & Exit

5) Power down computer and plug the hard drives back in

6) Boot up as normal.

 

You will have to do this every time you wish to change a setting in the BIOS. This is a known bug with the 7/05 and 7/11 BIOS'es

Share this post


Link to post
Share on other sites

Woah this is alot to digest.

Is the board brand new, if so what bios is it shipped with, 6xx,7xx,8xx ?

Changing the boot order on 6xx,8xx shouldn't cause a "no post" condition.

7xx, changing the time will cause a no-poster, so if you have 7xx, you just

got lucky being able to change things the first time.

 

The boot order should ALWAYS be: floppy/removeable, cdrom, hard drives, other.

Don't ever change that as right now I'm able to boot with a usb stick with a

"DOS" image on it and flash with it via usb, which is the "removeable" category.

 

If 7xx, like mentioned above, the bios "jump start" non-raid procedure, is

to:

1. Disconnect SATA, either power or data cable.

2. Reset cmos

3. Load optimized defaults, reboot to stop, reboot use

4. Change boot order, reboot to stop

5. Plug in power/data to SATA, reboot

6. Setup your other stuff, reboot to stop, reboot use

7. Setup all your bios stuff (peripherals), open cd, insert setup disk, save settings,

reboot

8. Install os.

 

Anything broken in the chain and you have other hardware problems...

(and this really isin't as bad as it looks, could be done in 5 minutes)

 

If you don't have 7xx...... disregard, you have another problem.

If 8xx, it could be the 216 fsb bug, if 6xx it could be the 349 fsb bug.........

 

Congratulations on your brand new mobo!!

gluck

Share this post


Link to post
Share on other sites

Do this:

1) Unplug the power or data cable from the raptor/mobo.

2) Boot up with said cables unplugged and go into the BIOS

3) Change boot order and anything else you wish in the BIOS (Boot Order)

4) Save & Exit

5) Power down computer and plug the hard drives back in

6) Boot up as normal.

 

You will have to do this every time you wish to change a setting in the BIOS. This is a known bug with the 7/05 and 7/11 BIOS'es

 

This fixed it.

 

Annoying as hell :(

Share this post


Link to post
Share on other sites

Just some extended info (cut & paste, and new):

 

Woah this is alot to digest.

Is the board brand new, if so what bios is it shipped with, 6xx,7xx,8xx ?

Changing the boot order on 6xx,8xx shouldn't cause a "no post" condition.

7xx, changing the time will cause a no-poster, so if you have 7xx, you just

got lucky being able to change things the first time.

 

The boot order should ALWAYS be: floppy/removeable, cdrom, hard drives, other.

Don't ever change that as right now I'm able to boot with a usb stick with a

"DOS" image on it and flash with it via usb, which is the "removeable" category.

 

If 7xx, like mentioned above, the bios "jump start" non-raid procedure, is

to:

1. Disconnect SATA, either power or data cable.

2. Reset cmos

3. Load optimized defaults, reboot to stop, reboot, get into bios

4. Change boot order, reboot to stop, shutdown

5. Plug in power/data to SATA, reboot, get into bios (if you can)

(at this point, if you had a bootable os on your hd, you will boot

into os without the opertunity to do step 6. From the os, you should change

the boot.ini file to offer you a menu before you boot. This will enable you

a stop point before your os boots, so you may reboot if necessary... always set this!)

6. Setup your other stuff, reboot to stop, reboot

7. Setup all your OTHER bios stuff (peripherals), open cd, insert setup disk, save settings,

reboot

8. Install os or "REPAIR" an os with a "different chipset". No need to do a fresh install!

Except when I had to redo my raid because of added drives, I hadn't done a fresh install in 3 years!

Only a "repair" that loads MS primitaves, keeping the registry intact for apps but invalidating

different chipset drivers. After which you can load proper chipset drivers and any others.

This is infinetly better than a reinstall, as if your like me, have every app registered since cpu time

day 0 !! BTW, apps have service paks too... After the old chipset drivers are invalidated and your able

to run, disable network and install all vid/chipset drivers, then do the windows update, then dx9c periodically.

This will preserve the REGISTRY on all your installed apps. And if your like me, my registry contains info

of mega installed apps for the last 5 years, that I don't even have a clue where the original disks are.......

If you want deailed info on HOW exactly to do this let me know. But you better be ready to do it with the

attitude of "go for it" I don't want any whiners if you crap it up !!! You can crap up a car wash after 48hrs of

on-line gaming so No excuses!!! I know xp pretty well, since I've installed it 20 times already without it F*cKing

up my installed apps (registry), and thats all you want. The data has carried over from si3112/nvidia raid/si3114

and back an forth from nf2/3/4 and its still here and works great. Don't listen to any bull crape that you have to

rebuild raid, thats pure crap !!!

 

Anything broken in the chain and you have other hardware problems...

(and this really isin't as bad as it looks, could be done in 5 minutes)

 

If you don't have 7xx...... disregard, you have another problem.

If 8xx, it could be the 216 fsb bug, if 6xx it could be the 349 fsb bug.........

 

Congratulations on your brand new mobo!!

gluck

Share this post


Link to post
Share on other sites

doesn't change with the latest bios either. I've got a board that refuses to power up now

 

did you clear the cmos right after the bios flashing? i need to do that with mine. ;)

 

in my case, stock settings work just fine, but it's kinda shaky if any oc is done on the board. :)

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...