I'm trying to get my new Promise Ultra100 TX2 to work with my computer (SuperMicro P6DLE motherboard, dual PII 333, brand new Seagate Barracuda IV 40gig HDD). Following the instructions, I first installed the card in a PCI slot and rebooted.
It found the card, loaded its BIOS, went through the detection phase (but found nothing, since no drives were connected to it), then booted to Win2K (itself a brand new install from earlier in the afternoon). Windows found the card and loaded the driver off the floppy, and I rebooted. No conflicts or problems in the windows hardware manager. I shut down and moved my hard drive over to the controller card. It found the HDD, correctly displayed its info, then tried to boot. Right away I got an error message - 'Windows 2000 something or other, cannot access boot disk.' (But obviously it was able to access the drive, or it wouldn't have displayed a Win2K error, right??
This wasn't a blue screen, just white text on a black backgound.) Rebooted, went into BIOS, changed boot sequence to try 'SCSI' first (per the instructions). Same problem. Went back into BIOS. Disabled the onboard IDE controller, and specified the slot of the Ultra100 TX2 as an offboard controller. Still in BIOS clicked on IDE detection - it found the HDD, correctly displayed info. Instead of loading the Promise BIOS, it found the HDD (still hooked to the Promise card) right away, but hung after that and wouldn't continue. Went back into BIOS and played around with the PCI interrupts for the offboard controller (options for each channel - disabled, hardwired, inta, intb, intc, intd).
With each change, it could still find the HDD in BIOS, but wouldn't boot. Finally, with the primary channel set to inta, it booted and got 3/4 of the way through loading Win2k, then bluescreened - 'Boot Device Inaccessible', or something to that effect.sigh. Am I S.O.L.?
I've tried switching PCI slots, removing the other PCI card, changing the boot order, etc. The motherboard BIOS, controller card BIOS, and Windows Driver versions are all the most recent (though most recent for the motherboard is still a couple years old). I could be wrong and somebody more knowledgeable may correct me later, but it seems that you can't move hard drives like that. The boot.ini files points to a specific hard drive on a specific controller. I did do pretty much the same thing that you did and managed to get it working with much fiddling. This was in XP, but I used the setup CD to boot to the recovery console. From there I did a fixboot, and checked the boot.ini to see if it appeared correct (this was a bit over my head).
Dec 15, 2014 Hi Alex, The problem is that the driver files don't include an executable installation program - just the inf, cat and sys files. The options are either use the OS' auto or manual install-new-hardware and then set the path to the driver needed, or right click INF-file -> install. Softpedia > Drivers > Other Drivers & Tools > Asus > Asus PCI ATA-66 Card - Promise IDE chip - Promise Ultra 66TM IDE Controller Driver 1.60 Build 19 FLASH SALE: Driver Booster 6 PRO 60% OFF! Asus PCI ATA-66 Card - Promise IDE chip - Promise Ultra 66TM IDE Controller Driver 1.60 Build 19. Promise technology inc ultra ide controller free download - Sonnet Tempo Ultra ATA66, Sonnet Tempo RAID66/133, Ultra ATA66, LiteSpeed Web Server, and many more programs. Driver Booster.
I remember fiddling with that for a while until it magically worked. Sorry if thats not all that helpful, but truthfully thats what I did. You're going to have way more problems with moving your install to a different mobo than to a different controller. Actually, you should have no problem moving your drive to a new controller.
The Ultra100 TX2 is accessed by drivers, so loading those drivers first before the transfer is crucial. That aside, I'd try contacting Promise Tech Support since there may be a BIOS conflict or some such. They used to have a problem hardware page, but it's gone now. BTW, if you have PNP BIOS enabled, disable it. If you have DMA enabled in the BIOS, disable it.
My suggestion, reconnect the drive to the onboard controller, reinstall the drivers, make sure you try connecting a CD-ROM or something to verify it took, then place the HD on the new controller. I have 1, and I had no such problems. Which Promise BIOS and Drivers are you using with that mobo? Promise has new BIOS and drivers at their site. Do not set it to boot PCI or anything first, just set it to boot the HD. Also, don't assign IRQ's to the card, 2k will take care of it. This procedure has never failed me - Install WinNT/2k on the mobo controller.
Add the Promise driver to the SCSI devices without installing the card. You should get the 'service or driver did not start' message.
Power down, and install the card to the appropriate slot. Remember that Promise cards don't like to share IRQs, and even if you're using ACPI remember that on some mobos the first PCI slot is not independent of the AGP slot. The Promise BIOS should post, but not install, since you haven't attached any drives. Power down once the system boots.
Move your drives to the Promise card in the same or equivalent configuration as you had them on the mobo and power up. You should have no troubles, unless you have an odd boot sequence set in the mobo's BIOS (set to boot from SCSI first usually fixes everything). Quote: Originally posted by kwikit: BTW, if you have PNP BIOS enabled, disable it.
I only see an option for 'PNP Aware OS', which I have enabled. Should I disable that? Quote: If you have DMA enabled in the BIOS, disable it. The only DMA options I see are for DMA Channels 0-7. The options for each are 'PNP' (default) or 'ISA/EISA'.
Pci Ide Controller Driver
Quote: My suggestion, reconnect the drive to the onboard controller, reinstall the drivers, make sure you try connecting a CD-ROM or something to verify it took, then place the HD on the new controller. Thats what I did the first time with no luck, I'm getting ready to try again. Quote: Which Promise BIOS and Drivers are you using with that mobo? Promise has new BIOS and drivers at their site. According to the website, I have the latest BIOS and Drivers for the card.
Plus I have the latest BIOS for my motherboard. Something interesting I noticed - when trying to install Win2k with the HDD on the Promise card, I hit F6 to specify the additional driver, and it read the floppy disk but only gave me options for the WinXP drivers. I though that was odd so I downloaded the drivers off their website and put them on another floppy, but it still only displayed the XP drivers. Quote: Do you have any other HD's in your system on the on board ide controllers? Not originally.
I tried to reinstall with the HDD attached to the Promise card, but Win2k wanted to write some files to a HDD on the onboard controller (though none was connected). I scavenged up a 2 gig drive and stuck it as the primary master on the onboard controller. Windows then appeared to installed just fine, but still won't boot (Error: 'Windows 2000 could not start.
could not read from selected boot disk' - though it can obviously access it enough to know its supposed to be booting Win2k (Why?)). Quote: Originally posted by Dilligaffny: I had a similar problem and solved it by moving my Highpoint Raid card to pci slot 1 (next to the AGP slot agp or the one closest to the cpu). My slots appear to run backward - from top to bottom its AGP, PCI 4 to 1, ISA 3 to 1. Quote: I'd try contacting Promise Tech Support since there may be a BIOS conflict or some such. I think I may do that - I've wasted two evenings on this with no results.
Aside - any idea what 'Onboard NAT307 Mode' in BIOS refers to? According to the BIOS instructions the options are Non-PNP (default) or PNP, but they don't actually tell what this is. Google was no help.
Aah, it sounds like you need to edit your boot.ini, it's aparently pointing to the wrong disk or partition. Stick the drive back on the original controller and reboot. In your root of the boot drive you will find the boot.in file (it's hidden and read only) and make sure it set to your windows partition and drive, if windows 2000 is on the first partition on the first HD it should look like this: default=multi(0)disk(0)rdisk(0)partition(1) WINNT Make sure there are no HD's attached to the regular onboard controller, stick back on the Promise controller and it will work. Also, with some boards you need to set the boot order to BBS0 (not SCSI) to boot off add on ide cards. Quote: Originally posted by kalahari bushman: Make sure there are no HD's attached to the regular onboard controller, stick back on the Promise controller and it will work.
Hmm, okay, but what if I do want to have devices attached to the onboard controller? Right now I have the CDROM and Zip drive attached to the secondary channel, but I also have a burner I'd like to hook up (according to the Promise documentation, removable media should remain on the onboard controller). Anyway, the hard drive is back on the onboard controller for the time being, and Win2k is reinstalling. I'll look at boot.ini when its done. Here's the ideal scenario for this to work on an existing install in 2K/XP.
Install the Promise card in a free slot without a drive attached, boot into windows and load the drivers. XP has native drivers for this card, I dont think 2K does. Next remove the Busmaster IDE device from the IDE channel the hard drive is currnetly hooked up to. Change it to a Standard IDE controller. Then shut down, hook up the hard drive to the Promise card and restart. The busmaster drivers (whether Intel/Via or whatever) are loaded in the boot process and creating the BSOD since it is not finding the boot drive. Okay, I reinstalled with the HDD attached to the onboard controller.
Boot.ini looks just like you described. Installed the Promise card and drivers, no problems in the Windows hardware manager. Shut down, moved HDD over to Promise controller, adjusted BIOS to boot to SCSI first. Rebooted - Promise BIOS loads, finds HDD.
Displays Searching for Boot Record from SCSI.OK - then hangs; no HDD activity. So now its not even getting to Win2k. I tried switching slots, and removing all other PCI and ISA cards.
Quote: Originally posted by StanFL: The busmaster drivers (whether Intel/Via or whatever) are loaded in the boot process and creating the BSOD since it is not finding the boot drive. Its not bluescreening - when I was getting a Win2k error, it was before Windows had even started the boot process. (Black screen, white text). Quote: adjusted BIOS to boot to SCSI first That's the part you do not want to do. Do not change that entry in the BIOS. The system will automatically scan the onboard and on PCI card controllers for a bootable hard disk.
Leave it at the default. I just plugged mine in and changed no settings in the BIOS and it's worked since day 1.
As far as the PNP aware OS crap, turn it off. 2k/XP do not use the BIOS to determine the status of PNP hardware, so leave that at NO.
Your boot.ini should not have to change at all, if it's the only hard disk in your system. There is a DMA option. Called PCI IDE Busmaster. Set that to NO. Offboard PCI IDE Card.
Leave it at Auto. Ok, that's all I can think of without going through the entire BIOS. My suggestion, reset the BIOS to default factory settings and try. You might have erroneous changes that's preventing the card from being used.
. Pci Controller Driver Windows 10 PROMISE Technology is committed to providing high quality service and support to its customers. Our technical support is limited to PROMISE branded retail products. Different OEM manufacturers may have made unique modifications to the PROMISE hardware or software and they are responsible for supporting their products. How to Update Device Drivers Quickly & Easily. Tech Tip: Updating drivers manually requires some computer skills and patience. A faster and easier option is to use the Driver Update Utility for Promise to scan your system for free.
Use the Vista driver for the Promise Technology Ultra 133 TX2. It should work for both the Ultra 66 and the Ultra 100.
Promise Pci Ide Controller Driver
I found the Vista driver at: The file name is: Ultra133 TX2 windows 2.1.0.3 logo driver.rar This file is compressed in the rar format. I decompressed it using 7-Zip. Folder amd64 contains the 64 bit driver. The amd64 driver worked even though I have an Intel mother board. Go to Device Manager. The problem device will have a yellow exclamation point.
Right click on the device and click 'Update Driver Software'. Zelio sr2 usb01 drivers for mac Automation and control solutions Schneider Electric automation and control products and solutions cover the breadth of the industrial, infrastructure and building sectors — from programmable relays to motion controllers and interface modules, for applications from simple machines to complex process systems. Point it to the driver folder and install. I am using the Promise Ultra 66 card to drive an old IDE Zip drive on a Windows 7 64 bit machine. It works perfectly.
Tell us some more. Upload in Progress. Upload failed.
Pci Ide Controller Driver
Please upload a file larger than 100x100 pixels. We are experiencing some problems, please try again. You can only upload files of type PNG, JPG, or JPEG. You can only upload files of type 3GP, 3GPP, MP4, MOV, AVI, MPG, MPEG, or RM.
You can only upload photos smaller than 5 MB. You can only upload videos smaller than 600MB. You can only upload a photo (png, jpg, jpeg) or a video (3gp, 3gpp, mp4, mov, avi, mpg, mpeg, rm). You can only upload a photo or a video. Video should be smaller than 600mb/5 minutes.
Photo should be smaller than 5mb. You can only upload a photo.