Posts by ClausSporer

    I've returned the hp OfficeJet Pro 8210. Maybe there's a error in the protocol of the printer.


    I've then successfully tested the printer hp Officejet Pro 6230. This printer supports PCL-3 Enhanced.
    So, I suppose the driver is ok.


    Thank you for your help.

    Thank you for the new driver.


    I've tested the new driver with hp OfficeJet Pro 8210, but unfortunately the error still persists.


    Now I've contacted the hp printer forum and they offered to analyse the print stream. Is there a way to "capture" the print stream to a file?

    I've tested another printer HP LaserJet Pro M203dn. This printer supports PCL-5c and PCL-6 as well. This printer is doing alright.
    Our older printer HP Deskjet 5940 is also ok.


    So, I think, the driver pcl.dll is up-to-date and compatible with the current PCL-levels PCL-5c and PCL-6.

    I've now bought and tested the printer HP OfficeJet Pro 8210. This printer supports PCL-5c and PCL-6.


    The text and grafics output seem to be ok, but the printer prints additional horizontal lines.


    I want to be sure, that I use the latest pcl.dll. My pcl.dll file is dated 2nd July 2010. Is this the latest version? If not, where can I get the latest version?

    OK, Thank you.
    Do you have in the meantime a driver for a higher PCL-level?
    Do you also provide drivers for further printer languages, e.g. GDI, PS, SPL?
    Do you have a list of tested or compatible printers?

    ; Copyright (c) Palm Inc. All rights reserved.
    ;
    ; Treo Modem Link Setup
    ; =================================================
    ;




    [Version]
    LayoutFile=layout.inf
    Signature=$CHICAGO$
    Class=Modem
    Provider=%PROVIDER%
    CLASSGUID={4D36E96D-E325-11CE-BFC1-08002BE10318}
    DriverVer=12/18/2006,2.1.0000.0
    CatalogFile=PalmTreoModem.cat


    [DestinationDirs]
    UsbModemFiles=12


    [Manufacturer]
    %MANUFACTURER_PALM%=Palm_DeviceList,NTx86,NTamd64


    [ControlFlags]
    ExcludeFromSelect=*


    [Palm_DeviceList.NTx86]
    %PALM_DEVICES_0001% = Palm_DeviceList.Install, USB\VID_0BB4&PID_00CF ; <- 700w
    %PALM_DEVICES_0002% = Palm_DeviceList.Install, USB\VID_045E&PID_0079 ; <- 750w
    %PALM_RESERVED_DEVICES_0100% = Palm_DeviceList.Install, USB\VID_0830&&PID_0100
    %PALM_RESERVED_DEVICES_0101% = Palm_DeviceList.Install, USB\VID_0830&&PID_0101
    %PALM_RESERVED_DEVICES_0102% = Palm_DeviceList.Install, USB\VID_0830&&PID_0102
    %PALM_RESERVED_DEVICES_0103% = Palm_DeviceList.Install, USB\VID_0830&&PID_0103
    %PALM_RESERVED_DEVICES_0104% = Palm_DeviceList.Install, USB\VID_0830&&PID_0104
    %PALM_RESERVED_DEVICES_0105% = Palm_DeviceList.Install, USB\VID_0830&&PID_0105
    %PALM_RESERVED_DEVICES_0106% = Palm_DeviceList.Install, USB\VID_0830&&PID_0106
    %PALM_RESERVED_DEVICES_0107% = Palm_DeviceList.Install, USB\VID_0830&&PID_0107
    %PALM_RESERVED_DEVICES_0108% = Palm_DeviceList.Install, USB\VID_0830&&PID_0108
    %PALM_RESERVED_DEVICES_0109% = Palm_DeviceList.Install, USB\VID_0830&&PID_0109
    %PALM_RESERVED_DEVICES_0110% = Palm_DeviceList.Install, USB\VID_0830&&PID_0110


    [Palm_DeviceList.NTamd64]
    %PALM_DEVICES_0001% = Palm_DeviceList.Install, USB\VID_0BB4&PID_00CF ; <- 700w
    %PALM_DEVICES_0002% = Palm_DeviceList.Install, USB\VID_045E&PID_0079 ; <- 750w
    %PALM_RESERVED_DEVICES_0100% = Palm_DeviceList.Install, USB\VID_0830&&PID_0100
    %PALM_RESERVED_DEVICES_0101% = Palm_DeviceList.Install, USB\VID_0830&&PID_0101
    %PALM_RESERVED_DEVICES_0102% = Palm_DeviceList.Install, USB\VID_0830&&PID_0102
    %PALM_RESERVED_DEVICES_0103% = Palm_DeviceList.Install, USB\VID_0830&&PID_0103
    %PALM_RESERVED_DEVICES_0104% = Palm_DeviceList.Install, USB\VID_0830&&PID_0104
    %PALM_RESERVED_DEVICES_0105% = Palm_DeviceList.Install, USB\VID_0830&&PID_0105
    %PALM_RESERVED_DEVICES_0106% = Palm_DeviceList.Install, USB\VID_0830&&PID_0106
    %PALM_RESERVED_DEVICES_0107% = Palm_DeviceList.Install, USB\VID_0830&&PID_0107
    %PALM_RESERVED_DEVICES_0108% = Palm_DeviceList.Install, USB\VID_0830&&PID_0108
    %PALM_RESERVED_DEVICES_0109% = Palm_DeviceList.Install, USB\VID_0830&&PID_0109
    %PALM_RESERVED_DEVICES_0110% = Palm_DeviceList.Install, USB\VID_0830&&PID_0110



    [Palm_DeviceList]
    %PALM_DEVICES_0001% = Palm_DeviceList.Install, USB\VID_0BB4&PID_00CF ; <- 700w
    %PALM_DEVICES_0002% = Palm_DeviceList.Install, USB\VID_045E&PID_0079 ; <- 750w
    %PALM_RESERVED_DEVICES_0100% = Palm_DeviceList.Install, USB\VID_0830&&PID_0100
    %PALM_RESERVED_DEVICES_0101% = Palm_DeviceList.Install, USB\VID_0830&&PID_0101
    %PALM_RESERVED_DEVICES_0102% = Palm_DeviceList.Install, USB\VID_0830&&PID_0102
    %PALM_RESERVED_DEVICES_0103% = Palm_DeviceList.Install, USB\VID_0830&&PID_0103
    %PALM_RESERVED_DEVICES_0104% = Palm_DeviceList.Install, USB\VID_0830&&PID_0104
    %PALM_RESERVED_DEVICES_0105% = Palm_DeviceList.Install, USB\VID_0830&&PID_0105
    %PALM_RESERVED_DEVICES_0106% = Palm_DeviceList.Install, USB\VID_0830&&PID_0106
    %PALM_RESERVED_DEVICES_0107% = Palm_DeviceList.Install, USB\VID_0830&&PID_0107
    %PALM_RESERVED_DEVICES_0108% = Palm_DeviceList.Install, USB\VID_0830&&PID_0108
    %PALM_RESERVED_DEVICES_0109% = Palm_DeviceList.Install, USB\VID_0830&&PID_0109
    %PALM_RESERVED_DEVICES_0110% = Palm_DeviceList.Install, USB\VID_0830&&PID_0110



    [Palm_DeviceList.Install.NT]
    include=mdmcpq.inf
    CopyFiles = FakeModemCopyFileSection
    AddReg = All, MfgAddReg, Palm_DeviceList.Install.AddReg, EXTERNAL


    [Palm_DeviceList.Install.NT.Services]
    include=mdmcpq.inf
    AddService=usbser, 0x00000000, LowerFilter_Service_Inst


    [Palm_DeviceList.Install.NT.HW]
    include-mdmcpq.inf
    AddReg=LowerFilterAddReg



    ;
    ; Explicitly states the usbser.sys should not be taken from the CD/Disk
    ;
    [SourceDisksNames]
    ;
    ; no media
    ;


    [SourceDisksFiles]
    ;
    ; no files
    ;



    [All]
    HKR,,FriendlyDriver,0,Unimodem.vxd
    HKR,,DevLoader,0,*vcomm
    HKR,,ConfigDialog,0,modemui.dll
    HKR,,EnumPropPages,0,modemui.dll,EnumPropPages
    HKR,,PortSubClass,1,02
    HKR, Init, 1,, "AT&FE0&D2&C1V1S0=0<cr>"
    HKR, Responses, "<cr><lf>OK<cr><lf>", 1, 00, 00, 00,00,00,00, 00,00,00,00
    HKR, Responses, "<cr><lf>ERROR<cr><lf>", 1, 03, 00, 00,00,00,00, 00,00,00,00


    [Palm_DeviceList.Install.AddReg]
    HKR,, Properties, 1, 00,00,00,00, 00,00,00,00, 00,00,00,00, 00,00,00,00, 00,00,00,00, 00,00,00,00, 00,C2,01,00, 00,00,00,00
    HKLM,SYSTEM\CurrentControlSet\Services\Tcpip\Parameters,"TcpWindowSize",0x00010001,0xFFFE



    [EXTERNAL]
    HKR,, DeviceType, 1, 01


    [MfgAddReg]
    HKR,, InactivityScale, 1, 3c,00,00,00
    HKR, Init, 1,, "AT<cr>"
    HKR, Init, 2,, "AT&F<cr>"
    HKR, Init, 3,, "ATE0V1&D2&C1S0=0<cr>"
    HKR, Monitor, 1,, "ATS0=0<cr>"
    HKR, Monitor, 2,, "None"
    HKR, Answer, 1,, "ATA<cr>"
    HKR, Hangup, 1,, "ATH<cr>"
    HKR,, Reset,, "ATZ<cr>"
    HKR, Settings, Prefix,, "AT"
    HKR, Settings, Terminator,, "<cr>"
    HKR, Settings, DialPrefix,, "D"
    HKR, Settings, DialSuffix,0, ";"
    HKR, Settings, Pulse,, "P"
    HKR, Settings, Tone,, "T"


    HKR, Responses, "0<cr><lf>", 1, 00, 00, 00,00,00,00, 00,00,00,00 ; OK
    HKR, Responses, "2<cr><lf>", 1, 08, 00, 00,00,00,00, 00,00,00,00 ; RING
    HKR, Responses, "3<cr><lf>", 1, 04, 00, 00,00,00,00, 00,00,00,00 ; NO CARRIER
    HKR, Responses, "4<cr><lf>", 1, 03, 00, 00,00,00,00, 00,00,00,00 ; ERROR
    HKR, Responses, "6<cr><lf>", 1, 05, 00, 00,00,00,00, 00,00,00,00 ; NO DIALTONE
    HKR, Responses, "7<cr><lf>", 1, 06, 00, 00,00,00,00, 00,00,00,00 ; BUSY
    HKR, Responses, "8<cr><lf>", 1, 07, 00, 00,00,00,00, 00,00,00,00 ; NO ANSWER
    HKR, Responses, "<cr>", 1, 01, 00, 00,00,00,00, 00,00,00,00
    HKR, Responses, "<lf>", 1, 01, 00, 00,00,00,00, 00,00,00,00
    HKR, Responses, "<cr><lf>OK<cr><lf>", 1, 00, 00, 00,00,00,00, 00,00,00,00
    HKR, Responses, "<cr><lf>RING<cr><lf>", 1, 08, 00, 00,00,00,00, 00,00,00,00
    HKR, Responses, "<cr><lf>NO CARRIER<cr><lf>", 1, 04, 00, 00,00,00,00, 00,00,00,00
    HKR, Responses, "<cr><lf>ERROR<cr><lf>", 1, 03, 00, 00,00,00,00, 00,00,00,00
    HKR, Responses, "<cr><lf>NO DIALTONE<cr><lf>", 1, 05, 00, 00,00,00,00, 00,00,00,00
    HKR, Responses, "<cr><lf>BUSY<cr><lf>", 1, 06, 00, 00,00,00,00, 00,00,00,00
    HKR, Responses, "<cr><lf>NO ANSWER<cr><lf>", 1, 07, 00, 00,00,00,00, 00,00,00,00
    HKR, Responses, "<cr><lf>CONNECT<cr><lf>", 1, 02, 00, 00,00,00,00, 00,00,00,00



    [Strings]



    ; Non-localized section
    PROVIDER = "Palm"


    MANUFACTURER_PALM = "Palm"
    PALM_DEVICES_0001 = "Palm Treo Modem"
    PALM_DEVICES_0002 = "Palm Treo Modem"
    PALM_RESERVED_DEVICES_0100 = "Palm Treo Modem"
    PALM_RESERVED_DEVICES_0101 = "Palm Treo Modem"
    PALM_RESERVED_DEVICES_0102 = "Palm Treo Modem"
    PALM_RESERVED_DEVICES_0103 = "Palm Treo Modem"
    PALM_RESERVED_DEVICES_0104 = "Palm Treo Modem"
    PALM_RESERVED_DEVICES_0105 = "Palm Treo Modem"
    PALM_RESERVED_DEVICES_0106 = "Palm Treo Modem"
    PALM_RESERVED_DEVICES_0107 = "Palm Treo Modem"
    PALM_RESERVED_DEVICES_0108 = "Palm Treo Modem"
    PALM_RESERVED_DEVICES_0109 = "Palm Treo Modem"
    PALM_RESERVED_DEVICES_0110 = "Palm Treo Modem"
    USBFilterString = "USB Modem Driver"


    ;
    ; add other strings here
    ;

    We have never used Palm Treo Modem before.


    I've compared the VendorID and ProductID between PicoCOMA5 registry (HKEY_LM\Drivers\USB\FunctionDrivers\FSUSBSER_Class) and the .inf file of usbser and Palm Treo Modem:

    PicoCOMA5 registry usbser .inf Treo Modem .inf
    VID 0x045E (1118) 0x045E (1118) 0x045E (1118)
    PID 0x0079 (121) 0x0079 (121) 0x0079 (121)


    VID and PID are all the same. That's maybe why Palm Treo Modem is installed automatically. Our company doesn't have a VID. Could we take the VID and PID of F&S? Which values?


    Yes, usbser.sys and usbser.inf are available. But if I connect a PicoCOMA5 to a PC for the first time, then automatically Palm Treo Modem is installed (when the PC is connected to internet).

    Hello,


    we use the Virtual COM for several purposes on PicoCOMA5 (WCE 6.0 R3) and it's working fine.
    But I have the problem, that Windows automatically installs a wrong driver (called "Palm Treo Modem") when the PicoCOMA5 is connected for the first time to a PC.
    Then I have to unistall the "Palm Treo Modem" and manually install the correct driver (usbser). This is ok for us, but not for our customers.
    Is there any solution? Could I adapt the registry of PicoCOMA5 to prevent installing "Palm Treo Modem"?

    At the moment I use VS 2008 to develop for WCE 6.0 R3 on a PicoCOMA5 device. Now I would like to switch to the new VS 2013.
    I found that VS 2013 is compatible with WEC 7 and WEC 2013, but nothing about WCE 6. Is WCE 6 not possible?

    Thank you for your answer. Now the printer is working (I had an older pcl.dll, that hadn't worked correctly).
    Do you know the PCL-compatibility of this pcl.dll? Is it PCL-3?

    The communication via Tera Term works fine and stable (as I've posted on 20th of March).


    But we can't establish the connection with further programs, e.g. Atmel Flip or Flachmann & Heggelbacher Docklight. As these are not our programs, I don't have sources and can't modify the COM detection.


    When I use DCUTerm, I see the errors 121 and 31 (see my post 7th of March). Thus I guess, maybe it could be the same reason.


    I suppose, that it's an error in the driver. Finding a solution for that is very urgent for us.

    Hello,
    I want to establish a virtual COM connection to PicoCOMA5 (Win CE6). I use the latest VirtualCOMPort.zip that has been posted here (1st march 2013).
    The driver on the host (Win7 - 32 bit) seems to work correctly, as it is shown in the device manager. I've adapted the settings in the registry according the description.
    But when I want to connect to the device, I get the same error as Festus (posted on 4th may 2011): error 121 "The semaphore timeout period has expired.". Sometimes I retrieve error 31 "A device attached to the system is not functioning.".
    What could I do?