I thanks you for the reply.
When I specified RC installed in the C:\, is actually the boot up option,
which I have done and the one that need the fix.
The OS-CD option will always need the diskette to provide the driver.
But the boot up option is the result of installation from the OS-CD, with
the command CDDrive letter:\386\winnt32.exe /cmdcons to the C:\
As I previously explain, the SCSI driver in question is not native to W2K or
XP, thus is NOT in the CD, consequently it will not be present in the RC
directory. This why when you double boot into the the console, you MUST be
immediately ready to press F6 and then provide the drivers for this
controller. IF YOU DO NOT, you will get a blue screen. Unfortunately the
diskette driver installation is only for that boot, as it will not get
permanently installed in the RC directory [C:\CMDCONS\]
Hopefully, you see the problem clearly now.
I am just looking for a way to get that driver to permanently "stay" in the
RC directory, just like others SCSI drivers. Just copy will not work, as it
need to be register somewhere in that program to be able to use it. That
could be one way to solve the problem.
Thanks again for your help.
Cheers
"DL" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Tried installing as a boot up option?
> http://www.kellys-korner-xp.com/win_xp_rec.htm
>
> I seem to recall it worked fine on a previous win2k sys that required a
> third party driver
>
> "Rolando E Creagh, MD FACS" <(E-Mail Removed)> wrote in message
> news:eB2t%(E-Mail Removed)...
>> Gentlemen,
>> Please indulge me with this peculiar question.
>> One of my computers with XP-Pro SP3, runs multiple SCSI-320 drives with
>> an Adaptec 29320 controller.
>> The driver for this is not native for the OS and of course it was
>> secondarily installed with no problem from a diskette, getting properly
>> installed in \Windows\System32\drivers.
>> But in using the Recovery Console for XP, either from the CD or after
>> installation on C:\, this particular scsi driver (adpu320.sys) must be
>> provided with the diskette on each instance. There is no obvious
>> Config.sys in the Console that can be edited (in the case of hard drive
>> installation) so that this diskette use is avoided.
>> I realize that since the console can only be installed from the CD using
>> the command \386\winnt32.exe /cmdcons and such driver is not present, it
>> will not be installed that way, as it will be obtain from the CD /386
>> directory.
>> Could it be safe and effective to place winnt32.exe in the \system32
>> directory of the hard drive, and perhaps obtain recognize installation of
>> the driver? Or would this be a catastrophe?
>> Is anybody has suggestion of how to do this other than the diskette.
>> Your knowledgeable advice shall be very much appreciated.
>> Cheers
>> --
>> Rolando E Creagh, MD FACS
>> Heartburn Center DM
>> Heartburn? WHY!
>>
>
>
--
R. E. Creagh, MD FACS
Heartburn Centre Des Moines
HEARTBURN?? WHY??!!
Demand a Peace Conclave!
Similar Threads
