Minimize test-variables!

[labeas]

So far I've failed to install:
different version, different booter, different Wifi, to difrnt Laptop.
 With non Inet, other than Wifi via the ver7.2, there have been too
many new variables to control in my attempts.
So I want to try to install the new: version 10.1, <grubDos Booter>
to the *OLD-proven* Laptop which so-far has been running Ver 7.2 TC64.
          This latest attempt's log is:--
*PowerUp with <grubDos Bootstik> plugged.
*<F7> = select bootstik: <UEFI> choice == brief mesg <video problem> ?
*Select my "TC64fix" from menu of <grubDos.cnf>
                   == progress is traced, ending with <TC logo>.
$ df = /mnt/sdb1
$ sudo umount /mnt/sdb1 = OK
I also want to be able to remove the BootStik, since the problematic
laptop has only 2 USBsockets. So far I was not able to umount.
But it's confusing that this umountABLE BootStik was <flashing>,
ie. exercising R/W cycles ?

Q: how should I proceed to install the fully GUI, WifiCapable Ver10
to the old laptop which DOES handle Wifi?

[Juanito]

If you have a working tc-7.x installation, you can install tc-10.x alongside it.

* copy and rename the tc-10.x files - for example use core_tc10.gz and vmlinuz_tc10
* create a new tce directory - for example tce_tc10
* create a new menu entry in your bootloader referencing core_tc10.gz, vmlinuz_tc10 and tce_tc10

Reboot and select the new menu entry.