Sat, Nov 23, 11:44 PM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 21 6:06 am)



Subject: HELP! ProPack SR3 upgrade on Mac - file curuption


cralph ( ) posted Sun, 02 February 2003 at 2:53 PM ยท edited Thu, 25 July 2024 at 8:02 AM

Okay - I really need some help now. Platform: Mac G4, Dual 1 Gig Processors, 1.5 Gig RAM. Operating System 9.2 Everything was working fine until I installed the Service Release 3, upgrading my Pro Pack to v. 4.2.1.179 Now - the application of any texture to a body crashes the computer.Resulting in a manual reset to reboot each time. I uninstalled all files from Poser and removed files from the System Folder(Poser Prefs) and (Python Folder). Reinstalled my original Poser configuration and the problem remains - crashes continue. I've spent 26 hours uninstalling and re-installing in every possible configuration of Poser 4.3, Pro Pack, and Pro Pack SR3 - to no avail. I've reviewed the Installation Logs and can find no other files installed. There MUST be something that I am not uninstalling that is causing this - if anyone out there knows - Please share!!! Only custom characters used: Daz3d Michael 1.0 Daz3d Tomy (texture for Michael)


lwanmtr ( ) posted Sun, 02 February 2003 at 3:01 PM

How much RAM do you allocate to Poser? had ta ask.


mateo_sancarlos ( ) posted Sun, 02 February 2003 at 3:09 PM

If you are already assigning 1 GB to Pro Pack, are you using the absolute minimum extension set (Quicktime, CD-ROM)? One other tip: use Installer Observer to find out what actually gets installed.


jerr3d ( ) posted Sun, 02 February 2003 at 5:02 PM

I'm guessing here, but I think it may be Poser is residing on bad disk space. After you have the whole Poser PP installed try copying or duplicating it to somewhere. If it copies fine. But I am guessing you will get an error that a file or file(s) will not copy because they are bad.


Charlie_Tuna ( ) posted Sun, 02 February 2003 at 11:05 PM

In my preferences folder I have a MetaCreations folder that has, along with Bryce and KTP pref files one named POSP400.txt hunt that up and chuck it in the trash and the one for ProPack which should be named similarly (don't have ProPack so don't know the exact name) then a reinstall should work right. If that don't work have Norton or TechTool look at your drive you may have some bad sectors where PP is sitting.

Why shouldn't speech be free? Very little of it is worth anything.


Gini ( ) posted Tue, 04 February 2003 at 9:01 AM

I had EXACTLY that same problem and pz3's I'd had open the day before either wouldn't open or crashed it all - I'm on a Powerbook 550 with 512 RAM , OS 10.2.3 running Poser in classic. What I finally did that made it install properly for me was ...... 1) drag everything out of runtime that didn't install with either P4 or ProPack and all saved pz3's worth keeping..... 2) trash the current installations of both and set extensions to Everything OFF . ,,,, 3) Re install P4, PP and that service release one right after the other and then reset extensions to whatever they normally are and Restart. Drag the saved runtime and pz3's back in & start up poser and try a test render. It worked for me after I tried about 4 other combinations of installing. Even setting extensions to Base didn't work . A TOTAL PAIN!! Hope this helps if you aren't already sorted out. At least you don't know where I live if you make a mess : ) just kidding

" Try and be nice to people, avoid eating fat, read a good book every now and then, get some walking in, and try and live together in peace and harmony with people of all creeds and nations."
-Monty Python


Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.