i don't get it.  
it's a pain this way.
no issues on my other machines- ALL running W7 64

I'm not understanding you, what exactly do you mean by not scrolling?
How exactly are you trying to scroll, clicking on scroll bars? With a mouse, with the middle button, the keyboard?
 
What works and what doesn't.
Do you have issues with other applications?
 
If it's device specific it's probably a driver issue or configuration of that device (i.e. for a mouse).
 
If it's JUST your mouse please check the control panel mouse settings. Also remove or disable any Sony specific mouse software/bloatware in add/remove programs.
 
If no dice please run windows update several times, and check this:
http://forum.cakewalk.com/Driver-Boost-m2928792.aspx
 
Also run any Sony updates (and update/reinstall your mouse software). You'll have to find out where this is as I don't know what the specific model of your laptop is, maybe you have sony autoupdate software.

Thanks...

on my desktop computer, there is a bar on the side of the prochannel window used to scroll up and down. when using my vaio laptop, the scrolling bar is missing. the laptop also does not have a mouse wheel built in.

on my desktop computer, there is a bar on the side of the prochannel window used to scroll up and down. when using my vaio laptop, the scrolling bar is missing. the laptop also does not have a mouse wheel built in.

What happens if you plug it into an external monitor?
Regardless please try #2. Thanks.

apparently, nvidia did have updated drivers. however, the scrolling bar dies not show up. if I plug in ausb mouse, scrolling works as it should. but the laptop " mouse pad" can't scroll because it doesn't have a wheel and the pro channel window didn't have a scroll bar.

So it's definitely your mouse pad drivers, please see #2.

thanks

i'm curious because i thought you were talking about prochannel in the track inspector, but are you talking about console view?

Well we've already established two different mice devices give different behaviours which proves this is not a Sonar issue (it's a device issue).