Asus TUSL2-C M/B, IBM deskstar 60GXP and Win2k
Results 1 to 5 of 5

Thread: Asus TUSL2-C M/B, IBM deskstar 60GXP and Win2k

  1. #1
    Registered User
    Join Date
    Jan 2002
    Location
    UK
    Posts
    20

    Post Asus TUSL2-C M/B, IBM deskstar 60GXP and Win2k

    Please help.

    I've just upgraded my motherboard from an Asus P2B to TUSL2-c. However I cannot boot into Win2k. An error message saying INACCESSIBLE BOOT DEVICE pops up everytime.

    I've tried disabling UDMA, changed IDE cables and swapped IDE channels but still no help. Anyone with any solutions? -other than reinstalling Win2k.

    TIA

  2. #2
    Registered User format c:'s Avatar
    Join Date
    Jun 1999
    Location
    Calgary Alberta Canada
    Posts
    881

    Exclamation

    Unfortunaitly you may have to reinstall Win 2k, If you are running win 2 k on fat 32 then you may get away with popping in a floppy and trying the fdisk/ mbr
    First pop in a system disk and run a dir. command on your c drive ( This will work as kong as your using fat 32 ) If you get invalid drive specification then you have to reinstall from fdisk, format c: , to win 2k set up
    I have also read here that Win 2 k does not like mother board changes
    Any time I swap a board I like to reinstall , just to be safe
    Format c I'm givin er all she's got cap'in !!! )

  3. #3
    Registered User AlienDyne's Avatar
    Join Date
    May 1999
    Location
    Athens, GREECE
    Posts
    3,772

    Post

    [quote]Originally posted by format c::

    I have also read here that Win 2 k does not like mother board changes



    This is true!

    Also, you should try to perform a Win2K Repair, using this option from the original Installation CD.

    Good luck!
    The wandering Odysseus of the web.

  4. #4
    Registered User
    Join Date
    Feb 2000
    Location
    Tolland, Ct.
    Posts
    60

    Post

    If the repair option doesn't work, try it again and when asked for special drivers for SCSI, etc, try installing the Intel ATA100 drivers. This will load the drivers and allow the drives to be recognized. I didn't think this was necessary with the Intel chipset, but many ATA100 devices are treated as SCSI (and based on it) so standard IDE drivers don't work.

  5. #5
    Registered User
    Join Date
    Jan 2002
    Location
    UK
    Posts
    20

    Post

    Thank you all for helping out. Unfortunately none of the proposed solutions worked.

    After long searching on the Microsoft site I managed to find a page which sorted my problem in minutes. Anyone with a problem like mine could visit this url: http://support.microsoft.com/default.aspx?scid=kb;EN-US;q271965&GSSNB=1

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •