V10L Trapt error

  • This topic is empty.
Viewing 15 posts - 1 through 15 (of 15 total)
  • Author
    Posts
  • #1395
    AvatarHellslayeR
    Member
    • Total Post: 13
    • Regular Joe
    • ★★

    Hello.

    I’ve just flashed two V10L with the new firmwareversion 6.2.0B08.

    This worked great but suddenly the wyse V10L clients started giving me this error:

    Trap: Protection fault, EIP = 0x1663f2

    I never got that error before the firmware upgrade.
    I’m gettingt the error after I’ve typed in username/password so they manage to connect to the TS, but after that i get thrown out to the wyse desktop so to speak and it displays this error.

    Any idea what’s wrong?

    #13643
    ConfGenConfGen
    Keymaster
    • Total Post: 11110
    • Jedi Master
    • ★★★★★★★

    Download this and put it in your wnos folder. Reboot and test again.

    CG

    #13644
    ConfGenConfGen
    Keymaster
    • Total Post: 11110
    • Jedi Master
    • ★★★★★★★

    BTW, this file is called RCA_boot. That’s all, no extension, no .txt

    CG

    #13647
    AvatarHellslayeR
    Member
    • Total Post: 13
    • Regular Joe
    • ★★

    Thanks for the tips, but it didnt make any difference I’m affraid.

    Did as you said: DL and put the file in the wnos folder.
    Startet the thin client again, but got the same message.

    #13648
    ConfGenConfGen
    Keymaster
    • Total Post: 11110
    • Jedi Master
    • ★★★★★★★

    Did you see an upgrade message?
    If not, try to downgrade once and then put RCA_wnos and RCA_boot in your wnos folder.

    CG

    #13649
    AvatarHellslayeR
    Member
    • Total Post: 13
    • Regular Joe
    • ★★

    No I did not see any upgrade message indeed.

    I’m not a 100% sure what to do if I’m going to downgrade.. All I know is how to return the thin client to factory defaults but that will not bring it back to it’s original FW version.

    Must the wnos file be called RCA_wnos for this to work? Atm it’s just called wnos.ini?

    #13650
    ConfGenConfGen
    Keymaster
    • Total Post: 11110
    • Jedi Master
    • ★★★★★★★

    The firmare file for S10 is called RCA_wnos, the bootloader is called RCA_boot and the configuration file is called wnos.ini – always and ever!
    Renaming one will not work.

    And if I would read your message correct, I would have uploaded the VL10_boot for your V10L instead of S10. Sorry for that.
    Download it here

    CG

    #13651
    AvatarHellslayeR
    Member
    • Total Post: 13
    • Regular Joe
    • ★★

    Well had I been more experienced in this I might have seen it myself 🙂

    Your link is atm broken, but I’m sure that will be fixed 😀

    The Norwegian seller that sold us the equiptment is going to have a talk with the UK Wyse team tomorrow and get back to me on wendsday about this case, but if this solves the problem I would be very pleased (So would all the schools in my district that is going to use the system) 🙂

    #13652
    ConfGenConfGen
    Keymaster
    • Total Post: 11110
    • Jedi Master
    • ★★★★★★★
    #13655
    AvatarHellslayeR
    Member
    • Total Post: 13
    • Regular Joe
    • ★★

    Started testing again now with the new file but sadly still no difference.

    I still can’t see any ugrade message tho and since you asked about that in a previous post I asume there’s supposed to be one?

    #13656
    ConfGenConfGen
    Keymaster
    • Total Post: 11110
    • Jedi Master
    • ★★★★★★★

    Yes, there should be an upgrade screen. But only if the VL10_boot is newer. Maybe you are already running on this level.
    Only way to check is to downgrade to an older firmware and then upgrade again by putting 6.2.08 VL10_wnos and VL10_boot in the wnos folder again.
    I have seen some Trap errors in the past and not all could be fixed by upgrading the bootloader. Maybe you are one of those that are not working.
    Can you easily reproduce the Trap error?
    If yes, then you should enable the inbuild Trace option by adding this line to your wnos.ini:
    Privilege=high EnableTrace=yes
    Create a folder “trace” beneath your wnos folder and give everyone write access. Reboot the unit and right click the desktop. Now select Trace.
    Open the ICA or RDP session and reproduce the Trap error. Stop the trace again and send the trace.ica or trace.rdp file from the trace folder to Wyse support.

    CG

    #13658
    AvatarHellslayeR
    Member
    • Total Post: 13
    • Regular Joe
    • ★★

    How would I go about if I wanted to downgrade?

    I see that you in this post http://www.freewysemonkeys.com/modules.php?name=Forums&file=viewtopic&t=944 state there is no way to force a downgrade?

    The trapt error I can easily reproduce by logging on x number of times indeed.
    Will enable the Trace option now and get working on it.

    *Update: Put the lines in my wnos.ini file and made the folder but the option to trace dosent show when I right click my desktop.

    **Update two: And all of the sudden after a reboot the trace option was there. Must have been a typo from my side.

    ***Update: Getting the error message when I turn on trace -> Capture: “Cannot write to [ftp:/wnos/trace/trace.rdp]”

    I’ve made the trace folder within the wnos folder and given everyone write access.

    #13659
    AvatarHellslayeR
    Member
    • Total Post: 13
    • Regular Joe
    • ★★

    Still struggeling with getting this logg to work.

    I’ve tried moving the wnos folder one step up since it seems to be looking there based on the error message, but that gave no result.

    I’ve trippled checked the user rights on the folder I made and they are correct.
    The error messag appear at the time I try to press the “connect” button in the connect manager.

    #13660
    ConfGenConfGen
    Keymaster
    • Total Post: 11110
    • Jedi Master
    • ★★★★★★★

    Recheck wether
    – the folder is really called “trace”
    – the folder has read/write access
    – FTP allows anonymous write connections

    #13662
    AvatarHellslayeR
    Member
    • Total Post: 13
    • Regular Joe
    • ★★

    Your 3’rd guess was right. No write access for anonymous logins.

    Logging on as best I can now to reporduce the error.

Viewing 15 posts - 1 through 15 (of 15 total)
  • You must be logged in to reply to this topic.