Notice: Folks, you see, at my place, I have a dual-boot system, consisting of Windows NT and Linux (each of them having their own partition(s) and file system). I wanted to have 'independent' operating systems that won't see each other. So I made two NT's partitions as NTFS partitions and rest of the space used Linux as ext2 & swap partitions. Well, at first I have installed WinFBB under NT and X11 LinFBB under Linux. Both of them worked, but there was a big "problem": I could not share their system files. You might say: So, what a big deal. But, my FBB's should serve as packet-radio forwarding stations (regardless of which one I boot at the moment), so it was really needed for new LinFBB to "know", for example, the position where WinFBB has stopped the mail exchange last time (and vice- versa, of course).
init.srv -> init_w.srv forward.sys -> forw_w.sys port.sys -> port_w.sys protect.sys -> prot_w.sys
FBB is able to recognize and accept those renamed files.
amsatforward_to_file routine (located in /mnt/win/fbb/system/fwd directory), because that file was composed like this (for example):
A AMSAT * P @ * C D:\FBB\SYSTEM\SAT\AMSAT.TXT <-- looks familiar to DOS/Windows only * G AMSAT * --------
On the other side, LinFBB's
amsat.sys (located in /etc/ax25/fbb/fwd directory) has suggested something like this:
A AMSAT * P @ * C /var/ax25/fbb/sat/amsat.txt <-- looks familiar to Linux only * G AMSAT * --------
Well, then I copied LinFBB's
amsat.sys into /mnt/win/fbb/system/fwd directory so it could become functional. As a result, I got two
amsat.txt files, one of them for each of WinFBB/LinFBB, and of course, both files appeared on different locations: the first one was /mnt/win/fbb/system/sat/amsat.txt and it was filled by WinFBB; the other one was in /var/ax25/fbb/sat/amsat.txt and was filled by LinFBB. I didn't like it that way.
In order to have only one result, regardless of FBB version, the newly copied
amsat.sys had to be slightly changed:
A AMSAT * P @ * *C /var/ax25/fbb/sat/amsat.txt C /mnt/win/fbb/system/sat/amsat.txt * G AMSAT * --------
As you can see now, when LinFBB is active, its
amsat.sys will not forward into its "native" location of
amsat.txt. Instead of that, it will go to the location of the WinFBB's
amsat.txt and just add some new materials into it, OK?
Well now it's up to you to decide what to do with your growing
amsat.txt. An old DosFBB manual says that the 'batch' file (I suppose, the old good
APPEL.BAT) should be adopted in order for SATUPDAT.EXE can update sat tracking data and, after that, to erase AMSAT.TXT because it is not needed anymore. Well, I haven't found a way to manage that in both WinFBB and LinFBB. Actually, whenever I perform housekeeping from either of them, it seems that AMSAT.TXT remains intact. Happily, it doesn't grow too much, so it's not a big problem. Any suggestion here?