Mattias Henningson created a memory utility for exactly this purpose. Check his website.
--Jay
--Jay
-
...which is http://www.musikbanken.se/gigastudio/index.htm">http://www.musikbanken.se/gigastudio/index.htm The utility is available on the Memory Optimizer page.
/Mattias
-
Very much appreciated Mattias. I'll give this a try.
As I say above the Gigasampler - config tool preset #1 fixed the other machine and now allows that machine to fully load VSL's VI. I have done this on yet another slave I have and same behavior. If the config tool in GS is set to any other than 'preset #1' - cannot successfully FULLY load the VI. Very strange.
Rob
-
Maybe not that strange after all. We're trying to decrease the size of the pools in order to free memory for GS's private use. This operation may very well cause limitations for applications that needs to allocate large amounts of paged or non-paged memory.
/Mattias
-
Thanks so much Mattias - you have been so helpful. Today I will try to run your 'get settings' (on your utility) on the machine that is now working right with VI. I'll duplicate that setting on the PC that is still not loading up VI properly.
Rob
-
Mattias - very nice tool to determine settings. Here's what I found on the PC that was not loading VI properly
8/800000
8/800000
On the machine that was working properly it was set to
0/0
0/0
I then set the 'bad' PC to
0/0
0/0
WORKS PERFECT - loading to capacity!!!! [:D]
(Again - thanks Mattias for the assist)
Rob
-
Rob, glad to hear that you're up and running now! If anyone else reads this and wants to know... What Rob ended up with is exactly how XP is configured from the beginning.
/Mattias
-
-
@DG said:
I'm sure that I said this weeeeeeeeeeks ago [:(]
DG
Yea but this was on a PC that NEVER had GS [*-)]
Rob