Jump to content
12 posts in this topic

Recommended Posts

Disk Utilty does it for me.

 

I have backup images of my 10.4.3 and of my 10.4.4. With all this trouble when patches don't take as expected, it helps when having to start from scratch. This way I avoid having to install 10.4.3 and then having to patch it to 10.4.4. Now All I need is to get this damn 10.4.5 to work. Once I get it running I plan on making a .dmg of that too.

Fdisk is what makes a partition bootable or not. The .dmg will boot as long as you flag that partition. You must have a bootable partition to begin with. Once you have one then it 's all booting in -s mode and typing fdisk -e /dev/rdiskx (x being the disk if you have more than one). Remember that partitions start counting from zero. Once in fdisk mode you can the type "print" to see the partitions on any given drive. Here you will see partition being counted starting with 1. The patition with an "*" next to it is the bootable partition. To change to like say partition 2, you would type

"flag 2"

 

"enter"

 

and

 

"quit" to save the changes.

 

Remember that you should have an image on partition 2 for it to load once the flag has been set. You would normally restore the image from another partition using disk utility/restore. If you don't have anything on partition 2, it will complain about not having anything to load.

you should have a small 6 or 7 gig partition set up with an emergency osX, you can then back up, or restore partitions or dmgs from there.

 

when you restore, DON'T FORMAT. formatting destroys the mbr.

 

make visible ALL files and folders, drag them to the trash, empty trash, then restore from your dmg or partition.

 

that way your mbr isn't screwed up.

 

probably obvious, and uncalled for advice, but it might be useful. ;)

This worked for me;

 

rm -rf /Volumes/amd64/*

ditto -rsrcFork /Applications /Volumes/amd64/Applications

ditto -rsrcFork /Developer /Volumes/amd64/Developer

ditto -rsrcFork /Library /Volumes/amd64/Library

ditto -rsrcFork /System /Volumes/amd64/System

ditto -rsrcFork /cores /Volumes/amd64/cores

ditto -rsrcFork /private /Volumes/amd64/private

ditto -rsrcFork /usr /Volumes/amd64/usr

ditto -rsrcFork /bin /Volumes/amd64/bin

ditto -rsrcFork /sbin /Volumes/amd64/sbin

ditto -rsrcFork /.hidden /Volumes/amd64/.hidden

cd /Volumes/amd64

mkdir Volumes Network dev

ln -s private/etc etc

ln -s private/tmp tmp

ln -s private/var var

rm var/db/.AppleSetupDone

rm var/db/netinfo/local.nidb

cp /mach_kernel.all_amd /Volumes/amd64/mach_kernel

Easy method with GHOST

 

Create Virtual Machine in VMWare

Guest operating system: Other

Version: MSDOS

 

In Disk section ...

If you have MacOSX installed in a VMWare .vmdk and Have another HDD for a native install

 

Use an existing virtual disk then browser for your installed .vmdk

 

In the created vmware Tab ... go to Edit virtual machine settings --- Add > Hard Disk > Use a physical Disk and chose disk or partition ( Be careful with no choose wrong drive or partition At your own risk !!

 

You can do any harddrive combination

 

Finally boot the VMWare Machine with MSDOS Startup Floppy or Cd Disk. ..

launch ghost.exe ( ghost 2003 in my case) .. copy partition to ... or where ever you want.

 

40 min for 5 Gbyte in my system.

 

Thanks.

Bye

PD: I use this method for My native install without Boot problem.

×
×
  • Create New...