Introduction Until 2017, I had been an employee of Intelligent Computer Solutions, Inc. (ICS) for a full decade; in three different locations. However, apart from my tech support role, since a number of my past jobs had been as an electronics tech, I was also assigned to repair and even
build a number of the products that ICS manufactured. Due to all of the above, a former owner gifted me with an Im If any of this page is of interest to you, please contact me (link below) with any questions you may have; or about PCs in general or anything else you might find on my website! NOTE: I am still adding details to this webpage!!!
Pictures of My Im Solo-4 G3 Device and Technical SpecificationsThe following pics (click of any of them for full size!) show my Im Solo-4 G3 units top, bottom (S/N not shown), sides and Motherboard connections at the rear:
LSI Hardware BIOSEvery time the device is powered on, the first thing displayed on the screen is a notice on how to access the LSI Configuration Utility; which one should never need to do. If you do, youll find that the SAS Controller card installed is an SAS9211-4i (supports 4 SAS/SATA connectors):
The Windows Embedded OSThis was my Im Solo-4 G3 Desktop before I installed a new HDD and made the changes as noted much further below (click on any of these pics to enlarge them):
From the above, you can see that I had added some utility programs, such as Speccy and also Process Explorer to my unit. The basic Specs as seen in the Properties window are: 1) OS: Windows Embedded Standard (2010), Service Pack 1, 64-bit, 2) CPU: Intel® Core™ i7-4771 (3.50 GHz), with Speccy adding that this is a "Haswell 22nm Technology" chip, 3) RAM: 2.00 GB (1.87 GB usable); Speccy adding the Memory is type DDR3, and 4) Motherboard: Gigabyte H87N (WiFi is not included on this board); if you search for GA-H87N, you can find a User Manual for this board. For other Specs, click on the pictures above.
Restoring the Original Windows Embedded OSThe following photo shows the RESTORE USB drive that came with my Im Solo-4 G3 unit: This is what you would need to use after replacing an original physically damaged HDD, upgrading the boot drive to an SSD or simply needing to overwrite the OS if its boot files have become corrupted. Except for needing to confirm you actually want to overwrite all the contents of the connected disk drive, the process is automatic. NOTE: You must enter the full word Yes (which is case sensitive!):
Drive Bay & Replacing the HDD This is the easiest hardware change you can do internally. All you need is a good screwdriver, and there are no warranty seals to break. The following pics show the
devices Drive Bay and the HDD that originally came with my unit. It should be possible for you to replace the HDD with an SSD designed for that purpose.
Shrinking the C: Drive for Dual BootingIf you decide to try using a Dual Boot setup on this device, mainly for communicating via the Internet with a more recent OS (such as Linux Mint) without the OS attempting to or even downloading any kind of Microsoft updates,[1] then you can use Windows built-in Shrink function to make room for a second OS partition. This will make it possible for you to still use the four SATA ports under the ICS control software that currently will only run under a Windows 64-bit OS. Otherwise, using the whole storage drive for a Linux OS would be recommended. Here are some screenshots of shrinking the C: Drive under the Windows OSs Disk Management tool:   You should see something similar to this after the SHRINK process has completed: Some Quirks and Inconveniences of Dual Booting the Solo-4 G3Since the H87N motherboard can boot either an older MBR scheme OS or a newer UEFI capable OS and the Solo-4 G3 Restore USB drive installs the Windows Embedded OS under the MBR scheme, you need to make sure that any other OS, such as Linux Mint, does not install under UEFI mode! If it does, you will never be able to get the Windows OS onto the linux grub boot menu! It would only be able to do so if the Windows OS had been installed on a GPT formatted disk and the OS could boot in UEFI mode! So, never allow the second OS to install an EFI/UEFI boot partition! It must also be noted: So far, every time I have booted into the Linux OS below, neither the Keyboard (USB) nor the Touchscreen have been functional when booting back into the Windows OS! Every time, I have needed to go into the BIOS/UEFI settings; even without making any changes, and click on SAVE. Apparently something in the GRUB or Linux OS boot code resets something concerning the USB drivers in some non-volatile memory chip, preventing the Windows drivers from functioning!? At this time, I have no idea why this is occurring or how to resolve the issue, so this is rather inconvenient. You must also realize, that after installing another OS, you would need to have a Keyboard attached in order to select booting from the devices original Windows Embedded OS from any menu (as shown here), since the OS touch screen drivers cannot function before one of the operating systems boots up!  
Installing a Linux OSI had tried to install the latest Ubuntu Linux OS (24.04.3 LTS), but with only 2 GB of memory, that became impossible to do! Just the OS by itself requires quite a bit of memory, and each time I tried an install, the unit locked-up about 1/2 to 2/3 of the way through; even when not connected to the Internet. So, I decided to try installing an OS that used less resources: I chose Linux Mint 22.2 Zara Xfce (an LTS release; supported until 2029). Be sure to get the Xfce edition from that page! I did the install offline; booting from a USB drive made with RUFUS and the downloaded .ISO file, along with an attached Keyboard of course, and it completed fine. Here is a pic of my unit running Linux Mint: NOTE: Its quite easy to install a linux driver for the eGalax touch screen on the Solo-4 G3 unit! I downloaded eGTouch_v2.5.13219.L-x.7z from here into the Downloads folder. The setup was fairly simple. I needed to install a 7-Zip app (sudo apt install p7zip-full) in order to extract the 7-zipped files into another folder, navigate to that folder and execute the setup program. Here are all the entries I used to install the eGalax driver from a Terminal screen:
Upgrading the Memory  Be sure to click on the pics here to see inside!   You can also see the location of the CMOS Clock and Settings CR2032 3 volt Lithium (round button) Battery in the photo below. I didnt bother replacing this, since its not that much trouble for me to go into the BIOS/UEFI settings and update the clock, etc. when I need to. Unless you have both nimble yet firm fingers, I would not recommend performing this upgrade yourself. Apart from having to remove ALL 12 screws (3 near the top of each side; one being under the Warranty sticker), you also need to disconnect the smaller DATA cable (start with this one first!) and then the POWER (Yellow, Red and 2 Black wires) cable from the Evidence/Target-2 PCB connectors. It can be difficult to use enough force to disconnect these (they are not locked-in by any means, though it may feel like they are!) but also to do so within such a small amount of space: Between the existing memory module (the one with the RED colored heat sink) and two PCBs! And once you have removed these, you will also find it difficult to insert the DDR3 Memory module into such a tight space; making sure the locking mechanisms on both sides are open as wide as possible (and depending upon how the unit was manufactured, I was very thankful there was just enough room to get my module to insert on the left side! Theres a PCB there that made it seem as if it might be impossible to do so; it took me a number of tries until it finally went in!).   The existing memory module for most units is a 2 GB module from G. Skill with an attached alloy heat sink (RED in color). You can see the exact specs for this
module in the last image under the Specifications section above. I ended up finding another 2 GB DDR3 module at Amazon.com made by Crucial without any heat
sink (which may have allowed it to fit in easier) for about $15. Both modules are PC3-12800 (800 MHz).
Footnotes 1[Return to Text] Whenever I forgot to disconnect the unit from the Net, it always required having to deal with updates, rebooting and having the OS decide that it could not do any of them until finally returning back to its previous state after yet another reboot (thats Microsoft)!
First Posted on: 24 DEC 2025 (2025.12.24). You can write to me here: contact page (opens in a new window).
|