1 post in this topic
Recently Browsing 0 members
No registered users viewing this page.
Hi guys, this thread is to show you a new and open source app, created by me, that I called TINU:
The name means: TINU Is Not #####, the U refers to a popular software that is used to create macOS hackintosh installers (that for good reasons is banned on this forum), but the aim of the name is to explain that this app is a totally different thing from that software and works in a totally different way.
This app basically is a graphical interface for the createinstallmedia executable that is inside the macOS and Mac OS X installer apps, it is capable to create a bootable installer completely vanilla like what you do using the command line method, and also this method is recommended by apple itself. In addition to this, this app provvides to you simplicity and flexybility, and lets you to avoid most of the steps needed with every other app.
TINU allows you to create easily a bootable macOS installer without messing around with command line stuff and without using disk utility, all you need to do is use the app and then install clover on the usb drive once TINU has finished or leave it as is if you want to use it on a real Mac.
- Simple-to-use UI that allows you to easily start the bootable macOS installer creation process.
- It can work with every macOS installer app that has the createinstallmedia executable inside its resources folder (including also beta and newly released installers).
- You can use any erasable volume that is at least 7 GB of size (if the volume's drive is not in GUID format, TINU will re-format it accordingly).
- Can work with the Mac OS recovery system, so you can create a bootable macOS installer from the macOS installer itself or from the macOS recovery partition, and you can use TINU to install macOS, too.
- 100% clean: The bootable macOS installers created with this tool are vanilla, just as if you created them using the command line "createinstallmedia" method in Terminal.
- Open Source: You can verify what this program does on your computer and you can create your own version by downloading and playing with the source code.
- Does not require any special preparations. Just open the program, make sure you have a USB drive plugged in and have a macOS installer app on your disk.
- No need to use Disk Utility. TINU can format your drive or partition for you.
- Integrated EFI partition mounter tool.
- Uses recent, modern, APIs and SDKs and the Swift 3 language.
- Transparent graphics style available (type alt-S or choose from the menu bar: View -> Use transparent style).
- Works using the latest versions of macOS and will also support newer Mac installers out of the box without requiring an update.
- Offers advanced features to customize your bootable macOS installer.
Features that are planned for future versions:
- Install and configure [Clover](https://sourceforge.net/projects/cloverefiboot/).
- Install kexts into Clover's kexts folder.
- Clover drivers customization
- Use custom DSDT in Clover
- Integrated pre-made Clover config templates database from a remote and open repository.
- Support for other languages, at least Italian.
- A computer that runs Mac OS X Yosemite or a more recent version (Mac OS X El Capitan is required to use TINU in a macOS recovery or installer).
- A drive or a free partition (on a drive which already supports GUID) of least 7 GB that you want to turn into a macOS/Mac OS X installer.
- A copy of a macOS/Mac OS X installer app (Maveriks or newer versions are supported) in the /Applications folder or in the root of any storage drive on your machine (excepted the drive or volume you want to turn into your macOS install media).
Frequently asked questions:
Thread (english) on insanelymac.com:
Thread (italian) on insanelymac.com:
Thread (english-german) on hackintosh-forum.de:
Post on Reddit:
Facebook hackintosh help and beta testing (Italian only):
Contact me (project creator):
- Insanelymac.com profile: http://www.insanelymac.com/forum/user/1390153-itztravelintime/
- email: firstname.lastname@example.org
- This software is under GNU GPL v3 license so any new branch/mod/third party release must be open source and under the same license
- I (project creator) assume no responsibility for any use of this app and this source code, and also for any kind of hardware and software damage to any computer and any device or peripheral that may come from this app or source code during it's use and outside it's usage
- I (project creator) do not guarantee support to you, this is only an open source project, not a product released by a company!
- This project is born only for educational and demonstrative purposes, it's not intended to be used for commercial purposes and it will never be, don't use source code from this project to create apps or software for that aim.
- This is a no-profit project, born only to let people to create macOS install medias in a more simple way and also to learn how to create this kind of apps.
- Apple for macos and installer apps and scripts
- People that helped me a lot:
Francesco Perchiazzi, Nicola Tomarelli, Roberto Sciortino, Raffaele Sonnessa, Ermanno Nicoletti, Tommaso Dimatore, Michele Vitiello Bonaventura, Massimiliano Faralli, Davide Dessì, Giorgio Dall'Aglio, Peter Paul Chato.
- Special thanks to Italian Hackintosh group!! for help (https://www.facebook.com/groups/Italia.hackintosh/?fref=ts)
- Thomas Tempelmann for help with the UI
- Pietro Caruso (ITzTravelInTime) for creating, maintaing and developing this project
I have a Mac mini server with Yosemite, and I plugged a VGA Display using a VGA/HDMI adapter.
The issue is, when I shut down or restart the server, the display is not recognized, then I need to go to unplug and plug again, and server now recognizes the display.
I need to know how to make a logical "reconnection" for the adapter.
For example on Windows I use a devcom application to enable or disable the devices.
I was reading that the possible solution is using a kextunload command on terminal.
I don't know which kextfile I need to "unload" for the HDMI adapter.
Anybody have an idea about my issue? Another way to solve it?
Thanks in advance
Greetings from Mexico.
By Col Crunch
Ok, so I am not sure if this is the best place for this post, but from the descriptions of the categories, it seemed to me to be the most fitting.
Anyways, on to the topic of the post:
The command key; an incredibly uncomfortable key to use, for me, and with the frequency in which I move between windows and OS X, it is just inconvenient to have to get used to the physical difference that often.
So, what I am looking for is a way to remap the command and control functions to the inverse keys, except in terminal (where Control+C is still Control+C). This would obviously have no affect on shortcuts that use Command and Control at the same time as I would be pressing both keys regardless (yes, someone on another forum, actually tried to tell me that this is a reason that such a remap would be a bad idea).
Doe anyone out there know of an application that will let me do this.
P.S if your response is "Just get used to it", please keep it to your self. I am obviously looking for this solution specifically so I don't have to sit there and be uncomfortable, and so that I can be more productive.
More info at: http://www.thegroovykosak.blogspot.pt Here is a video I made demonstrating the procedure. https://www.youtube.com/watch?v=04SLD2Kft60 Download your distro of choice, in my case Ubuntu Gnome edition Once that is done, use the command that follows to convert the iso to img: hdiutil convert -format UDRW ~/path/to/target.iso -o ~/path/to/ubuntu.img Note: OS X tends to put the .dmg ending on the output file automatically, delete the ".dmg" ending. Run diskutil list to get the current list of devices Insert your flash media Run diskutil list again and determine the device node assigned to your flash media (e.g. /dev/disk2) Run diskutil unmountDisk /dev/diskN (replace N with the disk number from the last command; in the previous example, Nwould be 2) Execute the following command while replacing /path/to/downloaded.img with the path where the image file is located; for example, ./ubuntu.img or ./ubuntu.dmg). sudo dd if=/path/to/downloaded.img of=/dev/rdiskN bs=1m Using /dev/rdisk instead of /dev/disk may be faster. Run diskutil eject /dev/diskN and remove your flash media when the command completes Restart your Mac and press Alt while the Mac is restarting to choose the USB-Stick or restart your PC and choose the USb from BIOS. This USB should work for any computer. Note: (If you see the error dd: Invalid number '1m', you are using GNU dd. Use the same command but replace bs=1m with bs=1M. If you see the error dd:/devdiskN: Resource busy, make sure the disk is not in use. Start the Disk Utility.app and unmount (don't eject) the drive. )
Thanks for watching
I set up a new X99 workstation based on the Intel i7 5960X a few months ago and Yosemite works very well on it. Except of a "small" part I normally use heavily in my daily workflow: The Terminal
Here is a descriptionof the problems I detected (maybe more are hidden but due to the problems I encountered I rarely use this workstation for development and fall back to my MacBook or my old Hack for now).
The architecture of the system seems to not be recognised correctly. When I try to install homebrew I get an error that it doesn't find the target platform. So I tried to look at uname and found that it doesn't show the current kernel or anything:
x99:~ me$ uname -a x99:~ me$ Same strange behaviour goes for find (in my home with quite a few folders and files):
x99:~ me$ find . x99:~ me$ After wondering about this I started zsh and tried both commands:
f35% find . zsh: exec format error: find f35% uname -a zsh: exec format error: uname What can I think of this? Any idea hear?
I can't really imaging what went wrong there and why everything else works. I can throw different image/video apps up and haven't had problems yet. It's only on the Terminal where I'm not sure what's going on and normally I'm quite often using the Terminal as a long time Linux/*nix user and do many stuff with small scripts and use homebrew to install a bunch of tools also.
Installation was done with a modified Kernel and a few modified extensions to get it running on the X99 platform.