Hi folks In the last days I'm finding the same bug in Poser6 SR2 time after time. When I open the program, or when I'm working for a while, and I try to open a folder, for example 'Characters', a message appears: 'this operation can spend some minutes' (or something like this) and it stops for a time like is re-building my folders. Sometimes the message don't appears directly, I want to open a folder and Poser isn't displaying my directories but a single option 'rebuilt libraries'... and again some minutes until it displays them again. This is annoying. How can I fix it ????

Hasn't happened to me. I have 2 Runtimes and never experienced a single problem. Has your disk indexing got screwed up somehow?

No AFAIK

If you are using XP you have to keep in mind that the file system is designed to handle about 100,000 files in his index by standard settings. This allocates about 12.5 % of the HD space. If you exceed this limit, the MasterFileTable has to be re-written every time you want access a file thats not in the actual MFT. You can overcome this limit by editing the Registry. Look at: HKEY_LOCAL_MACHINE System CurrentControlSet Control FileSystem and create an entry: NtfsMftZoneReservation With a DWORD = 2 This will allocate 25 % of your HD for the MFT. But before I would check the number of files on your HD Ulli

Hmm.. I've got zillions of files. And WinXP. And I've never poked around in the registry. Yet, I've seen that message Casette mentions, but only once, as far as I can remember. So if it was a MFT problem, shouldn't I be getting it over and over again, if it can be triggered once by that? I don't know what causes it. How big is your runtime? And when did you last defrag? Oh and make sure that indexing crap, findfast, is turned OFF, it makes all sorts of funky stuff happen otherwise...

My HD has 140.000 files My main runtime 13'5 GB And where oh where I turn off that indexing crap?

I have XP and I get this message sometimes too. I don't think it is OS related. The message says that it is rebuilding the runtime menu tree which might take several minutes, but actually it is very fast. Maybe it thinks that the state of runtime has changed because the user manually added or deleted some files. (I didn't though.) It only started to appear quite recently. Casette: maybe we should post in the CP support forum. I will try to make a note of the exact message next time it appears.

Maybe. I'll aks there. Thanks :)

Emailed. Now only I want to wait a billion days... or two :(

I am with XP and use Poser 6 with with two big runtimes.I have the same message and problems from time to time after the last Poser update.Never before.For now i live with it and take patience.I hope e-frontier correct this sometime

it first started appearing in poser 6 after sr2. not really a big issue for me though.

Same problem here but the message itself is rare. It's the frequent hang time for minutes that keeps getting in the way. o_O

I would recommend contacting Tech Support at e-frontier. I experienced this (before SR2 since I just installed that recently) when I had one really big runtime. I redid my Runtimes to get rid of the big one and I have not seen the error since then.

I havent seen this one myself but i remember reading about it in the SR2 readme. Library ------- - Library popup menu code rewritten to improve performance on building menu - Added 90 second timeout on menu building to avoid excessive launch time when extremely large runtime folder is active. Select menu item "Build Folder Menu..." to force building menu structure. basicly it means your runtime is fricking huge. Poser builds the menue structure each time you go into a runtime. thats why going to a big runtime takes longer than going to a small runtime. this is just a "friendly" reminder that it will take a while to open the runtime your selecting. and there is not a way to turn it off that i am aware of.

I've made a "dummy" runtime called A1 and it's completely empty. Because of its name it's the first one Poser looks at - so, the program launches pretty much OK, tho my main runtime is only about 3 GB - I keep it spring cleaned on a regular basis.

Well, their Technical Support is nicely working. The answer (I hope it helps anybody):

*Dear Sr. de los Rios,

Part of this may stem from running the English version of Poser on a Spanish operating system; the directory paths for a Spanish OS won't include the same folder names as Poser expects to find. That being said, you may be able to clear up at least some of this problem by deleting your Poser preference files; when Poser has been running successfully for a while, but then starts behaving badly, often it's because the preference files have become corrupted.

This is especially likely if Poser has crashed or been forced to quit, as then the preference files aren't closed properly. Corrupt preferences can lead to all kinds of misbehavior on Poser's part including frequent crashes. This is annoying but easily fixed- in short, you navigate into the prefs folder inside the Poser Runtime and delete the preference files found within; the process is described and illustrated in our Knowledge Base, here:

http://www.e-frontier.com/article/articleview/1761/1/595/

You should also be sure that you have updated Poser 6 to its most recent version (6.0.2.118) by downloading and running our SR2 updater (available from www.e-frontier.com/go/downloads/updates as a free download for registered Poser owners.)

If this doesn't fix the problem, please get back in touch and we'll see what else we can do.

I hope this helps!*

Me too :)

Cassette and anyone interested. To turn off the indexing right click your hd and select properties then on that window on the very bottom uncheck Allow Indexing Service to Index this Disk.... Caution tho it will take it a bit with a lot of files if its never been turned off.

I've never had any problems with the "Indexing Crap". What kinda funky errors does it cause TG? I'd like to know what to watch for to see if it's happening to me before I go turning it off.

Interesting that there are so many theories what causes this. Here is mine: The runtime exceeds a certain size and Poser stops indexing it, unless explicitely instructed. So either increase the cutoff size option (but WHERE?) or shrink the runtime.

Well, by the moment I've done the tip from EF. I don't know if it works, because I've opened P6 only a few minutes ago... usually the bug appears several times on a day, so in the next hours I would tell you if it worked to me or not

UH-OH The message again. I'm afraid the nice answer from EF was useless... :(

I'm afraid the nice answer from EF was useless... :( Not only that, but the issues they do cite could - and should - be addressed in ANY program. It's not hard to design a system which does NOT leave a critical file, esp. a small one, open in a state where corrupt would/could occur when the app itself crashes. Programming 101. And as for not being able to determine what the key folder names are on different language versions of the OS is equally pathetic. Most sadly, this message implies that eF Technical Support doesn't know under what condition this dialog is displayed either! > Interesting that there are so many theories what causes this. In the face of this, what else can we do, but theorize? Sad, sad...

I get that all the time.....but i just have one runtime and i figure its coz its huge lol

Check out the net for the limitations of XP and then try my suggestion above. I had the same prob until I used the settings above. It's for sure the limitation of XP and NTFS.

Mizrael.. Sorry for the late reply. Anyway, FindFast takes up a lot of system ressources and that's why I rate it as crap :o) It can also set your HD to work on idiotic indexing when you for instance is rendering and need the computer to work on the swapfile instead of putting things in little idexfolders ;o)

Yes, but drive indexing and fastfind are two different programs. I don't run fastfind but I've never turned off indexing on my drives either and never experienced the problems you mention.