Is this supposed to be happening on a Q6600?

Well good luck. I hope you can help me out with this, cuz I enjoy the fact that Im really familiar with xp lol.

Thx

Pimpaholic

 

Well I don't think so.. I'm going to have to send this puppy back.
Good luck with yours.

 

No, not at all, at least not from the forum. What you're running up against is lack of knowledge, not lack of will.

 

No prob. I understand. I guess I'll upgrade to vista soon. thx

 

In terms of memory - the more the merrier; if you're going to be going to 4GB eventually, it might be useful to do it now, to see if that alleviates any problems - just because the commit charge is showing less than 2GB committed does not mean that all of the processes running on your system need less than 2GB of physical memory in toto. In fact, given that a big chunk of physical memory is allocated to kernel use, it would be possible for most of the unused physical memory to be in kernel space, and for the memory in user space to be insufficient for all of the user-space processes that are running. One way to check this is to see how much virtual memory is being used, and to see how often your page file is being written to - if there are frequent reads/writes to your page file, that by itself could be the source of stuttering as the disk I/O would temporarily block a lot of lower priority threads, including every other thread that needs I/O access. More memory means less reliance, or less frequent reliance, on the page file, which should reduce the amount of time taken up with page file I/O operations. Along those same lines, you might check to see how big your page file is, if it's too big, then each read/write may be consuming too much CPU time, causing stuttering.

Another item that might be causing a problem is limewire itself. Version 4.16.6 should have an implementation of non-blocking I/O; however, that implementation is not problem-free, and more recent versions of limewire in the changelog have made changes that deal with nonblocking I/O. At the very least, you should upgrade to version 4.16.7 (which I believe is now the latest official release), and consider giving some of the versions beyond that a try, so long as they don't appear to be too buggy in other respects. Also, I would suggest going through some of the limewire fora and bug-reports to see if anything comes up vis-a-vis problems with the implementation of nonblocking I/O. Lastly, make sure that you've got the latest Java release, because limewire is only as good as the version of Java on which it depends.

In terms of monitoring your system to see if you can correlate events with the stuttering, I would suggest using several of the SysInternals utilities to watch what's going on under the hood, including Process Explorer to watch what processes are doing what, how many resources they're consuming, and how often they're hitting page faults and having to read/write from the page file, Disk Monitor, which will keep track of each individual disk transaction (read or write), including size, and TCPView, which will allow you to see all of the TCP and UDP endpoints on your system - i.e., TCP and UDP connections - this could be useful to determine whether or not limewire is taking up too much of your system's time by having too many connections open, whether or not limewire is orphaning any connections (which would be a bug in that app), and (I think, but don't quote me on it yet) whether or not the limewire connections are blocking or non-blocking.

In terms of getting your paging files running more efficiently, SysInternals also has a specific utility for defragmenting your paging files and your registry hive files, called PageDefrag. Most defragmenters cannot defragment these files because they're almost always in use (and thus locked); so this might help to speed up any page file read/writes that cannot be gotten rid of by using more physical memory.

Another SysInternals utility that I haven't played around with, but that might be helpful in your case, is CacheSet, which will allow you to manipulate the parameters of the system file cache; something else that might be interfering with the efficiency of your system.

In general terms, you might want to see what else is available on the SysInternals site at MS - SysIntenals was originally a website run by an independent company, Winternals, owned in part by Mark Russinovich, one of the co-authors of Windows Internals (now in its fifth edition - updated for _Vista), and, amongst certain quarters, is considered a very valuable resource, e.g., this excerpt from "Understanding Windows Shellcode" posted on insidepro.com.

 

Why are you even using LimeWire? I mean, torrents are much better and safer, to start with...

 

Wow shyster. Thx lol. I've done the pagedefrag, and I've also done it with perfectdisk 2008. Other than that I'll get right to your suggestions. Rep lol.

BTW eleron, I do agree with you there, but I'm a limewire veteran. I know exactly what I'm downloading there. It's kind of common sense not to download a song that is 10 kb, lol. I've used it for 2-3 years with no major problems. (BTW, only use it to preview songs, or download songs from artists who don't have a record label yet, e.g. Al Gator)

 

I thought I would link to this post by bigjohnsonforever here because it might have some relevance in terms of whether or not going up to 4GB RAM might help with some of the stuttering. Granted, he has the 5793, not the 9262, and has the T9300, which clocks at 2.8GHz; however, he does state in the post that he has 4GB RAM, that he turned off the page file, and everything runs smoothly, so you may get some relief by going up to 4GB RAM, and by either turning off your page file, or by playing around with the size of the file to find a size that minimizes the impact on your listening experience.