I did just that. INSTALL is happy with the hostadapter, but no disk..............

0

The procedure outlined by Know the Ledge is the ONLY way to install scsi drivers on NT---period. PS: your scsi host bios must be enabled to load an operating system and boot, select default settings in the scsi select settings (this will make the host card ID#7 and the boot device ID# 0, and set the ID# to 0 for the scsi hard drive (NO Jumpers at all for ID#0). If more help is needed, email me. I run 98SE-NT-W2000-XP-SuSE Linux on all scsi hard drives.

0

A little more info for scsi hard drives: You must have a ribbon with an "active" terminator on the last connector. The hard drive can be on any other connector between the terminator and the host card. You also must have a jumper on the scsi hard drive's front 36pin connector to supply "terminal power" to the active terminator. This is not the rear 12pin connector (ID selector jumpers) where the 68pin ribbon and power connect. I'm assuming this is a 68pin scsi hard drive! If it's an SCA 80pin unit I've never had any luck loading an operating system onto these since they don't supply "terminal power" unless used with a SCA Controller and not a 29160 Host controller. An SCA controller is different because it's designed for hot-swapping the hard drives. You can use SCA 80pin scsi hard drives as a second/third hard drive if the operating system is installed onto a 68pin unit as ID#0. Scsi hard drives may be a little difficult to install, but work GREAT once setup is correct. Good luck.

0

Guys, you seem to be missing the problem. Steinar apparently has NO PROBLEM installing the SCSI host adapter driver during NT installation. Apparently, it's the *drive* that's not being detected. Checking things out with Adaptec's SCSI Select utility should provide some clues as to why NT is not detecting the disk. > The procedure outlined by Know > the Ledge is the ONLY way to > install scsi drivers on NT > ---period. No, this procedure isn't the only way to install SCSI host adapter drivers for NT. Nevertheless, Steinar's problem does not appear to be that he can't install the driver. He has said that he's installing the driver during installation and that NT Setup accepts the driver without error. > You must have a ribbon with an > "active" terminator on the last > connector. This isn't always true, either. Sometimes a passive terminator is all you need. It depends entirely on what type of termination the SCSI buss requires. There are several types of termination: * Passive * Active * Forced Perfect * High Voltage Differential * Low Voltage Differential The type you should use depends on the electrical requirements of the SCSI buss. Steinar says he's using as Adaptec 19160 host adapter. If he's got an Ultra160 setup and is using the correct cable, he does not have to worry about termination at all as the terminator is built into the cable itself. If he has a termination problem, one of the fastest ways to find out is by running the SCSI Select utility as I suggested earlier. > You also must have a jumper > on the scsi hard drive's front > 36pin connector to supply > "terminal power" to the active > terminator. This is not always true either. This is true only if you're using active termination *and* if the SCSI host adapter itself is not supplying termination power. Every SCSI host adapter I've ever seen that could require active termination also provides termination power and is configured to provide termination power by default, although I wouldn't be shocked to see an exception. The Adaptec 19160 provides termination power by default; there is no need for any other SCSI device to provide it. However, no damage should result if you configure a drive to provide unneeded termination power. If you're using passive termination, it will make no difference. If you're using a different type of termination (such as FPT or LVD), the terminator is diode-protected against overvoltages. "on the scsi hard drive's front 36pin connector"? Huh? You're not talking about a connector, you're talking about a jumper block, and these are often DIFFERENT depending on what drive you have! I have several IBM Ultrastars and among them, there are at least two different completely different jumper block layouts. Many drives have a single isolated jumper for setting the termination power. I've a Maxtor that's like this. In this case, I suppose the termination power jumper would look like a 2-pin "connector" instead of a 36-pin connector. Consult your documentation for jumpers; they vary. As far as SCA, they work exactly the same as non-SCA drives if you use an adapter. Since my Adaptec host adapters all supply the necessary termination power, there is no need for these drives to supply termination power. In fact, I *USE* 80-pin SCA drives connected to an Adaptec 2940U2W and an Adaptec 29160. The reason I use them is that I got some 80-pin SCA to 68-pin LVD adapters very, very cheaply and the SCA versions of the IBM Ultrastars don't go for nearly so much money. There's a lot of confusion and misconception when it comes to SCSI, but there's a lot of good information available on the 'net. Check out Adaptec's site, do some google searches, and if you've got a copy of Scott Mueller's Upgrading and Repairing PCs, well... that may be the only resource you'll need!

0

Andrew Ordo: I don't see anything I said before that would cause him a problem----why muddy the water? His reply that NT found the host adapter but not the drive was posted after the F6 driver post. Every scsi hard drive I have calls for LVD "active' terminator. I use three adaptec 2940U2W hosts and they do have built in termination for the host card itself, but NOT the bus ends and adaptec says to enable terminal power. Also IBM, Quantum, and Western Digital calls the front jumper block a "Connector"--thank you. And I use the 68pin to SCA adapters for many 80 pin units, but they don't work in "my" SYSTEM as ID#0 because there is no terminal power selection. Enough said!

0

Gentlemen. Facts follows: I have built computer systems since -79 (actually built a CMOS PDP-8 clone from scrach). I know how to terminate a cable. As I wrote earlier: The SCSI disk runs like hell as long as I boot NT from the IDE disk: read: Cable OK, Terminator OK, Adapter OK, Disk OK. First and only partition OK (2,0 GB) The adapter ID is 7, the disk ID is 0. But the disk is still invisible for INSTALL. Now I'm trying WINDOWS 2000. Same problem. W2K does'nt even ask for supplemental drivers. I rather install LINUX.

0

Last message from me: Just for fun: I booted NT from the IDE drive and created a 500MB FAT partition on the SCSI disk. I then booted DOS from floppy and installed DOS on the SCSI disk. Now the machine boots DOS from the SCSI drive, no problem! According to NT and W2K there is no drive, bot DOS boots happily. Definately LINUX, life is too short to waste on Bill.

0

Steinar, This is certainly a peculiar issue. I am assuming you have enabled SCSI BIOS in the host adapter's setup utility and checked the adapter settings. I have used similar Adaptec SCSI host adapters with NT for some time and never heard of a similar problem. Have you contacted Adaptec about this? In my experience, Adaptec's technical support has been absolutely top notch. (I was really quite impressed--they even helped me track down an compatibilty issue between Tyan Trinity s1590s motherboards and Adaptec's Ultra160 host adapters (By the way, these motherboards are incompatible with Adaptec's Ultra160 host adapters and there's no fix. It's a motherboard firmware issue.) Try contacting Adaptec if you haven't already. Surely they might be of some help. > I rather install LINUX. Ha! I don't blame you. It certainly fixed all *my* Windows-related issues. Plus, with ext3fs, you get file system journalling without sacrificing ext2fs compatibility. Good luck getting your SCSI issue resolved.

0

> Definately LINUX, life is too > short to waste on Bill. I agree whole-heartedly. I was a CP/M and DOS user who migrated to OS/2 Warp, but eventually seeing so many products I wanted to use ran under Windows, I struggled for YEARS to get Windows working properly. I've worked with Windows 3.1, Windows for Workgroups 3.11, Windows 95, Windows 98 Second Edition, NT 3.1, NT 3.51, NT 4.0, and eventually Windows 2000 before giving up. I have never had any problems with OS/2, Solaris, Linux, or BeOS--ever. As soon as my computer boots Windows, it slows down, acts flaky, and is not nearly so easy to administer and use. The only way I have been able to make my computers work properly is (sadly) to use non-Microsoft products. I have wasted thousands (maybe tens of thousands?) of hours, become maddeningly frustrated, and driven my blood pressure up struggling to make things work under Windows--only to discover that all these issues disappeared when booting practically any other operating system. I still think you should contact Adaptec and see if they can help you resolve this issue, but I know from personal experience that much time and money can be wasted trying to get Wintel system working properly when you can cut your losses and switch to a different platform. I only realized this after I had wasted so much time and spent so much money... it's depressing to think about. I think Windows is a great operating system if it works for you, but it doesn't, it's stupid to beat your head against a wall trying to make it work.

0

Gentlemen. Thank you for your contribution. I have given up the SCSI/NT issue, but let me tell you why I tried. I am working with a company developing GIS systems. We need all the computing power and disk bandwith we can afford. We are transferring from SGI/Irix to AMD/Linux system and are very happy with that. We have always used SCSI drives, but lately somone is questioning if IDE may be good enough. To test this I took a system home to benchmark that. I only had NT at hand, but of course the relevant OS to use for the benchmarking is Linux. I will not use more time on NT, rather go out sailing. End of story.

0

Hello, At my company we have bought 3 Dell precision 530 computers with Adaptec scsi controllers. I had the same problem as you and I tried all the same things as you did to make it work. Finaly I have found a document on Microsoft's site that stated that Windows setup is not capable to work with large SCSI hard drives. If your disk has more than 1024 cylinders, windows setup will not recognize it. They offer a workaround but I don't really understand what they are talking about. This is the webpage: http://support.microsoft.com/default.aspx?scid=kb;EN-US;q127134 Maybe you know what to do with their solution? The only way we were able to install NT on that SCSI hard drive was booting the computer and installing NT through the LAN Greetz, Jurgen

0

Hello, I came across this page after having the exact same problem as Steinar with one of my customers machines trying to clean install W2000 Pro on a 17.0Gb SCSI disk using the Adaptec 19160 Controller card. After much searching and hair pulling we found out that we were using the wrong driver. The first option that the Adaptec floppy driver disk supplies is 4 driver options. There are actually 6 options and you need to scroll down to come across the other two. Funnily enough it's the very bottom driver our machine was looking for. Afterwards everything worked like a charm. I doubt this may help anyone here but i'm sure someone else may be interested. Thanks, Matt

0

FYI: Make sure that the scsi drive is formatted under fat16, and not fat32 (you can convert to NTFS later). IF you are formatted under fat32 - When you "FDISK" your drive, chose "N"o when asked "Do you wish to preform a large disk installation?" Format you scsi drive with FORMAT.com. Try NT install then again. Do these processes under MS-DOS until your NT install.

0