Thin Client: Wyse Cx0 Notes, Experiences (Updated: 02/03/2021)

 

I bought a super-cheap Wyse Cx0 Thin Client off eBay some time ago, and I have been toying with it a bit. This post serves as a catch-all place for my information regarding the device. Note: information may be added, updated, or deleted at any time.

Let's talk hardware specs to get things going:

CPU - Via C7

GPU - VX855 Chrome9

RJ45 (Wired Ethernet) - VT6122 (Velocity)

Sound - Vinyl HD (uses version 7.9 drivers)

Storage - 2.5-inch IDE interface (male connector on motherboard)

RAM - 1xDDR2 SODIMM

USB Ports - 4 USB 2.0 Ports (2 in front, 2 in back)

Video Ports - DVI Connector

Power Requirements - 12V, 2.5A AC Adapter

Other Ports - 1 PS/2 Mouse, 1 PS/2 Keyboard

Mine came preinstalled with some kind of thin client software (I do not believe it was XP Embedded)

BIOS was locked with a password. Password for WYSE is Fireport. The BIOS allows user to change boot sequence and enable/disable some basic items. Very limited BIOS. 

The system accepted bootable CD/DVDs and also USB floppy drive as bootable media. You can also boot from properly formatted USB storage. Makes for a very flexible installation environment.

Since the storage is IDE, everything just worked when installing anything from DOS 6.22 to XP as far as install goes. My unit had 512MB RAM and a 128 MB DOM (Disk on Module) 44-pin PATA board. 

I purchased a 2.5-inch ribbon cable (F-F) and a 2.5-inch IDE-to-SD adapter. This allowed me to swap out storage options at any time (er, with the top cover removed, of course).

Speaking of top cover, there are two plastic clips at the front corners of the lid, making it a bit of a hassle to remove. I snipped those off so that the lid can just come off when I remove the single screw (on back of unit) to open the case. 

OPERATING SYSTEMS - ALL MUST BE 16-bit or 32-bit ONLY!

In every case, booting with USB keyboard and mouse already plugged in showed no problems installing/using the OS. The speed rating (Class) of your SD card makes all the difference! Be sure to use Class 6 or higher.

DOS 6.22 (512MB RAM, 512MB SD) - DOS installs easily from USB Floppy (or bootable USB). In order to install games like Wolf3d or Duke3d, I had to employ the use of MoSlo. Once the games were installed, though, the Wyse ran the games themselves just fine without the helper. Duke3d ran VESA 800x600 smoothly. The Secret of Monkey Island Demo played nicely in EGA mode (hmm, maybe it was VGA mode). There is NO SOUND BLASTER SOUND. The Vinyl HD audio does not have a DOS driver. I tried a variety of VIA-related drivers, hacks, etc and in each case, the dreaded "No VIA Chipset detected" message (or something similar) would appear. Programs that support the PC Speaker will output sound to the piezo speaker built onto the motherboard. This would make for a compact, spry DOS game machine if only there was sound support.

I installed DOS on the 128MB built-in flash and then after I swapped out for the SD/IDE adapter, I installed DOS to a 512MB MicroSD with an adapter. Works great!

Windows for Workgroups (WFW 3.11) (512MB RAM, 512MB SD) - Installed on same SD as the DOS install above. Windows would not boot. Either got a scrambled splash screen or a "Divide Overflow" error on a mangled splash screen. I changed various video settings and tried MoSlo, but nothing worked for me. I gave up trying to make it work.

Windows 95 (512MB RAM, 512MB SD) - Formatted SD with DOS. Copied Win95 setup folder from CD to SD card. Did not choose Sound, Network, etc during setup. Could not get any drivers to work (even though they came from the VIA downloads site).

Windows 98 (512MB RAM, 512MB SD) - Installed with no problem that I recall. Used LAN drivers from the XP Drivers file below. Could not get sound nor video drivers to work. I installed VIA Hyperion Drivers v5.24a and the VIA Retro Drivers (from here) along with the USB 2.0 Driver Pack (Here). After the install, reboot and the system should find new system-level devices. If asked to search for drivers, just click NEXT and let Windows find what it needs. I also recommend Phil's Win98 Easy DOS Mode PIF! More info here!

Windows XP (512MB RAM, 4GB SD) - Windows XP installs with no problems. Finding drivers, however, was a royal pain. To help with that, I created a ZIP file that has the XP drivers for video, sound, networking, and chipset. You can grab those here.

Windows 7 - (2GB RAM, 40GB 2.5-inch Drive) - Straight-forward install from USB DVD drive (though could have used a bootable USB). Install takes a while. Windows 7 detected sound and network. Using the OS is painfully slow. The system hits the hard drive in a nearly constant state. Attempting to download, install, then use Chrome was a smack in the face of the reality of the limitations of older hardware - especially running at 1GHz with only 2GB of RAM. Firefox was slightly better in that I could at least surf pages, download video drivers, etc. However, the video drivers reported that I had the wrong version of Windows (perhaps because Win7 wasn't registered during testing?). In any case, Win7 saw it was a vx855 chipset and allowed me to change to all sorts of resolutions.

*Note: I tried to install on a 128GB SD card and Windows said it could not install it to that device because it couldn't find a bootbale BIOS setting for it. I switched to a 40GB 2.5-inch IDE drive from an old laptop.

Windows 10 (2GB RAM, Various drives) - I tried a variety of drives (SD, 2.5-inch IDE) and each time, the installer gave me an IRQ Not Less Than (or whatever) blue screen. I never could get Win10 to install on this device.

Windows 8.1 (2GB RAM, 128GB SD) - Since Windows 10 failed, I thought I would try Windows 8.1 Pro. Note that at several times during the install, the system will appear to lock up. Just be patient. System will countdown to a reboot. Shut off the unit here. Otherwise, it will boot back to the setup USB drive. Initial setup took quite a bit of time. This will vary based on the speed of your SD and the throughput of the onboard IDE controller. Again, be patient. During setup, got an error that UUID was not supported and it logged me out. I then tried to log back in, and setup continued. Like Windows 7, setup detected everything except for the video card. And, like Windows 7, I could change to a variety of resolutions. 

DOSBox Distro (1GB RAM, 16GB USB) - There is an interesting project that uses TinyCore Linux to serve as a loader for DOSBox. This actually worked decently on the Cx0. The software itself has issues. For example, some programs dump you back to the DOS prompt, but are actually trying to run in the Linux environment behind the scenes. You can't get to it, though, because task switching is disabled in the system. Overall, things boot and run rather slowly. However, you do get Sound Blaster sounds out of the headphone jack! There was no adlib music even though the games did detect adlib capability. Not sure what's going on there. This has potential promise as a workaround for running DOS games with Sound Blaster on the Cx0.

 

Lenovo e550 Thinkpad Red Light Only No Boot (Possible Solutions)

Have a user with a Lenovo E550 laptop. The laptop was working fine while watching videos, etc, but would sometimes appear to turn off without being able to come back on.

The Thinkpad light would come on (red light in the logo in the wrist rest area), but the unit would not power up. Fans would not spin up, no POST, no boot, no hard drive sounds.

We found several solutions that have worked intermittently  (that is, seemingly randomly):

• Remove the battery. Leave the AC plugged in. Hold power button for 30 seconds. Red Thinkpad light will blink 3 times. Unplug the power. Hold the power button down again for 30 seconds. Plus the AC back in, but leave the battery out. Turn on the laptop. If it boots, shut it down and put the battery back in. Boot the laptop.
• Remove the battery. Leave the AC plugged in. Connect an external VGA monitor. Hold the power button for 30 seconds (until red Thinkpad light blinks 3 times). Turn on the laptop. If the laptop boots, it will most likely show on the monitor instead of the built-in display. Once booted, change the display options to make the built-in display panel the primary display. Shut down the laptop. Unplug the VGA cable. Boot the laptop. If it boots, shut down the laptop, insert the battery, and reboot the laptop.
• Turn off the laptop (hold power button until Thinkpad red light goes out). Remove the battery. Unplug the AC adapter. Turn the laptop over and remove the three screws holding the large plate that covers the RAM and hard drive. Remove back cover. Near the hard drive, find a wrapped CMOS battery (looks like a watch battery). There are two wires with a plug adapter at the end. Disengage the plug gently. It is a TIGHT fit, so be careful. With the CMOD battery disconnected, turn the laptop over and plug in the AC. Open the laptop and turn it on. When it boots, you will get an error that the time and date a re wrong. Hold the power button until the laptop turns off. Unplug the AC adapter. Turn the laptop over again. Reconnect the CMOS battery. Again, this is a TIGHT fit, so be careful. Replace the back panel and attach the screws. Turn the laptop back over, reinstall the battery and connect the AC. Turn on the laptop. You should get an error about the time and date. Follow the on-screen instructions for setting those then you should be able to boot as normal.

As we find other solutions to this problem, I will update this post. Hope it helps!

 

Tract Computing, Inc - My days in computer retail

 

Back in 1989, I worked for a retail computer company called "Tract Computing." The operation had two locations: one in the Potomac Mills Mall in Woodbridge, VA, and the other in an office complex in Alexandria, VA. I have tried to research information about the company since, but have come up empty.

What I do remember, however, are a few of the things that I will probably never forget. They help lay the foundation for some of my core beliefs regarding business and handling employees. In this post, I'll share some of the things I remember (which may or may not have anything to do with business practices, but are rather memories).

• I worked with several guys at the store. There was Rick and CJ (I cannot remember their last names to save my life). There were at least two other guys as well. The place was managed by a woman named Karen (I believe her name is/was Karen Williams, but that could be wrong). The company was run by a man named Alex and his wife (also named Karen, I believe). Alex's brother did the books, but I'm afraid I cannot recall his name. Their last name was either Nassif or Nassir, perhaps.
• Alex had a vanity license plate with "DOS EXE" on it. So appropriate for the late 80's/early 90's.
• One of the guys had an Amiga 1500 or perhaps 2000. We would go to his house to mess with it and eventually cobbled together a very cool PC/Amiga hybrid. I don't remember the details, but we used an IBM-PC bridge card from the Amiga with a ribbon cable that led to an AT chassis where a separate board served to add expansion ports to the PC side. That was crazy.
• One of my most memorable moments came by way of a woman who came into the store one day. She held a computer mouse in her hands, and she approached me asking if we happened to sell just the balls that went into the computer mouse. In those days, we didn't have optical mice. Mice had a little ball that rolled around inside for movement. When I told her that we only sold complete mice, I asked her why she just needed the ball. She opened her hands and showed me a computer mouse that had been marred and scarred with a cable that looked like it had been chomped on for quite some time. She said, "Well, you see, my cat was playing with my mouse, and I think she killed it." Truly one of the funniest moments I've had. We sold her a replacement mouse.
• Another stand-out situation came by way of an older couple. The woman had come to the store early in the day, picked out some software, then asked if it would run on an IBM-PC. I assured her that it would and she bought it. Later that day, she came back with her husband. Her husband was angry about something. When I asked what was wrong, he barked, "Are you the one that sold this (holding up the box) to my wife?" "Yes, sir," I said, confused. "Well, it will NOT work on an IBM-PC! This has five and quarter inch disks and we need three and a half! Where's your manager?" I tried to explain that the software WOULD work, but that I was not told the computer only had 3.5" drives. Didn't matter. He found the manager and proceeded to tell her how incompetent I was (using pretty colorful words to do so), and that I should be fired on the spot. She got him calmed down. One of the other guys copied the program to a 3.5-inch disk and sent the couple on their merry way. The manager got my side of the story and we decided it was a lesson learned - one I still practice as best I can to this day: ASK ALL THE QUESTIONS, ASSUME NOTHING. From that day on, I have tried to ask all the possible questions I can when given a task or a project.
• Even though I couldn't find information online regarding Tract Computing, Inc, I do recall that the company had folded not long after I left in 1990. I was offered a manager's position in late 1989 as an enticement not to back to college (I was out for a semester, taking time off). They offered me a decent amount of money, but in the end, I thought it better to get my degree and return should the opportunity and offer still stand. By the time I graduated, they no longer existed. Plus, I wouldn't have gone back by then anyway. Life had taken me in a different direction.

In those days, we sold everything from hardware including PCs, Amigas, C64s, all kinds of peripherals. We were basically like Computer Shopper magazine in a little store. We weren't anything like Software, etc or Babbages or the myriad of other computer-related stores, but we were one of the few in the area. Sometimes, just being there is enough to have a moderately successful business. 

Shortly before I left, the manager was fired for allegedly stealing money from the company. Apparently, she wrote company checks to herself, which she signed, and then she endorsed on the back. The bank raised a few questions after the check amounts continued to grow, and things spiraled from there. Note: this is the story as I heard, so if facts are askew,  I am not making any accusations nor legal claims here. Nor am I trying to slander/libel anyone.

Anyway, I thought I would write this post in case any of the folks from back in the day started poking around looking for info about Tract Computing. Thanks for reading.

1997: The Year of Mystique (Mercury Mystique and Matrox Mystique)

In 1997, I fell victim to two of the worst purchases I have ever made. On top of that, they both shared the name model name even though they were vastly different pieces of equipment.

In those days, I had been driving around in a Dodge Neon. I had a 1996 Dodge Neon. I had seen the car through some trade show something or other as a concept car and instantly fell madly in love with the car. In 1996, I convinced my wife that we should get one. 

About a year or so later, I was having weird trouble with the car and decided to get rid of it. I went shopping at the local Ford dealer and came across a maroon sports sedan. Er, more like a compact sedan dressed up to look sporty. That should have been by first warning sign. Instead, it had bells and whistles I could have only dreamed about in my base model Neon. No, this car had a much better stereo system, power windows, power locks, remote trunk, fog lights, cool alloy wheels and a spoiler on the back! And, it had a cool name: The Mercury Mystique!

image from: https://www.iaai.com/vehicledetails/26779812?RowNumber=1

As if that weren't enough, though, at the same time (or around the same time), I had upgraded my computer. I saw a very cool ad with a clown-mime joker dude in it for an amazing new video card. Granted, the card had come out in 1996, but I could finally afford it a year later. Not only was this a supposedly awesome video card, but it share the name of the car I had just bought! This was the Matrox Mystique! How cool was it to own a car and video card with the same name!? Yeah, I was a doof. (Heh-heh "WAS?!")

By Swaaye at the English language Wikipedia, CC BY-SA 3.0, https://commons.wikimedia.org/w/index.php?curid=4855006 

Turns out, as far as the car was concerned, the only "mystique" was how Ford managed to sell a crap-ton of these things on poor unsuspecting schmucks like me. This car was a piece of junk. The power window system failed (just after warranty), the engine ran like crap, the air conditioner gave out, it drank oil like a man drinking water in the desert. Just anything and everything that could go wrong went wrong all in this one car. I got rid of it in 2000 and bought a Chevy Impala. Now, THAT was one of my favorite cars ever. That's a story for another time.

As for the video card, it ran my Windows installation at a higher resolution than whatever my previous card was. Nothing like squeezing more tiny dots onto a massive 19-inch CRT... As for gaming, though, I remember upping the resolution of certain games, but everything seemed muddy and blurry. It was like, in some games, I was playing with dirty glasses on. I bought some kind of daughter-card add-on for the card (TV tuner or video capture maybe), but it never worked. I even took it back to the store where I bought it and exchanged it. That one didn't work either. Now, it was still a better card than I had before, and even though it had been a year since initial release, the card still cost me a pretty penny that I didn't really have at the time. So, with the money invested and performance boost, I soldiered on with it until 2000 when I dove into the world of ATI and Nvidia graphics cards.

Both of the "Mystique"-branded equipment in life became unlovingly referred to as the "Mystakes." Both ended up being foolish purchases, which even to this day in 2020 I hold a deep hatred for both items. Though, I admit, I hate the Mercury far more than the video card.

FON-175 POST Mode Recovery (Factory Reset)

 

If you need to do a factory restore on a Fortinet FON-175 (or FON-175i, FON-375, FON-375i) device, they will send you a document that refers to the "Post Mode" in order to do a recovery via post mode. While the document is helpful, I couldn't make the recovery work as it was written.

In the document, it suggests you use FileZilla FTP Server. For whatever reason, I could not get the phone's built-in ftp client to connect to FileZilla. After much hair-pulling and Googling, I stumbled across another ftp server to use instead of filezilla: CoreFTP Server.

https://www.coreftp.com/server/

The setup is a little wonky, but in a nutshell:

• Click the SETUP button at the top.
• Click NEW in the "Domains" section
• Type the IP you chose for your IPv4 (192.168.10.x)
• Set the Base Directory to the folder where you stored your firmware
• Click OK
• Select your new domain
• Click NEW in the "User" section
• Enter a username
• Enter a password
• Set the HOME DIRECTORY to the location of the firmware file
• Check the "Always Allow Login" option
• Click OK
• Click OK to exit SETUP
• Click the "View Activity" option
  

Once you have done that, follow the steps outlined in the Post Mode document.

By the way, there is a version of the document online here (though in a foreign language):

https://startcom123.wordpress.com/2015/02/04/troubleshoot-ip-phone-fanvil-post-mode/

*Note: even though this method allowed me to update my phone, the phone itself was still bricked. It kept rebooting after getting to the user screen. At least it was worth a shot.