I'm about to try doing the 3GB switch on my DAW machine, and have just read through the sticky thread on that subject. At the top of the thread it was suggested that any tweaks done to optimise the running of Giga need to be reversed. I never ran Giga on this machine, but I was about to perform a lot of the standard tweaks recommended for general optimisation of XP for music - e.g. switching processor scheduling to background services, disabling system restore, etc (see www.musicxp.net for the full list). Is there anything I should avoid altering if I want to run VIs on the machine.
-
Tweaking XP
-
let me add: if you have configured your system reasonably (means: a seperate partition for system & applications) then i would _not_ switch off system restore for the system volume, but only for data disks/volumes (you can define this individually)
there are a lot of useless features beyond the background service tweak ... uPnP support, designs, terminal service (unless you access via remote desktop), automatic search for network devices, DHCP in case you use fixed IPs, automatic windows update, time service, series of other stuff not needed on a *true* audio machine.
had a short look on musicXP a few weeks ago -. the hints there are way better than they have been 2 years ago.
nevertheless you should try to understand what a twaek does before applying it, or at least note down the former settings in case something does not work as well as expected. just keep your hands off the memory managemet when running VI ...
christian
and remember: only a CRAY can run an endless loop in just three seconds. -
Thanks guys. cm, I've gone through most of the tips from musicXP, and it turns out that the people who built my machine had already done almost all of them anyway. The one that I'm slightly concerned about, in view of your comments, is that they have set a custom paging file size of 1024MB - is that what you mean by messing with memory management? Should I set this back to a system-managed value?
Sorry to keep bothering you, but I'm a real techno-idiot.
-
sorry, not clear enough ... with memory management i referred to the registry values for pagedpool ect ....
to set the pagefile size (*virtual memory*) to a fixed (and low) value is a good idea ... eg. min = max = 1024
whereever possible i switch it off completely or locate it on another drive.
for computers with *little* RAM one says the pagefile should be as large as the physical RAM, but this does not really apply for memory beyond 1-2 GB ... IMO you could actually go down to 512 MB ... or try to switch it off, though different setups behave different, so you might need to keep the 512 or 1024 for best performance.
christian
and remember: only a CRAY can run an endless loop in just three seconds.
