|
|
Post by ejgtuc on Oct 12, 2019 16:32:59 GMT 1
Hola, corri mi programa de ventas en una pc a modo local dentro de vDos, funciona bien, imprime bien, pero cuando mende la factura a la impresora fiscal que esta conectada en el puerto serial COM1 se congelo, creo que el vDos atrapo el puerto COM1 y la clavo. Alquien pudo solucionar esto? si es que la tiene. Yo intente poniendo en el config.txt
LPT1 = DUMMY
COM1 = DUMMY
pero no sirvio.
Ayuda por favor.
|
|
|
|
Post by Jos on Oct 12, 2019 17:38:32 GMT 1
I assume your program is communicating bidirectionally with the fiscal printer. It expects data to be returned?
The <DOS Device>= directive is primary meant for ‘plain’ printing, no data will be returned.
You would have to add in config.txt, supposing it’s COM1 in both your program and Windows:
COM1 = "COM1":
Mind the trailing colon, that signals vDos to handle that Windows device differently.
Prior to starting vDos you have to make sure the Windows device is setup correctly. Eventually set them at the Windows command prompt with MODE <Windows device>…
Jos
|
|
|
|
Post by ejgtuc on Oct 13, 2019 0:38:27 GMT 1
Gracias Jos por contestar, lo que entendi es que debo colocar tanto en config.txt del vdos y en config.nt del windows la instruccion
COM1 = "COM1":
Es asi?.
Gracias
Eduardo
|
|
|
|
Post by Jos on Oct 13, 2019 5:37:25 GMT 1
You have to add COM1 = "COM1": only to config.txt.
Your program will probably first setup the serial COM1 port, baudrate, parity and the like. That is however ignored by vDos, so you have to find out what those settings are.
Will be somewhere in the programs configuration, its documentation or that of the printer.
Then you open a Windows command line window and check the COM1 settings: MODE COM1.
If they differ, you’ll have to set them by MODE COM1 BAUD=b PARITY=p …. Or in the device manager.
When the COM1 settings are verified/set, you start vDos.
Jos
|
|
|
|
Post by ejgtuc on Oct 14, 2019 0:16:16 GMT 1
Ok, gracias Jos.
|
|
