Hello. Not sure if this will help... Under Audio/Wave directory: make it specifies a folder and not just the drive. You might also try specifying a new and different folder - create a new folder C:\\audio and point the Audio/Wave directory to the new folder.
Hope that helps. jmp
Are you using the same drive for Cakewalk\'s audio and your .GIGs? If so, you might try using separate hard drives for Cakewalk audio and Giga instruments. It could be that your drive can\'t keep up; when Cakewalk writes to disk, the operation doesn\'t complete within Cakewalk\'s desired time period, and then it gives you that error.
This is something that also might be helped (or hurt!) by playing around with vcache settings.
I get this error from time to time when I have memory over 70% in GigaStudio. It is not consistent. I have played around with buffer settings in Cakewalk which have helped. Sometimes I close Cakewalk and start it over and the error goes away.
You can find a lot of great information on optimizing your computer and OS for use with Calkwalk at Prorec.com and at Calkwalk.com. The Calkwalk newsgroups are very helpful.
As far as D:Wavedata - I ended up changing my folder in which I save wavedata for other reasons, but after doing so, I never got another \"...disk may be full\" message. This may or may not work for you. If you do decide to re-direct your wavedata folder, make sure you move over all of the existing wavedata to the new folder, otherwise CW won\'t be able to find it!!
try unplugging your midi controller from your MIDI input. I haven\'t experienced this bug myself, but I have seen two cases, one actually yesterday of friends getting this error due to \"MIDI in\" activity while recording audio.
If none of this has helped, try deleting the file AUD.INI from your Cakewalk folder. Cakewalk will generate a new .INI file the next time you run it. With CW, it seems that sometimes the .INI files themselves can go bad. Deleting AUD.INI and generating a new one might just do the trick.
You might want to check your hard drives (especially the audio recording drive) with Jose Catena\'s DSKBENCH program to see if it is performing as it should. I was getting the same error with Sonar, and found that the read speed on my drive was 2/3 slower than the other two identical drives in the system. Since I replaced it (under warranty from Maxtor) the system has been rock solid, and I have not seen that message once.