Fatal Error in VM Monitor in 3186

Discussion in 'Parallels Desktop for Mac' started by psyfil, Mar 1, 2007.

  1. psyfil

    psyfil Member

    Messages:
    21
    I have reported this problem over and over since the first betas came out after 1970. I get a fatal error in the virtual machine monitor when I try to install copy protected programs from a certain psychological test vendor, PAR Inc. This was true in 3120, 3150, 3170 and reported repeatedly. I was hoping it would be fixed with a final release. I need this to work for my business...

    These programs use a copy protection scheme involving software administration counters and files called CC Change, CC Move, CControl Sys. I would be happy to provide my .pvs file if this would actually help this get fixed. I did not expect a response from the beta and RC posts, now that this is a released product I would like to hear from someone at Parallels. i have certainly provided enough automated crash reports for someone to look into this problem. Thanks.

    MacBook Pro Core 2 Duo 2.33, 2048 ram, 1024 to Parallels VM.

    Phil K
     
  2. bob_nugget

    bob_nugget Junior Member

    Messages:
    15
    Good luck getting this fixed, Parallels don't seem to concerned about it...
     
  3. fbronner

    fbronner Pro

    Messages:
    384
    Maybe you could ask your psychological test vendor to look into it. After all, their software would probably work if it was not because of their copy protection.
     
  4. Hugh Watkins

    Hugh Watkins Forum Maven

    Messages:
    943

    exactly

    they sound a bit paranoid using over complicated protection systems

    If 50 or 100 users have the same probs

    the developers might see it as a general fault


    Hugh W
     
  5. uesjd

    uesjd Bit poster

    Messages:
    8
    I get this error without trying to install any copy protected programs. I get it just by trying to start my Windows XP virtual machine.

    I got the same error with the betas and didn't expect to get support from Parallels. Now that it's an official release that still causes the errors, can I (or any of us) expect support from Parallels?
     

Share This Page