cliffwms, Where there are 3 links for a product on Tomiya-san's site, the 3rd one is a link to the image. Also if you use Mozilla in place of IE (a good thing for many reasons), it's trivial to add the needed extra fonts. Instructions will appear when you encounter them.

This is probably obvious, but just in case as the installer doesn't say anything about it, the target folder you are expected to know to browse for is Poser (not Runtime). But if that's not the problem, and you are still intent on playing Poser 5 Roulette, I'm thinking that copying the SR4 exe into the Poser 5 folder first and executing it there will work. It appears to have been what the programmer who wrote the installer, and CL's QA dept(?), did.

A 6 rib version is available in PoserPros Free Stuff - near the top of the pile. There's also a link to another one in teh same thread.

Just another CL bit of clever programming - it can't find a known directory... (It needs to be installed in the same directory as it's to be installed in - a concept that died out right along with DOS ver. 2 I think it was.) Ignore its demonstrated lack of good programming, click Continue, and then Browse to find it yourself. Or take it as an indicator of things to come, and go no further ;-)

ynsaen, "that intolerable delay on the parameters has indeed been fixed" Wow. On mine it's even worse on SR4 than SR3 - much like it was before I removed CP. So looks as if I too will have to re-install from CD to remove SR2 "effects"... And thanks for the tests on Sector 0 - that was indded why I wasn't going to try the re-install.

Just a guess, but perhaps it's related to this fix: "Shadow map memory is now properly freed after calculating each frame." If it was previously effectively using a fresh copy of the "Shadow map memory" each time, then it wouldn't have matter whether it was cleared or not... Now it does.

ernyoka, Unfortunately the Interlok Sector 0 header is written, certainly by the Poser 5 CD initially shipped. It is highly probable that a later pressing of the CD, with SR2 already applied would not do this (to avoid the royalty payments to PACE for a feature CL wasn't using, if for no other reason). But whether there exists such a later pressing of Poser 5 I do not know. I'd like too, because if it does, I'd like to ask CL for one so that I can consider a full re-install of P5 (to see if it works any better with respect to the dumb floating separate focus parameter window). All the info about the Poser 5 SR2 and Interlok was here on R'osity posted by CL in the Poser 5 Beta forum, but all of that was deleted by R'osity ASAIK. CL was very clear at the time that SR2 does NOT remove any Interlok code at all ,in fact leaves it present, correct and running - for the reason I mentioned above. (They just dropped the links to it out of Poser 5 SR2 - and above.)

But installing an original Poser 5 CD will right Interlok code to the sector 0 of your primary drive again. That's the potentially dicey bit. The SR's (2 and above) do not write to sector 0, agreed. Reason is they do not remove the Interlok code. They simply remove Poser from being "watched" by Interlok. Interlok is still running (it has to be in case it was already "wathcing" another installed app). There was install code to permit the removal of the Interlok drivers on PACE's site if you no longer need it, but I understand they are no longer available. But even that wouldn't remove the entry from Sector 0.

WARNING, I've not tried this, but... I would only move the "content" folders. Within Runtime - no need to move anything outside of that - move Geometries, Libraries, Reflection Maps and textures. They are all folders that you install products into. If you've installed Python scripts, you may need move them -perhaps individually from /Python/poserscripts. Do NOT copy over things like ui and prefs - that's where the xml and the like are - which is possibly the "bits" left over from SR2. (It was a topic of some concern back in the public "beta" of SR2 that new files were being added, but nothing deleted.) Take it cautiously and if everything works, you moved enough. BTW, when you install Poser 5.0, apply SR4 before you even think of starting Poser 5 (no need to start all that copy protection code up that's going to be undone by the SR). If you've already installed the Figures SR, you may not need to apply it again (the fixes should move over with your content). Otherwise apply it last, after you've moved your content over (else you'll undo the update).

PoserPros, in the Poser 5 Tips & Tricks, as a "Stickie" - at least that's the easiest one to find.

However Poser - any version - is big. The files it opens and uses are large, and it pulls an unbeliveable number of them into memory, compared to other applications. Not saying that Poser can cause HDD failures per se, but if you have any weakness in your HDD sub-system then Poser will likely be the app that pushes it over the edge. Happened to me twice during the public "beta" of P5, until I realized that my Power Supply was marginal with all the extra HDD and stuff I'd installed. Finally P5 as it was first shipped included Interlok "copy protection". That does write to your HDD disk header "sector 0" area - an area that only Fdisk would/should normally write too. This could conceivably have some side-effects if the HDD sub-system wasn't in good shape. I'm not sure if later versions of P5 CD's still had Interlok code present. (Note SR2 removed the monitoring code, it did not remove the actual Interlok code.)

There are 2 variants of the .xml files (in the ui folder) - depending on... we're not sure... But with the invention of the logic to remove Content Paradise we became aware that some xml files were different. And these directly influence what's loaded and in what order. First thought was that either the very early versions were some how different, or that the patch path was different, depending if you went SR1, SR2<"betas">, SR2, etc., or straight to SR. Given that CL is reportedly suggesting re-install and patch to SR3 or 4 directly to some, this might suggest that the issue is with SR2... But this is all hypothesis. As Poser is clearly very buggy, it's of course not possible to predict behaviour, as repeatability just isn't ever there in buggy apps.

ynsaen,

You're free to be a CL booster if you want, same as I'm free to have opposing views, but please get your facts right:

8 - When you purchased P5, you had 30 days to return it. What? Oh, sorry, then.

CL would not honor returns on the first release of Poser 5. And as I bought it directly from them I could not return to the retailer either. Nor could I contest the credit card payment as CL (illegally) billed the card at order time before the product was available to ship, and so way too much time had passed o contest when they did finally ship.

And FTIW I have stopped using it, which is why I'd still like to get my money back. I just tried the SR4 update to see if it had fixed the intolerably slow and unpredictable parameter dial adjustments.

5 - The change to the library had nothing to do with png display speed at all. Or even library display speed. It simply makes it easier to see what you have in a folder that happens to be full.

"see" ... by not displaying them? Ha, ha, He, He. That's sooo funny as a reason to mess with something that wasn't even broke.

No it's apparently not coming until next year, and will cost $'s (P6). Whether it'll fix bugs - as the current (and the previous) CEO promised - or add features and bugs - as the survey effort seems to indicate - we won't know until ... some time after P6 ships.

I agree that they needed to speed up .png thumbnail display - it's even a problem on PP - but could they really not have speeded up the actually .png display code itself - on 4 year old code? I too find "Oh our .png display code is too slow for you, then let us turn it off for you" a tad insulting. (Even switching it back to .rsr would have speeded it up.)

And to rub it in they choose a relatively low value, and instruct you to use an editor to raise it! If they weren't at least going to address it via a Prefs setting in the ui, they could at least have set the default to something innocuous like 1000. I predict we'll see a steady stream of "What happened to my thumbnails?" posts in the future months. Like we do for shrinking library names, and the scene window off the upper left of window, and ...

What were they thinking? I'd REALLY like to see CL's definition of when a product is "good enough" to stop fixing it. It might make interesting reading. (I'm guessing it's along the "when it gets too hard" lines, rather than anything objective ;-)

And to avoid someone else having to say it, yes I am still "ungrateful" for CL shipping but not fixing all of it's problems in 18 months (on a release that appears to have had less than that as a development schedule). And yes, I'd still take my money back in exchange for putting my copy of the software out of its misery if they'd give it to me.

maclean, You suppose right, plus I leave mine on. But I think that has to be there, in case a trojan succeeds in issuing a shutdown request via an unforeseen means.