Hello, > I don't know any. But the problem with Windows is that cannot access the > hardware in a direct way; you'll need DLL's to do the job. And I haven't the > slightest idea how to do this. (If any one has some info about the basics of > it, please) Well, that's not true. With Win 95/98 (Me? I believe, too), you can directly access the hardware. Anyway, your access can conflict with access from the system. With NT/2000, you're right, you cannot directly access the HW. You have to write device drivers for this purpose. But this has nothing to do with DLLs! At least with NT, you have another option. There are drivers out there (DirectIO, GiveIO) with which you can access the hardware directly from your user program. IHMO, the biggest disadvantage with Windows and HW stuff is the timing: You cannot rely on any specific timing, so THIS is the problem. > This is one of the reasons I still work with DOS as long as HW is involved. Well, you're right, for this purpose, DOS is very nice. BTW: I have an old program for DOS, requiring a stand-alone machine with two serial ports and an special Y-cable, which let's you examine what is being talked to on an serial connection between two other machines. If someone's interested, I can put it somewhere for download. I used it many times for this purpose. Spiro. - This message was sent through the cbm-hackers mailing list. To unsubscribe: echo unsubscribe | mail cbm-hackers-request@dot.tml.hut.fi.
Archive generated by hypermail 2.1.1.