Hi Janek202. As per "Please report me any bugs or ideas for new features" (I did NOT read through the pages, so a duplicate submission is well possible), here's some *constructive* feedback:
- when installing new kexts to E/E, as of now the mkext there does NOT get rebuilt automatically. I basically consider this a bug because it might lead to the kext which got installed to E/E and is not included in the mkext might not get loaded correctly. So now, after installing kexts to E/E, one has to click onto Maintenance, activate 'Extra/Extensions', rebiult mkext. Those extra steps should not be necessary. It would be great if you could fix that. If there is some kind of pro for not auto-rebuild E/E mkext, then please at least ad an option field "Auto-Rebuild mkext", which is *activated by default*; whoever does for some reason *not* want the mkext rebuilt can toggle it off.
- please have "Backup kexts that will be replaced" *activated* by default! In times of terrabytes HDs, looking at the tiny size of almost all kexts, and noting the security aspect of backups in general I don't see *any* reason why this option shall not be active by default. Thank you
- again regarding kext backups: when I first utilized your tool I was totally startled because even though I had ticked "Backup kexts that will be replaced" I did not find them! I installed to a different volume, and after booting into that volume and realizing I had to restore one kext, first looked into the extension folder there, being used to Kext Utility's approach to simply rename existing.kext --> existing.bak. Then I remembered having read something about a folder 'Kext Backup' being created. Analog to what Kext Helper (and I think OSX86Tools) used to do, I looked on / of the volume to which I had installed kexts to, but to my disappointment did not find any like folder there. After finding and reading your ReadMe I was very amazed that the default backup path is the Desktop of the user account one installed FROM, not the / of the volume on installs TO. That is very awkward, esp. if one installed from as root user (...), and also makes much less sense than backing up to the actual volume. Reason is evident I dare say: when, after running an install for a while, one realizes one has to revert to an older kext, it would be easy to do so just looking on / of that particular volume. The backup on the desktop of some user folder (which might even be on a completely different computer if one installed to a USB volume .....) might simply not be retrievable anymore.
Right now I "jerryrig" by, after installing kexts to another volume, MANUALLY creating a folder "Kext backup" on / of that volume, then copy the appropriate date/time folder into folder I created on the other volume.
Again, if there is some pro of choosing the current desktop as backup, then, instead of ONE line "Backup kexts that will be replaced" you could change that to "Backup kexts that will be replaced to / of destination", and a 2nd line "Backup kexts that will be replaced to current Desktop". Not too much space lost there, but a highly usable feature addition. And PLEEAASE
, make "Backup kexts that will be replaced to / of destination" active by default
- after installing kexts to S/L/E, the option button jumps back onto E/E. Why? That's confusing because (esp. late @ nite ..
) I can make one doubt if one really chose the correct destination. This can be considered a bug. I think similar with "Target Disk": if one has chosen "S/L/E" and then changes the target disk, it jumps back to to E/E. But I am not sure about that right now (am not writing from OS X so cannot test)
Other than that, awesome tool! Makes deploying h'tosh soooo much easier (and I bet Hagar hates it because he kept on deleting my postings back then when I asked for exactly what you coded, labeling my requests 'forum spam' and eventually even blocked my account - and now look at the popularity).
Thank you Janek - RESPECT!