|Wayne A Parasram
|Posted on Sunday, February 4, 2001 - 11:16 pm: |
I recently bought a scsi controller card, an Iwill side 2930c (ultra).
I tried to put it into my new pc (p3 600). I dont have an ide primary hdd, but do have 2 small (1gig and 2 gig) scsi drives. The motherboard supports booting from scsi.
I connect everything up fine, and tried to boot from the cdrom. Which works, but no support for scsi. I created a startup disk with scsi drivers, and can boot into the system, however, the os refuses to install (have tried win95/98/2K/Me). Keeps giving me more or less the same error - It seems to think there is no fixed hdd, even though there are two. Also, although i run the scsi diagnostic which 'configures' the bios to work with/boot from the scsi disk, it will not. Also, even though the scsi controller manual says the card has a bios, the bios flashing utility says it does not.
Fdisk will also not recognise there being a fixed disk in the machine. Could it be the wrong type/mode?? I remember reading something about type/modes of 0-4 where 0 is a removable drive .... and i think it believes these are not fixed.
um, ANY help would be hugely appreciated, as Im kinda low on cash to go buy myself a new ide hdd.
|Posted on Monday, February 5, 2001 - 6:34 am: |
You should have received an installation disk with it. If not, you should be able to download one from their site. It might be referred to as a DOS installation disk. Also, make sure your drive settings in CMOS are set to none.
|Posted on Tuesday, February 6, 2001 - 4:51 am: |
Do you have your SCSI terminators right ??
|Posted on Tuesday, February 6, 2001 - 9:15 am: |
> First, thanx
> second, yes I have a cd of drivers and the manual and stuff. I have
> looked thru it, and by adding a few drivers to my congif.sys on my boot
> floppy, figured out how to access the drives in dos. The problem however,
> was getting an os, later than win3.11 to recognise the dirves as fixed
> disks. I have a feeling it might be thinking of them as removable or
> As far as the cmos goes, i shall try it tonight, however, mine is kinda
> new, and only really friendly to ide (i know it only autodetects ide).
> Thanx again for the help
You don't want the CMOS to detect anything and it won't. Just make sure the drives are set to none. Once the DOS drivers are loaded, you should be fine in any Windows. It must recognize the adapter card before it can see any drive. You may have to "Add New Hardware" and then use the Windows driver files for the card. once the adapter card is found and loaded correctly, then the drives should be recognized.
|Wayne A Parasram
|Posted on Wednesday, February 7, 2001 - 10:56 pm: |
have set the terminator on the hdd at the end of the cable ( and tried with only one hdd also) and the host card sets it terminator automatically, there is nothing to set on it.
thanx anyway tho
|Wayne A Parasram
|Posted on Wednesday, February 7, 2001 - 11:02 pm: |
the drives were set to none.... they were autodetect ... which ofund none, but even manually telling it none, and dont look, made no difference.
If I can get an OS installed ... i should be fine ... i have tried the hdds/host adapter on another win95 pc ... even without drivers it recognised fine and worked
|Posted on Friday, May 25, 2001 - 2:25 am: |
If the drives are not recognized at all there is no possibility to change anything with drivers (these are have to be loaded from the drive to be recognized in normal work -so this is a hen and egg problem. The BIOS have to do this work). Try to boot with a rescue disk into DOS and then figure out if the additional BIOS of the adaptor is really recognized (I think not). You have tried in another MB and it worked even with this adaptor? Then this motherboard isn't able to recognize the adaptor (if not present). Possibly a hardware collision or the memory settings in BIOS are wrong (caution with some settings regarding the memory area from C000 to F800 -real mode addresses. Since boot is in real mode with 20 Bit-addresses only even PCI have to map the BIOS into this area. Some settings possibly set this to additional RAM and overlap to it. Then the BIOS isn't reachable).