|
PureBytes Links
Trading Reference Links
|
I gradually raised mine. It is now at 500,000 (WinXP) and I still get
occasionally the problem.
I have had the best results (fewest problems) by being dilligent in
discarding runs or exporting the results to EXCEL. I realized that most of
the runs were not worth keeping and just a part of the development process.
So I export the results immediately to Excel, along with the description of
the system test/parameters were. Then record my thoughts in Excel, like
"didn't work, looks like the trigger was too high, try using higher
trigger". I found it helpful because you always tend to make some sort of
judgement immediately upon examining the results. Plus once results are in
Excel you can perform statistics on the results that you can not do in
Metastock. If you have recorded this, you can always rerun the system test.
I also run the Clean utility every few runs.
----- Original Message -----
From: "bex1210" <hmw3@xxxxxxxxxxxxxx>
To: <equismetastock@xxxxxxxxxxxxxxx>
Sent: Sunday, October 05, 2003 11:52 PM
Subject: [EquisMetaStock Group] MaxLocksperFile
> I have Mdtastock 8.01 EOD, running on Windows 98SE. I have recently been
running larger System Tests, and now when I go to Discard a test get a
Program Error with the message: "file sharing lock count exceeded. Increase
MaxLocksperFile."
>
> I contacted Metastock support, and they showed me how to change this
setting in the Registry. The "default" is 9500 locks. It was suggested to
double or triple this. The technician I spoke to has his set to 250,000, but
he also has Windows 2000.
>
> I did some checking, and apparently a very high setting can slow down
execution of some programs. I first increased mine to 20,000, and then to
40,000. If I run a System test with 100 stocks, 4 years of daily data, and
15 optimization settings (1440 tests in all), I still get this error message
when I Discard the file. If I run it with 8 optimization settings, I can
discard OK. (I select Discard and Clean-up after every system test, so their
are no residual tests which Metastock is also trying to discard.)
>
> The data for the system test is stored in ST_DATA.mdb. A file that is 43
Meg Discards OK. A file that is 71 Meg creates the error message.
>
> Has anyone experienced these same problems, and if so, what
MaxLocksperFile settings have been successful?
>
> Having to run optimization tests with such a small number of variables so
as not to trigger this error message is really labor intensive.
>
> Harry Ward
>
>
>
> To unsubscribe from this group, send an email to:
> equismetastock-unsubscribe@xxxxxxxxxxxxxxx
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>
------------------------ Yahoo! Groups Sponsor ---------------------~-->
Buy Ink Cartridges or Refill Kits for your HP, Epson, Canon or Lexmark
Printer at MyInks.com. Free s/h on orders $50 or more to the US & Canada.
http://www.c1tracking.com/l.asp?cid=5511
http://us.click.yahoo.com/mOAaAA/3exGAA/qnsNAA/BefplB/TM
---------------------------------------------------------------------~->
To unsubscribe from this group, send an email to:
equismetastock-unsubscribe@xxxxxxxxxxxxxxx
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
|