Changed drive Letter assignment - boot no finish
Results 1 to 6 of 6

Thread: Changed drive Letter assignment - boot no finish

  1. #1
    Join Date
    Nov 2000
    Location
    Wa State, in the NW corner
    Posts
    1,192

    Changed drive Letter assignment - boot no finish

    This may be premature since I haven't taken the time to write the incredibly long series of text lines with /crashdebug notices at the bottom but here goes.

    I have a dual boot setup, Win98 and NT4 SP5. Everything was working perfectly for the last month but I needed to use partition magic to add a new logical partion which in effect devided a large 25 GB partition in half. I also allowed drive mapper to run. It finished correctly.

    Prior to that I had this:
    a:
    c: Win98 boot FAT32
    D: 27 GB Logical FAT32
    E: 2. GB FAT (second HD)
    F: 2. GB Fat32 (second HD
    E & F just used for secure storage)
    G: Win NT boot
    H: CD-r
    I: CD-RW

    I split D: which moved the G NT boot to H, etc.

    No hardware changes except in logical theory.

    I use XOLS as my loader and it works fine and NT loads normally through the screen showing NT 4 SP 5, then goes black for approximately 3 to 5 seconds then brings up a blue screen with a mile of code and the /chrashdebg or call system administrator at the bottom.

    I reinstalled XOLS and it recognized the 2 boot drives; C and H properly and allowed a correct setup and boot so I assume that's OK. It must be something with WinNT I figure. Would you all recommend I re-install NT from the CD or is there a simple way to re-assign G to H if that's the problem in the start up string (for lack of a better word)

    Thanks, Griffin

    ------------------
    "Finest Kind"
    Athlon64 3800+, Asus A8V, 4x512 PC3200, 2x160GB SATA Seagate Barracudas, BFG GeForce 6600 OC 256MB, Thermaltake PurePower 500W, Antec P180 case (silent), XP Pro; home built

  2. #2
    Join Date
    Jun 2000
    Location
    Stockholm, Uppland, Sweden
    Posts
    1,141
    Post the BSOD firstly.

    But your config is actually a hell :-) FAT32 partitions before NT boot partitions isn't a very good idea.

    My intuition tells me that Windows NT boot parameters and instructions have become corrupted and that the BSOD tells "INNACESSIBLE_BOOT_DEVICE_"

    ------------------
    AMD650 Mhz, K7V, 384Mb RAM, Matrox Millenium G400 32Mb, SBLive!, 3Com 3C905C
    Windows 98 SE + Windows NT 4.0 Workstation

    Visit our webiste! -> N-Show 2000
    AMD650 Mhz, K7V, 384Mb RAM, Matrox Millenium G400 32Mb, SBLive!, 3Com 3C905C
    Windows 98SE + Windows 2000 Pro

  3. #3
    Join Date
    Nov 2000
    Location
    Wa State, in the NW corner
    Posts
    1,192
    Qwemliis, thanks for the reply. A couple of points. First the statement
    But your config is actually a hell :-)(Don't know the end of your sentence here) FAT32 partitions before NT boot partitions isn't a very good idea.
    really is so only in the absract.

    Physically on the disk "H" is in front of all but the "C" Win98 boot, within the cylinder limit and worked very well prior to the logical change of "G" to "H".

    2nd, you're correct that
    "INNACESSIBLE_BOOT_DEVICE_"
    is the primary message. I also get the same message when booting in VGA mode.

    I didn't get back sooner because frankly, after everything this week I just didn't feel like working on it.

    My best guess would be to re-install WinNT since I already re-installed XOLS and it recognized and setup both "C" and "H" perfectly.

    Last; the end message text is pretty much useless, "Restart and set recovery options in the system control panel or the /CRASHDEBUG system start option. If...contact, etc.

    Don't know any way to do that so back to my original question; Is there any way to assign G to H or am I looking at a re-install of WinNT?

    ------------------
    "Finest Kind"
    Athlon64 3800+, Asus A8V, 4x512 PC3200, 2x160GB SATA Seagate Barracudas, BFG GeForce 6600 OC 256MB, Thermaltake PurePower 500W, Antec P180 case (silent), XP Pro; home built

  4. #4
    Join Date
    Jun 2000
    Location
    Stockholm, Uppland, Sweden
    Posts
    1,141
    I don't think that the drive letter assignment is the problem. A drive letter assignment don't halt Windows NT boot process! I had an NT installation once that were on D: and every time you started with the CD-ROM the CD-ROM ended up on D: and Windows NT boot on E:. It started up nice but no services and all commands from the registry that pointed to the system partition did never start.

    Your problem is that the Windows NT bootdrive isn't accesible. So reinstalling the XOSL boot loader was intelligent.

    I would: uninstall the XOSL and then "sys" the disk and then I would repair WIndows NT installation.

    If you information on how to do it just ask me. I don't know if you know how to do it.. :-)

    ------------------
    AMD650 Mhz, K7V, 384Mb RAM, Matrox Millenium G400 32Mb, SBLive!, 3Com 3C905C
    Windows 98 SE + Windows NT 4.0 Workstation

    Visit our webiste! -> N-Show 2000
    AMD650 Mhz, K7V, 384Mb RAM, Matrox Millenium G400 32Mb, SBLive!, 3Com 3C905C
    Windows 98SE + Windows 2000 Pro

  5. #5
    Join Date
    Nov 2000
    Location
    Wa State, in the NW corner
    Posts
    1,192
    Pkease explain "sys" the disk.

    ------------------
    "Finest Kind"
    Athlon64 3800+, Asus A8V, 4x512 PC3200, 2x160GB SATA Seagate Barracudas, BFG GeForce 6600 OC 256MB, Thermaltake PurePower 500W, Antec P180 case (silent), XP Pro; home built

  6. #6
    Join Date
    Jun 2000
    Location
    Stockholm, Uppland, Sweden
    Posts
    1,141
    Start from a Windows 98 startup disk and type in "sys c:"
    After that you can only boot Windows 98.

    Start Windows NT4 installation from Windows 98 and run the installation until you can choose to repair the Windows NT installation.
    Repair it and then you should be back in bissunes.

    With your XOSL is not needed for your system and should be uninstalled FIRST. I don't know how to do that but it needs to be removed.

    In dualbooting I have two rules for myself:

    1, Don't use bootloaders - they aren't needed.
    2, Don't use Partition Magic - learn how to partition correctly instead. ;-)

    ------------------
    AMD650 Mhz, K7V, 384Mb RAM, Matrox Millenium G400 32Mb, SBLive!, 3Com 3C905C
    Windows 98 SE + Windows NT 4.0 Workstation

    Visit our webiste! -> N-Show 2000
    AMD650 Mhz, K7V, 384Mb RAM, Matrox Millenium G400 32Mb, SBLive!, 3Com 3C905C
    Windows 98SE + Windows 2000 Pro

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

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