Flip

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 18 total)
  • Author
    Posts
  • in reply to: Upgrade firmware via FTP #17111
    Flip
    Member
    • Total Post: 27
    • Regular Joe
    • ★★

    It seems even though I did not check “Use ini files for Configuration” in the System preferences, it kept on taking /wyse as the root path, even though I entered a different path in the network settings.

    in reply to: Upgrade firmware via FTP #17110
    Flip
    Member
    • Total Post: 27
    • Regular Joe
    • ★★

    @ConfGen wrote:

    Are you using DHCP option tag like OT161 or 162?

    CG

    No we do not, what do those tags do anyway ?

    The thing is we wanted to upgrade from another server, one that is not our DHCP server.

    It seems I had to change the following lines in our ini file to change the root path, the changes I made in the control panel were never used :

    FirmwareRootPath=/disk1/wyseFTP/wyse

    in reply to: PowerTerm Script Language Reference #13703
    Flip
    Member
    • Total Post: 27
    • Regular Joe
    • ★★

    @ConfGen wrote:

    You can find it here

    http://www.ericom.com/doc/TechnicalReferences/PTPSLReference.pdf

    BTW, Google is your friend.

    CG

    Thanks very much.

    And no, Googly is not my friend, it’s my best friend, but this time I was not clear talking to my best friend it seems 😉

    in reply to: Configuring TEC session #10179
    Flip
    Member
    • Total Post: 27
    • Regular Joe
    • ★★

    I have found the problem, the problem occured when we transfered the files to a windows ftp server, we are now using a linux ftp server and this works without any problems.

    Something with line feeds wich are stored in a different way in linux.

    Thanks to Wyse Germany Support !

    [edit]Apparently using the bin command in ftp would resolve this problem, to bad Wyse did not mention this in their technote, would have saved me lots of time 👿 [/edit]

    in reply to: Configuring TEC session #10159
    Flip
    Member
    • Total Post: 27
    • Regular Joe
    • ★★

    @ConfGen wrote:

    So, you created a TEC session locally on the unit.
    You started it once and did all needed configurations.
    You closed the session and answered “yes” to save the config to eg. /tmp/qterm/sessie
    You open a console and cd’ed to that folder
    You opened a FTP connection
    You switched to binary mode in FTP transfer
    You copied all 4 files to wyse/wlx/
    You added the needed parameters to your wlx.ini file

    ???

    That is correct, the icon appears on the desktop for the connection but when I start it the only thing retained is het host ip-address, I need to tell it, it concerns a 5250 session and everything else, a change we added to reprogram a key with another function is configured correctly from the .ptk file

    in reply to: Configuring TEC session #10156
    Flip
    Member
    • Total Post: 27
    • Regular Joe
    • ★★

    @ConfGen wrote:

    Hi Flip,

    your sessie.ptc file looks perfect to me.
    Do you really have copied all 4 files to wyse/wlx/i5?
    Try copying all files to wyse/wlx and adjust the path in your ini to filepath=wyse/wlx
    There is no need for “” in each line beside you are using spaces in the names.

    ConfGen

    Hi,

    yes I copied all 4 files.

    I tried your suggestion and changed the wlx.ini, but it still gives me the connect screen when I start the session.

    in reply to: Configuring TEC session #10152
    Flip
    Member
    • Total Post: 27
    • Regular Joe
    • ★★

    I finally succeded in installing the utils package.

    I followed the procedure in copying the files to my ftp server.

    But when I start the session the only thing it retains is the host ip address, even the fact that it is a tn5250 connection is not retained, I get a configuration screen to enter all the selections.

    This is part of my wlx.ini :

    # i5 sessie
    connect=TEC
    description=”i5″
    filename=”sessie”
    filepath=”wyse/wlx/i5″

    and this is the contents of the sessie.ptc file :

    []
    comm-type = tn5250
    host-name = 192.168.1.1
    device-name =
    message-queue = QSYSOPR
    message-library = *LIBL
    user-name =
    password = Zy
    security-type = unsecured
    terminal-type = 5250 display
    terminal-model = 3477-fc
    login-command-file =
    terminal-setup-file =

    in reply to: Configuring TEC session #10006
    Flip
    Member
    • Total Post: 27
    • Regular Joe
    • ★★

    For those interested, you can also find the pak here :

    ftp://support-emea.wyse.com/public/Linuxv6/addons/UTILS-3.0.7.pak

    Thanks to Wyse support !

    in reply to: Configuring TEC session #10004
    Flip
    Member
    • Total Post: 27
    • Regular Joe
    • ★★

    @ConfGen wrote:

    sorry, one technicalhelp too much

    http://www.technicalhelp.de/products/5000/UTILS-3.0.7.pak

    Thanks for that !

    The ConfGen tool on that site looks cool !

    Is there a link to that on this site ? Should be I think !

    Thanks again.

    in reply to: Configuring TEC session #10001
    Flip
    Member
    • Total Post: 27
    • Regular Joe
    • ★★

    @ConfGen wrote:

    you can download the UTILS pak here
    http://www.technicalhelp.de/technicalhelp/prod … -3.0.7.pak

    Sorry, but this url does not work 😥

    in reply to: Configuring TEC session #9988
    Flip
    Member
    • Total Post: 27
    • Regular Joe
    • ★★

    @gerjan wrote:

    @Flip wrote:

    Where can I find more information on what parameters I can put in a .ptc file to configure a TEC session to our AS/400 ?

    I use TEC sucessfully. The only pity is that you aren’t possible to save a session localy (with specific configuration settings). I’ve created a session with TEC. Saved it in de /tmp of the terminal.

    Then i’ve uploaded the saved data ( install UTILS pack or SSH) to the ftp server (you only need the .pts and .pts file) and in the added connection I point to the given filename (without the extension e.g. SCOADM5.pts becomes SCOADM5.

    Kind regards,

    Gerjan

    Where can I find the UTILS pack ?
    Can’t seem to find it here http://www.wyse.com/serviceandsupport/support/dlOraFW.asp?which=58&model=S50(Wyse%20Linux)

    Or could you tell me how to use SSH ?

    in reply to: Adding printer through wlx.ini #9610
    Flip
    Member
    • Total Post: 27
    • Regular Joe
    • ★★

    @thinkthin wrote:

    Cool, just use Generic Text for your TEC.

    For local FireFox add the GhostScript.pak and select PCL as the print driver.

    🙂

    It works fine when I add the printer manually, but I would like to add the printer through .ini files !

    in reply to: Adding printer through wlx.ini #9607
    Flip
    Member
    • Total Post: 27
    • Regular Joe
    • ★★

    We are using the printer mainly to print screens from out TEC sessions, if I add the printer manually I add the printer as Generic/Text Only, I do not use a winows print driver.

    in reply to: Adding printer through wlx.ini #9601
    Flip
    Member
    • Total Post: 27
    • Regular Joe
    • ★★

    I would like to use the default value :

    Defines a remote Unix LPD printer. Printer
    specifies the name of the printer and is required. If
    the ModelID is not specified, the default
    Generic/Text Only is used. If Enabled is not
    specified, the default is to enable the printer
    (Default = yes). If EnableLPD is not specified, the
    LPD service will not be enabled (Default = yes).
    NOTE: The parameters must be specified in the
    order shown. Be sure not to leave spaces in
    unnecessary places as they may produce
    problems to users.

    Do I need to mention Generic/Text Only as ModelID ?

    in reply to: RDP session with server list #9589
    Flip
    Member
    • Total Post: 27
    • Regular Joe
    • ★★

    Could I do some reverse engineering ? 😛
    Create the icon manually and read the settings somewhere ?

Viewing 15 posts - 1 through 15 (of 18 total)