Jim, no, the ref to Tech Forum was to that old, old article. Yes your method is the right one when the Inj files are set up correctly with no numbers. But the Daz ones still come out with Figure 1 set everywhere. So only fixes to date are: - Load figure, inject all required morphs, and save out as a post-injection figure for reuse as second or subsequent figure in a scene. - Edit every Daz inj file, including all the updates, as described way back in the Tech Forum. And then as you state, make sure you select the correct figure when you inject, else Poser will not know which figure is to be injected. Note also that this approach breaks crosstalk used for conforming clothing in P4 and PP, but Hogsoft's Crosstalker applet will address this, (and enable crosstalk in P5/P6, and defeat it in P4/PP in other situations). As Crosstalker is based entirely on a method discovered and published by you, Howard releases Crosstalker for free. I know of now other way ... currently ... ;-)

It's a limitation of the readscript() command used in Daz's Injection process. It's an old command, and it will always apply its injection to the first figure loaded in a new scene (note not a figure named "Figure 1", but the very first chronological figure in the scene). There is a way around it, but requires some extensive editing of the Daz inj files themselves. Do a search on FII or Figure Independent Injection in Poser Tech forum. There was work going on to provide FII capability on-the-fly, but the release of P6 has caused it to be back-burnered for a while :-(

Unconditional multiple undo's would require a rewrite of Poser code. Now we'd all like that for a number of reasons totally unrelated to undo's!!! But if it hasn't happened to date, in fact not even a part of the core Poser code has been rewritten in what 10 years, or ever, then it ain't likely to happen anytime soon for a trivial - in marketing terms - reason like no undo's. But a conditional multiple undo might be do-able without a rewrite. Changing dial values for example doesn't require any complex state retention, just store the prior value(s) and redo the action to equate to an undo. That should be easy to do and deterministic enough (ie. what is covered by multiple undo and when) to be viable.

You can try limiting the total of real and virtual (paged, swap, whatever you want to call it) to something less than 2GB total. E.g. 1GB real and 960MB virtual. It won't stop P6 wasting memory (even by P5 standards), but it might stop P6 failing quite so badly when it does deep six it's memory allocation. No version of Poser to date appears to be able to contain itself to the 2MB address limit imposed by Windows on all applications. Go over 2Gb in any version and the results vary, but they are all ultimately terminal. When it goes over 2Mb it'll be writing on memory allocated for other uses - presumably the 2Gb Windows reserves for each executing applciation for its own OS use - and things will go badly wrong. As to why P6 uses memory so badly relative to P5 - which itself was pretty bad versus P4/PP - check one of my recent posts (search on layingback) which links back to a post by WierdJuice than explained what he discovered.

There's a (stupid) setting in one of the xml files. If the value is left at default of 100, then any entry in a folder at poistion 101 or greater doesn't show. (This was branded as a feature by CL, despite cries from this forum of "people will keep running into this and getting confused" we were ignored.) Sorry, can't remember the name of the file offhand, but a search of this forum shoudl find many references to it. Change it to a huge value - eg 2000 - so it doesn't both you again.

RealDeal: The big hurdle for W2K that I see in the future is the dual core AMD 64 chips. Will they be able to run as anything more than single core systems? Hope so, 'cos AMD/W2K still seems to result a way more efficient system than XP/Intel...

Of course XP is more popular than Win2K, as most major PC vendors are induced to sell only with current versions of the OS - i.e XP - by guess who? XP does have a few features not available in Win2k as mentioned, but it also has a lot of floss that isn't really needed, in the same way that ME was just 98 burdened with extra stuff, and worse for it. More code equals more to go wrong, and more potential exploits to be exploited. Win2K was not ever very popular with home users, because pre-XP most home users where still content to use products from the 98/98SE/ME series.

Win2K - provided that you never install IE6 or later versions of WMP - will give you a lot less security traps than XP. But you will not benefit from security fixes from Micro$oft for much longer. You can also get much of the performance back from XP by disabling all the XP-specific ui flotsam, and using the old interface. But you will have to deal with the activation code of XP, and the DRM (digital rights management - as in, managing the digital rights of others on your computer) built into XP (and later versions of WMP for all versions of Windows).

So like most things, it really boils down to personal preference, and what's important to you in the trade off of features in the OS versus control over your system from a user rights perspective. You'll be able to make either work more than well enough to run Poser - well, as well as any copy of Windows can be with its "attractiveness" to viruses, trojans, spyware, et al.

QuickMat will build both at once - it's fully automated, no editing. Else you can convert your hand hacked PP ones to P4 by creating an .rsr from the .png - P3dO will do this on a per folder basis.

They are probably opening outside of your visible workspace - or under something else. If you can't find it, or you don't have a way of temporarily expanding your Windows desktop/resolution size enough to make it accessible again, then you'll need to go to General Preferences and reset to default. Snap a picture or commit you current set up to memory first, so you can later re-adjust everything back to your custom configuration once you have retrieved the missing component.

It happens to most of us sooner or later. Poser will let you drag things off the visible desktop, so it can occur quite accidentally. Once you do have everything repaired, consider saving it to a UI Memory Dot, so that next time you can just apply the UI Memory Dot to get it all back as it was.

Attached Link: http://www.renderosity.com/messages.ez?Form.ShowMessage=2174088

Scroll down to #15 on the attached link to a post by WeirdJuice. Not only does he provide a very clear and detailed description of the reason P6 has an even bigger memory problem than (even) P5, he also explains how 4 hours of work on his part appeared to improve things considerably.

But it's the sentence "The good news is that, as the morph loading and storage processing has been changed in P6, it can now be considered to be "live" code and it should therefore be open to further improvements" that expresses what I'd sensed back in the P5_SR2_beta discussions with the likes of Larry W: that some of the older code seems off limits, ie. inaccessible, to CL. If it were true it might explain for example, how a 2005 product which claims W2K or XP as a requirement, stills sports Win9x style file dialogs!

Attached Link: http://www.renderosity.com/messages.ez?Form.ShowMessage=2174088

Scroll down to #15 on the attached link to a post by WeirdJuice. Not only does he provide a very clear and detailed description of the reason P6 has an even bigger memory problem than (even) P5, he also explains how 4 hours of work on his part appeared to improve things considerably.

But it's the sentence "The good news is that, as the morph loading and storage processing has been changed in P6, it can now be considered to be "live" code and it should therefore be open to further improvements" that expresses what I'd sensed back in the P5_SR2_beta discussions with the likes of Larry W: that some of the older code seems off limits, ie. inaccessible, to CL. If it were true it might explain for example, how a 2005 product which claims W2K or XP as a requirement, stills sports Win9x style file dialogs!

Attached Link: http://www.hogsoft.com

Yep, Poser's .psd and .png file format readers are kinda old, so they are intolerant of the newer (last decade's? ;-) format enhancements. For .psd used in P5 and P6 UI folder you HAVE to use Photoshop to save them, nothing else seems to be able to save things "the way they used to" :-)

Happens when the .png is made by something that isn't 100% compatible with Poser (or at least Poser on Windows). First off, check the library folder where the .png file is stored in Windows Explorer or similar: - if there is a .rsr of the same name, then simple delete, or for extra safety rename, the .png file when PP is NOT running, then restart PP and go to that library folder. Poser will recreate the .png from the .rsr and the new one should be 100% compatible with Poser (obviousl ;-) - if there is no .rsr file of the same name, then first run P3dO's RSR/PNG plugin on that folder to create an .rsr from the .png. Then continue as described above. All in all a pain, but be thankful that it's at least readable in P3dO - 'cos just sometimes they are not, then you are down to fixing it in Photoshop by hand...

Jim, You can actually change the font size in Poser labels - eg. paramDialPrefs.xml - by changing textSize= for name and groupName. (And you can flip font betwen serif/san-serif.) Note however that a larger font will result in even more text overlap between param labels and the value - unless you adjust all the offsets.