A8V Deluxe - No IDE Devices Instlled Even Though the CDRW Works Fine ???

  • Thread starter Thread starter Gary
  • Start date Start date
G

Gary

I've just developed a problem where upon boot up I get a message that
the system is scanning for IDE devices. I then get a message that no
IDE devices have been found and that the BIOS is not installed. Even
though the CDRW is installed as master on the first IDE channel and
works fine. I'm using a Seagate SATA Drive and a Lite On CDRW. The PC
is only 3 months old and before this happened I never saw any message,
just a fast boot ( Fastrac ? ) into Windows boot. It works ok but it's
now slow to boot. Any help appreciated.

Thanks in advance.

Gary
 
Gary said:
I've just developed a problem where upon boot up I get a message that
the system is scanning for IDE devices. I then get a message that no
IDE devices have been found and that the BIOS is not installed. Even
though the CDRW is installed as master on the first IDE channel and
works fine. I'm using a Seagate SATA Drive and a Lite On CDRW. The PC
is only 3 months old and before this happened I never saw any message,
just a fast boot ( Fastrac ? ) into Windows boot. It works ok but it's
now slow to boot. Any help appreciated.

Thanks in advance.

Gary
Click to expand...

The drivers are looking for PATA RAID IDE drivers, not the ones on your
standard IDE Channels.
Sounds like you recently installed the Promise RAID Drivers.

Bobby
 
NoNoBadDog! said:
The drivers are looking for PATA RAID IDE drivers, not the ones on your
standard IDE Channels.
Sounds like you recently installed the Promise RAID Drivers.

Bobby
Click to expand...
More to the point, it sounds as if the RAID BIOS has been enabled, and set
as the first boot device. The 'BIOS not installed' message would come from
this, not latter drivers.

Best Wishes
 
More to the point, it sounds as if the RAID BIOS has been enabled, and set
as the first boot device. The 'BIOS not installed' message would come from
this, not latter drivers.

Best Wishes
Click to expand...

Yes, I forgot to mention that I shut off the PC one nignt and all was
well. The next morning I kept getting messages for some reason that it
wanted to see the MB installation disk. I put in the disk and all
seemed well until I booted up again, that's when I began having the
"scanning for IDE devices problem" How do I disable the RAID BIOS and
get back to my previous settings. It's no big deal but I'd rather not
waste the time waiting for the search.

TIA

Gary
 
The drivers are looking for PATA RAID IDE drivers, not the ones on your
standard IDE Channels.
Sounds like you recently installed the Promise RAID Drivers.

Bobby
Click to expand...

I believe so :( I shut off the PC one night and all was well. The next
morning ( for whatever reason ? ) it began requesting the MB CD, I
complied after it's request on each boot and then it seemed ok until I
reboot and got the message that it was searching for the IDE device(s)

How do I get it back to the original setting without the RAID Drivers
?

TIA Gary
 
Gary said:
I believe so :( I shut off the PC one night and all was well. The next
morning ( for whatever reason ? ) it began requesting the MB CD, I
complied after it's request on each boot and then it seemed ok until I
reboot and got the message that it was searching for the IDE device(s)

How do I get it back to the original setting without the RAID Drivers
Click to expand...
There was actually a two stage problem here.
The CMOS setup, turned on the RAID controller. A 'spike' or glitch here.
Once this was turned on, Windows then asked for the disk, because it found
the new device.
The drivers are not causing the problem, they are a 'symptom'.
Don't worry about the Windows side of it. If you turn off the RAID
controller in the BIOS, the drivers will stop loading.
In the CMOS setup. Advanced. On-board devices. On-board Promise
controller. Set to 'IDE mode'. If you are not using this controller
(remember this does not provide the 'main' IDE, and SATA ports), you can
disable the controller completely.

Best Wishes
 
There was actually a two stage problem here.
The CMOS setup, turned on the RAID controller. A 'spike' or glitch here.
Once this was turned on, Windows then asked for the disk, because it found
the new device.
The drivers are not causing the problem, they are a 'symptom'.
Don't worry about the Windows side of it. If you turn off the RAID
controller in the BIOS, the drivers will stop loading.
In the CMOS setup. Advanced. On-board devices. On-board Promise
controller. Set to 'IDE mode'. If you are not using this controller
(remember this does not provide the 'main' IDE, and SATA ports), you can
disable the controller completely.

Best Wishes
Click to expand...
Thanks again for the information !

Best regards ... Gary
 
Thanks again for the information !

Best regards ... Gary
Click to expand...

That did the trick, many many thanks ! I used to build my onw systems
but I haven't kept up with the technology in the past 5 or 6 years.

Warmets regards.

Gary
 
Gary said:
That did the trick, many many thanks ! I used to build my onw systems
but I haven't kept up with the technology in the past 5 or 6 years.

Warmets regards.

Gary
Click to expand...
In the past, this would still happen, with third party SCSI controllers.
Machines with such controllers built in (mainly 'server' style systems),
have done this since the ealiest days of the PC. What is new, is having it
happen on 'everyday' systems. :-)
Glad it is working now. The only 'question', is wha glitched the CMOS in
the first place. if this happens again in the near future, it could
reflect that the battery is getting low.

Best Wishes
 
In the past, this would still happen, with third party SCSI controllers.
Machines with such controllers built in (mainly 'server' style systems),
have done this since the ealiest days of the PC. What is new, is having it
happen on 'everyday' systems. :-)
Glad it is working now. The only 'question', is wha glitched the CMOS in
the first place. if this happens again in the near future, it could
reflect that the battery is getting low.

Best Wishes
Click to expand...

Thanks again Roger. Thinking back I think what happened was my own
silly mistake. I hit restart instead of shutdown for the computer and
then l tried to time it just right so that I could shut the computer
down instead of letting it go through it's reboot cycle. I've done
that in the past with no problems but it looks like I got caught this
time :( I'll not do that again !

Best Regards.

Gary
 
Back
Top