This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

My Virtual PowerDirector 11 seems to run on Windows 7 but fails onXP

I'm trying to virtualise Cyberlink Power Director 11.

I've installed ZAV 9.01 on a windows XP VM (no VM Tools)
I captured and build the virtual app there.

When I take my virtual exe to an alternate windows XP VM I get errors of
can't finding dlls mfc90.dll being one of them.

But if I take my virual exe and run it on a windows 7 VM it seems to run
OK.

Frankly I was kind of expecting the problems to be the other way around.

Why would my virtual APP be looking for dlls on Windows XP anyway?

I'm stumped.

Thomas

  • 0
    Thomas,

    You built on the XP, right? Did you turn off the quick snapshot mode in the options, prior to capturing the before snapshot? Were you logged in as the admin through the whole process?

    Try this on the build machine:

    1. Start a new project in ZAV
    2. Point the startup file parameter to the cmd.exe
    3. Without making any further changes, build the virtual app
    4. Use the virtual CMD to run the installed version of Cyberlink Power Director 11

    Does that run as expected? If not, we're looking at an issue where the application may not be supported by ZAV. Typically, if this test fails here there are no changes in the configuration that will help get the virtual Cyberlink Power Director 11 working in XP. If the test works, however, we know that this is a configuration issue.

    I can't access my ZAV machine at the moment, otherwise I would give you exact options to try working with in the configuration (I don't remember them off the top of my head). Try toggling the "always launch child process as current user" and "emulate elevated priveleges" options and building.

    If you can provide installation media, steps you went through, any other pertinent information, you may want to open an SR. The team will be able to attempt to reproduce the issue and, assuming that is successful, can file tickets with Spoon to get more in-depth assistance in resolving the issue.
  • 0 in reply to 
    Hi thanks for rsponding. I'll check what you suggest.


    Yes I captured it on XP.
    Quick snapshot is turned off. I never use quick snapshot.
    The DLL's the app looks for in XP are in the set of files that it captured
    in the snapshot
    My virtual app doesn't run on XP but does run on Windows 7. Weird or what?
    I'm thinking windows 7 may just have the dlls the app is looking for but I
    was assuming the virtual app ran independently of the OS.

    thanks
    Thomas



    >>> On 8/02/2013 at 9:56 p.m., in message

    <zeevromm.5qfr7b@no-mx.forums.novell.com>,
    zeevromm<zeevromm@no-mx.forums.novell.com> wrote:

    > Thomas,
    >
    > You built on the XP, right? Did you turn off the quick snapshot mode
    > in the options, prior to capturing the before snapshot? Were you logged
    > in as the admin through the whole process?
    >
    > Try this on the build machine:
    >
    > 1. Start a new project in ZAV
    > 2. Point the startup file parameter to the cmd.exe
    > 3. Without making any further changes, build the virtual app
    > 4. Use the virtual CMD to run the installed version of Cyberlink Power
    > Director 11
    >
    > Does that run as expected? If not, we're looking at an issue where the
    > application may not be supported by ZAV. Typically, if this test fails
    > here there are no changes in the configuration that will help get the
    > virtual Cyberlink Power Director 11 working in XP. If the test works,
    > however, we know that this is a configuration issue.
    >
    > I can't access my ZAV machine at the moment, otherwise I would give you
    > exact options to try working with in the configuration (I don't remember
    > them off the top of my head). Try toggling the "always launch child
    > process as current user" and "emulate elevated priveleges" options and
    > building.
    >
    > If you can provide installation media, steps you went through, any
    > other pertinent information, you may want to open an SR. The team will
    > be able to attempt to reproduce the issue and, assuming that is
    > successful, can file tickets with Spoon to get more in‑depth assistance
    > in resolving the issue.

  • 0
    Thomas,

    Sorry for not responding sooner. What was the result of the test I asked you to run?

    If you're still having an issue, you should probably open an SR; that will allow support to assist more than I can working through a forum (and whomever owns the case normally won't let it sit for 5 days with no communication).