- This topic is empty.
-
Posts
-
@thinkthin wrote:
I know this sounds weird but what you get the blinking cursor can you then unplug the unit, remove the cover and re-set the CMOS jumper switch next to the battery. Just move it across to the the middle and outside pin and then move the jumper back to its original position,
Cheers,
-TTHello,
I moved the CMOS-jumper to the other position and then back to its original position, but now not even the BIOS runs through – after starting it hangs at the wyse-logo.
I guess I´ll have to send it back…Regards, David
Hi,
Before you do enter the BIOS and select “Load Optimised Defaults” and then set the boot order to boot from the USB key,
Cheers,
-TTHi,
I can´t get to the BIOS, the only thing I see after switching it on is the fullscreen wyse-logo.
Regards, David
Hmmm, pull the battery and re-set the CMOS jumper one more time…
Does anyone know how to crear a 3V32.i2d file from a V30L Windows CE Terminal?
I have tried to do this via WDM and pulling the device config doesn’t create a .i2d file?
Has anyone managed to USB image a V30L?
Does anyone know how to create a .i2d file for a Windows CE V30L terminal, i’m basically trying to create an image using WDM and then using the USB imaging tool to push the image.
When I use the “Get Device Configuration” i don’t get back a .i2d file
Has anyone managed to usb image a V30L?
Hi,
You need to use the option “Get Device Image (Requires PXE)” If you do not see this option you need to have the device on the same subnet as the WDM server,
Cheers,
-TTJust as an update here, working fine on V90L/LE.
Not had a chance to test the x150 functionality yet, but i do have a dodgy 3150 that was converted from a 9150 that wont image (hardware code issue). I will have a go with that and a modifed (;))push.k file.One more tip on pulling the V30L image, also make sure that “LAN” is set to first in the boot order,
Cheers,
-TTHi
I successfully imaged a V90LE 2GB/1GB using a 2GB USB Memory Stick. The only issues I encountered was the image process failing during imaging from the USB. All you do to get around that is hit R for retry.I want to thank you all for the input and if I can be of any assistance I will be happy to advise on my experience.
I am now trying to figure a way to extract the image using a similar process to the above (excpet in reverse) and save it as a file. I have some custom software I use on the Thin Client and it saves me reconfiguring everytime…any suggestions?
Thanks
dinoc67TT,
I am getting the following error –
‘The Instruction at ox7ca58c0b’ referenced memory at ‘0c00000033’.
The memory could not be read
Click OK to terminate programI get this error, sometimes when windows loads, othertimes when going into the control panel.
It is an intermittant error. 🙁
The USB memory sticks I have tried so far are a new Kingston Datatraveler 2 Gb and an older 1Gb stick.
I am using the 256Mb Image.
The part number of the Terminal is 902115-02L
Could it be that the Wyse Terminal itself is faulty, or is it just a feature of the USB Imager ?? or am I doing something wrong.
Any help appreciated
ddaw
There is an issue where the image doe not always load. Can you load it again as it sounds like a windows file is corrupt,
Cheers,
-TTHi,
Works on V90L 1gb, takes a while though.
Am I right this all runs at USB1.1 not 2.0?
Magic though, thx to everyone involved in building this.
- You must be logged in to reply to this topic.