Error building ipnew and myndi

OSR_Community_User · July 8, 2002, 12:55pm

Hi,
We are developing an installer for a NDIS-intermediate driver. The
installation has to work on 98, ME, NT 4, 2k and XP.

For 98: While building the examples using the 16 bit c compiler (that
comes with winddk and is in …\WINDDK\2600\bin\win_me\bin16), the build
breaks within string.h, stdarg.h, stdlib.h at the following lines

#if !defined(_WIN32) && !defined(_MAC)
#error ERROR: Only Mac or Win32 targets supported!
#endif

Looks like it is not picking up the 16bit version of string.h. I do not
have the 16bit version on my machine (which has winddk, 98ddk, platform
sdk and msvc 6).

Kindly advise as to how I may get this built.

Thanks in advance
Sathish

p.s. would anybody have any information on installing intermediate NDIS
drivers, esp on 98/ME/NT. Thnx agn.

Bill_McKenzie · July 8, 2002, 5:16pm

Contact Bryan Burgin at Microsoft xxxxx@microsoft.com. He is probably the
only one that can help you. He has given out an IM sample before for 98
that is the only semi-working sample I have seen. The install is really
really tricky.

Intermediates on 98/Me are a MASSIVE pain in the neck in general, and they
don’t work quite right. I should say, a good number of protocols on 98
machines don’t work quite right, and thus won’t work with intermediates
quite right. This is only an issue if you need third party protocols, like
firewalls and such, to work over your IM. Microsoft’s protocols all seem to
work fine.

–
Bill McKenzie

“Sathish V J” wrote in message news:xxxxx@ntdev…
>
> Hi,
> We are developing an installer for a NDIS-intermediate driver. The
> installation has to work on 98, ME, NT 4, 2k and XP.
>
> For 98: While building the examples using the 16 bit c compiler (that
> comes with winddk and is in …\WINDDK\2600\bin\win_me\bin16), the build
> breaks within string.h, stdarg.h, stdlib.h at the following lines
>
> #if !defined(_WIN32) && !defined(_MAC)
> #error ERROR: Only Mac or Win32 targets supported!
> #endif
>
> Looks like it is not picking up the 16bit version of string.h. I do not
> have the 16bit version on my machine (which has winddk, 98ddk, platform
> sdk and msvc 6).
>
> Kindly advise as to how I may get this built.
>
> Thanks in advance
> Sathish
>
> p.s. would anybody have any information on installing intermediate NDIS
> drivers, esp on 98/ME/NT. Thnx agn.
>
>

Bryan_Burgin · July 8, 2002, 5:56pm

Sathish,

Check the order that is used to bring in include files and libs and make
sure that any 16-bit folders are listed first. Also make sure that
headers are brought in this order: DDK, SDK and then C.

The last time I built MyNdi I had to do so from within the Visual C v
1.52c IDE itself. This is not to say that it cannot be done, I just
never have done so. From the readme.txt file:

Tools that you need to build MYNDI.DLL
Microsoft Visual C 1.52c
Platform SDK
Windows 98 DDK

Installation steps
A sources. and makefile. are supplied for build.exe.
One must edit the …\98ddk\inc\master.mk file before
attempting
to build a 16-bit protected mode target. The C16_ROOT
environment
variable must be set to the fully qualified path of the
MSVC
root directory.

MyNdi.mak is supplied to build the sample in the MSVC IDE.
MyNdi.mak assumes that MSVC is installed to d:\msvc

If you want to try using the IDE, it is available as Disk #3 of the MSDN
Platform Archive. The CD is labeled “16-bit DDKs”.

My colleague Mike Stoccardo may have additional information regarding
building IPNew outside of the IDE, which I know is possible.

The big problem with installing IM drivers in 9x is that one must still
break the binding between the protocol (TCPIP) and the original miniport
manually. The concept of getting global notifications in your notify
object (ala custom NDI procedure, a.k.a. MyNdi) doesn’t exist, so you
won’t be able to veto bindings that are not directly associated with
your IM driver – and that binding, since it doesn’t touch either edge
of your driver, won’t be presented to your dll.

If you continue to have problems with building the sample, I’d be happy
to work with you directly.

Bryan S. Burgin
xxxxx@microsoft.com

This posting is provided “AS IS” with no warranties, and confers no
rights.

-----Original Message-----
From: Bill McKenzie [mailto:xxxxx@driver.attbbs.com]
Sent: Monday, July 08, 2002 2:14 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Error building ipnew and myndi

Contact Bryan Burgin at Microsoft xxxxx@microsoft.com. He is probably
the
only one that can help you. He has given out an IM sample before for 98
that is the only semi-working sample I have seen. The install is really
really tricky.

Intermediates on 98/Me are a MASSIVE pain in the neck in general, and
they
don’t work quite right. I should say, a good number of protocols on 98
machines don’t work quite right, and thus won’t work with intermediates
quite right. This is only an issue if you need third party protocols,
like
firewalls and such, to work over your IM. Microsoft’s protocols all
seem to
work fine.

–
Bill McKenzie

“Sathish V J” wrote in message
news:xxxxx@ntdev…
>
> Hi,
> We are developing an installer for a NDIS-intermediate driver. The
> installation has to work on 98, ME, NT 4, 2k and XP.
>
> For 98: While building the examples using the 16 bit c compiler (that
> comes with winddk and is in …\WINDDK\2600\bin\win_me\bin16), the
build
> breaks within string.h, stdarg.h, stdlib.h at the following lines
>
> #if !defined(_WIN32) && !defined(_MAC)
> #error ERROR: Only Mac or Win32 targets supported!
> #endif
>
> Looks like it is not picking up the 16bit version of string.h. I do
not
> have the 16bit version on my machine (which has winddk, 98ddk,
platform
> sdk and msvc 6).
>
> Kindly advise as to how I may get this built.
>
> Thanks in advance
> Sathish
>
> p.s. would anybody have any information on installing intermediate
NDIS
> drivers, esp on 98/ME/NT. Thnx agn.
>
>

—
You are currently subscribed to ntdev as: xxxxx@microsoft.com
To unsubscribe send a blank email to %%email.unsub%%

OSR_Community_User · July 8, 2002, 6:59pm

I second this. We maintain an IM driver for 2K/XP, and after trying to
port it back to 9x, we decided to go with a hook driver (Thomas Divine’s
approach). IM on 9x is really a pain…

-sd

On Mon, 2002-07-08 at 16:13, Bill McKenzie wrote:

Contact Bryan Burgin at Microsoft xxxxx@microsoft.com. He is probably the
only one that can help you. He has given out an IM sample before for 98
that is the only semi-working sample I have seen. The install is really
really tricky.

Intermediates on 98/Me are a MASSIVE pain in the neck in general, and they
don’t work quite right. I should say, a good number of protocols on 98
machines don’t work quite right, and thus won’t work with intermediates
quite right. This is only an issue if you need third party protocols, like
firewalls and such, to work over your IM. Microsoft’s protocols all seem to
work fine.

–
Bill McKenzie

“Sathish V J” wrote in message news:xxxxx@ntdev…
> >
> > Hi,
> > We are developing an installer for a NDIS-intermediate driver. The
> > installation has to work on 98, ME, NT 4, 2k and XP.
> >
> > For 98: While building the examples using the 16 bit c compiler (that
> > comes with winddk and is in …\WINDDK\2600\bin\win_me\bin16), the build
> > breaks within string.h, stdarg.h, stdlib.h at the following lines
> >
> > #if !defined(_WIN32) && !defined(_MAC)
> > #error ERROR: Only Mac or Win32 targets supported!
> > #endif
> >
> > Looks like it is not picking up the 16bit version of string.h. I do not
> > have the 16bit version on my machine (which has winddk, 98ddk, platform
> > sdk and msvc 6).
> >
> > Kindly advise as to how I may get this built.
> >
> > Thanks in advance
> > Sathish
> >
> > p.s. would anybody have any information on installing intermediate NDIS
> > drivers, esp on 98/ME/NT. Thnx agn.
> >
> >
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@positivenetworks.net
> To unsubscribe send a blank email to %%email.unsub%%
>
–

OSR_Community_User · August 5, 2002, 3:12pm

Hi all,
We have tried every possible way to acquire Visual C++ 1.52c and the 16-bit
environment, without success. Trying to contact the microsoft support site
gave us an error (“You are not authorized to view this page”; even though we
have an msdn subscription).

That aside, what are the options I have to install a NDIS intermediate driver
on windows 98. According to all your replies I absolutely need the 16 bit
ddks. Now that being unavailable, what are my options; coz I just need to do
this whatever the constraints. One suggestion given was:

Somehow install the driver
Change bindings programmatically later
No need for dynamic binding when a new card or protocol is inserted.

Is it possible to do this. If yes, then how may I do this. Any suggestions,
samples, tutorials or help?

Thanks and regards
Sathish

-----Original Message-----
From: Bryan Burgin [mailto:xxxxx@microsoft.com]
Sent: Tuesday, July 09, 2002 3:23 AM
To: NT Developers Interest List
Cc: Sathish V J; xxxxx@driver.attbbs.com; Michael Stoccardo
Subject: RE: [ntdev] Re: Error building ipnew and myndi