Strange boot sequence

  • Thread starter Thread starter Anonymous
  • Start date Start date
A

Anonymous

My computer boots up as follows :- floppy drive seek, cd-rom seek and
then hard drive. Windows splash screen appears with yellow line running in a
box......so far so good. The floppy drive activates again and the monitor
goes into sleep mode. The floppy drive activates again and the computer
comes to life and boots up to the windows desk top and works normally from
then on. Any ideas as to how I can get rid of the extra floppy disk activity
?
 
Anonymous said:
My computer boots up as follows :- floppy drive seek, cd-rom seek and
then hard drive. Windows splash screen appears with yellow line running in a
box......so far so good. The floppy drive activates again and the monitor
goes into sleep mode. The floppy drive activates again and the computer
comes to life and boots up to the windows desk top and works normally from
then on. Any ideas as to how I can get rid of the extra floppy disk activity
?
Click to expand...


At boot time, enter the BIOS (your owner's manual will tell you how)
and re-order the boot sequence (AKA boot order) so that hard drives
are put 1st. If you still want an installation CD to have boot precedence,
make the CD drive 1st, then hard drives. If there is no CD in the drive,
the BIOS will continue down the sequence looking for a hard drive
with an MBR.

*TimDaniels*
 
I've tried changing to a boot sequence which ignores the floppy drive, but
the second and third floppy access mentioned in my previous post still
happen. Its not a huge inconvenience as the computer eventually boots up as
normal, but it bugs me that I can't fix it.
 
Anonymous said:
I've tried changing to a boot sequence which ignores the floppy drive, but
the second and third floppy access mentioned in my previous post still
happen. Its not a huge inconvenience as the computer eventually boots up
as
normal, but it bugs me that I can't fix it.
Click to expand...

Something in the boot procss is accessing the floppy drive. The most likely
culprit is an antivirus program. Next most likely is a virus :-)

Kerry
 
Back
Top