At Fri, 24 Apr 2020 18:36:51 -0700 (PDT) Frank Rosenbaum <
frankro...@gmail.com> wrote:
>
> On Sunday, April 19, 2020 at 1:35:18 PM UTC-5, Frank Rosenbaum wrote:
> > I am setting up operations and would like to know, if you operate your ra=
> ilroad using switch lists or waybills, or nothing at all, and why you use o=
> ne over the other. Both seem very labor intensive. Are they worth the effor=
> t?
>
> Well, I got a response when I went to the bin folder.Is there a single file=
> that will run the whole program?
There isn't *one* program, there are a collection of different programs that
do different things. Some programs are "offline": Freight Car Forwarder and
TimeTable. Some are helper utilites, like Resistor (computes load resistor
values). Others are involved with actual operation (they interact with trains
or accessories -- there is a throttle program for a Lenz XPressNet DCC system,
and programs for OpenLCB/LCC). If you installed the Documentation archive,
there will be a user manual in share/MRRSystem/Doc/UserManual/index.html (HTML
format) and share/MRRSystem/Doc/UserManual.pdf (PDF format), which will
document all of the exe files. There is also a Development archive, which
contains documentation and things like C/C++ header files relating to the
libraries.
> I have opened several of the files, but everything is grayed out and would
> not respond. When I opened FCFmain the only function I could do was open. N=
That is correct. The FCFmain program needs a "data set" to work with. It can't
actually do anything without data to work with. The data set is a batch of 8
data files containing information that describe your railroad (its divisions,
stations, industuries and yards, trains, and cars). The data files are all
actually just text files and you *could* create them with a text editor, like
NotePad, but make sure that they are saved as plain 7-bit ASCII text files.
Most of the data is actually formatted as comma separated data, so you
possibly could create the files with Excel, but again be careful to be sure
the files are saved as 7-bit ASCII text files. Also since the files are not
really spreadsheet files, there might be some issues there. I've always used a
plain text editor (MicroEMacs) to edit the files. The Freight Car Forwarder
only re-writes the cars and stats files. The other files are only ever read in
by the FCFmain program -- that is all other other files are static readonly
data and are used by the Freight Car Forwarder in its processing to determine
where cars can go and which trains can get them there.
The FCFCreate program can be used to create these files (but FCFCreate is a
little funcky and not well tested). There are some sample data sets available.
The *original* one is in ChesapeakeSystem.zip -- this is the data set used by
the original author of the original BASIC program. This is probably a good
data set to work with to get a feel for how the program works. There is
another one, LHandBS.zip which is for my (much smaller) railroad.
The section of the User Manual for the Freight Car Forwarder has a section
that documents the format of the datafiles.
> othing else worked. I just tried to open a library and got Error: _40d09307=
> _p_fcfSupport_System{Error readi...=20
> Here is the Log report:
> _40d09307_p_FCFSupport__System {Error reading C:\mrrsystem-2.1.44\bin\libtt=
> classes.dll -- short file (TrainsFile)!}
> _40d09307_p_FCFSupport__System {Error reading C:\mrrsystem-2.1.44\bin\libtt=
> classes.dll -- short file (TrainsFile)!}
> while executing
> "System TheSystem [file nativename "$fileName"] [MakeSeed]"
> (procedure "LoadSystem" line 11)
> invoked from within
> "LoadSystem"
> invoked from within
> ".main.topf.tb0.open invoke "
> invoked from within
> ".main.topf.tb0.open instate !disabled { .main.topf.tb0.open invoke } "
> invoked from within
> ".main.topf.tb0.open instate pressed { .main.topf.tb0.open state !pressed; =
> .main.topf.tb0.open instate !disabled { .main.topf.tb0.open invoke } } "
> (command bound to event)
>
You can't actually *run* the library files. These .dll files are meant to be
be linked to either C++ or loaded into Tcl programs.