I'm new to the DDK. I've never developed any drivers. I
have the XP DDK.

We have developed a custom PCI card (64-bit @ 66 MHz).
We need to develop a throw-away driver that tests our
hardware/firmware design.

My driver needs only simple functionality.
1) Master true 64-bit transfers accross the PCI bus.
2) Allow our custom card to master single 64-bit transfers
back into PC memory.
I don't need to handle interrupts. My application will
periodically check for a transfer.

3) Control multiple cards.

Our target machine is a Dell Xeon Precision 650 under
Win2K. It is a 32-bit machine with a couple of 64-bit PCI
slots.

I've watched the DDK videos and begun architectural tests
on the toaster func example. For my first test, I've
added three integers to the device extension and defined
control codes for getting and setting each.

How do I periodically update my driver during development?
I seem to recall Brian Catlin suggesting that I need only
install the driver once. After that, I can simply copy
toaster.sys to C:\WINNT\system32\drivers. I can't get
this to work on Win2K. I have to update the driver from
the Device Manager using the inf file AND reboot the
system. Is there a better way?

Re: How do I periodically update my driver during development? by Maxim

Maxim
Thu Jul 31 12:43:09 CDT 2003

> I seem to recall Brian Catlin suggesting that I need only
> install the driver once. After that, I can simply copy
> toaster.sys to C:\WINNT\system32\drivers.

Correct.

> this to work on Win2K. I have to update the driver from
> the Device Manager using the inf file AND reboot the
> system. Is there a better way?

Yes. Copy the driver as Brian suggests. Then go to Device Manager and "Disable"
the device. WinDbg must show the driver being unloaded. Then "Enable" the
device back.

This is impossible with boot drivers though, where you will need to reboot
after the .SYS file copy.

Max



How do I periodically update my driver during development? by Mike

Mike
Thu Jul 31 12:47:39 CDT 2003

I've discovered the solution. I looked in the Device
Manager and discovered that I had toasers still plugged-
in. I unplugged the toasters, coppied my *.sys to the
driver folder, and plugged my toasters back in.


>-----Original Message-----
>I'm new to the DDK. I've never developed any drivers. I
>have the XP DDK.
>
>We have developed a custom PCI card (64-bit @ 66 MHz).
>We need to develop a throw-away driver that tests our
>hardware/firmware design.
>
>My driver needs only simple functionality.
>1) Master true 64-bit transfers accross the PCI bus.
>2) Allow our custom card to master single 64-bit
transfers
>back into PC memory.
> I don't need to handle interrupts. My application
will
>periodically check for a transfer.
>
>3) Control multiple cards.
>
>Our target machine is a Dell Xeon Precision 650 under
>Win2K. It is a 32-bit machine with a couple of 64-bit
PCI
>slots.
>
>I've watched the DDK videos and begun architectural tests
>on the toaster func example. For my first test, I've
>added three integers to the device extension and defined
>control codes for getting and setting each.
>
>How do I periodically update my driver during development?
>I seem to recall Brian Catlin suggesting that I need only
>install the driver once. After that, I can simply copy
>toaster.sys to C:\WINNT\system32\drivers. I can't get
>this to work on Win2K. I have to update the driver from
>the Device Manager using the inf file AND reboot the
>system. Is there a better way?
>
>.
>

Re: How do I periodically update my driver during development? by Mike

Mike
Thu Jul 31 12:51:58 CDT 2003

Thanks. Works fine.

>-----Original Message-----
>> I seem to recall Brian Catlin suggesting that I need
only
>> install the driver once. After that, I can simply copy
>> toaster.sys to C:\WINNT\system32\drivers.
>
>Correct.
>
>> this to work on Win2K. I have to update the driver from
>> the Device Manager using the inf file AND reboot the
>> system. Is there a better way?
>
>Yes. Copy the driver as Brian suggests. Then go to Device
Manager and "Disable"
>the device. WinDbg must show the driver being unloaded.
Then "Enable" the
>device back.
>
>This is impossible with boot drivers though, where you
will need to reboot
>after the .SYS file copy.
>
> Max
>
>
>.
>