Maxxuss has done it again by posting patches for the newest OS X 10.4.5 which allows non-Apple branded x86 machines to run the operating system. Before anyone attempts to upgrade to the latest version, there are some open issues that must be taken into account:
- Darwin kernel has been updated from 8.4.1 to 8.5.1 in OS X 10.4.5. This won’t affect Mac owners but it does affect everyone attempting to run OSx86 on non-Core Duo hardware. The most notable change is 8.5.1 drops support for general Intel power management and the LAPIC timer. In leu of that, the new kernel now only supports Intel Core Duo enhanced power management and its HPET (High Performance Events Timers) facility. To address this, the latest Maxxuss Patch Solution v1.0 for 10.4.5 uses the older 8.4.1 kernal until the power management code can be reinserted into a modified 8.5.1 kernel.
- AMD CPUs show some instability while running iTunes. Maxxuss is attempting to look into this matter.
- The install procedure is still very involved and prone to errors if not followed properly. Maxxuss and others in the community have already attempted to create a patched 10.4.4 Restore Disc in an attempt to address this issue. Unfortunately, the results aren’t showing the same level of success as following the the list of instructions posted on Maxxuss’ site.
- DVD playback is not 100% working yet.
The hiccups of the past few days involving DMCA threats and the unavailability of Maxxuss page has not hampered progress on the OS X x86 hacking front. On the contrary, it is continuing at a hurried pace which means that resolutions to the last few remaining issues aren’t too far off.
This does not mean Apple has given up fighting piracy of it’s operating system through direct intimidation tactics. Robert Braun, a developer involved in Apple’s open source efforts, wrote a column today that suggested Apple has been hampering releases of certain core components back to the community. He basically declares Apple’s open source efforts dead. Could this be another front in Apple’s war against the enthusiast community trying to get OS X working on white-box systems?
Update (3.2.2006): Maxxuss has fixed the iTunes problems on OS X 10.4.4 and 10.4.5 for AMD CPUs in Patch Solution 1.0a.
Update (3.4.2006): Maxxuss has a new domain. Update your bookmarks.
If there are any other new developments, don’t hesitate to shoot me an e-mail or dropping a comment below. I’ll post updates as this story develops.
As always, I don’t condone piracy so please don’t do anything illegal.
Serious Wheels posted preliminary pictures of the 2006 Koenigsegg CCX. For those that don’t know why this is significant, the predecessor of the CCX was the Koenigsegg CCR which held the top speed world record until the Bugatti Veyron spectacularly trumped it. The CCX should now be a contender to retake the title which means that car enthusiasts are in for a treat. For now there is very little information on this car so expect a few updates to this post.
Update (2.23.2006): David’s blog has links to the brochure of the CCX. According to the brochure, I have to agree with David’s conclusions that this is just a face-lifted CCR. I’m waiting for a full press release which should clear up everything.
I tend to install and reinstall operating systems quite frequently on my home system. With my hectic schedule, I don’t have time to sit down to reinstall and configure every last program. Although it is arguably easier to use a backup of my system for day-to-day mishaps, I tend to change out peripherals a lot and restoring a system that does not have certain drivers “cleaned out” tends to wreak havoc on a new configuration. To make this process go a bit faster, two years ago I created a “Ghost Image” of my hard drive after doing a basic install. Now, instead of it taking a few hours of toiling away to reinstall a system, I can do this all in about 15 minutes with only half a dozen quick mouse clicks. The trick is to use Norton Ghost or any other imaging software and Microsoft Sysprep.
Part 1: Install XP and Sysprep
- Install Windows XP on a clean hard drive.
- Do not install any drivers or other utilities that are hardware specific beyond what Windows itself installs.
- This is necessary to make sure the image is as portable as possible across different types of systems. However, different storage controllers and different HALs (Hardware Abstraction Layers) make this harder to predict.
- Most modern computers these days work fine with a standard ACPI HAL, but if this image is to be truly portable across multiple machines then it must be determined which specific HAL will be needed. Refer to Microsoft KB309283 if you are completely lost.
- It is also important to determine if the target system uses a storage controller that normally requires a driver disc during a regular XP install. If this is the case, then the necessary paths to the drivers must be included in the Sysprep.inf file. These must be added to the
[SysprepMassStorage]section in the form
PCI\VEN_###&DEV_#### = PATH_TO_DRIVER_ON_IMAGED_DRIVEwhere VEN_#### should be replaced by the Vendor ID number (i.e. VEN_1234) and the DEV_#### should be replaced by the Device ID number (DEV_1234). This information can usually be found in the specifc driver INF files. Here is an example for adding the VMWare SCSI controller driver to
….snipped out windows mass storage driver list….
testuseraccount with administrative privileges. Use this account to install and configure all the software and policies on the system.
testuseraccount to the
Administratorstart menu. (Note: This is necessary as some installers do not create start menu items in
All Usersbut within the
testuserprofile only. This leaves some items missing on the
c:\Documents and Settings\Default User. If you don’t understand then refer to Microsoft KB291586.
testuseraccount. Make sure that
c:\Documents and Settings\testuserhas been deleted too.
sysprep.inffile by running
setupmgr.exe. This a tool Microsoft provides for creating an answer file so the restore doesn’t involving asking the normal setup questions. The basic steps are below:
- Run setupmgr.exe
- Click Create New
- Click Sysprep Setup
- Then choose whichever product you are using. In our example it would be XP Professional.
- The next question asks: Do you want to fully automate the install? All this question determines is who is going to accept the EULA, you or the person restoring the image. Also, picking yes means that you must enter your Product Key. I pick no because this is for my own use and I don’t want someone to swipe my Product Key accidentally, but a large company or OEM may choose differently.
- The next few sets of options are for you to enter in any information like your Name, Organization, Time Zone, Product Key (I leave this blank), Network Settings, etc.
- I leave the Computer Name option set to Automatically generate computer name.
- Once completed, a dialog box will ask where you want to save the file. c:\sysprep\sysprep.inf is the path we’re using in this example.
- On the completion screen, click Cancel to close
The process of creating a basic
sysprep.inf file is now completed.
c:\sysprep\sysprep.infin Notepad and add the following lines to the relavent sections (if the heading doesn’t exist, create it):
sysprep.infyet! OemPNPDriversPath points to the
c:\driversdirectory created earlier. For organizational purposes, I split up my custom driver files based on category (i.e. hardware_cat in the example above). For example, all video drivers go under
c:\drivers\videoand network drivers under
c:\drivers\network. In each of those directories, the specific driver bundles are placed with their driver inf files (i.e. driver_dir). For example, the latest nVidia drivers would go into
c:\drivers\video\nVidia\. The last part is refering to
driver_infis just that, the name of the inf file. For example, for the latest nVidia driver, the path would be
sysprep.inf, the path would be written as
OemPNPDriversPath=drivers\video\nVidia\nv4_disp.inf;. Do not forget the semi-colon as a separator. For the next driver, repeat the procedure by placing the path after the semi-colon without leaving a space. Once all the drivers are added, save the file.
c:\sysprep\sysprep -bmsd. This will build the Windows XP standard mass storage drivers section.
InstallFilesPathwhich usually points to
c:\sysprep\i386. I usually copy the contents of my XP CD's i386 directory into
c:\sysprep\i386. This isn't necessary.
[SysprepMassStorage]section as detailed above.
Sysprep is now complete. Part 2 discusses imaging.