Online Talk to our
support team or
sales department.
Jun 26th, 2022, 11:31am
Welcome, Guest. Please Login or Register.
Pages: 1  Reply Reply  Notify of replies Notify of replies  Print Print
   Author  Topic: Data Corruption on Virtual Port  (Read 2581 times)
FabulaTech Forum Newbie

View Profile   Email       
Posts: 1
Data Corruption on Virtual Port
« on: Nov 5th, 2007, 7:10pm »
Quote Quote  Modify Modify

1 PC with com port going to a manual switch box which feeds two Zebra Label Printers.  
Using EasyLabel software for years which uses itís own drivers and I think talks directly to the port. (Com1).
Running XP SP2 and the latest version of Splitter.  
Looking at new Labelling software, to run on either of the printers. (but both programs need to run in parallel for 12months). New labelling software uses a Windows Printer driver so we couldnít use Com1 as it says itís locked already. So we purchased the Serial Port Splitter Kit and made a Com3 for the Windows driver.  
Independently they work fine on dedicated machines with dedicated COM ports. But the new software running via Com3 is just not consistent (labels are corrupted/upside down, missing bits) as if the data is being corrupted somehow when going via the virtual port.  
Any suggestions? The EasyLabel software refuses to use the Virtual Port so Iím thinking it talks directly to the Com Port. (says it canít access it). I canít put them on different machines as then Iíd need to buy another 2 label printers (which at $9K each is not an option)
IP Logged
FabulaTech Forum Moderator
FabulaTech Forum Senior Member

View Profile   WWW         
Gender: male Posts: 427
Re: Data Corruption on Virtual Port
« Reply #1 on: Nov 6th, 2007, 2:57am »
Quote Quote  Modify Modify

Hi David!
Thanks for interesting question.
So, how we can resolve that:
1) Your printer driver should be configured for COM1.
2) Configure the programs for using COM1 port.
3) Then using Splitter share COM1.
4) Try to use the printer.
If not successful, please try the following:
1) rename COM1 to COM2, for example using our Serial Port Mapper.
2) split COM2 to virtual COM1 and virtual COM3
3) the first application should be configured for using COM1, the second one - for using COM3.
Please let me know how it works for you. If does not work, we'll ask you for serial log files for COM ports.
« Last Edit: Nov 11th, 2007, 11:56pm by Andrew » IP Logged

Andrew Scott

Pages: 1  Reply Reply  Notify of replies Notify of replies  Print Print

« Previous topic | Next topic »