>>Ed,
>>
>>Thanks for the reply. I've installed a 14 Gig drive but NT will only see 8 Gig. The controller card sees the 14 gig after a bios update, NT still reports 8. Tech support had me download a driver to install but now I get the mentioned error when trying to install the driver. When I tried to run the devices applet I get a message "Not implemented in this version of OS". I'm running NT 4.00.1381
>
>FWIW, when specifying the version of NT you're running, note the latest Service Pack and Hot Fixes installed. All current versions of NT 4.0 report Build 1381; Service pack 1, 2 or 3, HotFixes, and the Option Pack, all adjust the internal files but leave the build number alone. And SP4 is right around the corner, too.
>
>NT doesn't use the BIOS at all; the only thing the BIOS upgrade got for you may have been making more of the drive visisble when NT is -NOT- running. I assume you've gone into Disk Administrator, and no unallocated space is visible on the drive. If this is the case, you're running into an internal driver limit on size in the NT driver in place now, and will have to replace it, and possibly rewrite the partition table for the drive to make the full size of the drive visible to your system.
>
>You need to update the existing driver, not install it fresh. You can either stop the existing driver, remove it, and then add it, in SCSI Adapters/Drivers, or replace the driver file, shut down, and restart the system if the file has the same name and needs no additional resources.
>
>If this is the only controller in the system, you may need to reinstall NT over itself to get the correct driver in place (NT doesn't like having its only disk driver stopped) - this will, in the process of installation, allow you to select the new driver (I assume you have it on floppy, so that it could be read in during install).
>
>Even replacing the driver may not be enough, since NT will use information in the partition table to determine what's available for free space. If this is the case, you'll have to repartition and reformat the drive after the driver is installed; if this is the drive hosting your system or boot partition, you're looking at a complete reinstall of NT, and you'll have to specify the vendor-supplied driver during the initial installation. If this is the case, do your install from the three disk NT Install disk set, so that you can completely delete and reallocate the partition table for the drive during the install before NT takes over.
>
>If you've lost the three disk set, you can recreate it using the /ox command line switch for WINNT or WINNT32.


Ed,

Again, thanks for the information.

FYI SP3 applied. The 14 gig drive is the primary disk on the secondary IDE, it is not the boot disk and is currently empty. Disk Admin sees only 8 Gig. I have the new driver but thats when I hit the "Error reading INF err=0" message from the SCSI adapters/drivers. I know this sounds like a NT reload but I'm looking for another solution (I'm running multiple development systems in a large corporate environment - a complete reload would take several day).

Is there a way I can ID the driver, remove it and apply the new one without the SCSI adapters/drivers working or locate/correct the INF error it reports?

Regards,
Mike