Topic awaiting preservation: Mac Blue Screen like Death (Page 1 of 1)

I recently went to upgrade my girlfriends Mac from 10.2 to 10.2.8, I was running the installer and when trying to close a seperate application closed the installer instead. I was unable to restart the installer, getting an errer warning that I didn't bother to commit to memory. I then restarted the computer with hopes that it would resolve the latent issue. When I did this the computer booted up to the blue background with the mouse cursor showing (and able to move) but duesn't actually load the desktop icons or the dock, or the top menu bar.

I have the OS 10.0 install CD and the 10.2 install CD but neither can do an over install, because it says the version on the HD is greater than what I am trying to install over.

I can get into single user mode (i.e. the command prompt) but don't know what to change to get the system to boot correctly, and I don't know how to mount the .dmg file so that I can try the install from the command lne (assuming this is even possible).

Does anyone have any ideas?

Dan @ Code Town

To mount a .dmg from the command line:

hdiutil mount <imagename>

And it will appear as a subfolder of /Volumes. Everything that can be done in OSX (system administration wise) can be done from the command-line. It might not be simple or easy, but it can be done.

Yay for administering an Xserve cluster at work.

"Any sufficiently advanced technology is indistinguishable from magic." -- Arthur C. Clarke
"Any sufficiently arcane magic is indistinguishable from technology." -- P. David Lebling

good info, thanks wallaby.

thanks for OSX being unix-based

chris


KAIROSinteractive | tangent oriented

So, once I do this, how would I then run the program found inside to update the mac?

I wish I could work on Unix like systems at work. I just get to sit behind a windows box all day.

Dan @ Code Town

Is the updater a program that opened softwareupdate or was it a self-contained program? An OSX "program" is actually a UNIX directory containing a number of files needed for the program to run.

If it was self contained, you will want something like... /Volumes/<nameofthing>/<pathtoprogram>/Contents/MacOS/<program> or something similar... just poke around in the programs subdirectories until you find what you want.

Otherwise, try man softwareupdate, and read up.

"Any sufficiently advanced technology is indistinguishable from magic." -- Arthur C. Clarke
"Any sufficiently arcane magic is indistinguishable from technology." -- P. David Lebling