Tomasz, I sent this message to the User's List over 9 days ago. When I sent it, the problem had not been resolved, and I was getting desperate to figure things out. I have no idea why the message posted well over a week after I sent it. As you recall Tomasz, I sent you two messages via support where I specifically asked you if you were going to post my message to the User Group, as it hadn't shown up a day or more after it was posted. You did not reply to my messages, but I can certainly forward them to you (and to the user group here) again to remind you that I inquired why my post wasn't available on the user's group. I erroneously assumed you chose not to post my messages to the User Group since the problem was resolved by support a day or two after I posted to the group.
I am upset that you would state that I've resorted to "unjustified bashing" of AmiBroker. Truth be told, I publish a blog which receives over 30K hits a month, and I often sing the praises of AmiBroker. I have never mentioned your service or software as being anything other than the best. Perhaps I should alter that practice. Perhaps, instead of speaking highly of your software, I should mention that it took me practically begging you to help me before you got involved in a meaningful way to resolve my problem. Perhaps I should mention that on your advice, I reformatted my entire hard drive, and re-installed Windows, as you thought that Windows was the problem, only to find out afterwards that the problem was a simple software setting. --- In [email protected], "Tomasz Janeczko" <gro...@...> wrote: > > It was NOT any problem with AMiBroker just > ridicolously high "max. open positions" setting set to 1000. > > With 26 years of EOD data and 10000 symbols that means > 10GB of RAM! > > And of course he ran out of memory. > Once "max open positions" is reduced to some value > that actually makes sense (100 or less), there are no problems. > > The most annoying fact is that this issue was resolved > via support channel weeks ago, yet AmiBroker is target of some unjustified > bashing again. > > Best regards, > Tomasz Janeczko > amibroker.com > ----- Original Message ----- > From: "etoketrader" <et...@...> > To: <[email protected]> > Sent: Sunday, August 30, 2009 6:28 PM > Subject: [amibroker] Re: Please Help, AmiBroker Crashing > > > > Hi Woodshedder, > > > > are you the woodshedder from ibankcoin? I follow your blog :) > > > > I had lots of crashing issues until I (or rather, Tomasz told me to) set > > the in-memorey cache size (max. symbols) to 11 and max. > > megabytes to around 850 (in preferences). While it means that AB will run > > generally slower because it will interact more to your > > hard disk, it will not run out of memory, which was my main issue with AB > > when I started working with large databases. > > > > I also suspect that the beta is crashing more for you because the new > > format of the DB contains two more fields and results in a > > larger DB. If you were on the verge before, you definately are over that > > limit now. > > > > cheers, > > eToke > > > > > > > > > > --- In [email protected], "woodshedder_blogspot" > > <woodshedder_blogspot@> wrote: > >> > >> I'm running Vista-32, 3gb RAM, on a Dell inspiron 1525. I use Norgate > >> Premiumdata, US-history going back to 1985. > >> > >> I started with 5.20 but moved up through the betas as they were released, > >> until the latest Alpha. > >> > >> AB has always hanged (even before using the betas) or went non-responsive, > >> whenever I attempt to close the program, and sometimes > >> when I open the database to run the Norgate integration script. It has > >> sometimes went non-responsive when running simple > >> optimizations (never complicated ones). Typically this occurs as soon as > >> the first step completes running. It almost always has > >> went non-responsive when switching between meta-stock format and local > >> database. > >> > >> When I downloaded the Alpha, everything got much worse. It started during > >> the installation process, when AmiBroker's auto back-up > >> program crashed. Then, it started crashing/hanging during almost every > >> optimization. > >> > >> I have run Prime95, scandisk, and I defrag my disks regularly. I have > >> never had any problems with this computer, which only runs > >> Tradestation, office suite, and mozilla, besides AmiBroker. > >> > >> I have moved the original AmiBroker folder, and re-installed 5.20. I have > >> re-installed all of the Norgate/Premium data files. > >> > >> I am still getting crashes directly as the first optimization step > >> finishes. I have been trying to problem-solve this for a week > >> now and am getting nowhere. > >> > >> Do I sound desperate to get this running again? I feel that way. > >> > >> Thanks for any help. > >> > > > > > > > > > > ------------------------------------ > > > > **** IMPORTANT PLEASE READ **** > > This group is for the discussion between users only. > > This is *NOT* technical support channel. > > > > TO GET TECHNICAL SUPPORT send an e-mail directly to > > SUPPORT {at} amibroker.com > > > > TO SUBMIT SUGGESTIONS please use FEEDBACK CENTER at > > http://www.amibroker.com/feedback/ > > (submissions sent via other channels won't be considered) > > > > For NEW RELEASE ANNOUNCEMENTS and other news always check DEVLOG: > > http://www.amibroker.com/devlog/ > > > > Yahoo! Groups Links > > > > > > >
