SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Non-Tech : Quote.com QCharts

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Michael Watkins who wrote (13167)3/22/2001 9:18:17 AM
From: minnesotatv  Read Replies (1) of 17977
 
Hi Michael:

got a question maybe you can help with.
After the horrendous day I had with QCharts on Tuesday, I decided that maybe a "back to basics" approach might improve the situation. So, I uninstalled QCharts, deleted all extraneous files off my hard drive, scoured my registry for all keys and pointers and deleted them all. Then after a reboot, I reinstalled SP4 (NT 4.0), vb60sp3, QCharts V 4.0.1.12 and Qfeedstart. Qfeedstart pointed me at the Chicago router, rather than the sunnyvale's.

The only 2 differences between Tuesday's disasterous install and Wednesday's, was the Chicago router connection, and the fact that this time, I did not install the CC.dll update that I had previously downloaded off the website.

My experience Wednesday was totally different that Tuesday. While the charts were not quick, they didn't "snap" up, only twice did I lose the data stream and each time it wasn't out for more than 45 seconds or so.
A 1000% improvement over Tuesday.

Which got me to wondering why? Why the improvement? Obviously I can't see behind the scenes to anything that the techies at QCharts may have done overnight, but would connecting to Chicago rather than sunnvale have made that much difference in stability? Or could it be that that CC.dll update is buggy and creates instability in the software?

Are you aware of any issues with that update?

Thanks,
Tom
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext