One thing to watch is wireless networking - it does terrible things to dpc latency.

If you have a wireless networking device, disable it in device manager before launching Sonar (just dropping the connection in Windows isn't enough to prevent the problem).

Other than that, if Sonar runs OK for you, then that's all that matters really.

I used to use a dual-boot Vista setup with one boot specifically for Sonar and it made a big difference to Sonar's performance. I expected to have to do the same with my current i7, but to be honest I've not (yet) found that necessary.

If, on the other hand, I were running a commercial studio that provided the bulk of my income, or I couldn't afford a few days downtime should the worst happen, I'd build a dedicated DAW.

 Hello again and Thanks,
you guys are great.
i'm pretty serious about my projects,but ultimately,
i don't generate an income from it(and don't anticipate
it either).
so, while it would be nice to have a replacement,i suppose
i'll hold off for the moment.
i tend to keep my projects small anyway,5 or 6 tracks and
then i bounce.
Thanks Again  m.r.

I used to have a dual boot system but since discovering that Win 7 x64 uses more HD space than the 32 bit version, I decided not to dual boot my new computer. Plus, I've been using my Mac Book Pro for most of my Internet usage anyway. 

Get a netbook or a tablet then if you want something separate. It's cheaper than a new computer and you won't need all that processing power to be on the net anyway.

Having your DAW on a network has many advantages, from ease of authorizing plugins to convenient project backups to a file server. 

However, network adapters, drivers and associated software are responsible for most of the CPU and I/O overhead that limits your DAW's efficiency and system latency. If you're on the internet you need firewalls and antivirus protection, which impose additional overhead. Network adapters assume that they are the most important components in your computer and that servicing network traffic should take priority over everything else, including audio. Wireless adapters in particular are horribly inefficient.

The solution: set up a way to disable the network while you're doing audio work, and to re-enable it when needed. Hardware profiles are one way to go, but may require a reboot to switch from one mode to another. Another approach is to create a batch file that turns the network off and shuts down unneeded processes. This method allows you to easily switch between dedicated DAW and general-purpose networked machine, for the best of both worlds.

I don't. I use the DAW computer only for music, with a stripped down version of Win 7 installed. 

But, I also have a laptop with internet access on the desk with the DAW.

Works for me.

For years I went to a dual boot but 1 computer. Both boots were connected to the internet but the DAW boot was not used for general browsing.

The biggest problem I found was not the internet but other programs that like to add services and background processes and make tweaks to the system without telling me.

My current DAW is a dedicated machine connected to the network but not used for browsing. I have dual DVI output and a dual DVI switch so I can easily flip from one computer to the next. I did find it better to use a different mouse and keyboard for each computer, but they share the same dual output widescreens.

I think the "danger" of going online is greatly overestimated. You can't get a virus just by browsing. You have to download an executable and knowingly run it. #1, don't download anything suspiicious or unverified, and #2 don't run any executable before scanning it. In 20 years of using Windows based PC's I have only ever gotten one virus, and that was because I let my guard down and stupidly ran some BS I downloaded off of the Pirate Bay. 

PS this forum's language censorship is ridiculous. Note how I had to spell "suspiicious" just to stop it being censored!

I don't work with clients and use Sonar for my own stuff - CD releases and backing tracks.  Personally I like the Dual Boot approach, one stripped down for DAW use and one for general purpose use.  Both have Sonar available.  Typically i use the DAW side when I am creating new projects and recording actual audio.  For editing / exporting / and live work (I use the matrix at times) I use the general purpose boot.  Both boots share a common folder structure.  I do have an internet connection on the DAW side, but I only use it for updates to Sonar and Plugins - Although most times I download from the general purpose side and place files on a common drive.


Cheers

Grif

I use the laptop for surfing when in the studio, but when I do want to authorise and/or download music software, I just plug in the network dongle, do what I want to do, then pull it out again.

All I can say is that I somehow picked up very ugly viruses on two separate occassions without engaging in any obviously unsafe Internet practices.  (I suspect one was picked up from Facebook.  The other one started immediately after I tried to update iTunes.)

I picked these up even though I was running up-to-date virus protection (WebRoot).

These viruses required completely rebuilding my machine which meant reinstalling all software and drivers, reconfiguring everything, and going through enormous pain to get back to where I was.  I lost all my Melodyne edits on an album when I reinstalled Melodyne.  The V-Studio interface set-up was completely wrecked and it took some time to get that right.  It was ten days before I was operating, and it was only weeks later that I finally got the last of the VSTs reinstalled and back as they were.  A lot of project work had to be redone.

I now connect my music PC to the Internet only to download, authorize, or update music software or to publish music to the Internet.  I bought the cheapest laptop I could find at BestBuy ($400) for email, Facebook, iTunes/etc. and I use either the laptop or an iPhone for all non-music Internet stuff.

It's up to you, but that is my experience.