Ultra ATA 133 TX2

jasonaerts · 04-15-2008, 02:50 PM

Hello to all here at TSF, my first post :) and i could really use ur help.

I am trying to get my back-up HD connected using the Ultra ATA 133 tx2 from Maxtor as my 680I sli mobo only has 1 IDE slot which im using for my ROM/cd/dvd drives.
The card has been detected via bios, and drivers installed succesfully in windows. Everything seems fine so long as i dont plug any drives into the PCI - IDE maxtor controller.
If i plug my HD in everything is detected correctly and it goes all the way to boot into windows but.... then i get nothing but a black screen?

I have tired swapping the DVD/ROM's into the Maxtor but there are issue's with the detection, and it only seeing 1 drive.

So the closest it gets to working is properly detecting my HD WD250gb

Motherboard bios is most recent, just updated hoping that would help but no go :(
Xp SP2

Thanks to all in advance and sorry bout the post not being very concise already late to work.

**eneles** · 04-16-2008, 10:47 AM

Welcome to TSF.

When connected to the controller card the HDD should be configured as single drive - no jumper.

Also - see if can boot with the HDD as the only drive on the CD/DVD cable.

jasonaerts · 04-16-2008, 11:45 AM

Yes the HDD is set as single (no jumper) and it also is the only IDE HDD connected.

Im stumped atm...

Thanks for the reply though

**eneles** · 04-16-2008, 11:57 AM

Did you try with the HDD alone on the CD cable?

jasonaerts · 04-16-2008, 12:11 PM

Well i know the drive works so long as i plug it in directly to the motherboard IDE.
It is the only drive hooked up to the Maxtor Ultra ATA-133, and its not boot-able, just random files and such and my other drive is SATA

Do you mean i should try unpluging my SATA drive?

*Also*
I got everything to boot up with my DVD/Rom drives hooked up to the Maxtor, but windows booted up weird, then i got mouse lag and such. Could that be caused by and address conflict?
I just need everything hooked up and working so i guess i really dont care whats hooked up to the Maxtor so long as it all works, maybe i should go that route ?

Should i be using a CD cable for my HDD and not an HDD cable?

**eneles** · 04-16-2008, 12:24 PM

Quote:

Originally Posted by jasonaerts

Well i know the drive works so long as i plug it in directly to the motherboard IDE.
It is the only drive hooked up to the Maxtor Ultra ATA-133, and its not boot-able, just random files and such and my other drive is SATA

Do you mean i should try unpluging my SATA drive? No.

*Also*
I got everything to boot up with my DVD/Rom drives hooked up to the Maxtor, but windows booted up weird, then i got mouse lag and such. Could that be caused by and address conflict?

Is there a Windows installation on the IDE HDD? Make sure the boot order in BIOS is set to SATA HDD first.

I just need everything hooked up and working so i guess i really dont care whats hooked up to the Maxtor so long as it all works, maybe i should go that route ?

Maxtor? Isn't the controller card from Promise?

Should i be using a CD cable for my HDD and not an HDD cable?

The IDE ribbon cables (and SATA) are the same for CD and HD drives.
Use an 80-wire cable.

jasonaerts · 04-17-2008, 01:04 PM

The card does have the Promise chip on it, but says Maxtor so...

I am using an 80 pin connector...

Bios is set to load my SATA drive first.

Thanks again for trying to help, but im still totally stumped why she wont boot up when the Drive is connected to the Maxtor/Promise controller

zenobia · 04-26-2008, 02:55 PM

I'm somewhat glad and somewhat disheartened to find this post. I have been struggling with almost the same scenario. My 2nd PC is equipped with an Athlon 64 3700+ on a Tyan S2865 motherboard, with 5 IDE hd's and an IDE DVD writer. I also have the Maxtor branded Ultra 133 controller (actually the same as the Promise Ultra 133 TX2) installed in order to run the additional HD's. The Maxtor controller is only being used for storage drives, not bootable. Here is what happens:

1) If the controller is plugged in, but with no drives attached, Windows (in this case Win2k8) boots fine.
2) If the controller is plugged in, but with drives attached, the bootup process fails shortly after the text screen shows up for the Maxtor controller indicating it found the HD's successfully. The bootup process just hangs at a black screen.
3) If I reset at this point, I *do* get the "Windows failed to start" screen which gives me options, but any one of those fails immediately afterwards at, guess what? A black screen.
4) Trying to boot from Windows setup disks or certain live cd's causes the black screen to appear and the bootup process fails.

I have tried all the following troubleshooting:

1) Verified all connections, jumpers, and verified the HD's do work.
2) Verified all BIOS settings, including boot orders.
3) Updated the controller's BIOS to the latest revision available from Promise (According to one troubleshooter, that solved this exact problem but did not for me.)
4) Removed anything extra from the PC not needed for bootup purposes
5) Switched PCI slots

More interesting facts:

1) This setup worked previously in an older motherboard/cpu setup, running under Ubuntu 7.10
2) Running a Ubuntu livecd (8.04) works perfectly. Ubuntu sees all the HD's and can access them, no problemo.

I am stumped. I have searched and searched for solutions. All I find are dead-end threads with other people explaining this same problem but with no solutions.

Any ideas?

jasonaerts · 04-26-2008, 07:52 PM

Quote:

Originally Posted by zenobia

I'm somewhat glad and somewhat disheartened to find this post. I have been struggling with almost the same scenario. My 2nd PC is equipped with an Athlon 64 3700+ on a Tyan S2865 motherboard, with 5 IDE hd's and an IDE DVD writer. I also have the Maxtor branded Ultra 133 controller (actually the same as the Promise Ultra 133 TX2) installed in order to run the additional HD's. The Maxtor controller is only being used for storage drives, not bootable. Here is what happens:

1) If the controller is plugged in, but with no drives attached, Windows (in this case Win2k8) boots fine.
2) If the controller is plugged in, but with drives attached, the bootup process fails shortly after the text screen shows up for the Maxtor controller indicating it found the HD's successfully. The bootup process just hangs at a black screen.
3) If I reset at this point, I *do* get the "Windows failed to start" screen which gives me options, but any one of those fails immediately afterwards at, guess what? A black screen.
4) Trying to boot from Windows setup disks or certain live cd's causes the black screen to appear and the bootup process fails.

I have tried all the following troubleshooting:

1) Verified all connections, jumpers, and verified the HD's do work.
2) Verified all BIOS settings, including boot orders.
3) Updated the controller's BIOS to the latest revision available from Promise (According to one troubleshooter, that solved this exact problem but did not for me.)
4) Removed anything extra from the PC not needed for bootup purposes
5) Switched PCI slots

More interesting facts:

1) This setup worked previously in an older motherboard/cpu setup, running under Ubuntu 7.10
2) Running a Ubuntu livecd (8.04) works perfectly. Ubuntu sees all the HD's and can access them, no problemo.

I am stumped. I have searched and searched for solutions. All I find are dead-end threads with other people explaining this same problem but with no solutions.

Any ideas?

Sadly this is my problem exactly to the >T<
Lets hope someone can help us sort this out ;)

04-15-2008, 02:50 PM	#1 (permalink)
jasonaerts Registered User Join Date: Apr 2008 Posts: 5 OS: Xp pro sp2	Ultra ATA 133 TX2 Hello to all here at TSF, my first post :) and i could really use ur help. I am trying to get my back-up HD connected using the Ultra ATA 133 tx2 from Maxtor as my 680I sli mobo only has 1 IDE slot which im using for my ROM/cd/dvd drives. The card has been detected via bios, and drivers installed succesfully in windows. Everything seems fine so long as i dont plug any drives into the PCI - IDE maxtor controller. If i plug my HD in everything is detected correctly and it goes all the way to boot into windows but.... then i get nothing but a black screen? I have tired swapping the DVD/ROM's into the Maxtor but there are issue's with the detection, and it only seeing 1 drive. So the closest it gets to working is properly detecting my HD WD250gb Motherboard bios is most recent, just updated hoping that would help but no go :( Xp SP2 Thanks to all in advance and sorry bout the post not being very concise already late to work.

04-16-2008, 10:47 AM	#2 (permalink)
eneles Moderator Hardware Team Join Date: Jan 2007 Location: Sweden/Denmark Posts: 21,187 OS: 98SE/XP SP3/Vista SP1/Ubuntu 8.04 My System	Re: Ultra ATA 133 TX2 Welcome to TSF. When connected to the controller card the HDD should be configured as single drive - no jumper. Also - see if can boot with the HDD as the only drive on the CD/DVD cable.

04-16-2008, 11:45 AM	#3 (permalink)
jasonaerts Registered User Join Date: Apr 2008 Posts: 5 OS: Xp pro sp2	Re: Ultra ATA 133 TX2 Yes the HDD is set as single (no jumper) and it also is the only IDE HDD connected. Im stumped atm... Thanks for the reply though

04-16-2008, 11:57 AM	#4 (permalink)
eneles Moderator Hardware Team Join Date: Jan 2007 Location: Sweden/Denmark Posts: 21,187 OS: 98SE/XP SP3/Vista SP1/Ubuntu 8.04 My System	Re: Ultra ATA 133 TX2 Did you try with the HDD alone on the CD cable?

04-16-2008, 12:11 PM	#5 (permalink)
jasonaerts Registered User Join Date: Apr 2008 Posts: 5 OS: Xp pro sp2	Re: Ultra ATA 133 TX2 Well i know the drive works so long as i plug it in directly to the motherboard IDE. It is the only drive hooked up to the Maxtor Ultra ATA-133, and its not boot-able, just random files and such and my other drive is SATA Do you mean i should try unpluging my SATA drive? Also I got everything to boot up with my DVD/Rom drives hooked up to the Maxtor, but windows booted up weird, then i got mouse lag and such. Could that be caused by and address conflict? I just need everything hooked up and working so i guess i really dont care whats hooked up to the Maxtor so long as it all works, maybe i should go that route ? Should i be using a CD cable for my HDD and not an HDD cable? Last edited by jasonaerts : 04-16-2008 at 12:15 PM.

04-17-2008, 01:04 PM	#7 (permalink)
jasonaerts Registered User Join Date: Apr 2008 Posts: 5 OS: Xp pro sp2	Re: Ultra ATA 133 TX2 The card does have the Promise chip on it, but says Maxtor so... I am using an 80 pin connector... Bios is set to load my SATA drive first. Thanks again for trying to help, but im still totally stumped why she wont boot up when the Drive is connected to the Maxtor/Promise controller

04-26-2008, 02:55 PM	#8 (permalink)
zenobia Registered User Join Date: Apr 2008 Posts: 1 OS: N/A	Re: Ultra ATA 133 TX2 I'm somewhat glad and somewhat disheartened to find this post. I have been struggling with almost the same scenario. My 2nd PC is equipped with an Athlon 64 3700+ on a Tyan S2865 motherboard, with 5 IDE hd's and an IDE DVD writer. I also have the Maxtor branded Ultra 133 controller (actually the same as the Promise Ultra 133 TX2) installed in order to run the additional HD's. The Maxtor controller is only being used for storage drives, not bootable. Here is what happens: 1) If the controller is plugged in, but with no drives attached, Windows (in this case Win2k8) boots fine. 2) If the controller is plugged in, but with drives attached, the bootup process fails shortly after the text screen shows up for the Maxtor controller indicating it found the HD's successfully. The bootup process just hangs at a black screen. 3) If I reset at this point, I do get the "Windows failed to start" screen which gives me options, but any one of those fails immediately afterwards at, guess what? A black screen. 4) Trying to boot from Windows setup disks or certain live cd's causes the black screen to appear and the bootup process fails. I have tried all the following troubleshooting: 1) Verified all connections, jumpers, and verified the HD's do work. 2) Verified all BIOS settings, including boot orders. 3) Updated the controller's BIOS to the latest revision available from Promise (According to one troubleshooter, that solved this exact problem but did not for me.) 4) Removed anything extra from the PC not needed for bootup purposes 5) Switched PCI slots More interesting facts: 1) This setup worked previously in an older motherboard/cpu setup, running under Ubuntu 7.10 2) Running a Ubuntu livecd (8.04) works perfectly. Ubuntu sees all the HD's and can access them, no problemo. I am stumped. I have searched and searched for solutions. All I find are dead-end threads with other people explaining this same problem but with no solutions. Any ideas?