Hi :)

I am having a weird trouble.

I have lot of my promos PZ3 files, all correct, all saved with the correct locations of each thing.

I recently changed my machine but the installed Poser content is all in the same disk letter, so I think is not a problem of paths.

I installed Poser7 NOT in the default destination, I putted it in the same diske where all the runtimes are.

It works, and open the recently saved files, but cannot open my old files, not so old, a month ago approx the newest... it hangs, and eventually appear as if "Libraries Palette" and "Parm dials" are failing. There  is not other solution that close the program, and open again.

I unistalled it, and installed again. Loaded all the runtimes past night and seemed to work because I opened 3 of those files I was not able to open. Regarding the LOT of memory and power of my new machine, took too long, but opened.

Now, after the night, is not working again.

Cannot open the files.

Some help needed, please.

I am waiting for the other big disk to put PP2012 there but now I need my poser 7 opening my files...

thanks!!!!!!!!!!

fabi

Fabiana - where did you install your DAZ figures?

It might be you installed them in the original P7 runtime on your old machine and now on the new machine Poser has trouble finding them.

Just a guess

Do you still have the old configuration?  If so, you can re-load each scene and use the python; Utility Func, Collect Scene Inventory.  Choose Copy to Folder.  All of the scene resources will be gathered to a folder of your choice.

Good Luck,
Rªnce

I installed them now in the P7 runtime. And in the past I also had Poser installed in the same disk letter... the thing is that some files finally FINALLY open but take too long...

Rance: not sure if I get what you say... I want to open the scenes, as they are, with camera, settings, lights, poses... and if I cannot open the scene, how can I duplicate it?

Sorry am lost today :S

A possible reason is that the pz3 contains references to files with a different path (example would be the V4 files which were stored in the P7 runtime). If Poser cannot find it in the path which is references is goes on a hunt to locate tham in all the runtimes which are attached. If those runtimes are very large, it might take a very long time.

One thing you can do (I think this was introduced in P7) is to limit the search range by setting the search to "shallow" in the General Prefences. It will then only look in the most logical places in all the runtimes and give you an error when it is not there. At least then you know which files cannot be found. - that is, if that is really the problem

I mean, do you still have the original machine, runtimes, etc.  From that machine you could use the python script to gather the resources, copy that folder to your new machine and load the scenes from there.

If the problem is that your runtimes aren't setup correctly (the same as the original machine) the export tool should work for you.

Another option is to use a utility to sync the runtimes between the two computers.  Something like SyncBack.

SyncBack is a great tool for keeping the runtimes of two machines the same.

http://www.2brightsparks.com/freeware/

I use this alot using two copies of Poser 7 on two of my networked machines.

-R

Quote - SyncBack is a great tool for keeping the runtimes of two machines the same.

http://www.2brightsparks.com/freeware/

I use this alot using two copies of Poser 7 on two of my networked machines.

-R

Of course you can also share the runtime on one machine and then attach this shared runtme on the other machine in Poser. You can do this if you have mapped the share as a networked drive (with a driveletter)

I am doing this for years with P5 and up

You DO have Deep File Search selected, yes?

Just trying to think of reasons your scenes will not load correctly.

Do the scene files use 3rd party light sets or custom light sets that you didn't add to this install of P7.

Back in the early days of P7, I had issues with scene files from P6 opening in P7.  EF tech support told me that I needed to install the custom light sets to P7.  I did and it solved the problems.  Their long explanation didn't make a whole lot of sense to me but it worked so I really didn't care. 

When you reinstalled Poser 7, did you reinstall SR3?

You could also try copying over your Poser directory from the old to new machine-it is self contained so it will work that way...

Thank you all for the help... finally I found the problem and believe me that this made me think I was living in a parallel world or so where the machines take decissions...

I installed and uninstalled ALL POSER7 with the SR 2 times... and the problem was the same. Finally, I plugged all on my old pc, that for reasons of space is not operating now and then all opened fine there... So well, went to the new pc again and started to blame Win7 and Flash... till I opened in Cr2 editor one of the pz3 files... You won´t believe this... in the first path calling the file has, instead of the disk letter and the (:) after that, whatever the letter disk was or could be, Poser or something else in the clonation of the files in the disks, putted the letter with TWO (:)!!!!!!!!!

So, the pz3 was calling to F::Poser:Victoria4:Runtime:Geometries, blablabla... then this could take forever to load or never load as happened... but never gave error, or prompted for search... nothing, just freezing or crashing.

I was going to change the disk letter on the pc but then preferred to make a batch replacement and just change the ocurrences on the pz3 files. That solved all and now all files can be opened and edited.

Incredible. Never saw something like that in files saved directly from Poser and never edited... that could happen in files where you replace paths but no in direct savings.

Well, more data to add to our infinite collection of curiosities from Poser :)

Thanks to all and next time you clone a disk, take a look what happen with the colons LOL

see ya

Fabi

Congratulations.  I am happy you got to the bottom this.

Best Wishes,
Rªnce