Wyse S10 .l2d Firmware

Viewing 14 posts - 1 through 14 (of 14 total)
  • Author
    Posts
  • #49376
    cwager990
    Participant
    • Total Post: 12
    • Regular Joe
    • ★★

    I have a Wyse S10, Part No: SO2110-02L

    Running: 6.5.0_47.

    I have a problem and need to reimage this unit,

    I don’t have the correct l2d file for this unit and dell were less than helpful on the matter.

    If anyone can help I would be most greatful.

    Regards

     

     

    #49380
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    I only have 6.2_08 as .i2d

    CG

    #49381
    cwager990
    Participant
    • Total Post: 12
    • Regular Joe
    • ★★

    That would be better than nothing will my unit accept that ?

    Could you link it me to try ?

    Thanks

    #49382
    cwager990
    Participant
    • Total Post: 12
    • Regular Joe
    • ★★

    If that will work then. To at least reflash and get the unit working that would be a start.

    I would then need to find RCA_wnos updates to upgrade to a later version which is a whole other issue.

    #49383
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    I have uploaded it to the Download section

    CG

    #49385
    cwager990
    Participant
    • Total Post: 12
    • Regular Joe
    • ★★

    Thank you I will try that in a little while.

    Do you have any idea where I can get later RCA_wnos files from I saw one for 7 on you downloads page but that won’t fit in the flash on the S10 I tried it on of my other terminals and got an error to that effect

    Thanks

    #49386
    cwager990
    Participant
    • Total Post: 12
    • Regular Joe
    • ★★

    I am getting an error saying incompatiable firmware come up at the bottom of WSI, What am I meant to type in the

    Image Version

    Flash Size

    Description

    is that what is causing the error or it something else?

    #49387
    cwager990
    Participant
    • Total Post: 12
    • Regular Joe
    • ★★

    This is what I get in the log

    Evaluating: ‘sym/NO’ to ‘sym/YES’
    Evaluating: ‘sym/YES’ to ‘sym/YES’
    Evaluating: ‘sym/YES’ to ‘sym/YES’
    Evaluating: ‘sym/NO’ to ‘sym/YES’
    Evaluating: ‘ftp//anonymous:[email protected]/Rapport/Tools/sa/1S10/push.k’ to ‘stream/sec/test’
    Evaluating: ‘sym/YES’ to ‘sym/NO’
    Evaluating: ‘sym/NO’ to ‘sym/YES’
    Evaluating: ‘sym/NO’ to ‘sym/YES’
    Evaluating: ‘sym/UNKNOWN’ to ‘sym/UNKNOWN’
    Evaluating: ‘sym/YES’ to ‘sym/YES’
    Evaluating: ‘sym/YES’ to ‘sym/YES’
    Evaluating: ‘sym/MEDIA_AND_ARCHIVE_SIZE_CHECK’ to ‘sym/NOTFOUND’
    Evaluating: ‘sym/YES’ to ‘sym/YES’

    #49389
    cwager990
    Participant
    • Total Post: 12
    • Regular Joe
    • ★★

    Do you have any idea shat the issue is? Consequently is there anyway for me to pull an image from a. Fully working S10 to push to another ?

     

    Thanks

    #49397
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    I have uploaded a second file called S12 I2D Image.

    Try that one.

    CG

    #49413
    cwager990
    Participant
    • Total Post: 12
    • Regular Joe
    • ★★

    Do you have any idea how to fix this ?

    Why I’m here the reason I’m doing this is because I stupidly locked down the terminal without enabling the g-key.

    And forgot to put the ftp:/ before the up in the file server field

    it simply has: 172..16.4.11

    Which since it does not have a protocol is not going to work

    so I now have the device locked down and no way to get it to read a wnos.conf

    im starting to think this will be brick forever now.

    #49414
    cwager990
    Participant
    • Total Post: 12
    • Regular Joe
    • ★★

    Resolved: This issue is now resolved, I no longer need to flash the unit.

    The first problem was due to me having enabled lock down with permissions set to none. As I did this in ye oldie text editor and not with the ConfGen tool I got no handy warning to tell me what the consequence would be.

    This was further compounded by me putting the wrong string in the aforementioned file for the file server.

    In desperation I called a guy from my old college that managed a couple of dozen terminals and asked him what I could do, he told me that if I used the DHCP option  tags for 161, and 162 (if necessary. The WTOS terminal will ignore what it has in its stored wnos.ini and use the information from DHCP.

    I have no idea why I didn’t think of this, I had assumed that the config file would take president especially when locked down. Thank you Wyse for not thinking like I do! if I had designed it locked down would have meant “Locked Down”.

    So with that set it was a simple matter of removing the command for lock down and changing the privilege setting to high.

    Regarding the issue with Firmware Version 7.X

    Dell sent over the firmware files for 7.1_207, in response to my request for firmware, along with a note to the effect of there is no such thing as an .i2d file for that version. They were going off my serial number.

    This makes me wonder if the S10 units I have are not .i2d flash-able and cannot do push/pull which might explain why I was getting incompatible firmware with WSI.

    What do you think about this Confgen ?

    The firmware they sent me consisted of the a RCA_boot and RCA_wnos, which also explained my other problem.

    When I tried to put the RCA_wnos on my tftp for 7.X it refused to install saying compressed file was too big but if you clicked okay it would boot it from network.

    The files I was sent gets around this by installing a mini-rom that automatically does the network boot for you.

    Thank you for your advice Confgen, I would very much like you thoughts and feedback on the above.

    Thanks Chris

     

    #108611
    scowley
    Participant
    • Total Post: 2
    • Newbie

    Hi and firstly, apologies for reviving an old thread but the scenario above is the closest I can find on here to my situation. I have a Wyse S10 and it was on sys version 7.1_207 however I borked it and I have no idea how. I hope you can help, so here goes:

    1. Sys version now showing as 7.0.0_34

    2. BIOS is v1.14

    3. It is in LockDown

    4. I have Option 161 configured on my DHCP server and has been like this for years and working. IP is that of the working FTP server where wnos.ini and RCA_wnos and RCA_bios files are held. No username or password required for FTP access.

    5. I’ve tried several of the USB imaging tools from the downloads (starting at 1.10) and used the 2x .i2d files mentioned in this thread. The latest one gives a ‘no xml’ error and quits for me.

    6. USB boot does work (set in the bios as 1st) but all attempts display a message like “no operating system was found…please remove device…” or similar.

    7. Then it retries to boot off PXE. It gets a DHCP IP and so should be reading option 161 but nothing happens. It shows as a TFTP timeout. My 161 is FTP so not sure why TFTP timeout is showing. I can’t ping the S10 DHCP IP from my laptop on the same network so not sure why that is but perhaps I borked the network driver too.

    I am hoping somebody can guide me as to how to fix it locally using USB – what version of the imaging tool would work and what firmware version I should be loading to the USB, and anything after that. In my multiple testing I’ve set it to Push and used WTOS as the boot type and loaded the .i2d files. All fail with the OS missing message.

    Thank you in advance.

    #108612
    scowley
    Participant
    • Total Post: 2
    • Newbie

    Ok, getting a bit further. I’ve used the USB imaging tool 2.0.9.15 and just used a ‘Merlin image’. I then copied the 2x .12d folders onto teh USB. The S10 10 is now booting up off the USB and offering to ‘Push’ and showing me the 3 options – Merlin and the 2 .i2d folders. Merlin has full Bios, CMOS and OS. Both the .i2d folders only show as having CMOS.

    I’ve tried both and I just get a blank screen. When I hit Enter, I get a message that it is beginning to ‘Push’ but then “unable to open the file to read size of flash drive”.

    Any ideas would be greatly appreciated?

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