On power-up the DEL key takes you into the BIOS. If you're prompted for a password the old Wyse password of Fireport still works on these modern thin clients.
The Wyse Z90D7 BIOS identifies itself as Phoenix SecureCore Tiano Setup
My unit was running version 1.0F dated 04/11/2011.
The Boot Tab listed:
Any pendrives you have plugged in will appear under the USB HDD entry. I did note that there is another entry under the Advanced tab which read Boot from USB which could be set to Enabled or Disabled. Something to bear in mind if you find you can't boot from USB.
You can also bring up a one-time boot menu without fiddling with the BIOS settings:
This brings up the Boot Menu. In my case it showed:
The cursor up and cursor down keys let you pick what you want to boot.
The Tab key switches you between the Boot menu and the App menu. In my case there is just one entry in the App menu - Setup - which is the standard BIOS Setup utility.
The Z90D7 is running Windows 7 Embedded.
I recently installed a larger SSD with the intention of using the Z90D7 as a development machine and ran into a few problems which made me think about updating the BIOS - my Z90D7 was running with BIOS 1.0F dated 04/18/2011. A quick Google found me this link where the author recommended an immediate upgrade to Version 3.0E.
One problem I found, having installed Tiny Core on an SSD connected to the SATA port, was that it wouldn't boot. This turned out to be the SATA Mode setting in the BIOS. This can be set to either IDE or AHCI. The latter would be the preferred mode and I obviously had changed it at some point. However I found with the mode set to AHCI the Z90D7 would not boot anything from the SATA port - neither the original firmware on the 4GB flash drive nor Tiny Core from a 16GB SSD. Set it to IDE and then both the original flash drive and the new SSD work fine. Later on, having updated the BIOS to version 2.0C, I found that Tiny Core would boot quite happily with the SATA mode set to AHCI.
I find updating the firmware on Wyse systems can be a bit of a hassle as you have to track down a suitable version of of the USB Firmware Update tool - often not an easy task. Anyway my first attempt to upgrade to BIOS 3.0E failed with an error message along the lines of a 'security key' mismatch and a refusal to carry out the update. An article in the Wyse Knowledge Base provides an explanation:
This issue is the result of a manufacturing change done to the Z and Xm series of thin clients for both Windows Embedded Standard and Windows Embedded Standard 7 operating systems. When Upgrading any of these devices (Z90SW, Z90SW, Z90S7, Z90D7, X90MW and X90M7) from any firmware version below build 830, you will need to install the "2nd Generation Compatibility Kit" before re-imaging the thin client in order to re-image them.
I downloaded the compatibility kit (which advanced the BIOS to 2.0) and waded through the release notes and upgrade path. It's all documented under the Updating Tab.
As always things are not helped by Wyse continually changing their USB Firmware Imaging tool along the way and not making available the early versions for download.
[July 2019] With the switch to the new Dell support site the "2nd generation compatibility kit" download has vanished along with the article in the Dell Knowledge Base.
FYI Below is a README that came as part of the 2nd Generation Upgrade Kit.
Thank you for purchasing the Wyse Z class desktop and XM class mobile products with AMD T56N 1.65GHZ Dual Core or T52R 1.5GHZ Single Core 2nd Gen Processors.
These new thin clients have been enhanced using the latest technology. Customers with older versions of these products can upgrade to BIOS version 2.0C or later which is compatible with either AMD's 1st Gen or 2nd Gen Processors.
Models affected are as follows:
|Zx0- Single Core||Z50S||909588‐xxL,909589‐xxL||909688‐xxL,909689‐xxL|
|Zx0- Dual Core||Z00D||909592‐xxL,909593‐xxL||909692‐xxL,909693‐xxL|
|Zx0DE -Dual Core Extended chassis||Z00DE||909610‐xxL||909710‐xxL|
Please contact your Reseller or Wyse Technical Support for custom versions of the embedded operating system. An incorrect upgrade path will render the product unusable and subsequently require the Product to be returned for servicing.
Any comments? email me. Added August 2016 Last update July 2019