Merry Christmas. I have several Win2kpro workstatons
(Asus CUBX-L system boards)that I would like to move from
the IDE connector to the Promise ATA-100 connector. How
do you add the Promise driver without reinstalling
Win2kpro and pressing F6 to add the driver? I already
checked the Asus web site, but to no avail.

This brings up a good point. If my Win2K server SCSI
controller dies, and I cannot get a exact replacement, how
would I add a new controller and driver without
reinstalling the OS?

Thanks,

Control Panel|Add Hardware

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft MVP [Windows NT/2000 Operating Systems]

"Brian" wrote:
| Merry Christmas. I have several Win2kpro workstatons
| (Asus CUBX-L system boards)that I would like to move from
| the IDE connector to the Promise ATA-100 connector. How
| do you add the Promise driver without reinstalling
| Win2kpro and pressing F6 to add the driver? I already
| checked the Asus web site, but to no avail.
|
| This brings up a good point. If my Win2K server SCSI
| controller dies, and I cannot get a exact replacement, how
| would I add a new controller and driver without
| reinstalling the OS?
|
| Thanks,

why try to answer a question if your answer is as ignorant as this. I
imagine his problem is he is using his old drive but with a new controller
(wouldn't refer to the promise 100 as SCSI) so if it wont boot how will he
go into add new hardware. My suggestion would be to boot to the recovery
disk hit F6 add the driver then tell the system to recover system files.
hopefully on the next boot it should automatically grab the right drivers.
hope it helped.


> --
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft MVP [Windows NT/2000 Operating Systems]
>
> "Brian" wrote:
> | Merry Christmas. I have several Win2kpro workstatons
> | (Asus CUBX-L system boards)that I would like to move from
> | the IDE connector to the Promise ATA-100 connector. How
> | do you add the Promise driver without reinstalling
> | Win2kpro and pressing F6 to add the driver? I already
> | checked the Asus web site, but to no avail.
> |
> | This brings up a good point. If my Win2K server SCSI
> | controller dies, and I cannot get a exact replacement, how
> | would I add a new controller and driver without
> | reinstalling the OS?
> |
> | Thanks,
>
>

You'll probably want to try reading the post again then you'll find out this
isn't the case at all.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft MVP [Windows NT/2000 Operating Systems]

"Rowan" wrote:
|
| why try to answer a question if your answer is as ignorant as this. I
| imagine his problem is he is using his old drive but with a new controller
| (wouldn't refer to the promise 100 as SCSI) so if it wont boot how will he
| go into add new hardware. My suggestion would be to boot to the recovery
| disk hit F6 add the driver then tell the system to recover system files.
| hopefully on the next boot it should automatically grab the right drivers.
| hope it helped.

Time out guys. Although it's good to get the juices
flowing with a little competition. Wish I had this type
motivation at work.

I understand the difference between SCSI and the Promise
connection on the system boards. My point was that they
operate in the same fashion, so I was hoping someone with
SCSI experience could answer.

Both ideas have merit because I understand where both of
you are going.

I'll experiment with both suggestions and post the results.

Thanks to you both.



>-----Original Message-----
>You'll probably want to try reading the post again then
you'll find out this
>isn't the case at all.
>
>--
>Regards,
>
>Dave Patrick ....Please no email replies - reply in
newsgroup.
>Microsoft MVP [Windows NT/2000 Operating Systems]
>
>"Rowan" wrote:
>|
>| why try to answer a question if your answer is as
ignorant as this. I
>| imagine his problem is he is using his old drive but
with a new controller
>| (wouldn't refer to the promise 100 as SCSI) so if it
wont boot how will he
>| go into add new hardware. My suggestion would be to
boot to the recovery
>| disk hit F6 add the driver then tell the system to
recover system files.
>| hopefully on the next boot it should automatically grab
the right drivers.
>| hope it helped.
>
>
>.
>

Time out guys. Although it's good to get the juices
flowing with a little competition. Wish I had this type
motivation at work.

I understand the difference between SCSI and the Promise
connection on the system boards. My point was that they
operate in the same fashion, so I was hoping someone with
SCSI experience could answer.

Both ideas have merit because I understand where both of
you are going.

I'll experiment with both suggestions and post the results.

Thanks to you both.


>-----Original Message-----
>
>why try to answer a question if your answer is as
ignorant as this. I
>imagine his problem is he is using his old drive but with
a new controller
>(wouldn't refer to the promise 100 as SCSI) so if it wont
boot how will he
>go into add new hardware. My suggestion would be to boot
to the recovery
>disk hit F6 add the driver then tell the system to
recover system files.
>hopefully on the next boot it should automatically grab
the right drivers.
>hope it helped.
>
>
>> --
>> Regards,
>>
>> Dave Patrick ....Please no email replies - reply in
newsgroup.
>> Microsoft MVP [Windows NT/2000 Operating Systems]
>>
>> "Brian" wrote:
>> | Merry Christmas. I have several Win2kpro workstatons
>> | (Asus CUBX-L system boards)that I would like to move
from
>> | the IDE connector to the Promise ATA-100 connector.
How
>> | do you add the Promise driver without reinstalling
>> | Win2kpro and pressing F6 to add the driver? I already
>> | checked the Asus web site, but to no avail.
>> |
>> | This brings up a good point. If my Win2K server SCSI
>> | controller dies, and I cannot get a exact
replacement, how
>> | would I add a new controller and driver without
>> | reinstalling the OS?
>> |
>> | Thanks,
>>
>>
>
>
>.
>

For the other issue you might have a chance booting with a floppy. For the
floppy to successfully boot Windows NT/2000 the disk must contain the "NT"
boot sector. Format a diskette (on an NT machine, not a DOS/Win9x, so the NT
boot sector gets written to the floppy), then copy ntldr, ntdetect.com, and
boot.ini to it; and possibly ntbootdd.sys. Edit the boot.ini to give it a
correct ARC path for the machine you wish to boot.

In order for this to work you'll want to change the arc path in boot.ini
from multi syntax to scsi syntax to indicate that Windows 2000 will load a
boot device driver and use that driver to access the boot partition. Then
also copy the new manufacturer scsi driver to the floppy but renamed to
ntbootdd.sys

Something like this below;

[boot loader]
timeout=10
default=scsi(0)disk(0)rdisk(0)partition(1)\winnt
[operating systems]
scsi(0)disk(0)rdisk(0)partition(1)\winnt="Windows NT 0,1"
scsi(0)disk(0)rdisk(0)partition(2)\winnt="Windows NT 0,2"
scsi(0)disk(1)rdisk(0)partition(1)\winnt="Windows NT 1,1"
scsi(0)disk(1)rdisk(0)partition(2)\winnt="Windows NT 1,2"

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft MVP [Windows NT/2000 Operating Systems]

<(E-Mail Removed)> wrote:
| Time out guys. Although it's good to get the juices
| flowing with a little competition. Wish I had this type
| motivation at work.
|
| I understand the difference between SCSI and the Promise
| connection on the system boards. My point was that they
| operate in the same fashion, so I was hoping someone with
| SCSI experience could answer.
|
| Both ideas have merit because I understand where both of
| you are going.
|
| I'll experiment with both suggestions and post the results.
|
| Thanks to you both.