Hoi,
Ik ben ook een DAW gebruiker, Cubase3,DFHS etc etc
Persoonlijk heb ik een dual boot met XP en Vista gemaakt, gewoon om de reden
dat Vista trager is met Cubase dan XP. Dus XP Pro gebruik ik als DAW OS.
Ikzelf heb 2x1GB dual channel en 2x512MB dual channel, dus 3GB in totaal.
Eerst had ik 2GB, maar had id problemen om al mijn samples te kunnen laden
in een project.
4GB wordt niet volledig herkent, dus 3GB was de gulden oplossing.
Wat bleek nu? Vanaf dat ik meer dan 1.3GB aan samples laadde, begon Cubase
heel raar te doen en crashte zelf mijn PC volledig.
Na wat opzoeken te doen, blijkt dat XP SP2 32bit per applicatie+windows nie meer dan 2GB aan RAM kan geven/gebruiken.
Hiervoor is echter een oplossing, /LargeAddressAware in combinatie met de /3GB switch
Na dit beide toe te passen, kan ik nu vlot over de 2GB aan geheugen gebruiken in Cubase.
Ongeveer 2,3GB. De rest is voor het OS.
Ik geloof dat Cubase 4 nu wel /LargeAddressAware is (hoop ik voor jou).
Maar de 3GB boot switch, zal zowieso als je RAM bijsteekt zijn nut bewijzen.
info
The /3GB switch only works in XP or higher, and as far as I know, is not supported in 2k. With any amount of RAM, you'd be insane not to use the /3GB switch if your work required access to more memory. /3GB switch tells windows to allocate 1GB Virtual Address Space to the OS Kernel and 3GB Virtual Address Space to the User Environment. The 4GB Virtual Address Space being divided is always present in a 32bit OS because it's how memory is managed. Memory is the global container, RAM is just 1 of its components, all managed by the Virtual Memory Manager (VMM). That 4GB is then assigned to either physical RAM or pagefile or released from RAM and just left unpaged because some things aren't written to as much as read and referred to. When you do use the switch, XP will try to use as much RAM as possible, and page out what hasn't been used recently in doing so, but it decides if something is required in RAM, because it is volatile and being modified frequently, or if it is in pagefile, because it has not been accessed recently. Not using the /3GB switch basically limits all your work to 2GB, which is fine if you can work in that limitation.
Now some systems cannot use the 3GB switch and still run... they have drivers or other components that reside below the allocated 3GB and above memory range. In those cases, you use /3GB /USERVA=xxxx, where xxxx is a range of memory in MB between 2048 and 3072 (above 2GB and below 3GB).. you try working down from the top auntil your system runs without crashing freezing. For ex, my system with the newest vid card and its memory demands, uses USERVA=2850 . Anything higher and it doesn't want to work consistently. Anything lower and I'm just not using the memory.
If Sonar is not Large Address Aware, it should be made so pronto. Just to allow for expansion.
By the way, in that screen grab of the TaskManager, Sonar was using about 2.35GB of Virtual memory, which indicates the 3GB switch was working. Otherwise, you'd have crashed the program or it would have told you no way am I going there.
Maneswar
The 3 Gig switch ONLY works for applications that support LargeAddressAware. You can take a hex editor and modify the EXE to make it LargeAddressAware. Be aware though you probably won't get support from the vendor though if you do. The 3 gig switch works fine though when the application supports 3 gigs. Tracktion supports it without a hack. I've known people with Cubase who've hacked it and it worked too. That's up to you. Not sure if Cubase 4 automatically supports this, but SX 1, 2, and 3 did not. Not sure if Sonar 6 does? Anyone know?
Dus int kort, als je meer dan 2GB aan RAM gaat steken, ben je vrijwel verplicht
de /3GB switch toe te passen.
Meer info op het forum van DrumkitFromHellSuperior hoe dit toe te passen.
En over cubase wordt hier wat gezegt
http://forum.cubase.net/p...39d44931288640bbb43f71a55