Re: Re:slow re-boot after installing slave hard drive:1/27/2006




"knotsmart" <knotsmart@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0FF99131-DE42-4B1D-A25A-3013E24A285F@xxxxxxxxxxxxxxxx
> Greetings,
> As a new user, I am probably posting in the wrong place, again! I want to
> thank Glen, and Anna, for their help with my problem, as described above.
> It
> took me some time, but I studied information suggested by both of these
> fine
> folks, and I hope they see this. The problem was solved, and all seems
> well
> with my system now. It turned out to be a BIOS problem after all, but not
> a
> serious one. It seemed that I somehow, in doing the new installation,
> reset
> the BIOS to boot from the removable storage device, so the slow speed was
> the
> machine trying to boot from a CD that was not in the CD-ROM. When I reset
> the
> BIOS to boot from the primary hard drive, VOILA!, problem solved, and the
> boot time was right back to normal. Thank you both for the assistance!
> Still knotsmart, but hopefully a little closer to the cure!
> P.S. Glen, I tried bootvis. It's a nifty little utility, that as you
> pointed
> out, may not be useful for my specific problem. You were correct about
> that,
> but the utility works, helps with boot time in general, and I'll keep
> using
> it. Cheers!


knotsmart:
Glad to hear you were able to resolve the slow-boot problem, but I'm still
puzzled re the solution.

Ordinarily, many, if not most users set their boot order priority in the
BIOS so that the first boot device *will* be the CD/DVD drive. This is so,
of course, in the event the user desires a boot from a bootable CD, for
example, the XP installation CD before the system would boot to the HD.
Sometimes the boot order is set so that the floppy disk drive will be first
(or second) in the boot order - before the HD.

In these situations there should be *no* significant time differential
between booting straight to the system drive when the system does not detect
bootable media in the optical drive or the floppy disk drive. Two or three
seconds at most. In your original post I believe you said there *was* a
significant lag in bootup time when your slave HD was connected but that
when that drive was disconnected bootup time was normal (although you never
indicated the time differential involved as I recall). I really can't
understand why the change in the boot order would make any significant
difference (time-wise) in this particular situation. But, like everything
else in this business, if it works, we count our blessings.
Anna


.



Relevant Pages

  • Re: Boot.ini file contents
    ... master/slave settings and check with the MB company for a BIOS update. ... "Dale Sampson" wrote: ... > your boot disk is set as the active partition. ... >> repeatedly checked the boot order in BIOS to select the HD as the first ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: 2 wondows versions detected on pc startup?
    ... if not put there by the BIOS? ... BIOS examines the very first sector of the disk for a Master Boot Record ... table which describes the layout of the fixed disk and the partition loader ... This is where Windows and NTLDR comes in, ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: Dual Boot Question
    ... change the boot order, so, your master is putting up the boot menu. ... the hard drive boot order in the BIOS. ... The entries in this file control where the boot ...
    (microsoft.public.windowsxp.general)
  • Re: maximum hard drive size in Latitude cpi
    ... > actually written a boot loader they won't be so adamant about how "Windows ... > of the disk, and while it is being read off of the disk the machine is ... > limitatoins of that BIOS. ... After that the kernel takes over. ...
    (comp.sys.laptops)
  • Re: Question about backups with Ghost
    ... we're speaking about PATA drives here... ... following the cloning operation and make that initial boot with only the ... a change in the BIOS boot order should both drives be ...
    (comp.sys.ibm.pc.hardware.storage)