There are some explanations why updating/replacing the CF card (BTW, no less than 10 screws have to be removed to get at it) may fail.
The only appropriate file available from Eizo seems to be 630ln_276.zip
In it, take this path to another archive (unless you prefer Japanese over American English of course): 630ln_276/Web/USA\630ln276e.zip
Therein lies yet another subdirectory named 630ln276e, finally containing the files with the two longest names as fodder for uneizo.exe:
Code: Select all
ICA_LN_US_45942.bin
nk.bin
RDP_LN_US_0040.bin
readme.pdf
However, besides the bug of unclean termination already documented in this thread, uneizo.exe seems to garble the name of the first file it extracts by omitting the first letter, as can be seen below:
Code: Select all
D:\uneizo ..\RDP_LN_US_0040.bin
Found file: btwizrd.exe, length: 0x1F600
Found file: wbtprnwiz.dll, length: 0x12600
Found file: wbtprncpl.cpl, length: 0xA400
Found file: wbtcpl.cpl, length: 0x44E00
Found file: inetcpl.cpl, length: 0x6400
Found file: wbtsetup.exe, length: 0x1D600
Found file: tsconwiz.exe, length: 0xCC00
Found file: tsconman.exe, length: 0xBA00
Found file: taskman.exe, length: 0xC600
Found file: mstscax.dll, length: 0x80C00
Found file: mstsc.exe, length: 0x39A00
Found file: ssfloat.dll, length: 0x1600
Found file: rdp.inf, length: 0x292
Found file: RasDial.exe, length: 0x11400
Found file: 0040.reg, length: 0xD8
Found file: divide.exe, length: 0x12E00
Found file: FN-153xEvaApp.exe, length: 0x44200
Found file: RegEdit.exe, length: 0x6800
Error: Too long file name encountered
runtime error
In this case, the error won't prevent the system from booting and may easily be rectified by renaming that file to start with an extra "w", but one may not always be that lucky.
After renaming, the RDP setup wizard in all its click-thru EULA glory may still appear (nagging) repeatedly through the next few reboots but should finally disappear as all settings have been saved.
Unlike the older version, this updated RDP client works just fine (in 65k colors) with Windows XP Professional.
One more point to be aware of (especially where using passwords) is that you might need to change the keyboard layout to your locale as the update will have set it back to U.S. "QWERTY".
From the file names seen at the start of this message, it might be that e.g. what becomes 5942.reg in the ICA subdirectory is actually 45942.reg, but I haven't tried yet whether renaming this has any effect.
Having found all of these files, the next step is writing them to a CF card.
Easier said than done, the eClient 630L was unable to boot from 2 out of 2 alternative 32-64MB CF cards, leaving no choice but to overwrite the original Eizo-labelled one.
To err on the side of caution, a bit-level backup seems indicated and dd is the tool for the task, with
http://www.chrysocome.net/dd allowing us to stay on Windows for something like (details depending on your card reader):
Code: Select all
dd if=\\.\k: of=d:\630l272e.img --size --progress
rawwrite dd for windows version 0.5.
Written by John Newbigin <jn@it.swin.edu.au>
This program is covered by the GPL. See copying.txt for details
32,030,720
62560+0 records in
62560+0 records out
For writing it back in the event everything goes wrong (or to clone the card - which has not worked with any of those I had available), one would inverse the if and of (input and output file - pretty much everything is a file under Unix where this comes from) and add a parameter of BS=1M or similar (the writing block size).
To try and figure out whether there is anything special about the type or organization of the card used by Eizo, state-of-the-art nanoscale photography [;)] has been used to decipher the smallprint on it:
One more thing in desperate need of being hacked ASAP is the web browser's User Agent string, as the WinCE machine will be mistaken for a mobile phone and shown only minimalist versions by major sites such as Google News - suggestions welcome.
. Unfortunately my SO-DIMM is in use by my laptop server now, but new memory is ordered so it's not a dead project.
.