NTDEV : Ndis Wan Driver Does not come up?????? WHY??

Developing a NDIS - WAN Miniport Driver for NDIS 3.1
Hi all,
straight to the Problem::::

Problem: Driver is not getting loaded. DriverEntry is not hit.
In Windows 98 code is working.

System Configuration:
Windows 95 OSR 2.5
DDK for Windows 95
SDK for Windows 95

Loaded Debug version VxD by running C:\DDK\Debug\DDkDebug.bat Set
After Reboot following debug prints appeared in the SoftICE console.

*******************************
InitComplete:Device failed to iinitialize DDB=C0037A14 SDVXD
.
.
.
peldr: unresolved import: ntoskrnl.exe, memmove
peldr: image processing failed !

CM_WARNS: ROOT\NET\003 returned CR_FAILURE
#0028:C0386348 is calling the memory manager incorrectly
_DeAssign_Device_V86_Pages Global failed, bits are clear.
*******************************

Note: In all versions of Windows 95 (OSR 1.0/2.0/2.5) code is not working

Can anybody help???
Ajitabh Prakash.

>>Problem: Driver is not getting loaded. DriverEntry is not hit.

>peldr: unresolved import: ntoskrnl.exe, memmove
>peldr: image processing failed !

Assuming proper installation, a driver will not load if it contains
unresolved externals or if it has improper sections defined in the image.
I’m sure there are other reasons as well, but from what you have said, it
appears that the OS can not find memmove(). The driver probably loads under
NT because memmove() is defined in ntoskrnl which does not exist under
95/98. I personally use memcpy() (as an intrinsic function) which will work
as long as there are not overlapping block copies.

>Do you have any idea how can we control the load sequence of two NDIS
miniport drivers on 98 platform???

The order of loading NDIS files is determined by the INF file created for
the driver. I haven’t spent much time looking at how to force one driver to
load before another, but it would seem that you should (or could) define one
driver as an intermediate NDIS driver (even if it is not) and get the OS to
load the intermediate driver before it loaded the miniport. It is a kludge,
but it appears that your design is a kludge if one miniport driver requires
a separate miniport driver in order to work.

-----Original Message-----
From: Ajitabh Prakash [mailto:xxxxx@future.futsoft.com]
Sent: Saturday, February 26, 2000 8:39 AM
To: NT Developers Interest List
Subject: [ntdev] NTDEV : Ndis Wan Driver Does not come up??? WHY??

Developing a NDIS - WAN Miniport Driver for NDIS 3.1
Hi all,
straight to the Problem::::

Problem: Driver is not getting loaded. DriverEntry is not hit.
In Windows 98 code is working.

System Configuration:
Windows 95 OSR 2.5
DDK for Windows 95
SDK for Windows 95

Loaded Debug version VxD by running C:\DDK\Debug\DDkDebug.bat Set
After Reboot following debug prints appeared in the SoftICE console.

*******************************
InitComplete:Device failed to iinitialize DDB=C0037A14 SDVXD
.
.
.
peldr: unresolved import: ntoskrnl.exe, memmove
peldr: image processing failed !

CM_WARNS: ROOT\NET\003 returned CR_FAILURE
#0028:C0386348 is calling the memory manager incorrectly
_DeAssign_Device_V86_Pages Global failed, bits are clear.
*******************************

Note: In all versions of Windows 95 (OSR 1.0/2.0/2.5) code is not working

Can anybody help???
Ajitabh Prakash.


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

Thanks Dray,
It was a problem with the memmove.We have been able to do it.
Actually we got a Library without the source code and we were not able to
trace this before.anyway Thanks a lot.
I am also able to find that how my card was working even with tha wrong
mac.I enquired it with the manufacturer of the card and i found that the
card always operates in Promiscous mode.

THANKS A LOT…

Ajitabh

-----Original Message-----
From: xxxxx@moore-solutions.com [SMTP:xxxxx@moore-solutions.com]
Sent: Monday, February 28, 2000 7:04 PM
To: NT Developers Interest List
Subject: [ntdev] RE: NTDEV : Ndis Wan Driver Does not come up??? WHY??

>Problem: Driver is not getting loaded. DriverEntry is not hit.
>peldr: unresolved import: ntoskrnl.exe, memmove
>peldr: image processing failed !

Assuming proper installation, a driver will not load if it contains
unresolved externals or if it has improper sections defined in the image.
I’m sure there are other reasons as well, but from what you have said, it
appears that the OS can not find memmove(). The driver probably loads under
NT because memmove() is defined in ntoskrnl which does not exist under
95/98. I personally use memcpy() (as an intrinsic function) which will work
as long as there are not overlapping block copies.

>Do you have any idea how can we control the load sequence of two NDIS
miniport drivers on 98 platform???

The order of loading NDIS files is determined by the INF file created for
the driver. I haven’t spent much time looking at how to force one driver to
load before another, but it would seem that you should (or could) define
one
driver as an intermediate NDIS driver (even if it is not) and get the OS to
load the intermediate driver before it loaded the miniport. It is a kludge,
but it appears that your design is a kludge if one miniport driver requires
a separate miniport driver in order to work.

-----Original Message-----
From: Ajitabh Prakash [mailto:xxxxx@future.futsoft.com]
Sent: Saturday, February 26, 2000 8:39 AM
To: NT Developers Interest List
Subject: [ntdev] NTDEV : Ndis Wan Driver Does not come up??? WHY??

Developing a NDIS - WAN Miniport Driver for NDIS 3.1
Hi all,
straight to the Problem::::

Problem: Driver is not getting loaded. DriverEntry is not hit.
In Windows 98 code is working.

System Configuration:
Windows 95 OSR 2.5
DDK for Windows 95
SDK for Windows 95

Loaded Debug version VxD by running C:\DDK\Debug\DDkDebug.bat Set
After Reboot following debug prints appeared in the SoftICE console.

*******************************
InitComplete:Device failed to iinitialize DDB=C0037A14 SDVXD
.
.
.
peldr: unresolved import: ntoskrnl.exe, memmove
peldr: image processing failed !

CM_WARNS: ROOT\NET\003 returned CR_FAILURE
#0028:C0386348 is calling the memory manager incorrectly
_DeAssign_Device_V86_Pages Global failed, bits are clear.
*******************************

Note: In all versions of Windows 95 (OSR 1.0/2.0/2.5) code is not working

Can anybody help???
Ajitabh Prakash.


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


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