Forum: Poser - OFFICIAL


Subject: Opening PZ3 files in P5 with P4 also on the drive

Dore opened this issue on Feb 10, 2005 ยท 7 posts


Dore posted Thu, 10 February 2005 at 4:55 PM

I have for a long time had P5 and P4 living quite happily together on the same drive, with linkage between the libraries. However, just recently my boot disk started to die and I had to rapidly shift everything onto a new disk. Now I find that if I try to reopen a PZ3 file done in P5 it tries to load into P4 and hangs up the machine. I would appreciate it if someone could tell me what is fouled up here. Thanks in advance. Regards, David


PhilC posted Thu, 10 February 2005 at 5:07 PM

Try this:-

If that was the problem then this will be the solution. If its something different then ... errr ... ummmm ???? :)

philc_agatha_white_on_black.jpg


Dore posted Thu, 10 February 2005 at 7:03 PM

PhilC,
Thanks for the response. I tried that but Win Explorer seems to be the root of the problem, it only lists P4 for some reason. However, I tried importing a PZ3 file into P5 and that seems to work okay, so there is a work around.


PhilC posted Thu, 10 February 2005 at 7:24 PM

It may only list P4 but if you "Choose Program" and use the Browse button can you select P5?

philc_agatha_white_on_black.jpg


Dore posted Thu, 10 February 2005 at 7:34 PM

Unfortunately, no. I should have said so in my first response but neglected to so say. I tried it several times without effect. Thank you for your attention, I guess I will just use the "import" route for the time being. David


hauksdottir posted Fri, 11 February 2005 at 11:12 PM

If you just copied everything, the registry might not know it is there. Have you tried "add program" ?


Dore posted Sun, 13 February 2005 at 4:40 PM

As suggested by someone off line, I backed everything up and then reinstalled the P5 program. That fixed the problem. Watching the backup I discovered that somehow, I have no idea how, I had ended up with two copies of the P5 executable file with differing URLs and suspect that was the root cause, just confused the machine I guess. Thank you to those who offered suggestions.