Is "Memmove' a problem in Windows 95/98 ???

Hi all,

First the Problem:::::::

I observed a problem with Memmove in windows95/98.I had a Ndis driver that
uses calls from a “.lib” file.This library file uses c runtime library
calls as “memmove”.
The problem that i observed is that my Driver entry was hit on NT and the
driver was working fine but in some flavours of 95 and 98 even the Driver
entry was not hit.
we were able to solve this problem when i came to know that ONLY ntoskrnl
implements the memmove and some flavours of 95 and 98 do not.So my driver
was not coming up on these flavours.

Here the lazyness of Microsoft is indicated…These people are in such
a hurry to release the product that these people forget to document these
things.What the hell !!! we have waisted a full week fighting this problem.

The worst case was that i did not have the library code to look into it and
if i would had the code i could have eradicated this problem earlier as I
had some idea on these issues.

I Have a question to all Microsoft supporters IS THIS THING DOCUMENTED ANY
WHERE.??? and if NOT then WHY???

Thanks
Ajitabh

hi kannan,
Even i had this thing in mind but i am not supposed to do it because it is
a generic library that is also used by a GUI interface.So obiviously i
cannot use the Ndis calls in that Library.

Ajitabh

-----Original Message-----
From: Kannan. S [SMTP:xxxxx@hclt.com]
Sent: Thursday, March 02, 2000 12:14 PM
To: xxxxx@kailash.future.futsoft.com
Subject: RE: [ntdev] Is "Memmove’ a problem in Windows 95/98 ???

Hello Abijith,

Why dont you use NdisMoveMemory?, for portability reasons it is
always advisable not to use calls other than Ndis, wherever Ndis Calls
exist. NDIS wrappers should have done the work for you, and that is
what NDIS is for.

/Kans.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Ajitabh Prakash
Sent: Thursday, March 02, 2000 11:40 AM
To: NT Developers Interest List
Subject: [ntdev] Is "Memmove’ a problem in Windows 95/98 ???

Hi all,

First the Problem:::::::

I observed a problem with Memmove in windows95/98.I had a Ndis driver that
uses calls from a “.lib” file.This library file uses c runtime library
calls as “memmove”.
The problem that i observed is that my Driver entry was hit on NT and the
driver was working fine but in some flavours of 95 and 98 even the Driver
entry was not hit.
we were able to solve this problem when i came to know that ONLY ntoskrnl
implements the memmove and some flavours of 95 and 98 do not.So my driver
was not coming up on these flavours.

Here the lazyness of Microsoft is indicated…These people are in such
a hurry to release the product that these people forget to document these
things.What the hell !!! we have waisted a full week fighting this problem.

The worst case was that i did not have the library code to look into it and
if i would had the code i could have eradicated this problem earlier as I
had some idea on these issues.

I Have a question to all Microsoft supporters IS THIS THING DOCUMENTED ANY
WHERE.??? and if NOT then WHY???

Thanks
Ajitabh


You are currently subscribed to ntdev as: xxxxx@indus.hclt.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)

hi Ajitabh,
If u r writing an NDIS driver use the NDIS support library. U can take
this as a thumb rule.
If u r verymuch interested in a generic library , protect u r library
with flags appropriately.
Poor M$ is really not aware of your requirement for a generic library ,
maybe u can put it
across to them:-)
// balu
----- Original Message -----
From: Ajitabh Prakash
To: NT Developers Interest List
Cc:
Sent: Thursday, March 02, 2000 12:18 PM
Subject: [ntdev] RE: Is "Memmove’ a problem in Windows 95/98 ???

> hi kannan,
> Even i had this thing in mind but i am not supposed to do it because it is
> a generic library that is also used by a GUI interface.So obiviously i
> cannot use the Ndis calls in that Library.
>
> Ajitabh
>
> -----Original Message-----
> From: Kannan. S [SMTP:xxxxx@hclt.com]
> Sent: Thursday, March 02, 2000 12:14 PM
> To: xxxxx@kailash.future.futsoft.com
> Subject: RE: [ntdev] Is "Memmove’ a problem in Windows 95/98 ???
>
> Hello Abijith,
>
> Why dont you use NdisMoveMemory?, for portability reasons it is
> always advisable not to use calls other than Ndis, wherever Ndis Calls
> exist. NDIS wrappers should have done the work for you, and that is
> what NDIS is for.
>
> /Kans.
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of Ajitabh Prakash
> Sent: Thursday, March 02, 2000 11:40 AM
> To: NT Developers Interest List
> Subject: [ntdev] Is "Memmove’ a problem in Windows 95/98 ???
>
>
> Hi all,
>
> First the Problem:::::::
>
> I observed a problem with Memmove in windows95/98.I had a Ndis driver that
> uses calls from a “.lib” file.This library file uses c runtime library
> calls as “memmove”.
> The problem that i observed is that my Driver entry was hit on NT and the
> driver was working fine but in some flavours of 95 and 98 even the Driver
> entry was not hit.
> we were able to solve this problem when i came to know that ONLY ntoskrnl
> implements the memmove and some flavours of 95 and 98 do not.So my driver
> was not coming up on these flavours.
>
> Here the lazyness of Microsoft is indicated…These people are in such
> a hurry to release the product that these people forget to document these
> things.What the hell !!! we have waisted a full week fighting this
problem.
>
> The worst case was that i did not have the library code to look into it
and
> if i would had the code i could have eradicated this problem earlier as I
> had some idea on these issues.
>
>
> I Have a question to all Microsoft supporters IS THIS THING DOCUMENTED ANY
> WHERE.??? and if NOT then WHY???
>
> Thanks
> Ajitabh
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@indus.hclt.com
> To unsubscribe send a blank email to $subst(‘Email.Unsub’)
>
> —
> You are currently subscribed to ntdev as: xxxxx@hclt.com
> To unsubscribe send a blank email to $subst(‘Email.Unsub’)
>

hi Balasubramanian,
You way be right on that …but don’t you think that they should document
it somewhere. How can you trace out a problem when the same code works on
one machine and not on other???

Ajitabh

-----Original Message-----
From: Balasubramanian Krishnamoorthy [SMTP:xxxxx@hclt.com]
Sent: Thursday, March 02, 2000 12:29 PM
To: xxxxx@kailash.future.futsoft.com
Cc: xxxxx@lists.osr.com
Subject: Re: [ntdev] RE: Is "Memmove’ a problem in Windows 95/98 ???

hi Ajitabh,
If u r writing an NDIS driver use the NDIS support library. U can take
this as a thumb rule.
If u r verymuch interested in a generic library , protect u r library
with flags appropriately.
Poor M$ is really not aware of your requirement for a generic library ,
maybe u can put it
across to them:-)
// balu
----- Original Message -----
From: Ajitabh Prakash
To: NT Developers Interest List
Cc:
Sent: Thursday, March 02, 2000 12:18 PM
Subject: [ntdev] RE: Is "Memmove’ a problem in Windows 95/98 ???

> hi kannan,
> Even i had this thing in mind but i am not supposed to do it because it
is
> a generic library that is also used by a GUI interface.So obiviously i
> cannot use the Ndis calls in that Library.
>
> Ajitabh
>
> -----Original Message-----
> From: Kannan. S [SMTP:xxxxx@hclt.com]
> Sent: Thursday, March 02, 2000 12:14 PM
> To: xxxxx@kailash.future.futsoft.com
> Subject: RE: [ntdev] Is "Memmove’ a problem in Windows 95/98 ???
>
> Hello Abijith,
>
> Why dont you use NdisMoveMemory?, for portability reasons it is
> always advisable not to use calls other than Ndis, wherever Ndis Calls
> exist. NDIS wrappers should have done the work for you, and that is
> what NDIS is for.
>
> /Kans.
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of Ajitabh Prakash
> Sent: Thursday, March 02, 2000 11:40 AM
> To: NT Developers Interest List
> Subject: [ntdev] Is "Memmove’ a problem in Windows 95/98 ???
>
>
> Hi all,
>
> First the Problem:::::::
>
> I observed a problem with Memmove in windows95/98.I had a Ndis driver
that
> uses calls from a “.lib” file.This library file uses c runtime library
> calls as “memmove”.
> The problem that i observed is that my Driver entry was hit on NT and the
> driver was working fine but in some flavours of 95 and 98 even the Driver
> entry was not hit.
> we were able to solve this problem when i came to know that ONLY ntoskrnl
> implements the memmove and some flavours of 95 and 98 do not.So my driver
> was not coming up on these flavours.
>
> Here the lazyness of Microsoft is indicated…These people are in
such
> a hurry to release the product that these people forget to document these
> things.What the hell !!! we have waisted a full week fighting this
problem.
>
> The worst case was that i did not have the library code to look into it
and
> if i would had the code i could have eradicated this problem earlier as I
> had some idea on these issues.
>
>
> I Have a question to all Microsoft supporters IS THIS THING DOCUMENTED
ANY
> WHERE.??? and if NOT then WHY???
>
> Thanks
> Ajitabh
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@indus.hclt.com
> To unsubscribe send a blank email to $subst(‘Email.Unsub’)
>
> —
> You are currently subscribed to ntdev as: xxxxx@hclt.com
> To unsubscribe send a blank email to $subst(‘Email.Unsub’)