Tillbaka till svenska Fidonet
English   Information   Debug  
ASIAN_LINK   0/651
ASTRONOMY   0/417
AUDIO   0/92
AUTOMOBILE_RACING   0/105
BABYLON5   0/17862
BAG   135
BATPOWER   0/361
BBBS.ENGLISH   0/382
BBSLAW   0/109
BBS_ADS   0/5290
BBS_INTERNET   0/507
BIBLE   0/3563
BINKD   0/1119
BINKLEY   0/215
BLUEWAVE   0/2173
CABLE_MODEMS   0/25
CBM   0/46
CDRECORD   0/66
CDROM   0/20
CLASSIC_COMPUTER   0/378
COMICS   0/15
CONSPRCY   0/899
COOKING   27611
COOKING_OLD1   0/24719
COOKING_OLD2   0/40862
COOKING_OLD3   0/37489
COOKING_OLD4   0/35496
COOKING_OLD5   9370
C_ECHO   0/189
C_PLUSPLUS   0/31
DIRTY_DOZEN   0/201
DOORGAMES   0/1974
DOS_INTERNET   0/196
duplikat   5999
ECHOLIST   0/18295
EC_SUPPORT   0/318
ELECTRONICS   0/359
ELEKTRONIK.GER   1534
ENET.LINGUISTIC   0/13
ENET.POLITICS   0/4
ENET.SOFT   0/11701
ENET.SYSOP   33774
ENET.TALKS   0/32
ENGLISH_TUTOR   0/2000
EVOLUTION   0/1335
FDECHO   0/217
FDN_ANNOUNCE   0/7068
FIDONEWS   23439
FIDONEWS_OLD1   0/49742
FIDONEWS_OLD2   0/35949
FIDONEWS_OLD3   0/30874
FIDONEWS_OLD4   0/37224
FIDO_SYSOP   12841
FIDO_UTIL   0/180
FILEFIND   0/209
FILEGATE   0/212
FILM   0/18
FNEWS_PUBLISH   4155
FN_SYSOP   41520
FN_SYSOP_OLD1   71952
FTP_FIDO   0/2
FTSC_PUBLIC   0/13565
FUNNY   0/4886
GENEALOGY.EUR   0/71
GET_INFO   105
GOLDED   0/408
HAM   0/16041
HOLYSMOKE   0/6791
HOT_SITES   0/1
HTMLEDIT   0/71
HUB203   466
HUB_100   264
HUB_400   39
HUMOR   0/29
IC   0/2851
INTERNET   0/424
INTERUSER   0/3
IP_CONNECT   719
JAMNNTPD   0/233
JAMTLAND   0/47
KATTY_KORNER   0/41
LAN   0/16
LINUX-USER   0/19
LINUXHELP   0/1155
LINUX   0/22002
LINUX_BBS   0/957
mail   18.68
mail_fore_ok   249
MENSA   0/341
MODERATOR   0/102
MONTE   0/992
MOSCOW_OKLAHOMA   0/1245
MUFFIN   0/783
MUSIC   0/321
N203_STAT   894
N203_SYSCHAT   313
NET203   321
NET204   69
NET_DEV   0/10
NORD.ADMIN   0/101
NORD.CHAT   0/2572
NORD.FIDONET   189
NORD.HARDWARE   0/28
NORD.KULTUR   0/114
NORD.PROG   0/32
NORD.SOFTWARE   0/88
NORD.TEKNIK   0/58
NORD   0/453
OCCULT_CHAT   0/93
OS2BBS   0/787
OS2DOSBBS   0/580
OS2HW   0/42
OS2INET   0/37
OS2LAN   0/134
OS2PROG   0/36
OS2REXX   0/113
OS2USER-L   207
OS2   0/4779
OSDEBATE   0/18996
PASCAL   0/490
PERL   0/457
PHP   0/45
POINTS   0/405
POLITICS   0/29554
POL_INC   0/14731
PSION   103
R20_ADMIN   1117
R20_AMATORRADIO   0/2
R20_BEST_OF_FIDONET   13
R20_CHAT   0/893
R20_DEPP   0/3
R20_DEV   399
R20_ECHO2   1379
R20_ECHOPRES   0/35
R20_ESTAT   0/719
R20_FIDONETPROG...
...RAM.MYPOINT
  0/2
R20_FIDONETPROGRAM   0/22
R20_FIDONET   0/248
R20_FILEFIND   0/24
R20_FILEFOUND   0/22
R20_HIFI   0/3
R20_INFO2   2632
R20_INTERNET   0/12940
R20_INTRESSE   0/60
R20_INTR_KOM   0/99
R20_KANDIDAT.CHAT   42
R20_KANDIDAT   28
R20_KOM_DEV   112
R20_KONTROLL   0/13030
R20_KORSET   0/18
R20_LOKALTRAFIK   0/24
R20_MODERATOR   0/1852
R20_NC   76
R20_NET200   245
R20_NETWORK.OTH...
...ERNETS
  0/13
R20_OPERATIVSYS...
...TEM.LINUX
  0/44
R20_PROGRAMVAROR   0/1
R20_REC2NEC   534
R20_SFOSM   0/340
R20_SF   0/108
R20_SPRAK.ENGLISH   0/1
R20_SQUISH   107
R20_TEST   2
R20_WORST_OF_FIDONET   12
RAR   0/9
RA_MULTI   106
RA_UTIL   0/162
REGCON.EUR   0/2055
REGCON   0/13
SCIENCE   0/1206
SF   0/239
SHAREWARE_SUPPORT   0/5146
SHAREWRE   0/14
SIMPSONS   0/169
STATS_OLD1   0/2539.065
STATS_OLD2   0/2530
STATS_OLD3   0/2395.095
STATS_OLD4   0/1692.25
SURVIVOR   0/495
SYSOPS_CORNER   0/3
SYSOP   0/84
TAGLINES   0/112
TEAMOS2   0/4530
TECH   0/2617
TEST.444   0/105
TRAPDOOR   0/19
TREK   0/755
TUB   0/290
UFO   0/40
UNIX   0/1316
USA_EURLINK   0/102
USR_MODEMS   0/1
VATICAN   0/2740
VIETNAM_VETS   0/14
VIRUS   0/378
VIRUS_INFO   0/201
VISUAL_BASIC   0/473
WHITEHOUSE   0/5187
WIN2000   0/101
WIN32   0/30
WIN95   0/4275
WIN95_OLD1   0/70272
WINDOWS   0/1517
WWB_SYSOP   0/419
WWB_TECH   0/810
ZCC-PUBLIC   0/1
ZEC   4

 
4DOS   0/134
ABORTION   0/7
ALASKA_CHAT   0/506
ALLFIX_FILE   0/1313
ALLFIX_FILE_OLD1   0/7997
ALT_DOS   0/152
AMATEUR_RADIO   0/1039
AMIGASALE   0/14
AMIGA   0/331
AMIGA_INT   0/1
AMIGA_PROG   0/20
AMIGA_SYSOP   0/26
ANIME   0/15
ARGUS   0/924
ASCII_ART   0/340
Möte BBS_INTERNET, 507 texter
 lista första sista föregående nästa
Text 407, 136 rader
Skriven 2004-12-13 22:12:18 av mark lewis (1:3634/12)
    Kommentar till text 405 av Michel Samson (1:106/2000.0)
Ärende: 2/2 - LSPPPDlr 2003
===========================
[trim]

 MS> not ~RS-232~/~ANSI~ as in a local DialUp call.  Now, consider
 MS> that there is a similitude here compared to ~FOSSIL~-based
 MS> BBSes:  the BBS SoftWare owns the Serial-Port during interactive
 MS> sessions and when it's due for a transfer it hands down the
 MS> control over the ~FOSSIL~ Serial-Port to some external
 MS> File-Transfer Protocol-Driver (being `FDSZ' in this case).
 MS> ;-)

true in some cases and only for some bbs software... on my system, the FOSSIL
is required before /any/thing can happen... this is because most all of my
software doesn't do direct serial comms... as a developer, i can see and fully
understand why this is, too... as a developer, i can whip out numerous comms
apps without having to know anything about serial comms if i simply talk to the
FOSSIL driver and let it handle all that stuff... i perfer to let the FOSSIL
developers worry about the serial comms stuff whilst i concentrate on my
application and its functionality rather than having to clutter my head and
other stuff up with comms knowledge... not that i don't have a good
understanding and not that i haven't done my share of comms coding without a
FOSSIL...

MS>> Right now, i can "share" connections (alternately) using `LSPPPDlr'
MS>> with `MS-Kermit' run as a Protocol-Driver - when used via `COM/IP' -
MS>> but not with `RLFossil' (the later reboots my PC instead)!...
ML>> If you have and are using COM/IP, that indicates WIN9x (at least) is
ML>> installed...  i'm assuming that your statement above is saying that
ML>> you have the reboot problem with RLFOSSIL when using it in WIN9x?

 MS>      `Win-32' isn't involved here, i once evaluated `LSPPPDlr'
 MS> in a DOS box

"DOS box" to me means opening a DOS command prompt window... is this the same
meaning you are using it as?

 MS> and i also conducted tests with `COM/IP' but i don't use `W98'
 MS> very often these days and i sort of abandoned the idea that
 MS> `COM/IP' will be the perfect alternative someday
 MS> (TacticalSoftware became so greedy with their costs i bet that's
 MS> why i've read that Mike Ehlert and his company "discontinued
 MS> selling COM/IP licensing" after October 14, 2004)...  8-o

that is exactly why ME left them... i have that info from direct and personal
contact... ME and i go way way back as we were both beta testers for several
fidonet packages... the RemoteAccess BBS package being the main one between
us...

MS>> I wonder what feedback i'd get from a person like Sylvain Lauzon...
MS>> i have to wonder if he wouldn't happen to know where to go for the
MS>> source-code or, maybe, even a quick fix.
ML>> ...there are some out there who can reverse engineer things back to
ML>> source code...  ...enough that it can be fixed and recompiled...

 MS>      I have no idea what string he may have pulled in order to
 MS> obtain it but `RLFossil v1.23' is improved compared to its
 MS> predecessor and this is a good reason to bring `LSPPPDlr' to its
 MS> full conpletion, in my opinion.

 MS>      In the end, i'd like to get back to the origins of this
 MS> project and have it stand on a single 3.5" - 720 Kb Stand-Alone
 MS> diskette, because of no other reason than to prove the BBS
 MS> community could have done it!  ;-)

excellent reason... i fear, sadly, that it may fall on deaf ears, though... too
many supposed sysops are really little more than advanced lemmings and like all
lemmings, they, too, follow the rest of the pack over the cliff into the sea...

MS>> `TelNet Port' suffered from the same problem when i checked...
ML>> What problem?  ...when you say "share" you don't mean at the
ML>> same time from different windows/tasks, do you?

 MS>      The problem with `RLFossil', `TelNet Port' and perhaps a
 MS> few others is that something very wrong usually happens when a
 MS> terminal emulator is trying to pass control of the ~FOSSIL~
 MS> Serial-Port (or is it more like a ~BIOS INT-14~ one?), euh...

it may very well be the INT-14 hand off... something that's always bothered me
once i learned about the FOSSIL stuff is why a coder has to go about
readjusting the port settings and such once they are handed the port from the
BBS... seems to me they should be able to just use the port as is... especially
when using a FOSSIL... if they really need to adjust settings in their code,
then they should be able to _query_ the port to see what it is set for and then
go from there... especially in a BBS situation where the BBS has already been
communicating successfully with those on the other end of the line...

 MS> Novell's `TelAPI' (`LAN WorkPlace for DOS') is the only adapter
 MS> with which i've ever been able to start the external
 MS> Protocol-Driver from `{COMMO}' or `MS-Kermit';  as i recall, a
 MS> 3rd-party ~TelNet~ "Shim" for `PC-NFS' also allowed it but it
 MS> was so unreliable it didn't get much of my interrest.  In any
 MS> case, the fact that a very same macro-file succeeds when my
 MS> terminal emulator launches a Protocol-Driver with `COM/IP's
 MS> `INT-14'/~FOSSIL~ support and that it fails if `RLFossil' is
 MS> used indicates that one is more Level-5 compliant than the
 MS> other.

or that something still has hold of the interrupt vector or is otherwise "still
standing in the doorway"... RLFOSSIL must be there since it /is/ the FOSSIL and
not a normal TSR FOSSIL driver like X00 or BNU...

 MS> Of course, a professional might have a better explanation but
 MS> that's only a hobby and those guys rarely hang around just to
 MS> help with some problems.
 MS>                                   %-(

and then there are those like me who are here and are willing to contemplate it
based on prior knowledge and experiance ;)

ML>> ...one can redefine the BIOS table...
MS>> ...i depend on the talent of others for my modest hobby...
ML>> But the table did make some sense...  ...and helps to explain where
ML>> comm programs get the info for the basic ports when they don't have
ML>> any real port setup capability...

 MS>      I patched a small utility embeded in the `LSPPPDlr' macro
 MS> to manage with ~UART~ types so, it was necessary to find the
 MS> bytes which addressed the Serial-Port attached to the MoDem (i
 MS> wanted to set the ~FIFO~-buffer trigger level).  I see some me
 MS> relevance if HardWare Serial-Ports are on topic but my idea of
 MS> how a ~BIOS INT-14~ port differs is pretty vague...

 MS>      If some terminal uses an option-setting saying ~BIOS INT-14~
 MS> and it works with `RLFossil' - note it's not called `RLINT-14' -
 MS> well, it's all i need to know and i do my best with that...  %-)

that's about all one can hope for! ;)

 MS> Others can take over, nothing else would please me more!  I try
 MS> to use my findings to ignite a form of interrest:  tiny miracles
 MS> may happen if i'm patient, right?  ;^)

right!

)\/(ark

 * Origin: (1:3634/12)