Printable View
I think the Device Manager tab of System Properties is there just to tease vb programmers with devices you'll never be able to access directly from vb.
Am I right?
No?
Well how do I access those devices? I can do it just fine from Quick Basic, but I need the windows interface. I'm not looking for work around or OLE Controls. I'm looking for the real-deal access through the Win API. (If that's possible)
Any ideas? Somebody out there has to be smarter than me... Now's your chance to prove it...
I was reading in the VB tutorial that is hosted here at vb-world by Karl, and he said that you cant even access that crap with VB. I dunno but I think it would be safe to say that you cant. All VB does it use API, and the API just draws from the operating system, and that is what actually does the dirty work, like bytes and bits and all that jazz. Maybe im wrong, if I am then i will eat my hat.
Bye
Ok, so how do I go about writing one of those .vxd files?
Now how should I know how to do that? I am only 15, I dont even have a class other than basic C++ programming at my school, so everything I learn I get help from others and basically teach myself. If you are going to as some crazy professional programming jargon you better ask some crazy professional programmer.
If you use the inp and out commands in qb, then there's a replacement. Vbio.dll, you can download it for free.:)
i wouldn't try making VXD's in VB, it will only end in tears.
VXD can't be made in VB. They can be made with C++. Use the DDK in MSDN to help you make VXD in C++.
I've never done it, but the API call CreateFile can be used to open/create files, pipes, mail slots, communication services, devices and consoles.
td.
yeah, createfile is very flexible, it might just work.
vxds are horrible - if you want to write drivers u need ASM - millions of lines of incomprehensible rubbish :)