Sorry, Dizzi - Don't agree. Windows uses RAM for disk buffering, but it is transient. Windows doesn't store entire files in RAM for any significant length of time. When loading multiple textures and objects, it's highly unlikely that they will all be in the cache at the same time, especially since Windows only reserves a certain amount of the total RAM for the cache, and releases cache RAM on a fairly constant basis so that it is available for other tasks.

Besides, changes to the file require a re-read even if the data is cached. If you are working on tweaking a texture - re-loading it and then doing a test render after a few small edits - a RAM disk would save you a fair amount of time by reducing both the time spent saving from your graphics editor and loading the newly modified texture into Poser. In the many times I've used this workflow, I've never seen Windows "skip" the trip to the HD and complete the whole transit using cache RAM. My hard drive light always flashes and there is a delay while the files are saved and loaded.

• Jimdoria  ~@>@