![]() For instance to stop somebody from getting iWork for free on old hardware. Or maybe Apple has found one more point of control they want to enforce on us by making sure each computer is running the version of OS it should be running. This could be a one time problem and 10.9.2 may (we can only guess) pull things together. The point is neither update runs on the the computers running the 2093 image if they are the wrong hardware. My computers that are non-MBPr from this year with 2093 on it do not see the 10.9.1 update, if you try to install the 42 version it says you need to have OS 10.9 installed and if you try to install the 3116 update it says wrong architecture or something like that. FYIĪgain the only problem may be that when 10.9.2 comes out it may not install on a non 2013 MBPr that has a build version of 3116 and you wont know that until the day it comes out. update supposedly includes all the 10.9.1 stuff plus the additional bits for the retina I figured that this would work and it does. I put the 2012 MBPro into target disk mode, and applied the 10.9.1 RETINA upgrade to the 2012 MBPro via the 2013 retina. Upgraded that one to it's version of 10.9.1 Then I cheated. Took a 2012 13" MacBook Pro (non-retina) running a base for my. I took a 2013 late MBPro retina (13") with a fresh OS. My new nbi universally boots all mac's capable of running ANY form of 10.9 nbi with Casper Imaging 9.22.įYI, just verified. So please understand that I've created a universal 10.9.1. nbi's can be created easily for any model of mac and just as easily, automatically assigned to such a group). There are plenty of great ways NOT to have to do this. For this one, I've decided that I'm going to make a universal. nbi and a mostly universal base OS package. because I am a glutton for punishment I do prefer to have a universal. BuildingĬlone the repository and open the project file located in Disk Inventory X 1.0 src/make/src/Disk Inventory X.xcodeproj and then hit CMD+B.Well. The Xcode project file is no longer compatible with contemporary versions of Xcode so I had to manually copy the header files, which was ok because they were only a handful. There's no need to go hunting in all the folders to extract the headers, just go to the target settings > build phases > headers: Fortunately, it didn't change much, and I was able to extract the header files and integrate them with the prebuilt version of the framework that was distributed with DIX. ![]() OmniGroup has kindly made available their source repo, but it goes back only as far as 2009. I did have to modify them slightly, but overall it was easy. Took the generated headers and placed them inside the framework bundle in the Headers folder. Feed it a framework bundle and it will output a header file for each class it finds along with the correct methods and members. ![]() Luckily, there's a tool called class-dump that came to the rescue. This has proved most annoying as I haven't been able to find versions of the Path Finder SDK from the same epoch as DIX and the contemporary SDK is incompatible, in the sense that it's wholly different. Therefore, I extracted the prebuilt frameworks from the Disk Inventory X.app bundle and recreated the headers as follows: CocoaTech Even if the source code was available, compatibility problems between early versions of Xcode (2.x) and the latest Xcode (7.2) would make it troublesome to compile. Except for TreeMapView which is provided by the original author, finding the source code for the other two proved difficult. The main problem in fixing this was that DIX relied on three main external frameworks: OmniFramworks, CocoaTech and TreeMapView. Setting the NSNumberFormatter behavior to NSNumberFormatterBehavior10_0 results in the correct values: This new behavior would cause DIX running on OSX 10.4+ to format the volume sizes incorrectly, for example my 465.6 GB HDD was being displayed as 4,65.6GB: Since DIX 1.0 was written, OSX APIs have continually changed and one of them was the introduction of new behavior for NSNumberFormatter in OSX 10.4. If you've ever wondered where all your disk space has gone, Disk Inventory X will help you to answer this question." It shows the sizes of files and folders in a special graphical way called "treemaps". There are many alternatives available, myself personally I use Disk-Inventory-Xįork of Disk Inventory X with the correct volume size formatting and rebuilt external frameworks headers.Īs the original author states, "Disk Inventory X is a disk usage utility for Mac OS X 10.3 (and later). This repository was just an exercise to revive the ancient code base of Disk Inventory X but the compatibility issues with newer OSXs make it unusable. ⚠️ Attention! This application is no longer supported! ⚠️
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |