[Sophie]

I have this as my "quit_vmware.sh", set to "Run before copy":
#!/bin/sh
osascript -e 'tell application "VMWare Fusion" to quit'
------------

The scheduled backup worked fine with VMWare 2.x.

A couple of days I upgraded to VMWare 3.0. Now my backup stops at the Run-before-copy stage, although the quit_vmware script runs and successfully shuts down VMWare. The SD log shows:

| 10:04:41 PM | Info | ...ACTION: Running shell script quit_vmware.sh
| 10:04:41 PM | Info | ......COMMAND => Invoking Before Copy shell script: /Users/s/Library/Scripts/quit_vmware.sh
| 10:04:41 PM | Error | file:///System/Library/ScriptingDefinitions/CocoaStandard.sdef:2: I/O warning : failed to load external entity "file://localhost/System/Library/DTDs/sdef.dtd"
| 10:04:41 PM | Error | <!DOCTYPE dictionary SYSTEM "file://localhost/System/Library/DTDs/sdef.dtd">
| 10:04:41 PM | Error |
-------------
When I run the script from Terminal, I see this:
>> ./quit_vmware.sh
file:///System/Library/ScriptingDefinitions/CocoaStandard.sdef:2: I/O warning : failed to load external entity "file://localhost/System/Library/DTDs/sdef.dtd"
<!DOCTYPE dictionary SYSTEM "file://localhost/System/Library/DTDs/sdef.dtd">
^
>> echo $?
0
------------
So, VMWare seems to be printing out some message (no idea what it means), but, importantly, seems to exit with a "Success" code of 0.

Am I reading this correctly? Should SD be aborting the backup if the exit code of the script is "0"?

Thanks!

p.s. strange thing, running the script even with VMWare Fusion not running still gives exactly the same result, both in Terminal and in SD.