From rowan_crowe · 1996-04-10 19:25 · #73143 in FREE25
In reply to FOSSILs and serial numbers... What a l by joaquim homrighausen
Answering msg from joaquim homrighausen to Pierre Phaneuf, on Saturday April 06 1996 at 15:20 >> I was checking out a special FOSSIL doing about the same thing >> as VModem, but for DOS using a DOS TCP/IP stack, and I >> noticed how it operated in a singular way... Instead of >> being a normal FOSSIL, load as a TSR or device driver and be >> happy, it loaded itself, set up an ISR, then shelled to the >> application... jh> [..] jh> Uh, fair enough, but what's wrong with: jh> FOSSIL /load jh> FOSSILapp jh> FOSSIL /unload The fact that it consumes 70k+ of memory when 'resident' might be one reason why it is done on a single execution only. ;-( It uses the WATTCP C library, which explains the size. You should see a PPP driver I have, also coded in C -- a 100k TSR. jh> BTW: Are the VMODEM specs. available anywhere? I am planning to implement a virtual FOSSIL for DOS, so it would be a bonus if I could also support the VMODEM protocol. >> And another idea came to me looking for something in >> FSC-0015... About the talks lately on the creation of an >> uniform serial number for a site... Many sites running >> Fidonet software also uses FOSSIL. jh> Indeed - but what about editors/mail readers? They seldom need a jh> FOSSIL driver to be loaded, and when run in a LAN environment, there's jh> little or no use for them on a workstation not running a mail delivery jh> agent, no? A FOSSIL is also quite irrelevant for non Windoze/DOS users, and non PC users. Cheers. --- * Origin: Melbourne, Australia (3:635/727.1)