Macintosh Computer Help Log Out | Lost Password? | Topics | Search
Contact | Register | My Profile | SO home | MOL home

M-SO Message Board » 2003 Attic » Please Help » Archive through September 14, 2003 » Macintosh Computer Help « Previous Next »

  Thread Originator Last Poster Posts Pages Last Post
  ClosedClosed: New threads not accepted on this page          

Author Message
Top of pagePrevious messageNext messageBottom of page Link to this message

Ignatius J
Citizen
Username: Ignatius_j

Post Number: 12
Registered: 8-2003
Posted on Tuesday, September 2, 2003 - 5:59 pm:   Edit Post Delete Post Print Post    Move Post (Moderator/Admin Only)

I need to create a Boot Disk that contains my System folder so that I can run Norton Utilities but my System folder on OSX.2 is larger than the 700MB that will fit on a CD.

So, what I need to know from someone that actually knows about computers is which are the essential files and folders that I need to copy and which ones can I not worry about to make it fit on the CD????

Thanks,

Iggy
Top of pagePrevious messageNext messageBottom of page Link to this message

monster
Citizen
Username: Monster

Post Number: 34
Registered: 7-2002
Posted on Saturday, September 6, 2003 - 4:16 pm:   Edit Post Delete Post Print Post    Move Post (Moderator/Admin Only)

Well... your best bet is to not use Norton on OSX installs, Norton seems to create a lot of problems in OSX. the first thing I prefer to do is to repair permissions (can be done via Apple's Disk Utility) I prefer to use Cocktail for this. I also use Cocktail to re-prebind the apps on my system along with running daily, weekly, and monthly cron scripts, it's good for viewing and deleting log files also, and a few other things too.
You can find it here, http://www.macosxcocktail.com/

Running all the actions above, not to mention deleting temp files can make a noticeable difference on a system.
I also recommend using Diskwarrior, as the next step, it can solve a lot of problems and the CD is bootable.
TechTool 4 will be out anytime now and will be bootable also, if it is anything like TTP 3 it is a blessing for OSX.

Why do you need to create a boot disk?
Do you have firewire, and if so is your Mac bootable via an external firewire drive?
The reason I ask is that you can use Carbon Copy Cloner to make an exact copy of your hard-drives contents onto an external drive, this allows you to boot from it and use various utilities. Heck, you can even use it to restore a hosed system, and to make exact copies of you setup on more than one computer.

Anyway, bootable disks...
I know you can use terminal to make one by following the below instructions, I haven't done this but I guess it works, don't know what the size will be but you may be able to trim it down.

*YOU CAN ALSO USE CARBON COPY CLONER TO MAKE A BOOT CD* http://www.bombich.com/software/ccc.html

Terminal Boot CD Instructions

1. Preparation:

Backup volume: 1. Ensure that the backup volume has no existing Mac OS X folders.
(System, Library, private, ...)
2. "Get Info" of the backup volume and ensure that the
"Ignore ownership on this volume" is unchecked.
3. Ensure that there is enough free space on the backup volume.

Finder: 4. Click on "show" Hidden System Files in the "System ..." drawer
of Xupport and restart the Finder.


Important:
In this example the backup volume is simply called "Backup". So if you use
"copy-paste" (Xupport->Terminal) instead of typing into terminal window,
don't forget to replace the word "Backup" with the name of your backup volume.


2. Copy procedure:

>> Go to Terminal and enter:

Visible Folders:

1. sudo ditto -rsrc /System /Volumes/Backup/System
2. sudo ditto -rsrc /Library /Volumes/Backup/Library
3. sudo ditto -rsrc /Users /Volumes/Backup/Users
4. sudo ditto -rsrc /Applications /Volumes/Backup/Applications
5. sudo ditto -rsrc /Developer /Volumes/Backup/Developer
(only if Developer Tools are installed)

Hidden Folders:

1. sudo ditto -rsrc /bin /Volumes/Backup/bin
2. sudo ditto -rsrc /private /Volumes/Backup/private
3. sudo ditto -rsrc /sbin /Volumes/Backup/sbin
4. sudo ditto -rsrc /usr /Volumes/Backup/usr

Hidden Files:

1. sudo ditto -rsrc /.hidden /Volumes/Backup
2. sudo ditto -rsrc /mach_kernel /Volumes/Backup


3. Create empty folders:

>> Go to Terminal and enter:

1. cd /Volumes/Backup
2. mkdir dev
3. mkdir Volumes
4. mkdir Network


4. Create symbolic links:

>> Go to Terminal and enter:

1. cd /Volumes/Backup
(only if changed after creating empty folders)
2. ln -s private/etc etc
3. ln -s private/var var
4. ln -s private/cores cores
4. ln -s private/tmp tmp


5. Finishing:

1. Verify that all folders and files are located to the first level
of your backup volume (just as on the source volume)
2. Click on "hide" Hidden System Files in the "System ..." drawer
of Xupport.
3. Try to boot from your backup volume (use System Preferences)



Troubleshooting:


Applications folder not copyable with "ditto":

If an error occurs when copying the "Applications" folder using "ditto",
try to copy it with the Finder (drag and drop) and press continue when error
dialogs appear. This appears when third party applications contain resources
that are not copyable.


If system (backup) is hanging during startup:

Try to start in single user mode using shortcut "Command + s",
then check your volume using "fsck -y".
If this doesn't work, use verbose mode (Command + v) to find out where
the boot procedure hangs, or what component failed when initializing
}}
Top of pagePrevious messageNext messageBottom of page Link to this message

monster
Citizen
Username: Monster

Post Number: 35
Registered: 7-2002
Posted on Saturday, September 6, 2003 - 4:44 pm:   Edit Post Delete Post Print Post    Move Post (Moderator/Admin Only)

aaarrrggghhh! I fogot to mention that you should also run a file system check as one of the first things you do, before and/or after restoring permissions, or by itself. this sometimes can fix whatever problems you're having.

To run fsck, you need to start up in single user mode. Do this by restarting and holding down the Apple (command) key and the s key during startup.
This will start your system up into console mode, the Unix command line.
After your system is finished starting up you will be presented with the "localhost#" prompt, type
fsck -y
note the space between the "k" and the "y"
press enter and the comand will run.
The file system check will run 5 sets of tests, after it is don you will see a message saying that your HD appears to be OK, or that the file system was modified.
If you get the OK message, simply type exit or reboot, and then press enter,the system will boot into the GUI mode.
If you get the modified message, retype fsck -y and press enter, repeat the command as neccesary until you get the HD OK message, then proceed as previously mentioned.

You can also use fsck -y in Terminal.
Top of pagePrevious messageNext messageBottom of page Link to this message

monster
Citizen
Username: Monster

Post Number: 36
Registered: 7-2002
Posted on Sunday, September 7, 2003 - 1:03 pm:   Edit Post Delete Post Print Post    Move Post (Moderator/Admin Only)

note the space between the "k" and the "-y"

Can't forget to add the hyphen before the y, and after the space, that's what I should have typed on the above post. 10th line from the bottom.

Topics | Last Day | Last Week | Tree View | Search | User List | Help/Instructions | Credits Administration