Search
You can find the results of your search below.
Fulltext results:
- 233 @doc:changelog
- iler) =========== (*) Fixed printing of received messages. (*) Fixed problem with label after IFNOTEXIST ... emaphore and then not remove it if no further messages were received from the modem. (*) Added sup... rely correct. It states that only IMM(ediate) messages are not affected by this, it should say that "Crash and Immediate messages are not affected". (*) Fixed problems with
- fd @faq
- nt types of ring signals and issue different RING messages; e.g. RING1, RING2, RING3, .. Once you have configured your modem to issue the appropriate RING message for your modem/BBS number, you must change the MODEM.STATUS MESSAGES.RING setting to the appropriate message; e.g. RING1
- 231 @doc:changelog
- G", "ALERTING", and "CALL SENT" modem reponse messages has been added; they are treated just like the "RINGING" response message and should no longer cause problems for FD.
- start
- a free FrontDoor Commercial/MultiLine key? Drop a message to 2:20/4609@fidonet or send an [[mailto:defsol@d
- nodelist08feb85 @archive
- opriate inbound host (and save ; you money as all messages to a given host are sent in one call).Check ; th
- windowsxp @howto
- rdware). You do not have to create custom CONNECT messages in FDSETUP. FrontDoor can parse the strings that
- 232 @doc:changelog
- omewhat more bullet-proof against corrupt JAM message bases. (*) The nodelist browser has been modifie