The start of uniplat.log looks like this;
(setup: win7sp1, this time is first time I test with 100mb system partition in addition to windows partition, but still no difference, vanilla install with only network+wyse util installed after fresh windows install)
*************** Wyse Universal Platform Tool ***************
06182013 [13:46:47:771]  INFO: LogLevel = 17
06182013 [13:46:47:771]  ERROR: Failed to query registry Software\Wyse\WSM Client Utilities\UniPlat\LastWUPName - 2
06182013 [13:46:47:771]  ERROR: Failed to query registry Software\Wyse\WSM Client Utilities\UniPlat\LastDriveName - 2
06182013 [13:46:47:771]  ERROR: Failed to query registry Software\Wyse\WSM Client Utilities\UniPlat\LastSourceDrive - 2
06182013 [13:46:47:771]  ERROR: Failed to query registry Software\Wyse\WSM Client Utilities\UniPlat\LastDriveType - 2
06182013 [13:46:47:849]  INFO: opening file
06182013 [13:47:08:894]  INFO: CCapture::SetLog(17)
06182013 [13:47:08:910]  INFO: InitExcludeList(C:\Program Files\Wyse\WSM Client Utilities\UniPlat.ini)
Same issue with vanilla win7 without SP1, only thing installed are NIC + wyse util ... Now I'm out of ideas... The document mhaase pointed me to looked pretty simple and straight, and I can'tsee what's the problem ...
There MUST be something silly simple thing I overlooked, but what could it be?
After backing up Uniplat says about the image file:
OSM Version: 4
Image HAL: UNKNOWN
Image OS Version:
As we look here, there are something missing. Does it point towards anything I missed?
To clarify what I've been trying:
Used WSM Client utilites setup that came with latest WSM version 5.0.1
Windows 7 Professional w/ SP1 - English
Windows 7 Professional - English
Windows 7 Professional w/ SP1 - English - without 100mb boot partition
Windows 7 Professional - English - without 100mb boot partition
(And all the same for Norwegian version, and tested both the user that windowssetup created, and enabled the builtin administrator, no success)
Also I tried to uniplat-backup from a network connected WSM client, same problem.
I'm wondering, are there different uniplat versions which I could test? What other things could influence this?
Thanks for sharing!
Let us know how it works to create an image for different laptop types.
Be careful with the vendor specific utilities that start with Windows, as these often throw an error message when the hardware is different and/or eat up system resources unnecessarily if not used.
The best advice I can give is to start with the minimum drivers required and go with the built-in drivers of Windows first.
It fits perfect with my habits, as I always let Windows drivers be, and only installs drivers only on those yellow-marked devices in Device Manager. I never use to run "setup", I'll rather unpack with 7zip and let the update device driver find the files and install itself. At this way I keep vendor-specific programs down to a minimum. However, I've stumbled upon some devices which I HAVE to run Setup, but its rare. 🙂
So far I got a golden image up for HP Probook 6460b and 6570b, planning to add more later. Looking good so far.
In this case the best option is to Startup Repair from the Windows Recovery Environment. Put the CD in and select option "Press any key to boot from CD" when the system is booting. Then select Repair, go with windows installation, and select Repair your computer at system recovery options. Check whether this fixes the issue.
microneedle derma roller