The source of this problem is that p14.06.00 was built
One way around this is to build your exe against p15... and then setup
p14.06.00 to run it. But that can have other, sometimes nasty effects.
You may be getting unintended initialization data, for example.
A better way would be to allow you to chose the version of rcpfiledb you want
to use. Since all versions of rcpfiledb contain every rcp that
existed up to the time that version was created. So you never lose any rcps
by using the latest database.
To chose the newest rcpfiledb:
If you wish to use the MAXOPT version of D0RunII, just replace
whatever you do now with:
and later corresponding to
rcpfiledb t04-02-00 and p16-01-00
(and temporarily amj-01-br)
where (at FNAL) we'll declare the latest rcpfiledb "current" so you
won't have to specify [ver] if you don't wish to.
NOTE: [ver] > t04-02-00 and p16-01-00 in chronological order.
"setup rcpfiledb" and "d0setwa" can be done in either order.
Due to interactions between the new rcpfiledb and the old d0setwa routines,
you'll have to do the following in the exact order:
NOTE: setup rcpfiledb twice.
Sorry about that, but we can't retrofit all copies of all versions of
D0RunII everywhere in the world.
for older releases. For the new ones, just add a "setup rcpfiledb" somewhere
after you've setup D0RunII.
Comments, complaints, bug reports to:
Alan M. Jonckheere
Last modified: Mon Feb 2 17:44:02 CST 2004