The problem of NdisAllocateBuffer In VMWare
in [Device Drivers]
|
Prev: How do I let audio device in "Sounds and Audio Devices"?
Next: DeviceIoControl returning ERROR_INVALID_PARAMETER
From: havegone on 6 Apr 2008 23:27 Hi Now, I want to construct my own icmp packet in IM, but when the driver running to NdisAllocateBuffer, the computer shut down at once, the blue screen output the message is DRIVER_LESS_OR_EQUAL_IRQL. I donot know why, eventhought I lower the IRQL. In addition, NdisAllocateBufferPool return Successful, but the return pool handle is NULL. -- havegone ------------------------------------------------------------------------ Posted via http://www.codecomments.com ------------------------------------------------------------------------
From: PCAUSA on 7 Apr 2008 02:08 On Apr 6, 11:27 pm, havegone <havegone.37h...(a)mail.codecomments.com> wrote: > Hi > Now, I want to construct my own icmp packet in IM, but when the > driver running to NdisAllocateBuffer, the computer shut down at once, > the blue screen output the message is DRIVER_LESS_OR_EQUAL_IRQL. I donot > know why, eventhought I lower the IRQL. In addition, > NdisAllocateBufferPool > return Successful, but the return pool handle is NULL. > > -- > havegone > ------------------------------------------------------------------------ > Posted viahttp://www.codecomments.com > ------------------------------------------------------------------------ NdisAllocateBufferPool returns NULL on current Windows versions. So, that is nothing to worry about. Clearly some parameter that you are passing to NdisAllocateBuffer is invalid. You do understand that the fourth parameter (VirtualAddress) is an input to NdisAllocateBuffer. You should have allocated the virtual memory before making the call. You simply cannot lower IRQL ever!!! You can only raise IRQL. You can only call NdisAllocateBuffer when you are at IRQL <= DISPATCH_LEVEL. It is also vertain that the bug you are seeing has nothing specific to do with VMWare. This paper at NDIS.com may be helpful: http://ndis.com/papers/ndispacket/ndispacket1.htm Thomas F. Divine http://www.pcausa.com
From: PCAUSA on 7 Apr 2008 02:11 On Apr 7, 2:08 am, PCAUSA <pca...(a)gmail.com> wrote: > On Apr 6, 11:27 pm, havegone <havegone.37h...(a)mail.codecomments.com> > wrote: > > > Hi > > Now, I want to construct my own icmp packet in IM, but when the > > driver running to NdisAllocateBuffer, the computer shut down at once, > > the blue screen output the message is DRIVER_LESS_OR_EQUAL_IRQL. I donot > > know why, eventhought I lower the IRQL. In addition, > > NdisAllocateBufferPool > > return Successful, but the return pool handle is NULL. > > > -- > > havegone > > ------------------------------------------------------------------------ > > Posted viahttp://www.codecomments.com > > ------------------------------------------------------------------------ > > NdisAllocateBufferPool returns NULL on current Windows versions. So, > that is nothing to worry about. > > Clearly some parameter that you are passing to NdisAllocateBuffer is > invalid. > > You do understand that the fourth parameter (VirtualAddress) is an > input to NdisAllocateBuffer. You should have allocated the virtual > memory before making the call. > > You simply cannot lower IRQL ever!!! You can only raise IRQL. You can > only call NdisAllocateBuffer when you are at IRQL <= DISPATCH_LEVEL. > > It is also vertain that the bug you are seeing has nothing specific to > do with VMWare. > > This paper at NDIS.com may be helpful: > > http://ndis.com/papers/ndispacket/ndispacket1.htm > > Thomas F. Divinehttp://www.pcausa.com Sorry. You can certainly lower IRQL _IFF_ you have previously raised it yourself but I don't think that is what you are talking about. Good luck, Thomas F. Divine http://www.pcausa.com
From: Maxim S. Shatskih on 7 Apr 2008 06:32 > know why, eventhought I lower the IRQL. In addition, > NdisAllocateBufferPool > return Successful, but the return pool handle is NULL. This is normal, buffer pools are non-op in NT, they were only used in Win9x/Me. In NT, NDIS_BUFFER is MDL, NdisAllocateBuffer is IoAllocateMdl+MmBuildMdlForNonPagedPool, and NdisFreeBuffer is IoFreeMdl. -- Maxim Shatskih, Windows DDK MVP StorageCraft Corporation maxim(a)storagecraft.com http://www.storagecraft.com
From: HRcrestron on 7 Apr 2008 10:52
I am looking for a WDK software develper for a ft perm position in northern NJ. Would you be interested. Please contact me at bblum(a)crestron.com "havegone" wrote: > > Hi > Now, I want to construct my own icmp packet in IM, but when the > driver running to NdisAllocateBuffer, the computer shut down at once, > the blue screen output the message is DRIVER_LESS_OR_EQUAL_IRQL. I donot > know why, eventhought I lower the IRQL. In addition, > NdisAllocateBufferPool > return Successful, but the return pool handle is NULL. > > > > -- > havegone > ------------------------------------------------------------------------ > Posted via http://www.codecomments.com > ------------------------------------------------------------------------ > > |