Hi Swamp- Well I experimented on both Win2K and XPPro machines. I tried COMPLETELY reloading everything on ATA and SATA drives over a two day period, even re-formating the drives, etc. The dll effect was VERY NOTICABLE in every instance. I did it several times just to be sure it wasn't something else-. BTW- the dll's ARE different in size and dates in all three cases, and I saw the speed-up BEFORE I put the asi32_13.dll in as a final experiment. However, throwing it into the mix seemed to also be nothing but positive in its effect. One other trick that I found for Pro-Pack is with multiple Libraries within the runtime. I had broken my libraries out as: libraries A#Libraries B#Libraries H#Libraries M#Libraries N#Libraries V#Libraries W#Libraries The other libraries are for Mike, Vicky, Nature, etc. The letter is to ID them and the # is to make sure PP didn't read them so it would load FASTER. Heh- HOWEVER I discovered that if I named the libaries as zA#Libraries zB#Libraries zH#Libraries zM#Libraries zN#Libraries zV#Libraries zW#Libraries With a "z" to force them to the BOTTOM of the runtime directory, this made PP load HUGELY faster. It seems that even though a "#" should tell PP to IGNORE the other libraries, PP will in FACT rummage through those that come AHEAD of "libraries" in the loading process. By forcing all the other libraries to the BOTTOM with the "z", I found that PP zipped through the "finding" process, finding "libraries" first and then snapping open. Something in Poser's code uses alphabetical searching, but nothing apparently tells it to NOT look in "#" folders, even though it will in fact NOT use those folders anyway! BTW- this MIGHT have an effect on P5 loading- or users of Hogsoft's PBooost. I haven't tried it yet, but if it would seem that once PP with PBooost, or P5 find the first "libaries", it should be a Happy Camper and snap open. (Rather than rummaging through them before opening.)