Jump to content
Compatible Support Forums

aegris

Members
  • Content count

    4
  • Joined

  • Last visited

    Never

Community Reputation

0 Neutral

About aegris

  • Rank
    stranger
  1. well, in the end, i just put the HD on the regular ata 66 controller and installed win2k on that channel, then installed the drivers and switched it back to the ata 100 controller and it works fine.. i gave up on installing on the regular drive..heh. so thanks for the help all
  2. well i tried the build 19 drivers and it still only asked for them once, then gave me the same inacessable boot device message. I have a feeling the only way it will get installed to use the regular ide channel. and to brian, what good will moving the ATA drive from the first boot device?, just curious and yes, i am asking other people for advice, this column. if i knew how to do it myself, i wouldnt be here, thanks...
  3. Quote: <font face="Verdana, Arial" size="2">Originally posted by Dirty Harry: What you mean, where and when did you try ? During the W2K setup, it gives you an option to load these from a disk. You should have the (newest) drivers on a floppy and feed the PC at that stage. Are you set to boot from the correct drive? Are the settings in the promise bios OK? H.</font> yes, i have the latest drivers on a floppy and load them when i try to install.yes my computer is set to boot the correctly im pretty sure, check cd , then floppy then the ata 100 drive, im not sure what you mean when u say check the promise bios.. its build 35, so im guessing it is correct, not really sure though. A
  4. I have an Asus a7v with a 1 ghz athlon and 256 meg of pc133 ram. i have a ibm deskstar 45 gig HD and it uses the promise ata 100 controller. i am trying to install windows 2000 on a seperate partition. the problem is win2k wont even find my HD when i run the setup. I tried to provide the 3rd party drivers for the promise controller but i still get the inacessable boot device error msg. any one with any ideas on the reason for this?? thanks
×