Subj : Re: This version of LordCfg...
To : Donald Tidmore
From : michael preslar
Date : Tue Jul 10 2007 12:25 am
> I have no firsthand knowledge of the 32-bit igms situation other than for the
> Lord/32 game's usage of them. All of the LORD versions use the same data
files
> names, but in different ways. They all use a 3rdparty.dat file, but only DOS
> LORD and LORD/32 can actually RUN an igm that is listed in one.
Fact: Lord, Lord/32, lord/x, and Lord/2 all use the same data files the
same way. The files are named the same, the structures are the same, and
the data within these files are used the same way no matter what
platform the game is running on.
I can only guess that DonDon's ASSumption here is because he doesn't
know how to use the compilers properly.
> DOS LORD can not run a LORD/32 igm, and vice-versa.
What? DonDon speaks truth? Woah! When did this happen?
Lord running Lord/anything IGMS: A 16bit environment (Dos) cannot run a
32bit program (Lord/32 and any IGMs made for it)
Dos Lord IGMs running on Lord/32: This is theoretically possible, but
not through Lord/32 itself. The theory is that the IGM would have to run
a comport/fossil emulator that pipes input and output to a Windows COMM
handle before the IGM runs.. Why? Dos IGMs talk to either a comport (or
if theyre properly written) a fossil. Win32 programs talk to a COMM
handle. comport != COMM handle.
> The structures for DOS
> LORD use one set of variable names and variable types, whereas LORD/32 has to
> use a different set. One was designed for Turbo/Borland Pascal by Seth
> Robinson (DOS Lord), and the other was designed by Preslar to only work with
> Free Pascal v2.00, Virtual Pascal v2.19, and I think Borland Delphi
(LORD/32).
Ah. I know where DonDon's assumption comes from. Lord's player.dat
structure includes a field called "class". That is a protected word in
32bit compilers that include OOP support. So, while I was working out
the rest of the code, I had an {$ifdef FORDOS} class: integer; {$else}
pclass: integer; {$endif}.. Then I found the Right Way to do that,
turned off OOP support, and was able to use "class" as a field name again.
> Preslar gave me instructions in June 2006 for compiling a 32-bit LORD igm,
> however, they don't work for me since my Windows XP system installation of
Free
> Pascal v2.00 refuses to compile the Manndoor Toolkit component files.
Funny thing about most doorkits: You get the entire source to it and can
use it in most any way you want. Which means that had DonDon found an
issue, he could have fixed it himself. Or at least emailed Rick Parrish
("Manning", Manndoor's author) or myself. DonDon did not.
Most likely, DonDon ran into a compiler directive issue. More
specifically, DonDon was probably running {$H-} in his IGM sources, but
Manndoor, by default, runs as {$H+}. The fix: Change (or add) {$H-} to
manndoor.pas
> The 3rdparty.dat file format is reversed in LORD/32 where the IGM Title line
> comes first, then the command line is listed. And it integrates the INFO
node
That was a temporary bug for like a week while I was polishing the
Lord/32 IGM support.
--- SBBSecho 2.11-Win32
* Origin: Data Stream - telnet://dsbbs.net - www.dsbbs.net (1:124/7013)
