- This topic is empty.
21. August 2006 at 5:51 #171AnonymousMember
- Total Post: 162
- Jacked into The Matrix
First of all, thanks to ThinkThin for helping me with my first question.
I have setup a wnos.ini file to update a dozen Wyse1200LEs at a site.
All except 1 have worked perfectly.
This particular Wyse1200LE comes up with errors as it is reading through the wnos.ini file, most like this:
Invalid Profile’s key “VNCD Max” etc…
and finishes with:
To me it seems that it does not have all the options enabled for the firmware, but the version we are using is Blazer 5.05 (is that right?)
I have tried re-creating the wnos.ini file from scratch, but no joy.
This is the wnos.ini file:
DeskColor=”255 255 255″
Screensaver=”10″ LockTerminal=no Type=2 Image=logo2.jpg
Device=Ethernet Speed=”100M HD”
Description=”Special App – Wyse”
What am I doing wrong?
Matt21. August 2006 at 6:08 #8768
Sorry, the above post was by me…forgot to login 😳
Matt21. August 2006 at 10:58 #8769
Thanks for posting!
I would check the firmware version on the terminal anyway, maybe for some strange reason it has not upated correctly.
Anyway, after looking at the wnos.ini file I would just delete the MaxVNCD=1 statement as the system default is =1 anyway so its not really doing anything.
Also the VncPrompt=No Accept= have no prams (maybe you left them out for security reasons, thats cool)
Finally as you have the localcopy=yes it looks like you want to save the connection in case the ftp server goes down, in this case also include the enablelocal=yes in general section of the file. You could also set a Privilege= setting as well.
I hope this is of use,
-TT22. August 2006 at 7:23 #8772
Thanks ThinkThin for your suggestions, I will add them to the wnos.ini file.
The two that don’t work seem to be the oldest 1200s in the place, and I suspect you are right, they didn’t upgrade properly.
I did try changing the autoload=1 instead of 2 to see if it would reload the firmware, but I think I need to do a reset (G Key) to get it back to original.
I also remember there was another way of sending firmware to the Wyse1200LE using something like NetX? but I don’t recall much about it…do you have any information on this?
Matt22. August 2006 at 11:19 #8774
You can use netXfer (avaliable on the Wyse site) to download firmware but its not really worth the effort. Its only usefull if the OS is corrupt and you need some special code from Wyse support.
I have seen it when a device will not upgrade until a G-Key, if you have a lot of devices you could install the free version of Rapport and that will report on the firmware version of all the units. Newer units can have a g-key sent from Rapport or from the wnos.ini file. You may just end up VNC’ing the devices out of hours and do a reset to factory defaults.
-TT22. August 2006 at 11:51 #8775
Will give the G-Key a go.
As I understand it, the power has to be off for 45 seconds before boot up, with the G key held down.
Matt23. August 2006 at 2:26 #8777
Just an update as to how I resolved this issue…it was all my fault 😳
So much to learn, so little time 😥
I wasn’t aware that the file I was using in the wnos directory was a network boot file (BTC_wnos). So all the Wyse Terminals that had current firmware worked fine with the features I was enabling in the wnos.ini, however, two were on very old firmware, and for some reason didn’t update. All I did was take the BTC_wnos file out of the ftp directory, change the autoload=1, allow them to update to the current Blazer firmware and they were happy again.
I have not had much experience with the network boot setup, but it seems to be a good option for the 1200LEs.
Matt23. August 2006 at 3:48 #8778
Cool, thanks for posting the solution back as I would have not thought of that as the issue.
To be honest I think I will find out some more details on the net boot option and where it is at as I have not played with it recently,
-TT23. August 2006 at 5:13 #8779
From the little time I spent working with it:
The network boot option gives you an OS image size of 1487 KB as opposed to 512 KB, so there are many more options you can set (perhaps like the S10). The important thing I learnt from it is you really need to have an up to date UTC_512 to work with it, otherwise many of the options wont work.
I am currently using Blazer 5.0.056 (not network boot), which seems ok at this stage. The network boot image I was using was Blazer Version 5.0.053 and that worked ok too.
I might try connecting to a CSG using the network boot option, who knows, it might just work!
I have ordered a S10 to play with too!
- You must be logged in to reply to this topic.