Did you power cycle the scanner?
I was wondering the same thing.Did you power cycle the scanner?
The posts all indicated it wouldn't be a connection because it happens on the wired and wireless, based on the info you provided.You are saying it may be a connection? Odd that it would be both wired and wireless tho.
Just as I suspected. Did you power cycle the scanner? Even the GLG protocol command is not right.To answer a question, the test screen shows ASC on the characters not displaying. For instance, ASC(255) and ASC(239) for the lower case o in Columbus among others as below.
MDL,BCDu36HP
STS,0000100, F0:***3****** 11:43 ASC(198)ASC(199)ASC(172)kASC(2)ASC(2)ASC(2)bbASC(2)ASC(154)ASC(193):-123------ May31 DAT ,,CASC(255)lumbus LAW ,,CASC(255)lumbus Police ,,Sheriff East Dispatch ,, Law DASC(233)spatcASC(232) ,,TGID:v1033 ASC(15)ASC(16)ASC(14)ASC(11) [F3]GASC(239)lumbus LAW<,1,1,0,0,,,u,_FF,3
GLG,,,<,,,,,<,,
VOL,7
SQL,2
I know this was for ThomasMcKean. But I had done Windows Update today. ProScan wouldn't work after the update. When I logged into RR, I noticed this instruction. Realizing I had taken a lightspeed trip into DUH!! Once I power-cycled my scanner, ProScan worked again!!!!Did you power cycle the scanner?