- This topic is empty.
-
AuthorPosts
-
March 16, 2010 at 3:53 pm #5757
Hello,
I’m deploying the WYSE V10L for my company. I don’t have any experience on the network side of things. I have come across something that has puzzled me and a few of my co-workers. One or two of the devices hang at the splash screen in the boot up process. I have no idea what is causing this problem, no beeps, no keys respond, all we can do is reboot but the same thing happens every time. We have tried unplugging the network cable and tried booting but it does make a difference.
Has any one else come across this problem? How can a remedy this problem or can I do anything about it?
Any input would help!
Thanks
-Joseph TurnerMarch 17, 2010 at 10:27 am #17942Can ou enter the BIOS by pressing Del while in the splash screen? Password is Fireport.
Load the optimized BIOS default.CG
March 24, 2010 at 4:19 pm #18002When the device locks up at boot nothing responds. I tried pressing and even holding the Del key down but it does nothing. Eventually I was able to get into the Bios and I loaded the optimized BIOS default. It still intermittently locks at the WYSE splash screen.
March 24, 2010 at 5:50 pm #18007So smetimes the client cmes upand sometimes not?
Sounds like a HW issue. Maybe RAM.CG
March 30, 2010 at 7:21 pm #18059Are there any USB devices plugged into the thin clients that are hanging? We’ve had a similar problem where if a user had one of the newer Blackberries plugged into it at boot time, the device would hang at the bios screen. This was resolved by upgrading to the newest 1.19 bios revision for the V10L
November 1, 2010 at 11:56 am #19261Sorry to reopen a long dead post, but I’m having the same issue across our deployment of V10L clients. The solution I’ve found is to power off and unplug the power from the Thin client. Unplug the monitory from the TC, plug in and power on the TC, wait a few seconds, then plug the monitor in.
I’ve had a ticket opened and closed with Wyse support but got no useful information other than “you can hammer on the G key and that sometimes fixes the problem”.
Any body know if there is a preventative measure for this? Was it a known issue fixed in any a BIOS revision?Cheers
November 22, 2010 at 2:14 am #19424having the same issues with mine. unplugging power, and letting the unit set for 10-15 seconds without power will fix this issue (at least for me.) happens about once per month.
-
AuthorPosts
- You must be logged in to reply to this topic.