View Single Post
Old 10-01-2007, 07:44 AM   #6
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 79,997
Karma: 147448039
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by westsan View Post
If that was so this thread would not exist. On significantly lower spec machines I have seen even worse performance. Sony does terrible software period.

Actually the skin of the application adds a significant load on the software starting up. If you want to be objective (which I guess you are not) grab the window at the top and move it around quickly in a circle. Then compare it to any other software (including iTunes which also uses a skin).
If you are still not convinced take a screen shot and tell me how many trailskins you see on both!

The app has some serious QA problems. Not to mention usability problems.
The computer I have is currently is using an AMD Athlon 1900+ with an nVidia GForce 2 based video card and 1 gig of ram and Windows XP Pro.. That is hardly a new machine. The load time is not slow. The program does not run slow. Yes, when I drag it around the screen, I get trails. But, I don't have a need to do that so it's not really an issue. Heck, I can get trails from a command prompt if I circle it around the screen. The trails don't have anything to do with how well it's running or not. I am being objective. I'm running Connect on an older slower machine. As it is, Connect takes about 40K to run. That's not that mich ram overall and the speed is not slow.

A lot of the time, issues like these are the cause of one program casuing the problem for another. Has anyone withthe slowdown tried turning off EVERYTHING that starts when the machine boots? Has anyone with this issue tried running Connect in safe mode? I know the USB port won't work, but if it takes an excessive time to load, it might then load in a normal amount of time? What I'm saying, has anyone BOTHERED to try to debug this? If it really was such an issue, then by now you would have seen a lot more people posting about onnect and how slow it is.
JSWolf is offline   Reply With Quote