J
Juan Carlos
Hi,
I have a old DOS program that was working fine in Windows XP. This program
uses LPT1, LPT2 and LPT3 ports to print tickets and more.
Now we have bought new computers with Vista installed and we have a lot of
problems. I want to explain one of them.
I have configured the printers and using NET USE LPT2: \\computer\printer
/PERSISTENT:yes because I use printserver for the stand-alone printers.
it can print on all the ports with no problem. I had done a lot of test and
the printers work fine, but when the computer stay few minutes not working
when I tried to send a job to the LPT2 or LPT3, the ports was disconnected.
NET USE
LPT2 -> Disconnected
LPT3 -> Disconnected
After that, I send some data to that port, for example, ECHO Test > LPT2 and
first time appears a message with a port not ready alert, and second time it
prints fine. Now, when I test NET USE again appears:
LPT2 -> Connected
I do not understand this problem, but I think can be a new system
configuration from Vista, because everything were working in XP with the
same configuration for a long time.
Sorry for my poor english,
Best regards,
Juan Carlos
I have a old DOS program that was working fine in Windows XP. This program
uses LPT1, LPT2 and LPT3 ports to print tickets and more.
Now we have bought new computers with Vista installed and we have a lot of
problems. I want to explain one of them.
I have configured the printers and using NET USE LPT2: \\computer\printer
/PERSISTENT:yes because I use printserver for the stand-alone printers.
it can print on all the ports with no problem. I had done a lot of test and
the printers work fine, but when the computer stay few minutes not working
when I tried to send a job to the LPT2 or LPT3, the ports was disconnected.
NET USE
LPT2 -> Disconnected
LPT3 -> Disconnected
After that, I send some data to that port, for example, ECHO Test > LPT2 and
first time appears a message with a port not ready alert, and second time it
prints fine. Now, when I test NET USE again appears:
LPT2 -> Connected
I do not understand this problem, but I think can be a new system
configuration from Vista, because everything were working in XP with the
same configuration for a long time.
Sorry for my poor english,
Best regards,
Juan Carlos