WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: TinyCorePure64 only in uefi mode  (Read 389 times)

Offline bausi

  • Newbie
  • *
  • Posts: 1
TinyCorePure64 only in uefi mode
« on: December 02, 2021, 07:49:05 PM »
Hi everyone
I been looking for a tutorial that can help me to make an only uefi live system of tiny core pure 64 but only found 2 that make a dual uefi/legacy live system
I tried both but I can’t make it work because I’m very new at tiny core and can’t understand perfectly both tutorials
There’s a way to make only uefi live system of tiny core?


Offline gadget42

  • Full Member
  • ***
  • Posts: 103
Re: TinyCorePure64 only in uefi mode
« Reply #1 on: December 02, 2021, 11:44:17 PM »
at the present time, a search for the terms "uefi TinyCorePure64" has 41 results with yours showing up first in this search.
(although this post might also create another additional search result)

for our own benefit, are there any particular posts and/or threads that are specifically confusing?

Offline PDP-8

  • Hero Member
  • *****
  • Posts: 884
Re: TinyCorePure64 only in uefi mode
« Reply #2 on: December 10, 2021, 03:52:37 PM »
I'll take another stab at it from a different perspective that might help.

Just getting TC to boot properly on modern 64 bit uefi machines is only *part* of the issue.  Discovering what makes TC so special and if it is /right for you/ is the second part - but if you can't get it to boot in the first place without specialized prior knowledge it can become too frustrating.  I understand.

So here is a leg up to see if TC is right for you - it is much more than just being able to boot.

1) Assuming you have a modern machine, that means windows.  I highly recommend using YUMI-UEFI or later to create the bootable usb stick with the latest 64-bit TinyCorePure64 with "Try Unlisted Iso".  It will take it's time analyzing the tc iso, so don't fret too early if it appears nothing is happening.

Unlike some other methods, the way that Yumi-Uefi handles it, it most closely resembles the very early ideals and simplicity of booting a read-only CD going back to the dsl days.  That is, it will properly detect and use the CDE directory for the minimal graphical UI.

Unless you take alternate steps, nothing is saved, and everything is pristine again upon reboot.  This is by design, since for some this is all they need / want.  This was known as the "Internet / Cloud Mode", whereby one starts out with a small system, and builds up *temporary* systems of additional capabilities if they so desire.

This is fertile *training ground* to go beyond the mechanics of simply getting TC64 to boot onto hardware.  In the past, users were not required to know how to build their own El-torito bootable isos.  They were escorted directly into the USER capabilities of TC.  Currently Yumi-Uefi will provide this same capability on modern machines with usb sticks.

This training ground of TC usually involves getting to know how to add or modify the grub boot options when you eventually see it.  Here, you can specify a wide variety of things, such as screen resolution and a whole host of options to the kernel parameters.

Going beyond the "cloud / internet mode".  When you want to make automated saving of files, and other infrastructure to turn TC64 into the next Ubuntu-rival (grin), one has to know how to save their work and where to direct it.  The the options for doing this are many and are user-specific.  No installation of TC64 needs to be the same.  Discovering these options and how they work, and what makes TC more of a "toolkit", rather than a mere bootable distro becomes apparent.

This is a very long way of me saying that just knowing how to make TC64 "bootable" by using DIY methods is for most, a mere technical "one-off" exercise that when finished, does not by itself reveal what makes TC special.

So, the most convenient way to jump beyond this technical exercise, and see if the way TC *OPERATES*, is to perhaps whip up a bootable stick with Yumi-Uefi (try unlisted iso), kick the tires, and just know that there is MUCH MORE to discover from a user-standpoint - which may actually not be to the liking of some since much of it isn't always automated, or have more than one solution to the problem based on individual desires.
That's a UNIX book! - cool  -- Garth