Jump to content
Compatible Support Forums

athenis

Members
  • Content count

    4
  • Joined

  • Last visited

    Never

Community Reputation

0 Neutral

About athenis

  • Rank
    stranger
  1. I only start getting 'Inaccessible Boot Device' errors after I tried to install NT4 on my machine running on an Asus P3B-F The old harddisk I tried was an ancient 1.6GB drive. My mainboard currently has the most recent drivers..
  2. Ah... I don't have a CD-Rom on the secondary IDE channel. but I do have 2 CD Roms running off an Adaptec SCSI card that is supported. Will I need an IDE cdrom?
  3. Hmm.. But I had tried taking out the Fasttrak66 card and the drivers connected to it leaving behind a IDE drive with one small FAT partition.. Still no solution.. What's this error all about anyway?
  4. Hi, As I don't have a bootable CD-Rom drive, I tried to install NT by copying all the files onto harddisk and then running "WinNt.exe" from the command prompt, but the funny thing is after I rebooted setup crashed with an "Inaccessible boot device" error. What could be the cause of this? I tried: 1) Changing it with another harddisk with just one FAT partition. 2) Taking out all other SCSI/RAID controllers 3) Booting from floppy 4) I even got hold of a Windows 2000 RC2 CD and tried to install.. same problem. 5) Getting one old harddisk, zapping all partitions inside and created just one small partition using fdisk. One thing is, I'm using a Promise Technology Fasttrak66, and I even tried loading in the driver during installation, but it still doesn't work. I also have no SCSI harddisks, and no IDE CD-Rom drives.. Could it be possible that NT installation detects a SCSI card and expects to find a SCSI harddisk only to find the Promise Fasttrak partition? Or maybe it tried to access an IDE Cd-rom drive but to find nothing? Then it just gives me a dumb error? Is there anything more for me to try?? I started seeing this after I changed my mainboard to a Asus P3B-F.. but how can a mainboard cause this? Thanks!
×