I've found Poser v7 to be much more stable than v6.  The only problem I've had was with SR1. 

Yes, You can transfer your runtime directory to v7, but the best bet is to install v7 in a separate directory.  You can access multiple runtime directories out side of the v7 directory.

My problem with SR1 was with dyn cloth props I've created with Truespace.  As I loaded the prop, enter the cloth room, my system freezes up as I try and "clothify" the prop.

Other simuliar props had the same issue.

I uninstalled Poser 7, then reinstalled it.  Re-downloaded and reinstalled SR1 from eFrontiers and had no more problems.

I'm using the english version of Poser 7.  And I did change my regional settings as well.

The only other issue I saw with SR1 was regards to exporting to jpg.  The image quality seems to very low. 

Arcady,  thanks for the info, I'll certainly look into that,.  Again thanks WTB for a great job.

Strixowl, it appears you're correct,  and I obviously must have forgotten to download it and install it.  With all of the downloads for the Pro bundle its easy to do I guess) 

Nevertheless, a slightly expensive lesson for me on that. 

After my problems with Poser 6 hanging,  I decided to try this in Poser 5 (loaded V4 and applied the morph) and found it was looking for the Standar Res (not Hi-Res) textures.   (I purchased the Victoria Pro bundle and it comes with the Hi-Res textures.  )

So.... Poser 6 hangs because it couldn't find the standard res whereas Poser 5 gave up and provided a dialog box for where to find V4StTorsoS.jpg.  

I then purchased and installed the standard res textures from DAZ and it now works.  

Thanks much to WTB for a fantastic job and others who helped resolve this.

I hope this helps others with the Poser 6 hangs.

Russ

Thanks for all your work!

I have Poser v6 and applying the morph unforetunetly just caused it to hang.  

Has it worked for anyone else with Poser 6?

Wow!! Great to hear its' coming soon.

The following has swaths (flooring, carpeting, etc) which are used in the healthcare industry. http://www.flooring-solutions.com/products.htm# I too would purchase this product if offered. Please reconsider.

Boni, please see my post it describes how I was able to fix my Poser 5 after the update. It might work for you too.

This was the response from Tech Support. They read my mind regarding installing to a clean directory. It now works with SR4, although I have not copied my Runtime directory over yet. I'm going to do that soon. For those having the same problems I'm having, hope this works for you! Russ Here's the complete text that I got this afternoon: "I'd recommend trying to install Poser to a new directory and update that version. The uninstaller will only remove files that it installed, so newly created files (preferences and such) and added content aren't removed when you uninstall. If any of these files are damaged they can still be problematic for the new installation. I would suggest going right to the SR4 updater, but certainly if you would like to be cautious you could try SR3 first. Once that is running succesfully you can perform the SR4 update again. When you get a copy running in the new directory you can integrate the old content in a couple of ways. You can use the multiple Runtime support of Poser 5 to dynamically link to your older Runtime. To do this click the "Up" arrow at the top of any library until you reach the top level. You can then click the "+" at the bottom of the library to add a new Runtime. Double-clicking any of the listed Runtime directories will load the contents of that Runtime for the current library. If you use this method for accessing all your content I would recommend manually deleting every except the Geometries, libraries, and Textures directories. If you anticipate using this method it might also be a good idea to choose the Minimum installation when installing Poser 5, or select Custom and pick only the new Poser 5 content. This will help avoid having alot of duplicate content using up drive space. The other way of integrating the legacy content would be to simply move the older Runtime into the new Poser directory. The two Runtimes will be merged, however newly installed files will be overwriten by the older ones. Again I would recommend deleting everything except Geometries, libraries, and Textures directories before merging. This will prevent updated resource files from being overwritten by previous ones. Lastly, (with tongue partially implanted in cheek...) by all means please do move Poser to XP!! More seriously, it would be a good test to install Poser on the other machine. Note that the license allow installation of the software on any number of machines. It only prohibits running it simultaneously on mutiple machines. There would be no problem having it on each."

More on the Poser 5 "stops responding" at FFVrml.arp on startup after applying SR4 on ME. (I haven't heard back from Tech Support yet) I've backed up my large runtime dir (15+ gbs) so my "assets" are saved. (huge sigh of relief) next steps/test: 1) I'll install Poser 5 into a brand new and clean directory (barebones runtime) then reboot my system. (after deactivating antivirus software) 2) start Poser to allow it to initialize itself. 3) If ok, I'll re-install SR4 and restart my system again. 4) Restart Poser and if ok, copy back my Runtime dir into it. 5) Run Poser again to see if the runtime dir size still an issue. I'm thinking the first start of Poser either via install or SR, the relative size of the runtime dir may be a factor. Once this initial start runs, then the system runs ok after that. Secondly the usage of Cacheman had been recommended by Curious Labs as a way to deal with memory usage by ME systems. The OS limits an application to 128mbs ram only (even though I have 512mbs I can't use it). My second thought, does Poser SR4 require mote then 128mbs to startup? I'll keep you updated on progress. If all else fails, I'll move my Poser to my XP box. Russ

Ran defrag, unload Cacheman - still no luck. Still locks up at FFVrml.arp The clean reinstall of Poser 5 and SR4 didn't work for me and I even backed out to SR3 and it too failed at startup. That was what I was at before SR4. Back to tech support. Fortunetely for me I have 2 systems, the other is XP so I'm going to transfer my poser to it. OS is Win ME, very large runtime folder (15+) Gbs...

I talked to Tech support last night, very fast response. They recommended running defrag on my system (I had very large runtime folder 15+gbs) and suggested I not load Cachemann v5.11 to see if the memory manager is causing the issue. Only then they suggest uninstalling Poser5 and reinstalling it (note it will not touch content in runtime, only files it installs) then reinstall SR4. (for those who wish to backout to SR3 you can install this instead). They indicated the SR is cumulative but it prefers clean Poser 5 install. I had to do this for SR3 when it came out so my systrem (OS is ME) was already suspect. I'll let you know if it works.

I'm using Windows ME, working to get XP asap. I've found it to be a lousy OS and wouldn't be surprised if it is part of the problem.

I had a very similar problem with SR3, I had to fix it by uninstalling then, reinstalling Poser 5 then installing SR3 over it. I'll wait and see with tech support has to say, I might have to reinstall Poser again.