Ran into a program we use that required an older mac upgrade XP from SP2 to SP3. So per apple instructions I installed the bootcamp update, then installed the SP3 update and installed the program. Everything goes nicely (except apples RETARDED upgrade structure - force me to install the 3.0 update, then the 3.0-3.1 update, then the 3.1-3.2 update - WHY!?). So winXP is now working like a charm, and OSX won't boot.

Started in single/safe mode and still wouldn't boot
Started in verbose and get "the volume OSX could not be repaired" and "Launch_msg(): Socket is not connected"

ideas?

6/30/2011 4:20:17 PM

Quote :

"So winXP is now working like a charm, and OSX won't boot."

Not sure I'm seeing the problem...

( I can be of no help to you here, other than to say that my Bootcamp experiences have always turned into clusterfucks, though it's generally of the "your OSX disk is not formatted the right way" variety )

6/30/2011 4:58:24 PM

I just sold my Mac Mini because of how fucking shitty bootcamp is.

6/30/2011 6:09:26 PM

I'm almost to the ALL MACS ARE WORTHLESS rant stage again. But I'm holding it down because the laptop belongs to a good friend.

Still a little irritated there was no single upgrade to go from where I was to where I wanted to go. Upgrades should not require a disk and two downloads and rely on you to execute them sequentially.

7/1/2011 12:44:34 AM

I think the thing that irked me the most when I boot camped a Snow Leopard machine is that I had Snow Leopard installed on the laptop, but didn't have the disc onhand and needed to install Boot Camp 3.

Well I could download Boot Camp 2 from the website, and 3.1 and 3.2, but not 3.0. That was only on the disc and you couldn't install any later versions without the 3.0 release. And 3.0 didn't do anything particularly useful, it just sort-of enabled gestures, maybe?

Man, that pissed me off.

[Edited on July 1, 2011 at 1:02 AM. Reason : I probably have the version numbers wrong, but fuck it.]

7/1/2011 1:01:42 AM

^nope accurate

just glad i had a stupid disk on hand.... Didn't matter though, still hosed

7/1/2011 7:30:00 AM

I'm not sure where the problem is here. I downloaded 3.2 (at the time) without 3.0 or 3.1 and it worked fine...

did you defrag the OSX volume before putting on XP?

7/2/2011 2:58:00 PM

It started with leopard; then it allocated about 50GB to winXP SP2 in bootcamp 2.0; installed the updates on bootcamp up to like 2.3 or something. Then snowleopard, then we hit wednesday and the problems. Installed bootcamp 3 from the disk, installed 3.1 and 3.2 update. Installed XP SP3. Installed Access 2010. Everything working swimmingly in XP.

Reboot into OSX and get pinwheel of death. Boot into single user, safe, verbose trying to see the problem; everything reported in this thread. Genius idiots want to wipe it and start over

7/2/2011 6:07:28 PM

sounds like the partition map was borked. Can you mount the os x partition in single user mode? Can you force an fsck check? Can you boot the os x disc and run disk utility that way?

Do you hold option at boot or select the os x partition from the boot selector in windows?

You might also try a gparted boot disc to repair the os x partition.

7/3/2011 12:56:13 AM

^I assumed it was a partition problem. But it was my understanding that safe mode (holding shift when booting) was supposed to trigger an automated check to repair that.

Tried booting into single user - no dice.

Tried running fsck; but that wasn't done by me - so 50/50 chance

When we boot we hold option to get to XP; not sure we tried it to get to OSX - are you saying the boot flag has gotten switched to the XP partition and the OSX bootloader is all pissy about it?

7/3/2011 1:46:01 AM

Quote :

"Tried booting into single user - no dice. "

What do you mean no dice?

It doesn’t boot in single user mode? Does it crash?

Does the kernel load (you’ll see something about Darwin scroll on the screen)?

If you are getting to the kernel, then the bootloader is reading from the OS X partition properly, but your systems files got hosed somehow or the kernel can’t read the HFS partitions properly, which sounds like the case if you see the apple with the spinning circle.

It’s possible something went wrong with resizing your partition, in which case you might have to reinstall OS X (which you should be able to do without wiping out windows, but you might have to jump through hoops to get Windows booting again…).

If you know the OS X files are all in tact, you might could install GRUB or LILO or another bootloader in Windows to switch between OSes.

I would try Gparted (make sure it has an HFS driver— most gparted boot discs do) at this point though if you really can’t get single user mode working.

A common bootcamp mistake is that people choose the wrong partition when they install Windows, and end up nuking their EFI partition. If the OS X bootstrap doesn’t see the EFI partition, it acts weird. If this is what happened, it’s possible to salvage this situation without having to reformat.

[Edited on July 3, 2011 at 1:59 AM. Reason : ]

7/3/2011 1:56:10 AM

http://refit.sourceforge.net/

7/4/2011 12:52:34 PM

ok; we're back and OSX is WORTHLESS.

Booted from the DVD and tried to run disk utilities and it says "can't be repaired.... backup your files, wipe your disk and start over"

... and the problem, of course, is that I don't have the CS5 key on hand.

7/7/2011 10:32:17 AM

update: I've got the mac booted into firewire slave via ubuntu live cd that's copying data over to the network store.


.... except now the mag power thing is malfunctioning and it's going to die about 46 hours before the backup finishes

7/7/2011 12:28:04 PM

What kind of a consumer backup takes 46 hours?

7/9/2011 7:35:50 AM

that was my point....

At some point during the backup the power adapter caught fire. I came in to the laptop dead and the mag connector blacked and about 1cm of cord burned away. No one in town stocks macbook parts so I'm waiting until monday for the new one to arrive. Stupid thing is cursed. Just glad I didn't burn down the office

7/9/2011 10:36:48 AM

Wow.

7/9/2011 2:31:02 PM

Did a little research. Apparently this is a known problem with the mac chargers. That image is from another site (we hacked open our adapter to try and repair it). The one I'm working on looked exactly like that except the entire casing was charred all the way up and onto the square part, and the only thing visible was bare wires.

7/9/2011 5:29:19 PM

Yeah, it IS lucky that didn't start a fire.

7/10/2011 12:56:25 PM