J
James HE
a spoonfull weighs a ton
ChuckU said:
Holy Crap. Cakewalk/Sonar finally changed this! I am amazed! I might actually have to check Sonar 2 out now. You mean I can't badmouth sonar anymore?! lol
Holy Crap. Cakewalk/Sonar finally changed this! I am amazed! I might actually have to check Sonar 2 out now. You mean I can't badmouth sonar anymore?! lol
ChuckU
New member
This might help someone...
Since I was last on this thread, a few positive things happened.
1. I got a new system.
2. I got the old system back up. Fully intact.
As it was impossible to get into the Recovery Console due to my lack of a password, I took my C: drive and slaved it on the wife's machine. In Windows, I overwrote the corrupt files.
After returning the C: drive back to the DAW and with the Windows CD in the CDrom drive which I set as the boot drive in bios (I have no idea if this did anything for me), I started up the machine. It gave me a Windows dialogue box and asked me to update my password. I did so and Windows came up.
At this point, I went into Device Manager to see if there were any hardware problems and lo and behold, the drivers for the motherboard's RAID controller were corrupt. I downloaded the latest drivers and it was successful.
Now here's what I think happened:
When I put the DAW together, I had my audio drive set as master on the first RAID controller. The reason I did this was because I couldn't get it recognized as master on the second IDE bus for some reason (my CD burner was also on the secondary bus). So I treated the RAID bus as a third IDE bus.
I wonder if the RAID bus got wiggy enough on me to cause this corrupt registry problem as well as a few "Hard Disk Warning" messages in Sonar and some fluttery playback prior to the final insult. Anyway, that driver has been repaired and I have nothing on that bus. I'd like to disable it in bios, but if I'm not using it I wonder if that's enough.
Since I was last on this thread, a few positive things happened.
1. I got a new system.
2. I got the old system back up. Fully intact.
As it was impossible to get into the Recovery Console due to my lack of a password, I took my C: drive and slaved it on the wife's machine. In Windows, I overwrote the corrupt files.
After returning the C: drive back to the DAW and with the Windows CD in the CDrom drive which I set as the boot drive in bios (I have no idea if this did anything for me), I started up the machine. It gave me a Windows dialogue box and asked me to update my password. I did so and Windows came up.
At this point, I went into Device Manager to see if there were any hardware problems and lo and behold, the drivers for the motherboard's RAID controller were corrupt. I downloaded the latest drivers and it was successful.
Now here's what I think happened:
When I put the DAW together, I had my audio drive set as master on the first RAID controller. The reason I did this was because I couldn't get it recognized as master on the second IDE bus for some reason (my CD burner was also on the secondary bus). So I treated the RAID bus as a third IDE bus.
I wonder if the RAID bus got wiggy enough on me to cause this corrupt registry problem as well as a few "Hard Disk Warning" messages in Sonar and some fluttery playback prior to the final insult. Anyway, that driver has been repaired and I have nothing on that bus. I'd like to disable it in bios, but if I'm not using it I wonder if that's enough.
R
RWhite
Well-known member
Now that you have emerged from computer hell, I STRONGLY suggest that you pick up a program like Ghost or Drive image. Make regular backups of your C: drive, writing the images in 690 meg hunks that you can copy to CDR. If this computer is important to you, do this monthly, or after every major software upgrade.
ChuckU
New member
These programs won't interfere with system performance, will they?