Archives

Regarding the warning on flashing in a LAN environment – I understand the possibility of a problem if multiple Thin-Clients were in the same LAN environment, which is not my case.

In my case, I consult for a small local medical free clinic and we are migrating to a client-server environment using old eBay obtained thin-clients to same money. The thin-clients sold on eBay almost always have unknown passwords and modified programs, so, at my house, I flash them back to the default state before installing them into the clinic’s LAN environment. Once in the working environment they will never be flashed again as they simply are used to access the server in a very static manner. Thus, in my case, flashing in my own, segregated thin-client LAN environment is OK.

I think that Wyse’s warning about not flashing in a LAN environment, without explaining why, is a disservice. They should state why, as it obviously doesn’t apply to every situation – mine being an example.

Thanks for the warning, however!

Thanks, but that didn’t do it. Running eepo without arguments shows the current state is already 0. Anyway, it appears that eepo controls the “always on” state, not the PXE boot.

Nonetheless, I discovered my problem. On my interconnected PC there was a DHCPserver.exe program running in the background that was a zombie left over from previously running WSI. Once I killed that job the boots no longer hang.

Of interest – I have worked out a way to put RDP 5.1 onto a Wyse 8235LE, thus getting the full high-color display – wonderful!