Jos, thanks for answering and for your support Unfortunately in many cases software is provided 'as is', or even own developed software may rely on 3rd party communications library, binary closed source without support, and in those cases vDos users are quite unable to workaround that situation. Not to be expected with a program, occasionally communicating with a Fiscal Printer at a mere 9,600 bps.
Interrupt driven communications are somewhat specific to dedicated communication programs, supporting high transfer rates. The one could use interrupt driven communications, while the other doesn’t. PRUF.EXE working or not, doesn’t mean the actual program would likewise.
Emulador fiscal serial serial#
Though then the serial port has to be initialized correctly outside and before vDos starts, with MODE COMx (at the Windows command prompt). If those entries are missing, the program would directly poll the serial port(s). If the vDos.log shows “Int 0B =>XXXX:XXXX” or “Int 0C =>XXXX:XXXX”, it indeed implements these routines, that are then never called in vDos. You can check if a program does so by starting vDos with the /log option (“vLog.exe” /log).
Emulador fiscal serial install#
Problematic with serial communications in vDos are programs that install and rely on their interrupt driven routines. Well, that is quite a story, probably better to communicate directly: (the “a” should be an ”o”).
0 kommentar(er)
