New TC install won't start X - weird behaviour <SOLVED>

[herrMnnn]

This is probably just my noobiness, but I've searched and don't know why this is happening...

Recently purchased a HP thin client off ebay, booted to WinXP embedded, hardware all good

Installed TC to USB via windows installer (on another PC)
Booted HP box to USB, all good, nice clean TC X desktop
Installed TC-install, installed TC to HP Internal flash drive, no errors
Reboot (didn't backup, but doesn't seem relevant) and removed USB drive
Boot goes well, installs extension etc, ....... but no X (huh?)
StartX .... no such thing (or similar response)
reboot, same deal
Reinsert USB drive, reboot, still no X (what? why?)
Format USB drive, reinstall TC (same as original windows installer), reboot from USB, still no X (this is the weird bit)
set bios to only boot to USB, reboot, same result.
repeat, no change,

Any suggestions?

[bmarkus]

Without providing details (TC version number, used WINDOWS installer, ...) do not expect too much answers. Don't expect mind reading capabilities of forum members.

[herrMnnn]

I just assumed everyone would assume I was using the latest version of TC and Windows installer from website (the most logical assumption).  Never expected any mind reading ability.

 

[bmarkus]

Still you are not specifying version number, is it Core, TC or CorePlus neither which Windows installer used.

[herrMnnn]

I did specify TC in the OP, but...

TinyCore-current.iso (so version 4.5.2)

and just assumed that logically I would be using the installer linked from the wiki

Core2usb-1.4.exe

It's just strange that it booted into X fine the first time, yet now only gets to a CLI.  I actually only need a CLI for this project, but I now need to known WHY it's behaving like this...

[Rich]

Hi herrMnnn

StartX

That's   startx , lowercase.

[bmarkus]

In the root directory of the USB stick there is a /cd or a /tce directory?

[herrMnnn]

Solved.  User error/ignorance, as usual....

Adding TCE=sdb1 to the boot code gets it to load X properly from USB again. It must have been finding the TCE directory on sda1 which was faulty, as below.

When I originally installed to the internal drive I mistakenly selected to load extensions from /TCE/optional, rather than /TCE.  Reinstalled to the internal drive with the correct TCE directory and all is good in the world