thinkthin

Forum Replies Created

Viewing 15 posts - 1,621 through 1,635 (of 1,635 total)
  • Author
    Posts
  • in reply to: 3150 Boot errors on remote site #8589
    thinkthin
    Member
    • Total Post: 1649
    • Jacked into The Matrix
    • ★★★★★★

    Wow, thats a good one. Kind of a long shot but could the 3150’s at the remote site be trying to PXE boot off another server? Do you have a RIS or some other PXE server dumping out images to PC’s on that site? If this is that case try changing the boot order on the terminal with PXE last and see if it helps.

    Its just strage that you take a working device and put it there and it fails and I assume it comes back and works again?

    Let me know,

    Cheers,
    -TT

    in reply to: Modifying CE Images without PXE on the network #8588
    thinkthin
    Member
    • Total Post: 1649
    • Jacked into The Matrix
    • ★★★★★★

    Thats cool, did i answer your question regarding not having to use PXE for CE? (thats one of the good things about CE)

    in reply to: What is the WLX file for? #8587
    thinkthin
    Member
    • Total Post: 1649
    • Jacked into The Matrix
    • ★★★★★★

    I love it, you are not whining – bring it on, its good to challenge and question!

    Basically CE was the first embedded Thin Client OS so there is loads of terminals about with it. Being a low cost Microsoft OS people still like it and its good for terminal emulation and OK for RDP, but then there is drivers and ICA.

    CE started out 16 bit and its still a strange half baked OS, drivers are a pain to write and the ICA client is just not as strong as other platforms. Not just Wyse, put 2 of the same CPU hardware with CE together and they still will not be as fast as Blazer, Linux or XP. The fact that Citrix does the Win32 client followed by Linux then Java and finally CE tells me what they think of it.

    Anyways that’s my rant, don’t get me wrong. CE still does the job and loads of people use it, but ICA is not as kick ass as other operating systems.

    in reply to: What is the WLX file for? #8584
    thinkthin
    Member
    • Total Post: 1649
    • Jacked into The Matrix
    • ★★★★★★

    @SecretPants wrote:

    Hi,

    have you got a wyse linux based thin client?

    has anyone tested to see which one is faster? I’m shocked that the CE based s30’s feel slower than the 1200LE’s. but i’m getting a linux one soon to test, just wondering if anyone had set them up side by side and connected to the same app and noticed any difference?

    it’s been a long day time to go home..

    SecretPants.

    Why shocked? Blazer rocks, its the fastest ICA beast around as its built from the ground up for ICA. Its takes a high end PC to beat it.

    in reply to: What is the WLX file for? #8583
    thinkthin
    Member
    • Total Post: 1649
    • Jacked into The Matrix
    • ★★★★★★

    Hi,

    Wyse Linux will look for a WLX folder with a WLX.INI file and if its not there it will look for a WNOS/WNOS.INI.

    The syntax is similar for both, the reason for both is so if you have a mix of Blazer and Linux you can have them reading different files. There are some commands that are specific to each OS which is why you would want to keep them apart.

    in reply to: Modifying CE Images without PXE on the network #8582
    thinkthin
    Member
    • Total Post: 1649
    • Jacked into The Matrix
    • ★★★★★★

    Hi,

    OK, here is the answer…

    Yep, the the Wyse simple imager tool can reimage terminals one by one….but why bother…

    As far as PXE for CE, you don’t need it. Rapport uses TCP/IP for image upgrades so PXE plays no part, no need for IP helpers, here is how to do it:

    – Configure a terminal and then from Rapport select get device config.
    – Load a new image into Rapport by downloading it from wyse.com with the Rapport script.
    – Run the Packaging wisard to bundle a the image with the device configuration.
    – drag the new image to a device to deploy.

    Finally, yes you can have more than one PXE environment on your network, I have had ZENworks, Ghost and Rapport all playing nice after some tweaking.

    BTW – I thought the poll was a bit harsh in this case give its just a setup issue 😉

    in reply to: Rapport 4.4.0 to 4.4.1 upgrade #8580
    thinkthin
    Member
    • Total Post: 1649
    • Jacked into The Matrix
    • ★★★★★★

    Do you have the “Get device image (requiresPXE)” option still on the device menu? Or is it just that it fails to pull an image, in sheduled tasks there will be an error description which you can post.

    Also check the local rapport account is still set to never expire on the Rapport Server.

    in reply to: NetXfer help #8579
    thinkthin
    Member
    • Total Post: 1649
    • Jacked into The Matrix
    • ★★★★★★

    That’s good, whats the error? Does it appear on the client and server?

    Check the basics that the IP address of the netXfer server is 10.0.0.1 255.255.255.0 and that you rename the 3200 firmware to bootp.bin and place it in the same directory as the netxfer.exe. (And no firwall)

    If this fails post the error code, sounds like you almost have it, gald the Java download helped,

    -TT

    in reply to: NetXfer #8577
    thinkthin
    Member
    • Total Post: 1649
    • Jacked into The Matrix
    • ★★★★★★

    Hi,

    As netXfer is an old app you will need the Microsoft Java not Sun’s. Microsoft can’t provide it any more after Sun sued them however I will post MSJava under the Rapport downloads setion of this site.

    Hope this fixes it!

    Cheers,

    -TT

    in reply to: Can Windows CE handle MS ActiveSync? #8574
    thinkthin
    Member
    • Total Post: 1649
    • Jacked into The Matrix
    • ★★★★★★

    Sorry, its not in the feature matrix for the CE ICA client supplied by Citrix. You will only be able to use XPe or the new Wyse Linux 6.3 comming out soon.

    in reply to: Printing with the WT1200 #8573
    thinkthin
    Member
    • Total Post: 1649
    • Jacked into The Matrix
    • ★★★★★★

    So you say you have had it working when the name of the device was W*? Thats good if thats the case.

    If this works you should be able to use sitename or whatever. This PDF is just one example how to do this. You can use computer name or ip address. Sounds like a issue with the name syntax in the policy

    in reply to: FTP login?? #8572
    thinkthin
    Member
    • Total Post: 1649
    • Jacked into The Matrix
    • ★★★★★★

    Hi, What options are you using in the DHCP scope? If you are using the 161 and 162 tag then you will not need Rapport to control the wnos.ini file. In Rapport go to Configuration Manager-Preferances-Blazer Preferances and un tick Enable Return FTP/INI at Checkin. Rapport is trying to point the device to /ftproot/rapport/wnos and the ftp password is incorrect.

    in reply to: Update Blazer OS #8569
    thinkthin
    Member
    • Total Post: 1649
    • Jacked into The Matrix
    • ★★★★★★
    Sorry about all the HTML tags in the post, I ain’t figured out that one yet 🙂
    in reply to: Update Blazer OS #8568
    thinkthin
    Member
    • Total Post: 1649
    • Jacked into The Matrix
    • ★★★★★★

    Looks like you older firmware terminals are going to the wrong ftp directory (it said/wnos/ not /wyse/wnos).

    If you look at the system log does it say "profile not found"?

    Try this, force the directory in the DHCP scope by setting the 162 tag to /wyse or copy your WNOS directory from ftproot/wyse/wnos to ftproot/wnos.

    This should force the upgrade, hope it helps,

    -TT

    in reply to: Compaq T1010 NTe Capabilities #8567
    thinkthin
    Member
    • Total Post: 1649
    • Jacked into The Matrix
    • ★★★★★★

    Hi Shawn,

    The Compaq t1010 was OEM’ed to Compaq by Wyse, the equivalent models were the 3360SE (Windows CE) and the 8260SE (Windows NTe). If you have the Compaq NTe version you will still be download the firmware from the HP site but you will not be able to cross grade to CE as there is a Microsoft licence required.

    Your other option is to get a conversion kit from Wyse and you will be able to get a newer CE image on it. The conversion kit comes with the Microsoft licence, firmware and tools to do the job.

    You can leave the unit as NTe of course, this is the same binary files as in the NT workstation i386 folder so if your apps run on NT they should run on the terminal, you may just have to copy a few back. As long as you don’t put the device on the domain and lock it down it should run you TEC application just fine as is.

    -TT

Viewing 15 posts - 1,621 through 1,635 (of 1,635 total)