Beiträge von ITzTravelInTime

    As a small christmas present i released beta 2 for tinu 3.0, it can be downloaded from here:

    https://github.com/ITzTravelIn…releases/tag/3.0_BETA_(68)


    the source code can be found here:

    https://github.com/ITzTravelInTime/TINU/tree/development


    for the changelog, look at the release on github or at the recent commits


    there is also a telegram group for beta testing of the app if you want to join and have a direct contact with me (it's in english only) https://t.me/TINUBetaTesting

    al6042 I have seen you are not of aware of 2 things tinu does by design:

    1) formats the usb drive accordinggly to what is needed to make sure that the inteller will have guid and an efi partition

    2) tinu has it's efi partition tool built in since version 2.1 which is very handy to not have to use other tools


    Mirow302 Be aware of the fact that efi partitions are always completely invisible to the user unless you use a tool made on purpose to show, mount and unmount them

    Tinu uses the terminal method, so if it doesn't work when used correctly, tinu will also not work

    Do not use apfs disks with the 2.X.X versions of tinu because i discovered that this can mess up quite some stuff in some cases (it has already been addressed for the 3.0 version which is still in beta), for tinu just use any regular usb drive, because tinu handles all the format steps required, that said because tinu uses the terminal method, if there is an issue with that, it can't work with tinu neither

    I as the creator of tinu i can confirm that it's not tinu's fault, tinu just uses the terminal method, i think that the problem is somehwere with your bootloader configuration or the bios

    I have to say that TINU is really just an user interface for the terminal method, so it's basically the same thing except for a few checks and eventual format steps if needed, so don't be afraid or scared or to feel like a noob, it's just made to be usefoul and easy to use, and to be the extact same thing as the terminal creation


    speacking of tinu i am working on new versions of it btw, and i plan on adding more usefoul features to make it stand out a little bit, like bulk installers creations, but stuff like those will require time to be implemented, and so it's not something i can implement soon, because i need to rool out version 3.0 quickly

    And after one year i am back, i am working on a new tinu version and i released a first beta of it.


    The new version is the version 3.0 and it's still in developement with a lot fo things subject to changes in future betas and in the fi nal 3.0 release.


    you can find the download for the beta version's binary here: https://github.com/ITzTravelInTime/TINU/releases


    and the source code has been pubblished here: https://github.com/ITzTravelInTime/TINU/tree/development


    changelogs can be found in the github repo with the various commits, one final changelog will be made for the final 3.0 release

    Does E6230 refers to your cpu model like core 2 duo e6230 ? if so you must use el capitan since newer versions requires the sse 4.1 instructions set which is available only in later model of cpus and then you have also to apply a small mod to the mac os instalaltion in order to boot it from a cpu which only has sse 4.1 and not sse 4.2

    You don't have to change the kernel for a vanilla install, but you have to use the proper clover config with all the kernel patches in place, and this is absolutely the best system, and also replacing the kernel is not a great idea since you are going to break various system stuff.


    Thanks for using my app tinu, btw.

    Naja, weil das ganze jetzt auf APFS läuft. HFS+, ja aber da glaube ich musste man wieder was beachten. Da aber APFS der neue Standard von Apple ist, hat mich das nicht mehr interessiert.


    Also mit dem Stick und TINU hatte ich noch nie Installationsprobleme. Kommt dann ganz auf deine EFI drauf an.

    It depends only form the efi folder, the only problems you cn have with a tinu installer are if the installer app is corrupted, but the installer creation managed to be successfoul somehow, or if there is any physical damage on the usb drive, eg: usb drive nto working properly

    Also muss die App 1014.5 auf den Stick, Clover installieren EFI ersetzen und dann TINU aufrufen?

    Das habe ich gemacht - gleiches Ergebnis

    Ich bekomme aber bei Clover und bei TINU die Wahl zwischen (der T61 HDD) und meinem Bootsstick und einer "InstallESD". ich habe beide Male USB gewählt - das war wahrscheinlich falsch. Was ist "InstallESD"?

    Ich habe es probiert: Clover kann auf dem "InstallESD" nicht installiert werden und TINU auf "InstallESD" macht auch keine Änderung.

    Installesd is a component of the mac os installer app, but it's not sufficient, you need the complete installer app for mac os, downloaded from apple servers (with some sripts for example) or via app store (whatchout because in some cases the app store doesn't download the complete mac os installer, but just a web installer of around 20mb, the full blown installer app is about 5-6 gb in size), and then you need to use tinu first to make the base installer drive and then replace the efi folder in the usb's efi partition, and also you don't have to use disk utility first before using tinu.


    In tinu you need to select your target drive first and then lect the full blown mac os installer app you want to use, it will look for it the root of the storage drives, in the applications folder and in the desktop and user's folders. In the picture i don't see the fiull blown installer app so tinu is not going to find it.

    to check if an installer app is "usable" tinu checks just those 3 things: If the createinstallmedia executable inside the app exists, if an app has the info.plist file in the contants folder, if the folder sharedsupport is in place and if it contains the install esd and the base system dmgs and if those are about of the size they should be

    Hallo Willy,
    wenn du ein Videoschnittmonster haben möchtest, dann bist du hier richtig, insbesondere bei apfelnico, DSM2, CMMChris und al6042. grt ist zudem nicht nur extrem kompetent, sondern wohnt auch in Berlin. DerJKM, last not least, kann auch enorm viel!

    Übrigens hat sich in den vergangenen vier Jahren so viel in der Hackintosh-Forum-Szene getan, dass die Einrichtung und Pflege eines Hackintosh inzwischen nahezu mühelos erscheint, auch wegen Sascha_77, der ein wundervolles Tool für die updates entwickelt hat, und wegen des tools TINU, mit dem praktisch jeder einen Bootstick erstellen kann.

    English


    Thank you for appreciating TINU i put a lot of effort in it to make it simple to use

    Puh, also ich erstelle immer mit dem Kommandozeilenprogramm diskutil ein GUID Partitionsschema und eine HFS+ Partition, auf der ich dann mit createinstallmedia aus dem MacOS Installer Paket den eigentlichen Installer erstelle. Ich glaube tinu macht nicht viel anderes, also wäre das keine blöde Idee. APFS ist ab High Sierra das bevorzugte Dateisystem. Wenn du eine SSD hast, kannst du nur umständlich über das Terminal dann in der finalen Installation überhaupt vermeiden, dass deine Festplatte als APFS formatiert wird. Da bei mir selber aus irgendeinem Grund APFS nicht funktioniert, musste ich das auch wirklich so machen mit HFS+. Mein System ist aber mit deinem auch nicht vergleichbar (meins ist ziemlich ungeeignet für einen Hackintosh, deines erscheint eigentlich recht gut dafür gemacht zu sein). Also würde ich dir empfehlen den Installerstick mit HFS+ zu erstellen, auf der EFI Partition mal die Version aus meinem Post und die aus @rubenszy's Post zu testen und im Installer angelangt dann die SSD als APFS formatieren. Schlussendlich dann installieren und dann funktioniert idealerweise schon alles, ansonsten müssen wir dann immer nochmal weiter schauen, woran es immer hakt.

    TINU dev here.


    What TINU does:


    1) format the usb drive if needed, it's formatted in guid and hfs+ journaled (thenusb drive is completely formatted always when it does not use guid)

    2) Operations to avoid most common errors with the createinstallmedia process (like unmounting potentally conflicting partitions and closing potentially conflicting processes)

    3) create a command srtring to execute createinstallmedia correctly depending on the mac os version and the usb drive

    4) executes the command and so it lets the createinstallmedia proccess to start

    5)waits for the createinstallmedia process to finish (the progess bar during this step is poorly cosmetic since the way the command for createinstallmedia needs to handled doesn't allow tinu to read the process output in real time and it will slow up quite a lot the creation process if the progress is determinated by reading periodically the free space of the usb drive)

    6) once the createinstallmedia command has terminated and so createinstallmedia had run and gave us some outpiut, tinu reads this output and determinates if the operation has been successfoul or not, if yes it continues, if not, it displays an error screen and a clue about the possible cause

    7) additional optional operation (basically the stuff in the advanced option menu)

    8 )reset the status of the app to perform other installer creations if the users wants to


    So TINU is just a simpler way to make the base usb installer without clover, and so it's up to the user to install and configure clover properly for it's own machine, so don't blame tinu if the problem is that you are useing wrong clover settings or kexts or whathever

    Also ich weiß nicht was TINU tut, aber Mal angenommen, der macht nicht mehr als createinstallmedia...

    Hi am the developer of TINU


    TINU does basically 4 things: checks the usb driver and if it does not use guid, it formats it hfs+ with the guid partition table, so in that case you loose the entire data stored on the drive, for usb drives which are already in guid, tinu does just format the selected partition to hfs+. The second step is the createinstallmedia phase which is just launching the creatyeinstallmedia process with the right parameters for the installer appm version and the usb drive/partition and then wait for it to end. The third step is to check the createinstallmedia activity one it has ened (because tinu can't read the output of that process while it's running) and to check is everything has worked as expected. the 4th step is to apply the settings from the advanced options section of the app, which inludes an automatic efi folder installer (basically just select the efi folder and tinu can put it in the efi partition for you).


    But the app is open source at: https://github.com/ITzTravelInTime/TINU

    Maybe i can add a feature to auto partition the usb drive into as many installer-ready partition as possible, but making some bulk or automated stuff would require heavy mods to the app, so i don't think i will do it soon, but i think that a viable soulution for the actual appcould be to have an auto partition feature to add as meny installer ready partition as possible or as you want, and then you can put the installers yourself in the partitions using tinu multiple times, but i was thinking about redesigning the drive select screen and the installer app select screen for tinu 3.0 and so maybe adding a multiselect feature for the installer app and an auto format based on how many installers you selected could be good, but this would require also partially reworking the installer creation code to work multple times and to have the format process as a separated and more advanced thing, so there will be a lot of work required, but i can do it.


    And also an installer requires a 7gb partition, so i can optimize it a bit for larger drives and maybe being able to sqeeze more installer partitions, consider also some space needed for indexing and the efi partition, so a good algorithm can get the best out of the space you have, the challenge is to implement this within an app since i have to gather all the needed info and then create an optimized autoformat shell script i can run in tinu, since it uses shell scripts (this is for reliability reasons, and you can also take a look at that in the source code)


    In the meanwhile i am working on version 2.1.1 and so if you have some issues you want to be fixed, please tell me now.