- Joined
- Nov 4, 2011
- Messages
- 677
- Motherboard
- Gigabyte GA-Z170X-UD3 F23g
- CPU
- i7-6700K
- Graphics
- RX 580
- Mac
Hi @headkaze, once again from my side, this time with a modification suggestion to your Hackintool that I consider to be quite useful and actually begin falling in "love" with. 
Background.
When one runs "Rebuild KextCache and Repair Permissions from within Hackintool -> "Installed", everything works as expected, with the required routines being executed, as one was hoping they would, with the blue progress bar providing feedback when execution of these commands seem to have completed. However here lies a snag, to me at least, and that is whether the commands actually completed successfully or not.
Try this as a test.
Take the USBPorts.kext and modify the first line, which for the lack of a better word I will call "shebang" as is customary when scripting in a linux and even macOS terminal, and "destroy the required pattern" of that first line by placing a plus sign, or any other unwanted character, anywhere on that line as per this insert "+<?xml version="1.0" encoding="UTF-8"?>" . Now run "Rebuild KextCache and Repair Permissions from within Hackintool -> "Installed" and wait until you think, command execution completed. Then go into terminal and run "sudo kextcache -i /" and you will notice that the "exception" list has not been created "error free" something that one is not being told by Hackintool. I suggest a small command completion feedback routine, added to an upcoming release of Hackintool, should go a long way to prevent any doubts around this when using Hackintool to "Rebuild KextCache and Repair Permissions"
Greetings
Background.
When one runs "Rebuild KextCache and Repair Permissions from within Hackintool -> "Installed", everything works as expected, with the required routines being executed, as one was hoping they would, with the blue progress bar providing feedback when execution of these commands seem to have completed. However here lies a snag, to me at least, and that is whether the commands actually completed successfully or not.
Try this as a test.
Take the USBPorts.kext and modify the first line, which for the lack of a better word I will call "shebang" as is customary when scripting in a linux and even macOS terminal, and "destroy the required pattern" of that first line by placing a plus sign, or any other unwanted character, anywhere on that line as per this insert "+<?xml version="1.0" encoding="UTF-8"?>" . Now run "Rebuild KextCache and Repair Permissions from within Hackintool -> "Installed" and wait until you think, command execution completed. Then go into terminal and run "sudo kextcache -i /" and you will notice that the "exception" list has not been created "error free" something that one is not being told by Hackintool. I suggest a small command completion feedback routine, added to an upcoming release of Hackintool, should go a long way to prevent any doubts around this when using Hackintool to "Rebuild KextCache and Repair Permissions"
Greetings
Last edited:
.
