Does Windows 2000 Indexing Service help Poser (or Vue) to find stuff- like texture maps? I like Win2000's search function for finding texture maps among my thousands of folders on about 700 GB of total drive space- but of course it helps to point the search in the mostly LIKELY drive or folder to get the fastest results, but it still is very good at finding stuff. But- does the Indexing Service help to really CLUE Poser into where to start looking- or does Poser not notice this kind of indexing? Anyone know?

Poser remains clueless about the indexing system in 2000. for 2000 it's a great thing.. for Poser a complete mystery... shrug it'd be nice though na? CHeers

I don't know what the comparable mechanism is on the MAC, or if XP has an Indexing Service, but just imagine this: DAZ STUDIO comes out with an "Options" box that says: "When the loading model needs a missing texture map, use (LIST OF SEARCH OPTIONS) Windows 2000 INDEX SERVICE?" Instead of spinning off into endless space voyages like Poser does now, DAZ STUDIO would zip off using the Index Service and say "Found Matching Texture Maps, USE THESE?" ---------YEEEESSS!!!--------- Computer Science Applied!!!

No, please don't! P5 is sluggish enough at times without having to turn on extra services as well. Disabling Index service in 2000 or XP is a common step in improving performance (on various tweeking and overclocking sites). Besides, I think Index Service is vastly over-rated, having it turned on doesn't seem to speed up disk searches by any huge factor (perhaps 10% in best cases I've seen) and it can consume huge amounts of disc space for it's catalogues and be very agressive in grabbing processor resources to do indexing. -- Mark

I agree with yggdrasil: what other "things" are going on behind-the-scenes with Indexing Service? First, it has to build an index, which takes time to process and hard drive space to store. Then, it has to keep its index up to date with any changed, added, or deleted files (more processing time and reading/ writing of the Index files). So, really, what is the real benefit of using Index Searching, especially when looking for Poser files that will probably be in one of two places: Poser4Runtime or Poser5Runtime?

So how do you turn it off? Thanks, Marque

lol never mind, already had it turned off. Marque

Right now I don't have Indexing Service turned either. I'm just using the "Search" function, which for me seems to be VERY FAST. Couldn't that be used as a OPTION switch? (I have to now COPY the file name of what Poser wants and drop it INTO the search box- and then it finds it. Why couldn't this step be automatic- OR MAYBE- could someone write a ("Paging Mr. Ockham, Paging Mr. Ockham. Please report to the reception desk") Python Script that could do this? BTW- I have texture maps scatter all over the place on three drives and FOUR Poser folders- soon to be SIX Poser folders. Pointing it in one place only isn't the answer.

I know the feeling, out of control! lol I think these files must breed, I have so many scattered everywhere. Marque

I've never used this Indexing thing, so I'm not quite sure what it does. One thing for sure: there's no way for Python to grab control in the middle of a figure-loading operation. I'm working on a general Loader script, which will be for sale soon; this partially replaces the Poser library setup, including several labor-saving tricks. The Loader will include a similar feature: it will pre-process CR2 and PP2, trying to automatically locate missing tex & obj files before starting the actual load.

I'll buy it in a heartbeat! I KNOW there has GOT to be a better way. Were using COMPUTERS, after all. This is what computers LIKE to do. It's just that nobody is plugging into it. Since the general feeling is that the WIN 2000 Indexing Service creates too much overhead, that's o.k. The general search operation works great as it is- so if you could somehow tap into that feature- that would be a MAJOR Poser upgrade, I think.

(1) Poser loads up so slowly because it hunts through your entire runtime/textures folder. (2) Having ALL your textures in ONE place saves your sanity. If you have them spread out all over PLEASE take the time to put them in one place (3) How about putting ALL your textures in a folder outside of runtime. Run Correct Reference on your Runtime/Libraries (might take a few hours). Now Poser will load up fast!! and it will still find all your textures (because of C.R.)

Spin this one on it's head, how about a feature in Daz Studio that creates an index purely for Poser stuff. For example, an options panel which you list the directories where you store stuff that Poser/Daz would use. Daz Studio runs off, catalogues them and then off you go. This could then be maintained either automatically or manually by Daz Studio via an 'update catalogue' button somewhere or at regular intervals. That way it's contained in the program but seperate of the operating system, thus not slowing the system up. Best wishes Jody

But if you use Correct Reference regularly there is NO need for indexing or searching for anything. Seems to be the best kept secret around here.

Not entirely true Spit. Take my runtime, it's 17gb of stuff. Even though it's reseanobly organised it takes ages to scroll, click etc, if you had a search box in the runtime folder hierarchy where you could type 'corset' and then you get your thumbnails for all items matching the search phrase, that'd save no end of time. Another good example is textures, I want to apply my Nikkita poses from Mec4d I just type either Mec4d or Nikkita or whatever and I can get a shortlist of all I need without the need for scrolling, clicking etc. An organised runtime is half the solution I agree, but there's no reason why searching couldn't be utilised to save a lot of our precious time. best wishes Jody

Hrm. I had the indexing service turned off (indeed - it isn't even installed anymore) to increase performance - it eats more of Windows' resource pile than most people realize. Quite honestly, the benefits don't outweigh the costs, at least not to an old curmudgeon like myself who makes it a point to already know where all the important stuff goes on his hard drives. By the time I have to actually go looking for something, I will have already saved that manual search time 40 times over in previous faster rendering times, faster OS response times, etc etc. The Runtime issue has been partially solved with Poser 5 (though only though multiple runtime ability), and I suspect DAZ|Studio will be finding an efficient way to organize it's "runtime" as well... My best suggestion for either program is to only search and (as an option only) pre-index files in the designated areas within the runtime directory, and no where else. If a merchant screws up and misplaces textures/.obj files/ pose files/whatever, that's his problem, not the app's. /P

Attached Link: http://blackviper.com/WIN2K/servicecfg.htm

I killed the Indexing Service too (along with about 30 or 40 other useless pieces of junk that win 2k runs by default). If anyone's interested in what you can and can't turn off, follow the link. It helped me no end. Quote from the page 'It (indexing service) uses about 500 K to 2 MB in an idle state, not to mention the amount of memory and CPU resources it takes to INDEX the drives' mac