We seem to be having a lot of these S10 terminals in the past few weeks fail to boot with the same message:
PXE: No boot device present. Halting.
The error message comes up after normal use. They are simply used as internet browsing/word processing machines in the building, so no settings should be getting changed.
We have tried removing the network cable from the machine in hopes that it would skip booting from the network, but that did not work. Instead of the above error it simply states that it cannot find a network connection, and does not boot into the OS.
We have normally sent these out to Wyse to be repaired and/or replaced, however we have sent out over 5 in the past 2 months, and we're curious to see if there is any solution to our problem other than send them out for repair at Wyse.
All Boot devices in BIOS may need to be set to "NONE". When shutting down, select "Shutdown and Restart the system, then hold the "Delete" key down while clicking the OK button. Keep holding the "Delete" key until system restarts in setup. Password that I was given is "Fireport". If that gets you access, then set all boot order configuration items to "NONE", then "Save Values and Exit". Hope it works for you as well as it did for me.
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
The program you are using is telling the terminal to accept a VNC request, as it will send date on the port open for VNC. So the terminal is asking you to accept the prompt to allow a remote machine to control your session.
You can set the program to ignore the VNC ports, so it wont get prompted. Failing that you should be able to change the terminals behavior to the requests by editing the wnos.ini to not allow VNC connections. I think that can be done from there. Check on the config generator for wyse terminals on technicalhelp.de to find the correct syntax.
This is caused by the terminals default display resolution (or the resolution that it was set to in its previous environment). The easiest way to get a display, would be to use a different monitor with a higher range of supported resolutions.
Fingers crossed the previous wnos.ini file would allow a G-key reset.
If so, just hold down the G key when the terminal is booting, and it
will reset to factory defaults. This might allow your monitor to work. (I think the default resolution is 800x600)
The problem you have is that the terminal might be locked down via the .ini file. So changing the configuration might be difficult. You could use a program like Wireshark to perform a network trace, this would tell you where the terminal is looking for it its wnos.ini file.
Then you will be able to setup a new wnos.ini on an FTP server set to the IP address(and path) the terminal is looking for, and this will allow you to set your own configuration.
Basically, because the terminal is in loopback mode when in the OS, you would need to find an up to date .i2d file, and for the S10, then try and re-image it with Wyse Simple Imager. This will use PXE and DHCP option tags to grab the device, and push an image to it.
Make sure PXE is first in the boot order in the BIOS, people often forget this!!
All the software you need (apart from the i2d file) is available from the Wyse website. When it comes to the i2d file, you will need to contact Wyse directly to get hold of this. http://www.wyse.com/serviceandsupport/support/downloads.asp