VMware Communities
SMQ
Contributor
Contributor

Repaired permissions and rebuilt directory with DiskWarrior 4 and now can't logon to my virtual machine, error: Failed to connect to peer process.

I am running a MacBook Pro 2.4GHz Intel Core 2 Duo

4GB Memory

Mac OS X v 10.5.1

VMware Fusion Version 1.1 (62573)

OS X experience: User, not comfortable with the command line interface

Guest virtual machine came from Macintosh VPC7 w/ Windows XP Pro

I just got everything humming along great and am very happy with the Fusion. I just got a upgraded version of DiskWarrior 4 for Leopard, ran it and repaired permissions and rebuilt the directory and now when I try to run Windows XP under Fusion I get an error; Failed to connect to peer process. Please help!

Reply
0 Kudos
7 Replies
Technogeezer
Immortal
Immortal

Did DiskWarrior leave a log behind of what it changed? I suspect that it may have changed permissions on a Fusion component or the files which make up the XP guest.

- Paul (Technogeezer)
Editor of the Unofficial Fusion Companion Guides
Reply
0 Kudos
SMQ
Contributor
Contributor

The log files do indicate there were changes made, but I haven't found where there were changes made to anything relating to Fusion or XP... I've attached the logs, what do you think?

I just found this on the web...

http://software-robotics.com/graphic-design-prepress/viewtopic.php?p=7799

Message was edited by: SMQ

Reply
0 Kudos
Technogeezer
Immortal
Immortal

The "Macintosh HD Report.pdf" document doesn't make me feel comfortable. They've "fixed" some things without letting you know what they "fixed".

Here's how I would proceed:

First, put that DiskWarrior disk away for a while :smileyblush:

Then:

  1. Boot from the Leopard DVD, and use Disk Utility to verify and repair the hard drive. Don't repair permissions, you'll do that in step 2.

  2. Boot from the hard drive, log in as an administrator, and use Disk Utility to repair permissions.

  3. De-install Fusion using the Uninstall VMware Fusion.app located in the /Library/Application Support/VMware Fusion directory. A simple delete of the VMware Fusion application is insufficient, there are additional components that are installed on your hard drive.

  4. Re-install Fusion

If this doesn't take care of it, then I'd get Alsoft (the publisher of DiskWarrior) involved. My fear is that there's something wrong with a file on your system as a result of what DiskWarrior did - and it has given you no indication of what it messed with.

By the way, why did you run DiskWarrior? I tend not to run 3rd party disk utilities unless absolutely necessary (problem that OSX's utilities can't fix).

Message was edited by: Technogeezer - added the name and location of the Fusion uninstaller

- Paul (Technogeezer)
Editor of the Unofficial Fusion Companion Guides
SMQ
Contributor
Contributor

Thanks for getting back w/ me. You are very kind.

I've been freaked since I installed DiskWarrior and disabled my ability to access my corporate email and created general instability in multiple applications, including "Mail".

For some reason I thought the lastest version of DiskWarrior was Leopard compatible... I can't believe I wasn't more careful.

Anyway, I asked a friend at Apple if there was anyway to recover and this is what he said, see below. Interestingly it seemed to work and things seem to be back to normal (can access my virtual machine which contains Windows XP and all apps seem to work so far)(one problem I noticed just after rebuilding the directory and repairing permissions, which still persists. Just after using DiskWarrior I was organizing my email in my Mail Inbox and created a mailbox then tried to add mail messages to it. The message could not be dragged or moved into the mailbox... I checked and the mailbox and it was Read Only. I've been trying to delete it w/ out any luck, even after going to the finder level and changing the attributes to read and write. It may be that the mailbox was created by Root and I'm not sure how to delete it... The reason I say that is because in trying to copy the DiskWarrior log file to a new Text Edit document, when I went to save it, the first option of where to save it was root... I've never seen that before... However, beyond that I haven't fully tested everything yet, but will over the weekend and will hope for the best. ( I also tried a few other things before I tried his last suggestion, see below intermixed w/ your last suggestion.)

"OUCH! looks like this is the only answer

Note: If you have used any utility to repair permissions of a Leopard startup disk while started from Mac OS X 10.4 or earlier, Alsoft recommends that you perform an upgrade install of Leopard over your existing Leopard install.

This will restore any changed permissions to their original values without altering your data.

let me know how it works out

good luck s"

On Jan 3, 2008, at 10:36 PM, I wrote:

http://www.macfixit.com/article.php?story=20071203100756482

-


Original Message-----

From: "Technogeezer" <communities-emailer@vmware.com>

Subj: New message: "Repaired permissions and rebuilt directory with DiskWarrior 4 and now can't logon to my virtual machine, error: Failed to connect to peer process."

Date: Fri Jan 4, 2008 2:14 pm

Size: 1K

To: Me

A new message was posted in the thread "Repaired permissions and rebuilt directory with DiskWarrior 4 and now can't logon to my virtual machine, error: Failed to connect to peer process.":

http://communities.vmware.com/message/832677

Author : Technogeezer

Profile : http://communities.vmware.com/people/Technogeezer

Message:

-


The "Macintosh HD Report.pdf" document doesn't make me feel comfortable. They've "fixed" some things without letting you know what they "fixed".

Here's how I would proceed:

First, put that DiskWarrior disk away for a while :smileyblush:

Then:

  1. Boot from the Leopard DVD, and use Disk Utility to verify and repair the hard drive.( DID THIS) Don't repair permissions, (DID THAT TOO...) you'll do that in step 2.

  2. Boot from the hard drive, log in as an administrator, and use Disk Utility to repair permissions.

  3. De-install Fusion using the VMware provided utility (can't remember exactly where it is, but the documentation should tell you). A simple delete of the VMware Fusion application is insufficient, there are additional components that are installed on your hard drive.

  4. Re-install Fusion

If this doesn't take care of it, then I'd get Alsoft (the publisher of DiskWarrior) involved. My fear is that there's something wrong with a file on your system as a result of what DiskWarrior did - and it has given you no indication of what it messed with.

By the way, why did you run DiskWarrior? (MY APPLE FRIEND ASKED ME THE SAME QUESTION, GUESS ALL I CAN SAY IS I HAVE BEEN USING IT AS A REGULAR PREVENTATIVE PROCESS FOR MANY YEARS W/ NO PROBLEM...) I tend not to run 3rd party disk utilities unless absolutely necessary (problem that OSX's utilities can't fix).

Reply
0 Kudos
Technogeezer
Immortal
Immortal

Just saw the info you noted about Leopard compatibility on Alsoft's web site. It does appear that you may have run into one of the "compatibility issues" by repairing permissions with DiskWarrior 4 on a Leopard disk. If so, that's a pretty stealthy "issue".

Glad that you're making some headway with the re-installation. Was hoping that it wasn't going to be necessary, but, if it worked...

- Paul (Technogeezer)
Editor of the Unofficial Fusion Companion Guides
Reply
0 Kudos
SMQ
Contributor
Contributor

When I got my copy of DiskWarrior I booted from the CD repaired permissions and bebuilt the directory and was surprised at how many problems needed to be fixed...

Given the large number of items I opened up TextEdit and copied the logs, which rarely do. Interestingly, when I tried to save the TextEdit file the default was Root! I had never seen anything like that and had a feeling I had made a mistake.

I then rebooted the system and tried to log into Fusion which didn't work.

At that point I started researching the error using Firefox and sending out distress emails.

Reloading Leopard seemed to fix the bulk of the problems however, the files that were altered like the cached FireFox files and the email box that I created while the permissions were jumbled need to be trashed. I also had some printing issues that seemed to be cleared up by rerunning Apple Bonjour for Windows.

Having said all that the only problem I have yet to fix is being able to print PDF files on my Windows XP Virtual Machine under Fusion. I've reinstalled Adobe Acrobat 6 and Bonjour, recreated printers in the Windows Printers and Faxes file under the Start menu and still get an error: Your printer driver needs to be configured for printing to a PostScript Language Level 2 printer. Unfortunately changing the language level to 2 does not seem to fix the printing problem... Got any ideas??

Reply
0 Kudos
SMQ
Contributor
Contributor

After removing Acrobat 6 Pro and installing Acrobat 8 Reader, printing PDF's seem to work fine. As I have an older Apple LaserWriter 16/600 PS (Level 2 PS printer) and using Bonjour for Windows along with an older version of Acrobat may have created the printing problem. Anyway, I seem to be back to 100%.

Reply
0 Kudos