Want to highlight a helpful answer? Upvote!

Did someone help you, or did an answer or User Tip resolve your issue? Upvote by selecting the upvote arrow. Your feedback helps others! Learn more about when to upvote >

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

The Shad Guy Author

Level 3

656 points

Can't Open my Backup DMG years of data gone

Okay I'm going to try to describe this in as much detail as I can and hopefully someone out there can help. I'm using a Mac Pro that has one harddrive in it, 250gb. I also have a Macbook Pro. I also have an external USB drive that's 250gb, and it's partitioned in 2 parts, on is about 200 and the other is 50. I can NOT boot from this drive.

A couple of days ago I decided I would back up my Mac Pro in anticipation of Leopard. So I booted into the Tiger Install disc that came with my computer, and used the disc utility to create a restore image of my entire Harddrive, using the default settings. The image is saved to my external drive.

I got Leopard on Friday and installed it using a clean instal, erasing everything on my computer and installing it fresh. The install went fine and Leopard works magically on this machine. I decided it was time to start bringing my files over from my image I had created, so I attached my drive and opened the DMG, but it wouldn't open, giving me error -4960. PANIC ENSUED. I also tried to mount it on my MacBook Pro which is still running Tiger and I got the same error!

The next day (yesterday) I called Apple, and the man I spoke with told me the reason why it won't mount is because its a raw restore image and what I'll have to do is restore it using the disk utility again. That made sense to me. This morning I tried restoring the image with both the Leopard utility and the Tiger one as well (booting off the install DVDs, that is), but no matter what I do, I get the same error -4960!!

So at this point I'm basically shattered. I live on my computer, it's my whole life (I know that may sound sad haha but it's the truth). This is like having my house burn down, and on top of that, the IRONY of the situation is just too much. The whole reason for upgrading is to get Time Machine.. Ugh. Anyway, Im starting to run out of ideas here. I think maybe it could be because my external drive is a piece of crap or something, so I'm currently copying the thing over to my internal drive and I'll try that. Other than that, I'm thinking the image must be corrupt or something, does anybody know any hardcore tools that could be used in such a situation? Any terminal-fu that could possibly fix this whole problem? I did use data recovery software on the drive yesterday and managed to get a few things, I think,, but I havent really looked through them and it's really not the same as having the files themselves, you know? But I guess it's something.

So yeah, if ANYONE has any ideas on what to do, you have no idea how thankful I would be to hear it.

Jason

touch fuzzy, get dizzy

Posted on Nov 4, 2007 9:20 AM

Best reply

MJWeb

Level 1

125 points

Posted on Nov 4, 2007 10:06 AM

I'm very sympathetic to your situation and have been investigation error -4960 for you. These aren't specific answers but they might point you in the right direction, on your own, or communicating with Apple. Both of these, though unrelated, suggest the problem and solution is related to the User account. Just a hunch, but I'd try opening the DMG from your Guest Account. Keep bugging Apple, too!

http://docs.info.apple.com/article.html?artnum=93311

http://www.tech-archive.net/Archive/Mac/microsoft.public.mac.office.entourage/20 05-02/0052.html

View in context

85 replies

MJWeb

Level 1

125 points

Nov 6, 2007 5:13 PM in response to The Shad Guy

Unfortunately, you took the golden rule of backups for granted; verifying the target volume. You also seem a bit confused over how you created the image in DU to begin with. I use DU to created password protected DMG's and the interface does takes some getting used to.

I think your best bet is loopback and Apple. Have they escalated your case to a senior level? Do you have a Mac Store Genius Bar nearby? Hang in there, bro! I'm pulling for you.

gnawbone

Level 1

0 points

Nov 6, 2007 5:47 PM in response to The Shad Guy

Well?

Come on .... the suspense is killing me!

The Shad Guy Author

Level 3

656 points

Nov 7, 2007 8:33 AM in response to gnawbone

Yup, yer right I took it for granted! That was a huge mistake I made. But come on, when thing's don't error out, they are usually okay (especially if it's Apple!). But yes, I really should have checked my backup prior to doing the clean install.

When I was on the phone with Apple for the second time, the man I spoke with talked to a "senior" specialist but neither of them seemed to have any help to offer. Maybe I should call back again? If Steve Jobs heard of this he'd be horrified. I TRIED TO BACK UP STEVE I TRIED. Haha...

Disk Utility isn't too confusing, it's just been well over a week since I made the image so I'm foggy on how I did it, but now I'm pretty certain I did File->New Image from diskxy or whatever the selection was, with my boot partition selected in the list.

Nov 6, 2007 6:39 PM in response to The Shad Guy

I think, you need documentation about the format apple uses with their diskimages, especially the "compressed image".
From what I found, nowhere is written, if, and how the compression is done.
Most likely, the compression is achived by only ignoring empty space.
But still, that means, if you cannot convert the image to an uncompressed version, you only get garbage if you restore it with dd.
And, if there is some real compression in the image, you will not be able to get anything back with DataRescue.

The DiskImageFramework is AFAIK not open source.
But, maybe check that out yourself at http://opensource.apple.com

I found somthing on the web, where someone said, if the first byte of the image is hex 78, it is a compressed image.

Maybe check that.
Software: http://hexedit.sourceforge.net
It would help to know, if this is compressed or not.
Example of the first line of the same folder:

Uncompressed:
<pre>
50 4D 00 00 00 00 00 03 00 00 00 01 00 00 00 3F
41 70 70 6C 65 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
41 70 70 6C 65 5F 70 61 72 74 69 74 69 6F 6E 5F
6D 61 70 00 00 00 00 00 00 00 00 00 00 00 00 00
</pre>

Compressed:
<pre>
78 01 ED D0 B1 0D 00 20 08 04 C0 77 13 E7 72 1A
47 37 91 01 B0 B1 BB 2F A0 78 0A 72 49 C6 6A 92
9B 59 6B 27 CD F9 F7 BA 1E 31 09 10 20 40 80 00
01 02 04 08 10 20 40 80 00 81 57 81 03 0D 74 38
E2 78 01 ED D0 01 0D 00 00 00 C2 A0 F7 4F 6D 0F
</pre>

That suggests, that there is more then just omitting zeroes.

To check, if the image is truncated:
If it is not a "raw" image:
You should find about 200 hex bytes from the end, an embedded xml/plist.
If you find it and copy that with hexedit into a textedit window, you should get some information about the image.

it looks like this:
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>resource-fork</key>
<dict>
<key>blkx</key>
<array>
<dict>
<key>Attributes</key>
<string>0x0050</string>
<key>CFName</key>
<string>Driver Descriptor Map (DDM : 0)</string>
<key>Data</key>
<data>
bWlzaAAAAAEAAAAAAAAAAAAAAAAAAAABAAAAAAAAAAAA
AAII/////wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAIAAAAgv0dHMAAAAAAAGV14ACWZJAAAAAEAgWL0AIFi
AAAAAAQAAAAEAFWlgAAAAAAAGZkk8AgIACgAIkQAGZ2w
AIFiAAAAAAAABQAAAAUt3AAAAAEAAAABAAAAAACBYgAA
GbuY8AgIAAAFROQAGbwwAFWlcAAAAAQAA5bQki1YkJIt
9EgAAAACgAAABQAAAAoAAAAAAAAAAAAAAAAAAAABAAAA
AAAAAG4AAAAAAAAAFv////8AAAAAAAAAAAAAAAEAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAA=
</data>
<key>ID</key>
<string>-1</string>
<key>Name</key>
<string>Driver Descriptor Map (DDM : 0)</string>
</dict>
<dict>
<key>Attributes</key>
<string>0x0050</string>
<key>CFName</key>
<string>Apple (Apple partitionmap : 1)</string>
<key>Data</key>
<data>
bWlzaAAAAAEAAAAAAAAAAQAAAAAAAAA/AAAAAAAAAAAA
AAIIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAIAAAAghtdUTAAAAAAAGV14ACWZJAAAAAEAgWL0AIFi
AAAAAAQAAAAEAFWlgAAAAAAAGZkk8AgIACgAIkQAGZ2w
AIFiAAAAAAAABQAAAAUt3AAAAAEAAAABAAAAAACBYgAA
GbuY8AgIAAAFROQAGbwwAFWlcAAAAAQAA5bQki1YkJIt
9EgAAAACgAAABQAAAHgAAAAAAAAAAAAAAAAAAAA/AAAA
AAAAt90AAAAAAAABHv////8AAAAAAAAAAAAAAD8AAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAA=
</data>
<key>ID</key>
<string>0</string>
<key>Name</key>
<string>Apple (Apple partitionmap : 1)</string>
</dict>
<dict>
<key>Attributes</key>
<string>0x0050</string>
<key>CFName</key>
<string>disk image (Apple_HFS : 2)</string>
<key>Data</key>
<data>
bWlzaAAAAAEAAAAAAAAAQAAAAAAAAF3QAAAAAAAAAAAA
AAIIAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAIAAAAgUDLgJgAAAAAAGV14ACWZJAAAAAEAgWL0AIFi
AAAAAAQAAAAEAFWlgAAAAAAAGZkk8AgIACgAIkQAGZ2w
AIFiAAAAAAAABQAAAAUt3AAAAAEAAAABAAAAAACBYgAA
GbuY8AgIAAAFROQAGbwwAFWlcAAAAAQAA5bQki1YkJIt
9EgAAAA0gAAABQAAAHgAAAAAAAAAAAAAAAAAAAHBAAAA
AAAEMLkAAAAAAAALuQAAAAAAAAAAAAAAAAAAAcEAAAAA
AAAAPwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAIAAAAAAAAAAgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAEAAAAAAAAAAIAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAABgAAAAAAAAACAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAAAgAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAKAAAA
AAAAAAIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAADAAAAAAAAAACAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAA4AAAAAAAAAAgAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAIAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEgAAAAAAAAAC
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABQA
AAAAAAAAAgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAWAAAAAAAAAAIAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAGAAAAAAAAAACAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAABoAAAAAAAAAAgAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAcAAAAAAAA
AAIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
HgAAAAAAAAACAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAACAAAAAAAAAAAgAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAiAAAAAAAAAAIAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAJAAAAAAAAAACAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACYAAAAA
AAAAAgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAoAAAAAAAAAAIAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAKgAAAAAAAAACAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAACwAAAAAAAAAAgAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAuAAAAAAAAAAIA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAMAAA
AAAAAAACAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAADIAAAAAAAAAAgAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAA0AAAAAAAAAAIAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAANgAAAAAAAAACAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADgAAAAAAAAA
AgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA6
AAAAAAAAAAIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAPAAAAAAAAAACAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAD4AAAAAAAAAAgAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAABAAAAAAAAAAAAQAAAA
AAAAAAAAAAAAAAAAAIAAAAUAAAADAAAAAAAAQBAAAAAA
AAAACAAAAAAAAAAAAAAAAAAAAEGAAAAFAAALNQAAAAAA
AEAYAAAAAAAAAZAAAAAAAAzHfQAAAAAAACxJAAAAAAAA
AAAAAAAAAABBqAAAAAAAAAAgAAAAAAAAAAAAAAAAAAAA
AAAAAAIAAAAAAAAAAAAAQcgAAAAAAAAIcAAAAAAAAAAA
AAAAAAAAAACAAAAFAAAAEwAAAAAAAEo4AAAAAAAAAgAA
AAAAAAAAmgAAAAAAALVDgAAABQAAACUAAAAAAABMOAAA
AAAAAAIAAAAAAAAAwJwAAAAAAADzVIAAAAUAAAAxAAAA
AAAATjgAAAAAAAACAAAAAAAAAbPwAAAAAAACfMmAAAAF
AAAAJwAAAAAAAFA4AAAAAAAAAgAAAAAAAAgwuQAAAAAA
AuykgAAABQAAADkAAAAAAABSOAAAAAAAAAIAAAAAAAAL
7f4AAAAAAADZf4AAAAUAAAA/AAAAAAAAVDgAAAAAAAAC
AAAAAAAADPPGAAAAAAAAx/KAAAAFAAAAUQAAAAAAAFY4
AAAAAAAAAgAAAAAAAA27uAAAAAAAAKFngAAABQAAAEEA
AAAAAABYOAAAAAAAAAIAAAAAAAALHV0AAAAAAADQoYAA
AAUAAAA/AAAAAAAAWjgAAAAAAAACAAAAAAAADl0fAAAA
AAAAwCeAAAAFAAAAPQAAAAAAAFw4AAAAAAAAAZAAAAAA
AAQ8cgAAAAAAAICqAAAAAgAAAD0AAAAAAABdyAAAAAAA
AAAGAAAAAAAAuPsAAAAAAAAAAIAAAAUAAAA9AAAAAAAA
Xc4AAAAAAAAAAQAAAAAAALj7AAAAAAAAAIsAAAACAAAA
PQAAAAAAAF3PAAAAAAAAAAEAAAAAAAAAhAAAAAAAAAAA
/////wAAAAAAAAAAAABd0AAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAA==
</data>
<key>ID</key>
<string>1</string>
<key>Name</key>
<string>disk image (Apple_HFS : 2)</string>
</dict>
<dict>
<key>Attributes</key>
<string>0x0050</string>
<key>CFName</key>
<string> (Apple_Free : 3)</string>
<key>Data</key>
<data>
bWlzaAAAAAEAAAAAAABeEAAAAAAAAAAKAAAAAAAAAAAA
AAIIAAAAAgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAIAAAAgAAAAAAAAAAAAGV14ACWZJAAAAAEAgWL0AIFi
AAAAAAQAAAAEAFWlgAAAAAAAGZkk8AgIACgAIkQAGZ2w
AIFiAAAAAAAABQAAAAUt3AAAAAEAAAABAAAAAACBYgAA
GbuY8AgIAAAFROQAGbwwAFWlcAAAAAQAA5bQki1YkJIt
9EgAAAACAAAAAgAAAD0AAAAAAAAAAAAAAAAAAAAKAAAA
AAAAAEEAAAAAAAAAAP////8AAAAAAAAAAAAAAAoAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAA=
</data>
<key>ID</key>
<string>2</string>
<key>Name</key>
<string> (Apple_Free : 3)</string>
</dict>
</array>
<key>plst</key>
<array>
<dict>
<key>Attributes</key>
<string>0x0050</string>
<key>Data</key>
<data>
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAQAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAA
</data>
<key>ID</key>
<string>0</string>
<key>Name</key>
<string></string>
</dict>
</array>
</dict>
</dict>
</plist>

</pre>

If you dont find it, then, the image is truncated or it is not compressed and not an uncompressed image, but somthing else (unlikely)

nerowolfe

Level 6

13,090 points

Nov 6, 2007 6:40 PM in response to nobody loopback

It would seem to me that someone, perhaps an Apple developer could take care of this. Somone in Apple must have the ability or power to authorize someone to examine this dmg and fix it.

Nov 6, 2007 6:46 PM in response to nerowolfe

http://vu1tur.eu.org/tools/
which you mentioned.

I dont know If he tried one of these tools - its worth a try.

The Shad Guy Author

Level 3

656 points

Nov 6, 2007 6:57 PM in response to nobody loopback

I will try that tool in a moment, maybe it can offer some help.

I have previously opened the dmg in the tool called "0xed" (as in hex ed) which I believe is mostly the same as HexEdit. The starting hex byte is 78 (although I have read that is standard across all DMGs), and near the end of the file there is something of an xml/plist.

Trying to open the image in HexEdit which you linked me to, it would say there is no resource fork and asked if I wanted to make one, but I said no, and it wouldn't open. I then tried opening the file a different way and it crashed. I don't think "making the fork" would be a good idea, do you? I currently only have one copy of this image, so until I can get more harddrive space, I will not do it, I don't think it would help or harm any but I dont want to risk it right now.

Nov 6, 2007 7:07 PM in response to The Shad Guy

The file has no resource fork, and it does not need to have one.
If the plist is there, that would be good.

you then could try that dmg2img

however, you must build that from source, since on that page, there is only a windows binary.
It was easy to build the tool. And I could decompress some test image to somthing wich would be acceptable for dd, but I suspect, it might have a problem just because the size of your image.

The Shad Guy Author

Level 3

656 points

Nov 6, 2007 7:11 PM in response to nerowolfe

I will call Apple back tomorrow, I guess being a Canadian makes me too polite and too much of a pushover on the phone..huh. Well I will call them back tomorrow and demand answers. How should I go about getting ahold of the person I will need to speak with. I too believe someone at Apple can fix this, I just need to find them.

Also, I tried the dmg2img tool. It failed, giving me the error "dmg file is corrupted". Looking through the source code, this happens when two certain values read in from the end of the image file don't match. So I think that's a hint at where the file could be corrupted. It's starting to finally show itself, this corruption. I will keep at it!

nerowolfe

Level 6

13,090 points

Nov 6, 2007 7:15 PM in response to The Shad Guy

Whoeever or whatever team at Apple wrote the software has to be able to help you. It would be great if he were reading this right now, but you might, if you don't already belong, join the Apple developer's group. It's free. I joined because of my interest in all things *nix and just in general, but they may have some people over there who can help.
Here's a link:
http://developer.apple.com/macosx/
Nothing to lose, years of work to gain.
I am betting this gets resolved.

The Shad Guy Author

Level 3

656 points

Nov 6, 2007 7:20 PM in response to nerowolfe

Oh yes, I've been a member of ADC for a while now, although I haven't found anything too relevant to this issue yet. I hope that if someone "in the know" is *reading this* that they could lend a hand or let me know who I need to contact to get this issue fixed. I'm really pretty sure it's just a messed up header or two somewhere and any help on this would be a godsend from Apple.

MJWeb

Level 1

125 points

Nov 6, 2007 7:52 PM in response to The Shad Guy

I won't make any promises but I just e-mailed Steve Jobs.

Steve,
I want to refer you to a situation that requires special technical intervention. Kindly refer to the following Apple Forum link. This user lost all his data and is in need of critical assistance.

http://discussions.apple.com/thread.jspa?threadID=1218394&start=30&tstart=0
I'd appreciate you sending the troops.

Don't hold your finger but I believe he will receive this.

The Shad Guy Author

Level 3

656 points

Nov 6, 2007 7:54 PM in response to MJWeb

Wow! Thanks, wouldn't that be something if they did though.

Well I have to say, whether they send in the troops or not, you guys are the Red Cross!

MJWeb

Level 1

125 points

Nov 6, 2007 8:07 PM in response to The Shad Guy

You're going to crack this! Hang tough.

MJWeb

Level 1

125 points

Nov 6, 2007 8:19 PM in response to The Shad Guy

"I will call them back tomorrow and demand answers. How should I go about getting ahold of the person I will need to speak with. I too believe someone at Apple can fix this, I just need to find them."

Be polite and assertive. Act like you know exactly what you're taking about -- which you do! Then demand a solution. Be artful but nice. Never take no for an answer. Don't let them off the hook. Negotiate. Remain friendly. If you get a dud rep cut your losses and call right back.

Can't Open my Backup DMG years of data gone