This being an external serial device, communicating via modbus, I don't think I wil need any low-level access. Thanks for the advice Tom.
------------------
Announcement
Collapse
No announcement yet.
Communications driver toolkit?
Collapse
X
-
Guest replied
-
A DLL is far simpler to design, build, debug, and make portable between platforms. A device driver may be required if you need to do low-level hardware access, or if you need to make the hardware available to Windows as a device. The two are rarely interchangeable. The choice should be fairly clear, depending on your requirements.
------------------
Tom Hanlin
PowerBASIC Staff
Leave a comment:
-
Guest repliedThanks to Scott and Tom for your responses. At this point I'm not sure whether to develop the "driver" as a DLL or as an actual device driver.
Does anyone have any input as to the issues surrounding either choice?
Thanks...
------------------
Leave a comment:
-
If you're looking to write an actual Windows device driver, this can't be done with PowerBASIC. You'd probably be looking at Microsoft C or assembly language in conjunction with the MS DDK (Device Driver toolKit).
------------------
Tom Hanlin
PowerBASIC Staff
Leave a comment:
-
Leave a comment:
-
Communications driver toolkit?
Does anyone know of a good communications toolkit that can be used to build a serial communications driver with PB/DLL?
------------------
Tags: None
Leave a comment: