Can't run a 10.7.4 VMWare VM on MBP with Retina

Question

I have an old 13" Aluminum Macbook and a purchased copy of Lion that I created a VMWare OSX 10.7.4 VM with that I could use for work.  I had it running fine on my 13" that runs 10.7.4.  I just got a new MBP writh Retina display.  It came with 10.7.4 pre-installed.  I loaded VMWare, moved my VM over and tried to start it up.  I got the login screen, but right after login, I get an error "The CPU has been disabled by the guest operating system. Power off or reset the virtual machine."
I submitted a VMWare ticket and they said this is caused by a mismatch between the OSX10.7.4 builds on the two machines, and that the one on my old macbook is unaware of the ivy bridge architecture on the new Macbook.  They said this doesn't normally occur because Apple generally releases one build for all macbooks.  As a point of reference, the build on my Retina is 11E2620, while on my 13" it is 11E53.
VMWare said that it should be cleared up once 10.7.5 is released.  They had also heard from other clients that they had been successful in talking with Apple and getting a patch for the older Mac that would make it aware of ivy bridge.  So I believe I would apply the patch to both the host and guest on the 13" (although I didn't get into that level of detail with the resource). 
Anyway, I got Applecare with my retina so I submitted an Apple support ticket and talked to someone at Apple.  They checked with their supervisor and basically said they didn't know anything about a patch and if there was one, I would have to get it from VMWare.  They did agree that this should be clared up with 10.7.5 but again, pointed it back to VMWare. 
So now I have Apple and VMWare pointing fingers at each other, I still have a non-working VM for my new machine (I can still run it on my old machine thankfully) and too much time has been spent on that VM to completely recreate it on the new Macbook.  Anyway, not having the VM on my Retina really cuts down the amount I can use it.  So if anyone has any more details on how to get this supposed patch, OR if anyone has any detail on when 10.7.5 is likely to be released, please let me know.  Thanks,
-David

Answer 1

I can't answer the specific error message, but I can tell you a better way to do what you're asking.
on pathToScripts()
    tell application "Finder" to set parentFolder to (path to me) as text
    set scriptsFolder to parentFolder & "Contents:Resources:Scripts:"
    return scriptsFolder
end pathToScripts
There's no need to use the Finder here at all. 'path to me' is a standard command that doesn't require Finder input.
Secondly, if you're looking for a resource in the application's bundle then you should use 'path to resource' rather than 'path to me' + some hard-coded string.
As a result your first three lines of script could be reduced to:
set CloseBrowsersScriptPOSIXFile to path to resource "closeBrowsers.scpt" in directory "Scripts"
set theResult to run script file CloseBrowsersScriptPOSIXFile with parameters {"uninstaller"}