TinyCore 4.3 boot error

[curaga]

what is the difference between a ISO booted via USB-memstick and an CD-ROM burned one.

These "run from the iso" loop boots do need distro support too to be able to load their own files. As Robert said, please use a supported tool to install.

[wendeloo]

Stop searching for this "error"!

I coult not believe that there shoult be a difference between starting from CD-ROM or loading the same ISO image from USB stick. But it must be so. I burned a CD-ROM, connected some "hardware stuff", inserted and booted the CD-ROM, and VOILA! tinycore greets me with a X GUI.

So, I must say: I'm very sorry to waste your time. But one question is still in my head: Why is the USB stick booting the ISO image with "50%"? It must have to do with the new data structure while with older releases this behaviour was not seen. No matter: I can go further with my project if the other questions are solved. Once again: Thank you all!

[gerald_clark]

If you raw copy the CD iso to the USB stick, it will boot just like a CD.
The problem is with USB boot loaders that try to loop mount an iso file and boot it.
Core does not know about the trick, and when it reads the USB stick, it sees the iso file, not the
mounted contents of the iso file.

[bmarkus]

There is a dedicated installer core2usb for Windows which knows the TC tricks:

http://sourceforge.net/projects/core2usb/

Also, USB installation is described on the TC WEB and in the WIKI:

http://distro.ibiblio.org/tinycorelinux/faq.html
http://wiki.tinycorelinux.net/wiki:install_usb_win

It is good to read manual in case of trouble.

[beerstein]

HI:
Here is what I think might be the problem. If I am wrong pleae correct me:

I assume that you still have a /tce somewhere on your hard drive and an older mydata.gz
which holds the older config files (onboot.lst and bootlocal) where the new extensions from the 4.2; 4.3 Live CD are not listed.
The new 4.X live cd has a new /cde folder with extensions to be placed onboot.
I had a similar problem.  So I copied the /cde/optional content into my old /tce/optional and added the content of /cde/onboot.lst into my older /tce/onboot.lst

Having done that - my system did not get stuck in cmd line any more. It booted ok into the wm.

[wendeloo]

Thank you for your supports again.

Definitive I do NOT have older data on my fresh, clean, virgin hard disk (that's a fact).

I agree with Gerald, that the loop loader produce the problem. Unfortunately the problem doesn't appear with TC 3.7 or TC 3.8.4 (I added the TC 4.3 to my stick ... and the rest of the story fills this thread).

@Markus: You're right, documentation is a good chioce But imagine that two ISOs do the job but a third one did not (same stick, same environment, but other versions). And additionaly notice: The thread started with the same problem by an other member.

Hope others have also learned something from that.

[curaga]

I agree with Gerald, that the loop loader produce the problem. Unfortunately the problem doesn't appear with TC 3.7 or TC 3.8.4

TC 3 did not need to access the cd at all after boot.

[sadistic_angel]

ok so i googled this problem when i ran into it with 4.5 and YUMI. so i joined to post the solution i found.


first both the boot and cde folders from either the iso or if its already on your drive from \multiboot\tinycore need to be in the ROOT directory of your flash drive/HDD

next \multiboot\menu\tinycore.cfg needs to be the same (you can just copy paste) as whats inside of \boot\isolinux\isolinux.cfg

and taa daa! all done! you now should be able to boot with a GUI!