PCI133 Contrllr 60gig HD not showing in Explorer

[JBuffett]

Heres my set-up:
Aopen AK73 Pro(a) Mobo, Win 98se, IDE channel 1 40gig Maxtor- master("C" drive), 8gig Maxtor-slave("D" drive), IDE channel 2 has 2 cd roms. PCI Slots, 1-Voodoo V5-5500, 2- empty, 3-SB Live X-gamer, 4- New Siig PCI 133 Controller : Channel 1 has new 60 gig Maxtor ATA133 HD jumpered as master on the black (master) plug, 5- Supramax Modem.

My sytem is working fine, I justed wanted to add a new HD because my C and D drives are almost full. I followed the controller cards instructions, plugged it in and booted, Win 98se recognized the new hardware and I installed drivers using the floppy that came with card.
Chected system properties and the new controller card is listed under Hard Disk Controllers as SIIG CN2487 UDMA133 IDE Controller and has no conflicts, exists in all profiles, IRQ 10-No conflicts. Shut down, plugged in the new 60gig HD jumpered as master, put in the maxtor floppy and got to its utility screen and it only shows the HD's on the MoBo, not anything about a HD on a PCI Controller, so couldn't format. Re-booted, went into bios and couldn't find the HD listed there. Re-booted and went into new controller cards bios with "F10", and that shows its aware theres a 60gig HD plugged in as master. Booted to Windows.
When I go to My Computer or Explorer, the new 60gig is not listed. Went back to Device Manger\ Disk Drives and the new HD is listed there below the Floppy as MAXTOR (Model#) PM checked "settings" and it is not assigned a drive letter, should my C, and D drives be listed there to?
Re-boot to MoBo bios, its was on "no plug and play OS" so changed to yes to see if it helped. Re-booted, same thing.
Went to both web sights to get help and SIIG saids to partition/format in Dos, can't do that 'cause the hd is not recognized has no drive letter assigned, Maxtor saids pluggin the hd nto a pci controller card is enough the controller will know what to do with the HD.
Hard Dik controllers in my device manager also lists for the MoBo controller: VIA Bus Master PCI IDE Controller,
Primary IDE Controller dual fifo, Secondary IDE Controller dual fifo. The Primary IDE Controller dual fifo has a conflict. "error" 10".Device Status "is not working, not present does not have all its drivers installed-error code 10", "Try ugrading driver". I tried the upgrade driver and windows reports I have the latest driver for it all ready. So tried to remove Primary IDE Controller, it said I can't-to remove the Controller its associated with, removed the VIA Master Controller and both Primary and Secondary controller removed them selves. Re-booted and ended up in the same sitituation. I removed all the controllers, rebooted and ended up with the same thing.

I hope you can help, Jim B.

 

[Theslowone]

What I would do is hook this drive up as slave and go into dos and fdisk it and format it to fat32. Then take it and put it back on the pc133 controller card.

Your mobo is usually only going to see the card as a scsi type device anyway, nothing that is hooked to it. Windows can't see it because its not formatted, and win98 cant see unformatted or non fat/ntfs partitions.

 

[JBuffett]

Hi, Thanks for helping. I did as you said, then let windows load and the drive was called "D". So shutdown, hooked it back up to the controller card, plugged it in the the black plug, set jumper as master, hooked up the old "D" drive back up where it was. Started windows and have same thing. The hd should be "E" but its not listed in Explorer. It can be seen in Device manager as before. So, I shutdown. Plugged my "D" drive into the card as master including jumper, hooked the new HD back as slave with jumpers, booted windows, and Explorer does not recognise my old "D" drive on the pci controller card. In device manager\ disk drives the old "D" drive is there listed. The new hd is now "D" and is listed in Explorer. I copied some programs to the new "D" and the programs work fine so I guess the formating and stuff is ok. Did thorough scan on it anyway and it checked good.
I suppose I could install windows on the new drive as master, and the old "D" drive as slave, copy everything off of the old "D", shutdown, totally remove old "D", set the new hd as slave on the Mobo. I'll loose the ATA133 speed, but thats better than no drive. Oh, and yank this pci controller card out.
Even though the card is showing as being good in device manger, do you think it might be bad? I tried to swap it to another slot, but the only one open is right by my V5-5500 PCI and it would've blocked the cooling fans on the V5. I can't move the SBlive card 'cause the slot its in is the only one where it would work.
If my ASUS A7V-133 hadn't crapped out I could be using it and probably not have these problems.
I still show the primary controller conflict in device manager. Think that is causing the pci controller to not work right or blocking explorer from seeing the drive on the pci card?
Thanks, Jim B.

 

[Theslowone]

Have you tried one of your hd on cable select instead of master?

And have you tried newer drivers?

 

[JBuffett]

Hi thanks alot for helping me, this things driving me nut-so.

New drivers I checked for at the controller cards sight and downloaded/installed that and still had same thing.

For the Mobo, I downloaded new via controller drivers. Theres a new bios for the board to but I'm very gunshy about Mobo bios flashing after going through h... with my ASUS A7V-133. Three times I flashed bios on it. Went through big pains to get it back running, the 3rd time, all the tricks to revive it that I've gotten from the web has failed, so short of sending off the bios chip for flash, the mobo is dead and I ended up buying this Aopen as replacement.

In so far as cable select, I've seen that as a jumper option in hard drives I've purchased, the hd manufacturers always said to use Master or Slave as choices so I never used it. What is cable select? What should I expect to see in device manager on a drive thats jumpered cable select? Your saying to jumper the new HD(the one connected to the pci controller) to cable select, or the other master that has win98se on it? Right now I have the new drive connected as Slave "D" and my old "D" is disconnected entirely. Were I to set my old "D" as cable select and re-hook it to the card, will that mess up any files on it?

Do you think its odd my old "D" drive didn't show on Explorer when I plugged it into the pci card? Does that point to the card, or IRQ conflict type thing?

Thanks, I really appreciate all your help on this,

Take Care, Jim B.

 

[Theslowone]

Cable select might help but it was just a thing to try
cable select is just as it sounds the ide calbe that you uses has three connectors on it, one for the mobo one for prim ide, one for sec. ide.
The cable select allows the cable to select the device as master or slave depending on how connected.

I doubt it is an irq problem, not absolutly positive, because an irq problem usually has the added bonus of giving a windows protection error.
It could be a bad card, have you tried both ide slots on the card?

I have a question for you, when you boot your computer does a screen come up that doesn't normally come up.
Like showing the controller card?

Try installing the drivers anyway for your system, even if windows doesn't want you to.

 

[JBuffett]

Hi, Thanks for posting back.
I do get the added screen on boot showing the pci controller and the hd configuration. Its shows the HD a Prime Master, and shows its model number, Below the HD is a bunch of open lines I assume for any added Drivers.

I swapped to the cards other channel, and I got blue screen of death on windows boot. The boot screen that shows the cards info showed the hard drive as master on the other channel. Oh yeah, did the cable select thing to. Iwent ahead and re-installed the VIA drivers, the latest one shown at Aopen sight is same as I had downloaded earlier, tried to d/l latest mobo bios but all of Aopens sight are down.

Do you know of an absolute, sure fire way to remove the drivers for the ide controller on Mobo that won't mess with my files on my boot drive? I did have that Asus on here, (although I swapped to this board 4 or 5 months ago and everythings been great till I put the PCI controller card in) and maybe some Asus drivers are "floating" around, "hidden" and causing this to happen? See, I'm grasping aren't I. I'm just thinking back when I went from my Voodoo v3-3000 to the V5, man, if it wasn't for the guys at voodoosource.net(sadly they shutdown) and here at Anadtech, I would never have sorted it all out. I wasn't thorough enough in eliminating all of the V3's drivers and stuff, so the V5 just wouldn't work right.

Regards,

Jim B.

 

[MGMorden]

Ok, try this: put your main drive on the 133 controller as a master. then put your old d: and the new drive on the motherboard. Set the bios to boot from "SCSI controller", then reboot.

 

[JBuffett]

Thanks McMorden,

I tried that out and on boot, it locked at "Verifying DMI Pool".
I disco'd all the drives, hooked the ATA133 as prime-master, installed windows, went thru the whole win setup, shutdown, rebooted to win, check device manager and the primary controller conflict was gone, shutdown re-hooked everything like old, the ATA133 back on the card, then booted to bios, made sure Aopen recognizing the HD's, all good there, went to bios on card, it shows the ATA133, booted to win, and there was "E" (ata133). Well thought I had got smart and fixed something, started putting some programs on it and everytime I went to open/run something from "E" drive got lots of blue screen errors and then finally lock-up. Restarted scanned it(failed- files to long, no association etc), quick formated from explorer, scanned again, all checked good. Put some programs and zips on it and so-far knock on wood and all that stuff, its o.k now. The primary controller conflict has returned though.
Hopefully it'll work for good.

Thanks for giving me a hand. Jim B.

 

[JBuffett]

Hi Everybody,

I thought to give an up-date on this thread. I got word back from the card manufacturer SIIG, and they said to return to vendor, cards defective. So thats it, all along it was the card. I can't return to vendor though, Compusa has a 14day return/exchange policy and I'm past that now.
I'm using the new drive as a "D" now, my old "C" is same. I copied the contents from the old "D" 8gig to the new one. So far everything seems good. I want to thank you all sincerely for giving a fella a hand. Where'd fellas like me be with-out Anandtech and all you folks!

Thanks Again, Jim B.