boot takes 6 min

Discussion in 'Windows Desktop Systems' started by canadian_divx, Sep 5, 2003.

  1. canadian_divx

    canadian_divx Canadian_divx

    ok i built a computer before and i posted it before thinking it was raid but i didnt hvae time to look for the old post so here it is agian, it is an amd 2500+ 1.5gb ddr 333 2x 40gb 7200rpm and an ecs l7vta mobo with raid, i hvae turned raid off and unpluged it all from it. when i turn on the pc it takes takes about 2 min to detect the drives and then we i get it to boot from the xp cd it takea about 5 min to get into the windows install and it cant detect the HDD, it is all pluged in correctly and all and the dvd rom is new and working great.

    any ideas

    p.s. there is no new bios to flash, already checked and i am current
  2. punkandacoke

    punkandacoke eat me

    at the end of the rainbow
    you tried a bios refresh right. i mean. just try it. its not like its gonna make a difference.

    for not so knowledged ppl. take out the cmos battery and put it back in.
  3. punkandacoke

    punkandacoke eat me

    at the end of the rainbow
    and how much is that 8mb connection. i really need something faster than 1.5
  4. grimman

    grimman Guest

    Yell and/or cry. ;)
    Nah, but seriously. Are the cables ok? Sounds like they might be damaged.
  5. Hipster Doofus

    Hipster Doofus Good grief Charlie Brown

    Melbourne Australia
    Here's a couple of things>

    After you choose to start Windows from the Boot menu, you may experience a long delay (or pause) before your computer finishes starting. Note that this delay may range from 10 seconds to a minute. Also, this delay occurs before the Starting Windows progress bar appears, and your computer may appear to stop responding (hang) during this time.

    This behavior can occur if Windows is installed on a drive or a partition to which Windows cannot gain access with normal Basic Input/Output System (BIOS) INT-13 or INT-13 extension calls. When Windows Setup determines it cannot use BIOS calls to start, it uses scsi() or signature() syntax in the Boot.ini file instead of multi() syntax.

    When booting a system that requires scsi() or signature() syntax, Ntldr loads an additional device driver (Ntbootdd.sys) to initialize and interrogate the boot controllers in your computer. Ntldr then seeks the associated boot drive attached to the controller to finish loading the kernel. These additional operations take more time in Windows because of the Plug and Play nature of the operating system.

    This behavior is expected, however, Windows Setup may use scsi() or signature() syntax, even if your computer can boot using the normal BIOS calls. This may occur on Integrated Drive Electronics-based computers when using a large capacity boot drive. In this case, you can try adding an additional entry in the Boot.ini file and use multi() syntax on the new entry to boot from. Note that if this works, your computer starts without pausing.


    Correcting System Hang at Startup

    If your system hangs about 2 or 3 minutes at startup, where you can't access the Start button or the Taskbar, it may be due to one specific service (Background Intelligent Transfer) running in the background. Microsoft put out a patch for this but
    it didn't work for me. Here's what you do:

    1. Go to the control panel/admin tools/.
    2. Go to the 'Services' tab, find the 'Background Intelligent Transfer' service, disable it, apply the changes & reboot.

    Also if not on a network disable 'workstation' at the same place as above.

    That's all I have on slow booting.
  6. NetRyder

    NetRyder Tech Junkie Folding Team

    New York City
    Thread moved to OS
  7. Arniestan1

    Arniestan1 OSNN Addict

    If your harddrive is western digital and that is the only hardrive installed make sure you have it set to cable select. Also your memory should be pc2700 or higher.
  8. canadian_divx

    canadian_divx Canadian_divx

    ok been out at work for a while and net was down while upgrading network, teh cables were fine nad all but i figured it out, the 2 drivers were raided before and i was just trying to get one of them to work alon not in raid, it was a 40 gb drive but the computer saw it as an 80 and it was in conflict, so i zerod the drivers and it is all good and up and running now, and yea the 8mb connection is from fauther work. not a really public thing