Forum Replies Created
-
Posts
-
Turns out the last build for the 4GB flash models (B855) has the N-6230 driver per the Release Notes, so even the 2nd Gen 4GB models must have had the N-6230 card. Trying a AC-7260 card with that build doesn’t work, though the Release Notes for the B858 8GB build indicate drivers for the AC-7260 card, and indeed the 7260 cards I got will work on a unit with B858.
Thanks. I found a couple of older units, 1st generation 909587-41L, with Intel N-6230 (62230ANHMW) cards. Maybe wifi was changed for 2nd Gen as well?
Problem solved – best guess is that it was a problem with an unmanaged ‘green’ network switch.
I just tried a non-PXE update of a Z90D7 unit. The Merlin agent started, posted some status indicating connection to the WDM-server port 80 (#0), then closed the connection. The last status note indicated
“* Closing connection #0
Segmentation fault
BusyBox v1.00 [etc.]…
/bin/sh: can’t access tty; job control turned off
/bin #”I think with past WDM versions, that issue caused WDM to lose contact with the repository, which is working here. I am able to push HAgent updates, just not images via “roll to boot”. Pulling an image also no longer works. At any rate, the rapport User password is set to never expire, from the Users and Groups Manager.
I saw advice for this problem to disable the Windows Firewall and check the DEP setting. Both of these were OK already.
I decided to take the simple route, based on your advice. It would be nice to preserve the database history, but much of that is exportable. The reinstallation of packages is not too onerous.
I had begun setting up a C90LEW as a carputer, but now that tablets have come along, for me they are a better solution.
If more storage is needed, it’s a simple matter to install a larger flash module, available on eBay or elsewhere, or you can cable in a standard laptop IDE HDD or SSD if you don’t mind leaving off the C90LEW case cover.
I don’t recognize the W90 model designation. If you mean X90, I don’t know that those two models will accomodate a conventional HDD or SSD. The X90L and related models used the same form of horizontal (90 degree) IDE flash module as many earlier Wyse thin clients. These are readily available up to 32GB or even higher if you look around. I’ve never looked at the X90c but I assume it’s the same since it’s in the same series.
The next generation of laptop models, the X90M and related models, will take standard laptop-style SATA HDD and SSD.
In either case, the Wyse website has the licensed OS images for your units, and a freeware tool to permit installation via USB thumb drive, if you’d like to stick with the Wyse OS versions. You will only be able to use the images that are licensed for those units, so you have to make sure to choose the right download from among the many options. They can be installed on a larger drive as well.
Those Wyse laptops are very well made and should make a fine laptop for general use, though a bit slow. The Wyse OS installations are also somewhat barebones and you may find yourself having to add back some of what they left out, for full Windows functionality, depending on what you are trying to do.
RAM upgrade is simple, there should be two channels and the Wyse units seem widely tolerant of RAM brands.
I tried this but it didn’t work. I think the main issue with the chip-switch tactic is that the newer Wyse TCs don’t re-flash the BIOS from within the imaging sequence in the same manner as previously. The BIOS imaging now comes after a reboot, so with a corrupted chip, the process halts there.
Even with an older unit where the switch trick does work, there may be parts of the BIOS – related to the OS license? – that are not addressable during re-flash, so I’m kind of doubtful you could start with a blank chip.
Thanks, starting with the simpler XPe HAgent 5.1.1.59 which I knew would check in to WDM 4.9.1, I copied the files to the indicated client directories, then executed the commands from the install.bat file manually. Simply running the batch file in CMD prompt from the C:Temp directory did not work.
Interestingly, once the 9455 checked in I tried to upgrade the HAgent to 5.2.0.32 via WDM. Though the WDM Update Manager and log show the process completed, the client initiated but didn’t fully perform the familiar steps, and the HAgent still shows as 5.1.1.59 on the client and in Device Manager.
I think I went through the script steps, but without apparent effect.
With the FBWF off and in Admin mode, and using your excellent Creating Rapport 4 Packages pdf to understand the script command, I did the following:
1- copied all the files from the Rapport directory for XPe HAgent 5.2.0.10 to C:Temp on the 9455XL
2- from the CMD line, I navigated to that directory and executed PortRegtoIni.exe and install.bat. These were the only two executables I saw in the script.
3- rebootedThe only feedback during the process was several lines indicating files being copied upon execution of install.bat. The reboot appeared normal, with none of the HAgent updating evidence that you see whe using WDM. Client Info still shows the old HAgent.
The WDM Control Panel has disappeared from the client.
Did I follow the right process? Might it be worthwhile trying an earlier version of the HAgent, such as one that was current for WDM 4.8.5?
This is an old post, but in case it helps the next person finding this, I’ll add some comments.
I’ve used nLite to install XP to various Wyse thin clients, mostly old 9000 series (9455,9450,941G) as I recall. It worked for me, and I confess it’s been a long time but I’d make these suggestions:
1- check your nLite build on another PC (one for which you have chipset drivers) to make sure you didn’t leave out something critical aside from drivers. Frankly, I don’t recall that not having chipset-specific drivers up front has ever been fatal for an off-the-shelf full or nLite Windows build, but maybe I’ve just not encountered it. It’s usually the I/O stuff that’s critically missing.
2- check the VIA website (since this is a V90) for drivers that may relate to the chipset used on the mobo. I seem to recall doing this a few times.
3- use a driver extraction program like Double Driver to pull all the non-Windows drivers from the Wyse XPe installation, prior to moving on to your custom OS. This can probably be done w/o the extraction program but I wasn’t sure I understood enough about locating and IDing drivers, so I used this tool when installing a customized Windows OS to some Rx0L devices.
Just finished setting up WDM 4.9.1 and it worked that way.
thanks,
MikeFor posterity’s sake, note that the downloaded .exe installers for the last several WDM/USB V50L/V50LE images did not extract ALL the files to the suitably-named image folder. The .rsp file ends up at whatever directory level was chosen for the extraction, so all you see in the typical image-named file is the i2d. You have to go looking for the .rsp.
The connector is standard 44 pin IDE, same form as used in laptop computers from the IDE era (though the gender is reversed between board and drive). You can install higher cap 44 pin vertical flash modules (available up to 128GB) that match or are similar in form factor to the OEM module, or using various cable adapters, any IDE drive you choose (solid state or platter-based). Of course, the case lid would no longer fit in the latter instance. Having said that, I can’t vouch that the board would adequately power a standard hard drive. I’ve installed those in the older 9000 series thin clients with no issue, but I believe those units were designed with that in mind. I can’t imagine an IDE SSD would be a problem in that regard.
The imaging software, WDM or USB, will handle a larger flash module with little issue, that I’ve found. I also haven’t found the Wyse (or HP) thin clients to be particular with respect to the brand of module. Apacer, Kingspec, Transcend, and various others have invariably worked for me.
In short, your intention can be easily achieved. I’ve done it on many V-series units.
I don’t believe it would be easy to make a USB drive into the boot drive.
