what tools needed to develop IM

I have to start developing an Intermediate driver and I need to know exactly
what tools I need... through search in this news group, Microsoft site and
google I gather that I need the following and I need your feedbacks on it.
1. DriverStudio from Compuware which includes:
complete C++ and Visual Studio .NET with debuger; softICE and
VisualSoftICE
2. VMware!!! I found it on Intel site but not sure if this VMware is the
same as I need for development http://www.vmware.com/vinfrastructure/
3. Microsoft DDK
4. Latest MSDN

is this correct??? do I need all that or anything else???

Thank you.

Cody
Tue Mar 02 16:11:56 CST 2004

I have found the Microsoft DDK filled with enough tools and
documentation to fill my driver development needs.

cody

Lord of the Ring wrote:
> I have to start developing an Intermediate driver and I need to know exactly
> what tools I need... through search in this news group, Microsoft site and
> google I gather that I need the following and I need your feedbacks on it.
> 1. DriverStudio from Compuware which includes:
> complete C++ and Visual Studio .NET with debuger; softICE and
> VisualSoftICE
> 2. VMware!!! I found it on Intel site but not sure if this VMware is the
> same as I need for development http://www.vmware.com/vinfrastructure/
> 3. Microsoft DDK
> 4. Latest MSDN
>
> is this correct??? do I need all that or anything else???
>
> Thank you.
>
>
>
>

Thomas
Tue Mar 02 16:22:45 CST 2004

You need:

1.) Latest DDK and companion debugger. This would be from the Windows Server
2003 version of the DDK.
2.) The PassThru sample from that DDK
3.) Two PC's (at least) for debugging. One is target that executes the
software being debugged. Other is debugger console (WinDb).

VMWare is of some use, but not as good as real hardware in many cases.
Shines at the point that you are testing installations. It will be slower
then real hardware. And, you cannot actually debug just any old NDIS
adapter - just the emulated Ethernet drivers provided by VMWare. If you have
a problem adapter/miniport, then it will not be visible in an emulated
instance of an OS.

More documentation the better. MSDN is certainly needed.

For testing you may need an additional PC. For testing that leads to
acquiring digital signature there are specific hardware requirements.

Visit Windows Hardware and Driver Central as a portal for most DDK and
testing resources:

http://www.microsoft.com/whdc/

The Windows Driver Developer's Digest (WD-3) has a series of articles about
"Extending The PassThru NDIS Intermediate Driver Sample" and articles about
using the NDIS Tester. Visit:

http://www.wd-3.com

Also see:

http://www.ndis.com

Good luck,

Thomas F. Divine
http://www.rawether.net




"Lord of the Ring" <lordofthering@hotmail.com> wrote in message
news:ulgSp4JAEHA.1468@tk2msftngp13.phx.gbl...
> I have to start developing an Intermediate driver and I need to know
exactly
> what tools I need... through search in this news group, Microsoft site and
> google I gather that I need the following and I need your feedbacks on it.
> 1. DriverStudio from Compuware which includes:
> complete C++ and Visual Studio .NET with debuger; softICE and
> VisualSoftICE
> 2. VMware!!! I found it on Intel site but not sure if this VMware is the
> same as I need for development http://www.vmware.com/vinfrastructure/
> 3. Microsoft DDK
> 4. Latest MSDN
>
> is this correct??? do I need all that or anything else???
>
> Thank you.
>
>
>
>

Maxim
Wed Mar 03 18:08:15 CST 2004

> 1. DriverStudio from Compuware which includes:
> complete C++ and Visual Studio .NET with debuger; softICE and
> VisualSoftICE

Hardly necessary.

> 2. VMware!!! I found it on Intel site but not sure if this VMware is the

Very, very useful. I would recommend it.

> 3. Microsoft DDK

A must.

> 4. Latest MSDN

A must. It includes the DDK and MSDN Library (the latter is also on the web).

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com

Stephan
Thu Mar 04 14:20:38 CST 2004

On Thu, 4 Mar 2004 03:08:15 +0300, "Maxim S. Shatskih"
<maxim@storagecraft.com> wrote:

>> 2. VMware!!! I found it on Intel site but not sure if this VMware is the
>
>Very, very useful. I would recommend it.

Hmm, how about Virtual PC
(http://www.microsoft.com/windowsxp/virtualpc/). It's included in MSDN
(maybe only download area, don't know for the CDs)?

Has anyone given it a try?

Stephan

Thomas
Thu Mar 04 14:52:50 CST 2004

I have tried both. Don't find substantial differences so far.

What I have seen is that these are perfect for testing installations,
sandbox testing of software you don't want to keep around and for limited
debugging.

Performance of both the host and the virtal machine is naturally slow - in
some cases VERY slow.

Can run WinDbg from host to VM, but not super reliable (names pipe on
host...). Slow... (On 2.7MHz notebook with 1GB memory)

If you have MSDN, definitely give VPC a shot before trying VMWare.

I was hoping to retire my Windows 98/ME hardware (getting worn out...) using
these toys, but haven gotten that far.

Thomas F. Divine


"Stephan Wolf" <stewo68@hotmail.com> wrote in message
news:bp3f40hloi2fgqh12bkvknpm2srorm8q5s@4ax.com...
> On Thu, 4 Mar 2004 03:08:15 +0300, "Maxim S. Shatskih"
> <maxim@storagecraft.com> wrote:
>
> >> 2. VMware!!! I found it on Intel site but not sure if this VMware is
the
> >
> >Very, very useful. I would recommend it.
>
> Hmm, how about Virtual PC
> (http://www.microsoft.com/windowsxp/virtualpc/). It's included in MSDN
> (maybe only download area, don't know for the CDs)?
>
> Has anyone given it a try?
>
> Stephan

Lord
Thu Mar 04 15:53:52 CST 2004

Thank you all for your reponses and explanations

"Thomas F. Divine [DDK MVP]" <tdivine@NOpcausaSPAM.com> wrote in message
news:%231MdrqiAEHA.3804@TK2MSFTNGP09.phx.gbl...
> I have tried both. Don't find substantial differences so far.
>
> What I have seen is that these are perfect for testing installations,
> sandbox testing of software you don't want to keep around and for limited
> debugging.
>
> Performance of both the host and the virtal machine is naturally slow - in
> some cases VERY slow.
>
> Can run WinDbg from host to VM, but not super reliable (names pipe on
> host...). Slow... (On 2.7MHz notebook with 1GB memory)
>
> If you have MSDN, definitely give VPC a shot before trying VMWare.
>
> I was hoping to retire my Windows 98/ME hardware (getting worn out...)
using
> these toys, but haven gotten that far.
>
> Thomas F. Divine
>
>
> "Stephan Wolf" <stewo68@hotmail.com> wrote in message
> news:bp3f40hloi2fgqh12bkvknpm2srorm8q5s@4ax.com...
> > On Thu, 4 Mar 2004 03:08:15 +0300, "Maxim S. Shatskih"
> > <maxim@storagecraft.com> wrote:
> >
> > >> 2. VMware!!! I found it on Intel site but not sure if this VMware is
> the
> > >
> > >Very, very useful. I would recommend it.
> >
> > Hmm, how about Virtual PC
> > (http://www.microsoft.com/windowsxp/virtualpc/). It's included in MSDN
> > (maybe only download area, don't know for the CDs)?
> >
> > Has anyone given it a try?
> >
> > Stephan
>
>

Maxim
Thu Mar 04 17:57:03 CST 2004

> Hmm, how about Virtual PC
> (http://www.microsoft.com/windowsxp/virtualpc/). It's included in MSDN
> (maybe only download area, don't know for the CDs)?
>
> Has anyone given it a try?

I had. Faster then VMWare but more buggy, and I have troubles using WinDbg over
serial with it.

Connectix VPC 2003 is very buggy, but yes, by far faster then VMWare (at least
VMWare 3).

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com