I had the "vanilla' falvour of XP, then I downloaded some "updates" about a month ago and they turned out to be sludge.
Processes take longer now, the mouse is eratic in certain programmes.
"To Service Pack or not to Service Pack, that is the question!".
a tiny correction - XP recognizes at least 4 GB, that's what i can proove on a recent system here.
of course the final word regarding GS3 is not spoken, it is reported that in cooperation with M$ usable RAM could be possibly increased for 50%
If your DAW is not used for the net then there is no need for it.
This raises an interesting issue.
Are we required to register GS on line? KONTAKT, for example, uses the serial number on your hard drive, combines it with your grandmother's maiden name, plus the serial number of your issue of the software and divides it by the square root of your name to get you your activation key.
While you're on line doing this, someone is installing SpyWare on your system.
I would REALLY prefer not to have my GS system exposed to the 'net.
Another issue is, if I have 4GB RAM and GS uses 1.5 to 2.00GB, wouldn't the other 2.00GB be available for Windows, the sequencer, plugins etc.?
I would be VERY cautious in installing SP2 on your XP machines just yet. I have it on my personal PC computer (Not the gigastudio machine). A friend of mine works for Microsoft. It changes A LOT of underlying code (mostly security related)...most of which will probably NOT affect Gigastudio. But, I am afraid to use it on my Giga machine until I get some sort of confirmation from Tascam and the other driver manufacturers (Echo audio for me) on using SP2. This is a major rewrite of XP folks.
Brian W. Ralston Check out my new FREE iPhone App! Click Here!
I gotta 2nd that. A big thing it seems to affect is interprocess communication, mostly machine to machine. Problem is that a lot of apps and drivers do virtual machine stuff and get impacted in unexpected ways. Little things like recursive access over a loopback interface, for instance.
On my business lan I haven't had much trouble... mostly figuring out how and when to config the new internal firewall. But I've heard folks who don't implement Microsoft active directory domains (I do) having difficulty with their remote apps (pushed AV updates, for instance)... which I expect might also be the case for folks using MOL, Teleport, Giga VST, MLAN, and maybe even general purpose firewire or USB audio devices. So for now I'm also stearing clear on my audio machines till I get better acquainted, see more complete docs, and get some app and device feedback from manufacturers and other users.
It's really a shame that with all the activation code and machine id stuff we have these days that it's so hard to test apps and updates on a spare machine. Especially one-way updates that can't be uninstalled or easily backed out. I'm dreading the time when an audio app which is important to me gets released with a "requires SP2" or "DX9c" update. At which point it'll be time to fish or cut bait... and say a little prayer.