i did some serious research about the 2GB "thing".
First of all it does not seem to me to scary now, because it mostly told me "hello i am coming to crash your system now"
onestly, after a fixed % of samples loaded into kernel memory you get an "can`t allocate requested memory" (or something like that) error.
if you load more into ram: BSOD
i had systems which did not show any error before BDSO but after spending some time with mattias´s great "pagedpool tweaking tool" i found a somewhat more stable system. which means i get at least more then 5 "can`t allocate blah blah" error before bsod AND if i delete unused instruments in GS3 it brings GS3 back into "normal" status.
ok, besides the BSOD i am now getting these results:
1) i was able to load about 1310 MB into ram. i think this is 150MB more then GS2.54 ever did?!?
2) this ramload gives me only 77% in GS3 which tells me the % meter is not working right, or is changed to what 2.54 measured.
3) i did load 2.54 .gsp setting within GS3 and compared the ramload which was always about the same (again, maybe i am wrong here)
4) i installed 2 more GB which changed absolutly nothing. 1300-1400MB is the limit.
so, for me there seems a workaround:
do some serious mattias tweaking, find out what suits you best.
after that when you get a "can´t allocate" warning, save your session, unload some samples and with some luck it wont crash.
don't get me wrong!!! this only applies on 2gb machines i did not had any trouble on 1gb systems.
if you don't want to fiddle around with that just take out your 2. 1gig stick until they really fixed that and be happy with about 770mb loaded into ram just like it was on GS2.54.
More than 1GB was allways a problem and still is.