Some good advice in the other replies to your post.

If you are not writing drivers for actual hardware devices another
timesaver would be to use virtual machines. This way you can test the
driver without leaving the development system. Not only does this
simplify debugging but it also offers you a great deal of protection
as your development platform stays up and functional when your driver
under test causes a catastrophy in the VM. You can also create
multiple VM's for each operating system you wish to test under.

The only problem is that you may need to check your machine specs as
memory and processor cycles will be shared between your actual desktop
os and the virtual machine. Having said that, a 2ghz processor and
512mb ram is sufficient.

If you're driving hardware then this may not be an option for you, but
otherwise its certainly worth bearing in mind.


VMWare is a great product for this (I use VMWare myself). Also,
microsoft has its own excellent VM solution.

Brad.

On Tue, 25 May 2004 08:16:12 -0700, "finecats"
<finecats@noemail.noemail> wrote: