|
|
Post by ritalin on Dec 2, 2007 7:59:05 GMT
|
|
|
|
Post by aquamac on Dec 2, 2007 9:57:15 GMT
Saw this earlier, but get an error when I try to download it! Any chance you can email it to me if you have it?
|
|
|
|
Post by nikonnut on Dec 2, 2007 18:50:51 GMT
Rit, Excellent news! My G4 has purpose again  Leo here I come! Cheers, Nik |
|
|
|
Post by ritalin on Dec 2, 2007 19:39:31 GMT
Rit, Excellent news! My G4 has purpose again Leo here I come! Cheers, Nik Well its all theory at the mo, and I still haven't successfully booted my hackintosh from a APM hard drive. Good luck. |
|
|
|
Post by ritalin on Dec 2, 2007 20:13:14 GMT
Making some progress...  |
|
|
|
Post by aquamac on Dec 3, 2007 21:33:46 GMT
Ritts,
I can't believe it! Is that Apple Partition Map on a Hackie! If so, that is amazing! ;D ;D
|
|
|
|
Post by ritalin on Dec 6, 2007 20:38:35 GMT
It certainly is my hackintosh running on a APM drive.
The next trick is to get my machine to boot from my firewire hard drive. So far I haven't been successful. The problem is my cheap ass motherboard doesn't support booting from firewire in the BIOS. I've tried booting a from internal hard disk using the darwin bootloader, then redirecting to the firewire drive, and it nearly works, but then I get a kernel panic while loading OSX from the firewire drive.
I can boot fine from USB, and have successfully installed a minimal OSX system on a 4 Gig memory stick. I have also cloned my preferred "Mac OS X Install Disc x86" (JaS 10.4.8) onto a memory stick. This has dramatically reduced the time it takes to perform a clean OSX Install. Sod DVDs, Apple should ship Leopard on memory sticks.
I have found a compatibility problem with my old JaS installer and the new PC_EFI bootloaders. If I do a clean install onto a PC_EFI enabled volume (be it MBR, APM or GUID) it will not run. This is because the JaS install places AppleEFIRuntime.kext in the extensions folder (and AppleEFIRuntime.kext no worky on my system). So I have started to create my own custom installer for Tiger that is PC_EFI aware, and while I'm at it I may roll 10.4.11 into it, and include the hacks required for my system (NVinject etc). All a tad late as I will probably buy myself a copy of Leo in the new year.
|
|
|
|
Post by ritalin on Dec 6, 2007 20:54:00 GMT
and another thing.
If I boot from the JaS Install, then try load a previously installed system that is set up for PC_EFI, you guessed it, the system crashes. Just one more reason to make my own PC_EFI Tiger installer. If someone can save me some time and point me to a Tiger install that meets my requirements that would be great. I've looked but It does seem like the world just forgot about us Tiger hackintosh users.
|
|
|
|
Post by ritalin on Dec 6, 2007 22:49:20 GMT
I've made version #1 of my Tiger installer-
Will install a working system to a PC_EFI enabled volume
Working Realtek R1000
Working NVinject
Still to fix-
Sound (I forgot to remove AppleHDA)
10.4.11 update
Update the installers bootloader to PC-EFI
|
|
|
|
Post by ritalin on Dec 8, 2007 19:25:25 GMT
The Hackintosh Bootloader (GUID or FDisk partition schemes)
boot0
Is what would typically be placed in the boot code section of your MBR for a darwin-only system. On some system, It may not be installed and an alternative primary boot manager (which has it's own boot code) such as LILO may be used instead.
boot1h
Goes in the bootsector (first .5KB) of an HFS+ partition, and has enough code to parse an HFS+ volume header, find the extents associated with the "HFS+ Startup file" and load it.
boot
Boot is what is referred to by the Startup File extents for an HFS+ volume. This is the second-stage loader which is in charge of presenting the list of bootable volumes, and if applicable, loading a kernel + extensions from the filesystem. (cdboot is a modified version of boot for use on CDs.)
For a standalone single-partition HFS install, you would ideally have:
A) boot0 - in the MBR, or LILO or GRUB
B) boot1h - in the first 512-bytes of the HFS+ partition
C) boot - pointed to by the HFS+ Startup File
This can be achieved using the CLI of OSX. You will require the startupfiletool and the appropriate boot0, boot1h and boot files (all of which can be found on the WEB). Since we will be writing to the MBR of our disk, and the bootsector of our desired boot partition, we need to boot from an alternate disk (such as the install DVD). Also, every partition of the desired boot disk needs to be unmounted.
To install boot0 in the MBR-dd if=/path/to/file/boot0 of=/dev/diskX bs=400 count=1 To install boot1h in the bootsector-dd if=/path/to/file/boot1h of=/dev/rdiskXsY bs=512 count=1 To set the HFS+ Startup File-/path/to/file/startupfiletool /dev/rdiskXsY /path/to/file/boot (Note: Replace /path/to/file appropriately. It is conventional to install boot0, boot1h and boot /usr/standalone/i386/. Replace X and Y with the appropriate disk/partition identifiers.)Most of the above was copied from various places around the WEB. I think its accurate, no guarantee though. 
|
|
|
|
Post by ritalin on Dec 8, 2007 19:36:58 GMT
In addition if you are using a FDisk partition scheme then you must set the boot partition of the disk as active. Setting Your Partition "Active" Using Fdisk
Words in bold below are things you must type (followed by Enter).
1. Boot your Mac OS X install dvd
2. Once the installer is running, go to the Utilities menu and open Terminal
3. Determine which disk your MacOSX partition is on
Type diskutil list
Verify which disk number holds your partition (disk0, disk1, etc.)
4. Start using Fdisk
Assuming the MacOSX disk is the first disk ("disk0"), then
type fdisk -e /dev/rdisk0 (use "rdisk" with your disk number here !)
Ignore the error "fdisk: could not open MBR file ..."
5. Determine which partition for MacOSX needs to be set "Active"
Type p
Verify which partition is for MacOSX (1, 2, 3, etc.)
6. Set the partition "Active"
Assuming it is partition 1, then
type f 1 (use your partition number here !)
7. Save and exit
Type write
Type y (yes you are sure)
Type exit (to quit)
8. Remove the install DVD and reboot
Again this is just copied from the WEB. I've tried it and it works. |
|
|
|
Post by aquamac on Dec 8, 2007 23:32:34 GMT
Nice work Ritalin, I made this useful info a sticky!
|
|
|
|
Post by ritalin on Dec 9, 2007 13:32:59 GMT
We should collate the best tips and info on the forum and put it all into one easy to find place.
I've beaten my motherboard BIOS limitation and successfully booted a working OSX system on my firewire drive. ;D
|
|
|
|
Post by aquamac on Dec 9, 2007 15:27:38 GMT
Wow, I sure would like to know how you did that, any chance of a walkthrough?
|
|
|
|
Post by ritalin on Dec 16, 2007 16:47:28 GMT
Wow, I sure would like to know how you did that, any chance of a walkthrough? Its really a cheap tick. I boot using the Darwin bootloader (boot0) from a USB memory stick (could use any drive bootable from my BIOS). The darwin bootloader can see my firewire drive which allows me to continue the boot sequence (boot1h and boot) from my firewire drive. |
|
