(bottom of page)
JuanTahnahmahrah
Logician
I started using GS3 before I made the jump to Macs and Logic 8 and 9. The PC version of Logic (5.51) didn't have access to enough memory to play alongside GS3 loaded with all the samples from Miroslav Vitous.
I still link my Mac to another PC (with wordclock and ADAT) that holds the GS3/Miroslav Vitous samples, but until just yesterday had not decrypted the intermittant "bluescreens." If you have never used either GS3 or a PC, this information will be of little interest to you.
I had set multiple boot options between full network and GS3 optimization on the PC, but never figured out the bluescreens, the messages were always different. So how did I get rid of them?
My network printer needed a new fuser, so I bought an HP P1102w to get me through until the part arrived. The P1102w has a "Smart Install" that totally crashed, and messed up the file systems on the two hard drives (F and G, two separate SCSI drives) that contain the GS3 samples and the convolution reverb plug-in. After that, each time the XPSP3 system booted, it told me to run "chkdsk" -- but doing so in the "automatic" mode didn't help. However, when I ran chkdsk from DOS "safe" mode, I managed to correct the file system on the two GS3 drives. Now I was still getting bluescreens, but one said the culprit was "filespy.sys" -- never saw that before. The HP "smart install" has a fix on the HP site, but I am thankful HP messed up my drives (!!!) because it led me to unraveling the mystery of all the bluescreens. After doing a web search for filespy.sys, it turns out it runs in the background, even when GS3 is not loaded. It can be disabled in the GS3 config screen by unchecking the "monitor file system."
As many know, Tascam dumped GS3 right after they released an upgrade to a 64bit Vista compatible GS4. The bluescreens should have been covered in their FAQ section, but as far as I know, it is lore as this point. My system has been stable so far ever since I loaded GS3 and disabled the "monitor file system" checkbox. Apparently, the original intent of filespy.sys was to keep track of where all your samples were. I always keep mine on the same drive, but there are seven physical drives in the system, three SCSI in a RAID-5 array, two sample/convolution reverb SCSI drives, and two ATA drives, one of which is split into two partitions. Too much for filespy.sys.
The PC uses RME HDSP9652 ADAT ports to send the samples over to Logic.
So, there you have it. There must be some people out there who know what I am talking about. It's good to have a stable system again. The first time data actually got corrupted was when the HP "Smart Install" went to work. Supreme irony that two rogue programs would end up becoming "at one" and solving a mystery that has stumped me for about five years!
I still link my Mac to another PC (with wordclock and ADAT) that holds the GS3/Miroslav Vitous samples, but until just yesterday had not decrypted the intermittant "bluescreens." If you have never used either GS3 or a PC, this information will be of little interest to you.
I had set multiple boot options between full network and GS3 optimization on the PC, but never figured out the bluescreens, the messages were always different. So how did I get rid of them?
My network printer needed a new fuser, so I bought an HP P1102w to get me through until the part arrived. The P1102w has a "Smart Install" that totally crashed, and messed up the file systems on the two hard drives (F and G, two separate SCSI drives) that contain the GS3 samples and the convolution reverb plug-in. After that, each time the XPSP3 system booted, it told me to run "chkdsk" -- but doing so in the "automatic" mode didn't help. However, when I ran chkdsk from DOS "safe" mode, I managed to correct the file system on the two GS3 drives. Now I was still getting bluescreens, but one said the culprit was "filespy.sys" -- never saw that before. The HP "smart install" has a fix on the HP site, but I am thankful HP messed up my drives (!!!) because it led me to unraveling the mystery of all the bluescreens. After doing a web search for filespy.sys, it turns out it runs in the background, even when GS3 is not loaded. It can be disabled in the GS3 config screen by unchecking the "monitor file system."
As many know, Tascam dumped GS3 right after they released an upgrade to a 64bit Vista compatible GS4. The bluescreens should have been covered in their FAQ section, but as far as I know, it is lore as this point. My system has been stable so far ever since I loaded GS3 and disabled the "monitor file system" checkbox. Apparently, the original intent of filespy.sys was to keep track of where all your samples were. I always keep mine on the same drive, but there are seven physical drives in the system, three SCSI in a RAID-5 array, two sample/convolution reverb SCSI drives, and two ATA drives, one of which is split into two partitions. Too much for filespy.sys.
The PC uses RME HDSP9652 ADAT ports to send the samples over to Logic.
So, there you have it. There must be some people out there who know what I am talking about. It's good to have a stable system again. The first time data actually got corrupted was when the HP "Smart Install" went to work. Supreme irony that two rogue programs would end up becoming "at one" and solving a mystery that has stumped me for about five years!