Stock Watch Pro

[canyonman00]

Quote from agin1415:

I just upgraded my computer, with a 512 (RAM) chip, they are $29.97 with rebate at Compu USA. I'm running 768RAM now on my 1.5 G processor. OMG you talk about speed. I suggest every body go down and upgrade. I was runnin just 512 Ram and my cable was slow, the upgrade corrected the slowness.

Most folks don't understand just how big this little addition is. As a tech, I generally start there with most of my clients who think they need more speed. Here here for full memory upgrading!

As for the program lock up after adding memory. You may have now exceeded the memory management setup/design for the software. If it is a known buggy system that could be part of the problem. This might sound stupid but it is a (true) system designer possibility.

That problem would also be magnified if you are running any of the newer flavors of windows. Certain software/hardware drivers have not been tweaked to address maximum memory with the more potent OS's. A memory addressing pothole can now appear as a crater. This would easily account for "software manufacturer denial." A condition covered with the, "We aren't having that problem with too many (any other) of our users!" responses.

 

[debud]

Thanks for everyones response. Well, for 48 hrs. everytime I opened Stock Watch Pro it immediatly went to 100% CPU usage, up to 250,000K memory usage and locked up. This afternoon I decided I was going to do something to try and fix it. I opened it up one more time before I embarked on whatever, I'm sure would be a long and frustrating process, and SWP works just fine. Down to about 4% CPU usage (without streaming data). What happened? I don't have a clue. I'll just hope for the best Mon. A.M.

 

[canyonman00]

I'll be interested in seeing your post tomorrow afternoon. Good luck in trading.

 

[qdz]

debug, either case the ram does not work properly. It could be defective or incompatible (e.g. some sub-sepcification difference). Take out the new ram and see what difference it makes.

Quote from debud:

qdz, When you say that the memory may not work properly, do you mean that what I added was defective or not compatible?

 

[canyonman00]

Quote from qdz:

debug, either case the ram does not work properly. It could be defective or incompatible (e.g. some sub-sepcification difference). Take out the new ram and see what difference it makes.

I'd would not agree here if this is the only program that gives him trouble. That being the case, it is doubtful that the trouble is the RAM. If RAM is faulty, it's not program specific.

 

[qdz]

It really depends on programs and cases. When only low end of memory is used, everything seems alright. When faulty areas are used by programs in certain cases, there will be problems. I had experienced it once. So I just pointed out this is a possibility this time.

Quote from canyonman00:



I'd would not agree here if this is the only program that gives him trouble. That being the case, it is doubtful that the trouble is the RAM. If RAM is faulty, it's not program specific.

 

[Corso482]

SWP is horrible as far as reliablity. The damn thing crashes on me constantly. The data feed is also unreliable...I know...It's Qcharts data feed. But sometimes the data works on Qcharts and not SWP, go figure. Here's what really gets me. When I do scans, I can only imput a few hundred tickers at a time or it locks up on me. So I'm copying and pasting tickers a little at a time for scanning so SWP won't lock up, very annoying.

Maybe it's my comp, I only have 256 RAM w/ 800 MHz.

I'm really looking for something else to switch to, but haven't found something else with a scanner. Esignal looks good, but like I said, no scanner. Tradestation's too expensive. And I found Metastock not user-friendly.

Right now I'm getting do data on SWP.

 

[Corso482]

Oh and when I do backtesting, there will be mistakes in the report. They're rare, but they reveal SWP's backtesting to be inaccurate. Sometimes I'll do the exact same backtest over the exact same time period and stocks and I'll get different results

Very shady if you axe me!!!

 

[canyonman00]

Quote from qdz:

It really depends on programs and cases. When only low end of memory is used, everything seems alright. When faulty areas are used by programs in certain cases, there will be problems. I had experienced it once. So I just pointed out this is a possibility this time.

You reinforce my statement. Your condition could have been duplicated by opening several windows simultaneously therefore demanding more memory and then clipping into the bad areas of your chips. In this instance, the memory jumps to 100% usage ONLY when opening this particular product. When you add in the other buggy experiences that are being addressed here, you come closer to faulty software conclusions.

 

[debud]

SWP went back to locking up Sunday afternoon. I did download SWP on my other computer, and it worked great all day Monday. I also upgraded from 128 to 256mb. and am running WDO. XP PRO. on the second machine. I did get an email from CronTech Support asking for workspace files. I'll update when I get a reply. thanks for all your input.