TC on USB-stick

[gerald_clark]

For some strange definition of working.

[jls]

because tc autoscans for a dir called tce

[gerald_clark]

Then rename it yourself.

[jls]

people who just tries tc don't have the time to read corebook.
People try distro with unetbootin and tc doesn't work just because of this cde/tce problem; and most of the time also waitusb is needed.
The modern people which otherwise uses a virtual machine, or the old ones who burn the cd don't suffer the problem

[gerald_clark]

Don't use unetbootin.  Just dd the ISO to the flash drive.
Core is not for people who just want to try it.  It is a toolkit, and people need to learn how to use their tools.

[curaga]

Why should we support a third-party installer? There are lots of them in addition to unetbootin, slippery slope. It's also a known fact unetbootin botches many other distros as well.

[jls]

Unetbootin is the most famous. Maybe we could communicate with the makers to properly handle our distro.

[drtrppr]

So it's a catch 22,  it appears the drive needs a file system and a drive letter for core2usb to recognize it in win8.1 and up, yet if the drive has a file system the utility reports that the drive is not empty..

Ok, so core2usb doesn't work with win8/win10. Guess core2usb isn't maintained anymore, will look into the alternatives (Since the tool gets downloaded a few dozen times a week, a warning line in the wiki seems appropriate? What's the routine with TC?).

[gerald_clark]

With Linux
dd if=isofile of=rawflashdrive

[drtrppr]

In the meantime, try the "rufus" utility from http://rufus.akeo.ie/ .  select your ISO and leave all the default options.  before rebooting to the USB simply change the "cde" directory name to "tce"  (obviously without the quotation marks)
then boot to your USB and select "Tinycore with Wait for USB" option

Seems to work. Booted, installed some apps, rebooted, and aps were still available.

You might also want to remove the copy2fs.lst file within your new tce directory.

Didn't remove it, are there pro's/con's?

[drtrppr]

Hi
To help users, I think there should be 2 isos, one for cd (with cde dir) and the other for usb (with tce dir).

Think would have helped me.

[drtrppr]

ISO9660 is a read only filesystem, so it makes no sense to have a tce directory in it.
Just do a normal install onto the USB drive.

That's what puzzles me a bit, this is exactly what I haven done, didn't I?

[drtrppr]

But in  the end what puzzles me most, why have a core2usb, when you can get things working with rufus(-like tools)? Or is the main thing core2usb does is renaming the directory?

[Rich]

Hi drtrppr

But in  the end what puzzles me most, why have a core2usb, when you can get things working with rufus(-like tools)? Or is the main thing core2usb does is renaming the directory?

The purpose was to have a Windows based tool to install Tinycore to USB and put an end to people using one of the
dozens of install tools out there that don't handle Tinycore correctly.

[drtrppr]

Well, both with unetbootin and rufus i'm able to make bootable usb-stick with TC. Renaming directory cde to tce makes extensions persistent, without doing any further adjustments. Since the recommended core2usb doesn't work in a win8 win10 environment, at least nowadays the non-Core tool seem to me a better way to go.