Bonjour,
Cette "solution" m'a mis sur le chemin de l'issue de secoure :)
En effet, j'ai consulté la documentation de DDK (driver developpemet kit) (version Win 2000 pour l'instant) au sujet des VxD (Virtual Device Drivers) et j'ai trouvé ça: (je m'excuse pour le volume !)
Intro:
"A VDD need only be written to support special-purpose hardware devices that operate under an MS-DOS application. The provided VDM has built-in support for commonly used hardware such as serial communication ports, video, mouse"
aussi: (c'est mon application)
"there are some MS-DOS applications that depend on custom hardware, such as a fax board or a 3270 communications board. Generally, these applications have a plug-in hardware board they manipulate directly through 80386/80486 I/O port IN and OUT instructions and by writing directly to memory on the board. These applications might also use DMA to transfer data to and from the board. In an MS-DOS environment, these operations allow the application or its 16-bit driver to get direct access to the hardware device"
La solution:
"To support an MS-DOS application using special hardware in the Windows NT/Windows 2000 environment, the application developer must write a 32-bit kernel-mode device driver to access the board hardware. The developer must also write a VDD to translate operations performed by the MS-DOS application into the corresponding kernel-mode device driver calls for the particular board. The paired kernel-mode device driver and VDD for the device enable the original MS-DOS application to run in the VDM layer"
Bonjour,
Cette "solution" m'a mis sur le chemin de l'issue de secoure :)
En effet, j'ai consulté la documentation de DDK (driver developpemet kit) (version Win 2000 pour l'instant) au sujet des VxD (Virtual Device Drivers) et j'ai trouvé ça: (je m'excuse pour le volume !)
Intro:
"A VDD need only be written to support special-purpose hardware devices that operate under an MS-DOS application. The provided VDM has built-in support for commonly used hardware such as serial communication ports, video, mouse"
aussi: (c'est mon application)
"there are some MS-DOS applications that depend on custom hardware, such as a fax board or a 3270 communications board. Generally, these applications have a plug-in hardware board they manipulate directly through 80386/80486 I/O port IN and OUT instructions and by writing directly to memory on the board. These applications might also use DMA to transfer data to and from the board. In an MS-DOS environment, these operations allow the application or its 16-bit driver to get direct access to the hardware device"
La solution:
"To support an MS-DOS application using special hardware in the Windows NT/Windows 2000 environment, the application developer must write a 32-bit kernel-mode device driver to access the board hardware. The developer must also write a VDD to translate operations performed by the MS-DOS application into the corresponding kernel-mode device driver calls for the particular board. The paired kernel-mode device driver and VDD for the device enable the original MS-DOS application to run in the VDM layer"