Hello All,

I have windows 95. I am using 98 DDk, VC++ 5.0. I went through the different vxd-tutorials. I also tried building different sample code available like in ShellMsg.zip.

But on Win95 I get "error code 2" while loading the VXD. The same binaries are working fine on Win98.

Could someone let me know where I am going wrong.

Thanks,
Ashish
Posted on 2004-04-12 04:13:26 by ashishparkhi
Try using WIN95DDK or upgrade to WIN98SE
Posted on 2004-04-12 04:33:12 by Vaxon
Hi,

I am not getting 95DDK anywhere. Secondly the tutorials mentioned about using win 98ddk (I also have MeDDk, but still the same problem). The other problem is that I also want to make my VxD work on win 95, and any VxD that I build using my setup, the Vxd fails to load. The problem is that the VxDs in the sample code are also not getting loaded when I build them. (they are getting build without problems)

Please help me out.

Thanks,
Ashish
Posted on 2004-04-12 05:36:25 by ashishparkhi
There's some thing you have to do to make VxD's compatible with win95... I think it's something like "WIN40COMPAT equ 1" before including any headers, but I can't remember.
Posted on 2004-04-12 07:09:38 by f0dder
Hello,

Thank you for the information. I will try to get more information on this and see if it works.

But the other question that remains is "How come the already compiled binaries which have come along with the sample source code work in Win 95 and the ones which I build do not"


Thanks,
Ashish
Posted on 2004-04-12 08:01:11 by ashishparkhi
Perhaps because the examples have been built with this flag enabled? It can be done from the masm commandline, you don't *have* to put it in the source files.
Posted on 2004-04-12 12:08:51 by f0dder
Boss,

Thanks a ton. It worked.

Thanks,
Ashish
:) :) :)
Posted on 2004-04-13 04:00:45 by ashishparkhi
> WIN40COMPAT equ 1

This, or hack the version flag manually in the assembled vxd. There are 2 places in the binary which hold the DDK and Windows version, of which only one needs to be
hacked (but it doesn't hurt to check both... Look inside the vxds using a hex editor to locate those flags, it helps to know how to change'm when you get all a ready made VxD whose author forgot to build or test it for 95 ...)
Posted on 2004-04-13 05:12:07 by Czerno