Having a ton of content like most--- what is the best/recommended way to move P6 content over to P7... simply move the runtime folders? --- or reinstall every item individually (which would take forever..., but is the better way...) regards

Quote - Having a ton of content like most--- what is the best/recommended way to move P6 content over to P7... simply move the runtime folders? --- or reinstall every item individually (which would take forever..., but is the better way...) regards

Make the P6 Runtime an external one for P7.

Don't copy it into the P7 one, you'll break P7 completely and have to reinstall.

How would I make the P6 runtime and external one for P7?

Attached Link: http://www.renderosity.com/mod/forumpro/showthread.php?thread_id=2075638

See attached link.
The process is exactly the same for all versions of Poser that support external Runtimes (i.e. P5, P6, P7).

great-thanks

FWIW,

My successful formula was as follows:

I copied the entire Poser 5 and Poser 6 directories to my other hard drive, e.g., from C: to E:

I then ran SettingsControl PanelAdd Remove Programs and removed both Poser 5 & Poser 6. This left all of my additionally generated files, but **removed all the program files and content that had been installed with P5 & P6.
**
Next, I simply copied the runtime folders from my E: drive back into C:Program FilesCurious LabsPoser 5 & ...Poser 6 where they had been originally. **This replaced all of the content that the uninstall had removed.
**
I then installed Poser 7 as a custom install with new content only (there is a dialog during the install process that allows you to select this option.)

After P7 was installed, I added the P5 & P6 runtimes to the library with the Plus Sign while on the top level of the Library Palette by browsing to their location on C:. This method retained all of the original paths to all of my content and eliminated any possibility of crosstalk with *.dll's, registry issues or other unknown files left over from earlier versions of the program.

This also gave me the protection of a total backup of my content in case anything went awry.

P7 System has been totally stable, even the del key works. I have one 20-in monitor fully dedicated to a quad split of camera views with the other 20-in monitor handling the animation palette, graphs, libraries and parameter dials. Everything is working perfectly so far except for one time when the Enter key would no longer start and stop playback of a multi-layered animation.

HTH

 
<;))###><<  
 

Disclaimer: The above method worked for me and should work for you as well, however I will not be there to prevent you from doing something incorrectly, so I must clearly state that I can in no way accept any responsibility for your actions or their results from following my suggestions.

thanks for the ultra detailed walk-thru. i appreciate it.

Happy to help!

 
<",}}%%%><<  
 

nice work fuaho.

ok so copy the while entire poser 6 directory not just the runtime? and copy it to E:

I was happy to come across this thread and wanted to try out adding a old runtime folder. I was introduced to 3D graphics with Daz Studio and since have aquired Poser. Using the above methods, I tried to get Poser to recognise my DS runtime. I get the new folder showing the new runtime but it is empty and shows no content. Does this mean I will have to install any material I want to use in Poser as a separate and duplicate install? I even tried to access it from the collections folder but got no where there as well. Am I doing something wrong or can't this be done. When I installed content to begin with, I installed it to a blank folder and then manually copied the items into the DS runtime in the same folder/naming scheme as was installed in the blank folder. So it should be poser friendly with the same layout. Mind you there is also Daz stuff mingled in with it. Any thoughts or suggestions on this?

The Bob:

I copied the entire subdirectory over simply because I had no way of knowing exactly what the uninstall was going to remove. I wanted to be able to replace any missing files if necessary.

I used E: simply because that is my next hard drive. For you, it may be D: The point was to copy it to another hard drive connected to my system so I'd have the fastest copying times for the large amount of data involved.

Post Op, it appears that just copying the runtime folder back and forth will be sufficient, but I would still recommend copying everything since it gives you protection in case P7 causes you problems and you have to re-install P6. Remember, you are removing ALL the relevant P6 files when you do the uninstall.

Peterk2004:

When you add the new runtime, you must drill down all the way to the runtime folder. You cannot just stop at the DAZ, Poser X, etc. subdirectory level. 
Also, it is usually a bad idea to move or change any directory structures manually as you've done because some content uses absolute paths, not relative paths. This means that if you change the path, things get wonky. Better to use the installers and let them put things where they want and then always leave it there. That is exactly why I went through the above method. This got rid of my previous installs but kept all of my content in the same path locations. 
There should be no problems with Poser using DAZ content as people do it all the time.

HTH

 
<,"))###><<  
 

hmmm - I must admit that I am a bit concerned about this issue as well. I have the box edition of Poser 7 - but I am shy to admit I am a little concerned about installing it due in fact to this whole library issue. 
While I am a good software user - I am not good at all of the technical aspects of making a computer work - such as the technique described above. I do not have an external hard drive . . nor do I want the expense and complexity of this. 
I have spent a lot of time organizing files in the P6 library (renaming them to remove all of the annoying !!! symbols venders use, etc).  I am, admittingly affraid of feeling like I will start over. 
e-frontier - if you are reading this . . . I would like to request that Poser 8 uses the same library directory . . . . please don't make us recreate all of our work each time we upgrade. Maybe this is not a problem for all the techies out there. . . but for me, it is a real issue. 
I am reading the manual now . . . and will install once I feel comfortable. The manual text for this is not very clear to me about this. Seems like more tech talk . . . Please remember there are users like me who are not skilled or interested in discecting our computer hard drives.
Thanks for starting this thread - it is nice to know others are concerned as well. 
Tim

why cant i just instal all new poser 7 stuff to my poser 6 folder

I am not super clear on the absolute versus relative path concept that is mentioned. The reason I ended up doing things manually in the first place is that the installers usually gave me more troubles than I cared to have to correct. It certainly would have been less work but I wouldn't have learned much either. I did drill all the way down to the runtime folder and got the red dot on added runtime to boot, but still did not see the new content. I tried other stopping places, got the red dot too, but still no access. Maybe I should have rebooted and seen if that some how helped. But I didn't. Should I have? Also the Poser application and runtime is not on the boot drive, as that sucker is too full for all the stuff that adds up. I dedicated the secondary 400 Gig drive to 3D apps and so far have not regretted the decision. I am puzzled about adding my Daz runtime and don't want to have to re install everything.

Went back to Poser today and tried to add the Daz runtime again but was going to reboot immediately after. I did exactly the same thing as earlier and before you know it, I was looking at content. Don't know why it worked this time at all. Thought I would pass this along. If at first it doesn't work, don't give up. And there isn't a good reason for that either. Why do we punish ourselves so much ? Giving up is so much easier.

Um, am I mistaking, or doesn't D/S have its own file extensions that don't work with Poser?  I mean, I know that Poser stuff works in D/S, but things like those juicy freebies that came with D/S don't work in Poser.

Quote - Um, am I mistaking, or doesn't D/S have its own file extensions that don't work with Poser?  I mean, I know that Poser stuff works in D/S, but things like those juicy freebies that came with D/S don't work in Poser.

That is correct.  Poser files are backward compatible with D/S, but NOT vice versa. DAZ keeps their freebies to their selves with usage of proprietary file types that are not usable in Poser/.

To be fair, both programs have files the other cannot read. I am only a newbie at this but Daz cannot read the material files Poser uses because it does not have a material room. Poser uses PZ3 scene files Studio can't read and Studio saves its scene files with its own extension. So no wonder Poser can't read it. Except for areas each has developed that the other doesn't use of some reason, all the other stuff seems to work just fine. As for the freebies, it all depends on what they are. But plenty of them work just fine. It sure makes you pay more attention to file types and how they are used. Dynamic clothes are not part of Studio yet, but many people like the DS way of posing and lighting better. Since it is a free program it is not hard to find out the differences for yourself. Depending what I am doing , I will certainly be using both for a while. Both allow you save your render as an image in many formats which means both are recognized in Photoshop and other image editing software.

This worked like a charm for me.