At the moment I am currently running this version and have for some
days with no adverse results but cannot say that the conditions have arisen where this fix shows up but I do have at least one downlink
using Mystic (v1.12A39 binkp/1.0).
At the moment I am currently running this version and have for some
days with no adverse results but cannot say that the conditions have arisen where this fix shows up but I do have at least one downlink
using Mystic (v1.12A39 binkp/1.0).
At the moment I am currently running this version and have for
some days with no adverse results but cannot say that the
conditions have arisen where this fix shows up but I do have at
least one downlink using Mystic (v1.12A39 binkp/1.0).
You won't notice anything unless a Mystic node sends you .TIC files.
Mystic by default names .TIC files with the same name as the archive
they relate to.
ie: the .TIC file for fsxinfo.zip would be fsxinfo.tic.
This causes problems with MBSE versions before 1.0.7.9, because MBSE
expects that all .TIC files will be named with 8 character filenames followed by .TIC. The example above is only 7 characters, so it
wouldn't be processed automatically. The same applies to long
filenames (longer than 8 characters.)
The changes in 1.0.7.9 will handle .TIC files with filenames of 1
character up to the maximum the OS supports.
Hello Vince!
21 Sep 18 15:44, you wrote to all:
At the moment I am currently running this version and have for
some days with no adverse results but cannot say that the
conditions have arisen where this fix shows up but I do have at
least one downlink using Mystic (v1.12A39 binkp/1.0).
I've been running it as well, and my uplinks are Mystic - and no
issues with me others. Happy that all TIC's are now being processed :)
i see you are using a pi, what are you doing for hard drives as i could not see
how to remove the usage of an sd card and i have zero intention of doing so.
i would like to bay and set one up for some Cobol->java development
system which is free on that platform but major issues with mass storage. i have no intention of waiting around will it thinks that going back to the 70's and floppies.
I have another Pi - which is a 3 (not a 3+) - and its running qemu and
my BBS from 1995 (ezycom). I've been setting that up over the last
week, and while it is also slow (by todays standards) - everything
works (and it's probably faster than what it was in 1995!) (I did try getting Ezycom running as a DOS virtual machine on my Intel server -
it was fast, but most things didnt work - the Runtime Error 200. I did
have the pascal TSR loaded, and that fixed somethings, but many others
didnt work - like the ezymail tosser.)
There is a patch for the 200 error.
Some where on my system I do have it as I still do fixes to FileMgr
when ever needed. That any thing must find the time to read up fully
on FPC and convert the sources but I am rusty in Pascal and even more
so in asm.
1. Removed the requirement that incoming .TIC files have
exactly 8 character filenames with the .TIC extension.
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,094 |
Nodes: | 15 (0 / 15) |
Uptime: | 53:42:52 |
Calls: | 231,451 |
Calls today: | 10 |
Files: | 59,792 |
D/L today: |
5,179 files (840M bytes) |
Messages: | 296,034 |
Posted today: | 3 |