OpenBCM V1.13 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
DB9ER  > APPLE    27.02.97 21:48l 177 Lines 8505 Bytes #-10822 (0) @ EU
BID : 272733DB0EAM
Read: DH9MEC DJ3YQ DF5GI DB9SH GUEST DK3EL
Subj: Net/Mac2.3.62(JNOS)2/4.asc
Path: DB0AAB<DB0MWS<DB0RBS<DB0SWR<DB0FP<DB0SON<DB0SIF<DB0KH<DB0EAM
Sent: 970227/1810z @:DB0EAM.#HES.DEU.EU [Kassel TheBox DB8AS] $:272733DB0EAM
de DB9ER @ DB0EAM.#HES.DEU.EU   (Dieter)

to APPLE @ EU


 For SLIP-lines you may now issue modemcommands like ATDT in a 'param'
 command. The format of the command is: param <interface> <modemcommand>
 Examples:  param sl0 ATDT031174942153
            param sl0 +++
 Note: Only 1 string is sent to the modem.
       A <space> or <return> terminates the string.


 For KISS-lines you may now issue TNC-commands like KISS ON in a 'param'
 command. The format of the command is: param <interface> <TNC-command>
 Example:  param ax0 KISS ON
 Note: A <return> terminates the string.


 A new feature in NET/Mac(65) and higher is the 'anonymous anonymous' user.
 You can allow any user to log in by defining username * and password * in
 the ftpusers-file. When NET/Mac goes through the list of validated users,
 and it encounters a username *, then the search is terminated and the user
 is granted access to the system. You should put this line at the very end
 of ftpusers! You may also choose to remove any 'guest' or 'anonymous'
 user from the ftpusers-file, since * could cover all of those.


 Also new in version 65 is the 'prompt' command, which enables you to
 change the default 'net>' prompt.


 Version 67 and higher allow the user to define the location and size
 of the Trace-, RIP Trace-, LOG-, SMTP Trace- and CONSOLE-windows. If you
 haven't changed the commands that generate these windows, the windows will
 simply be like they used to be. If you want to change the size or location
 of a given window, simply add 4 numbers to the command, that creates it.
 (e.g.: log :spool:logs:log x y r c)
 The 4 numbers are: x and y: the coordinates of the upper left corner
                             default is 0 0
                    r      : number of rows (lines) in the window
                             default is 24 (on a 9" screen)
                    c      : number of columns (characters) per line
                             default is 80 (on a 9" screen)

 Since the TRACE-command has an optional filename as the last parameter,
 it is required to use all 4 parameters (x y r c) for the windowsize or
 NON of those. The optional filename remains the LAST parameter.

 To change the location and size of the console-window a new command
 'console [x y r c]' was introduced.

 I myself use on a 9" screen:
 rip trace on 0 0 24 72
 smtp trace 2 0 19 17 80
 log :spool:logs:log overwrite 0 0 24 71
 console 0 0 13 80

 Example for 13" screen:
 rip trace on 0 0 24 80
 log :spool:logs:log overwrite 0 310 3 80
 smtp trace 2 0 374 3 80
 console 0 0 24 80

 Starting up NET/Mac with   #$debug on   may be pretty slow, especially
 when you have a large screen (let's say > 12"). If you want to speed up
 processing of the autoexec.net file you can first reduce the size of the
 console-window.
 On PA0GLN's Mac LC with 13" color-screen the startup took 24 seconds.
 He then installed the following line as the first line of his autoexec.net:
 console 0 0 5 80

 At the end of his autoexec.net he selected the screen as suggested above.
 Startup then took only 15 seconds.


 FLOW [ON|OFF] now also controls the kind of screen you will get when an
 AX.25-, NET/ROM- or TELNET-session is started. With FLOW OFF you will now
 get a split-screen, with an incoming and an outgoing window. When FLOW
 is ON, you will get one window in which both the incoming and outgoing
 data will be displayed.


 KPC-4 TNC: When a kpc-4 is attached, an "a" or "b" is added to <label>
 and is used in place of <interface> in all autoexec.net (and live) commands.
 So, when you do  'attach kpc4 1 a ax25 kp0 2048 576 4800'  your <interface>'s
 will be kp0a and kp0b.


 RTNTOSES [ON|OFF] allows you to enable/disable a mode in which typing
 a single <RETURN> in the console-window will/won't bring you back to
 the active session. Default is ON.


 REALTIME [ON|OFF] was implemented because I discovered, that timers
 appeared to be only relative values. When the Mac is busy running more
 than just NET/Mac, sometimes my timers (like SMTP TIMER, retry-timers
 etc.) look like actual values, but in many cases the real value was 1.5 to
 3 times higher than the ones shown by various commands. I always wondered
 why a ping with a delay of 900 seconds only got handled about twice an hour....
 When you switch on REALTIME, NET/Mac will try to investigate how busy the
 Mac is, and how little time NET/Mac gets from the system. By doing so and
 adjusting the timervalues these become more realistic. NET/Mac will average
 the values it found over some time. When you type REALTIME, it will show
 you the value it has calculated. The program usually uses the value 100,
 so if REALTIME shows 200 mSec per tick, this means, that all timers and
 counters are twice as long as you would expect. Also look at SMTP TIMER
 some time after switching on REALTIME, and you will see a more accurate
 value of the timer there.
 When you quit NET/Mac by using the 'exit' command, NET/Mac will put the
 average tick-value of the last NET/Mac-run at the beginning of your
 autoexec.net, so that it will automatically start up using this value when
 you activate NET/Mac the next time.

 !!!  The REALTIME command, described above, is no longer supported  !!!
 !!!  Instead of this command ON1XK implemented a timer-task, which  !!!
 !!!  forces the clock to tick at exactly 100 millisecond intervals. !!!
 !!!  This timer task may not work (at all) on a Mac 128 or 512, or  !!!
 !!!  when using pre 6.0.4 versions of the Mac Operating System...   !!!
 !!!  If this causes you problems, then I can send you a version of  !!!
 !!!  NET/Mac that does NOT use the timertask, but has built in sup- !!!
 !!!  port for the REALTIME command instead... Just let me know...   !!!


 CMDTOCLIPB [ON|OFF] appears to be handy when you want to have a possibility
 to redo the last command. This new command allows you to copy each and every
 command to the clipboard, so that you can 'retype' the command by simply
 pressing command-G (Do Again). It's a lot more comfortable to type (a lot of)
 command-G's than to type like 't s 5f873c' a number of times, just to monitor
 a given session. Command-V acts just like command-G, but the command will not
 really be executed, so that you can edit the command if you like.


 RIP really works in version 80 (and higher)!


 ADDMENU <string> allows you to enter commands from the menubar. Look at the
 HELP info for ADDMENU for more info.


 SOURCE <filename> allows you to split up the autoexec.net file into a number
 of smaller files, each performing a specific task, like 1 file for 'route add'
 commands, 1 file for 'arp add' commands etc... Also you may choose to group
 together a number of NET/Mac commands, that can be activated later from the
 'Custom' menu. See also the NET/Mac HELP-windows for 'addmenu' and 'source'.


 SMTP NDAYS <number> will make sure, that SMTP-files that have been inside your
 Macintosh (and could not be delivered) for more than <number> days, will get
 returned to the sender. The default value for <number> is 365 (days), but I
 think you should set it to some value of between 10 and 30. Mail-files are
 being checked against this <number> when they are queued for transmission.
 When NET/Mac stays on for very long without being restarted, this could mean,
 that there may be a session, waiting in SYN SENT mode for the destination to
 show up, for as long as NET/Mac is running. This would mean, that the outgoing
 mail to that (unreachable?) destination will only get queued when SMTP kicks
 for the first time, and never after. Therefore I implemented a mod, which makes
 sure that outgoing SMTP-sessions that reach retry-timer 128 (see 'tcp status')
 will get requeued again.
 Also outgoing SMTP-sessions that wait for a command from the destinationhost
 and seem to be 'forgotten' by that host will be reset after about 2 hours.


 TITLE <new consolewindow title> allows you to change the default title of the
 console-window (which now defaults to 'hostname') to any title you like.


 Sometimes it seems hard to disconnect a simple AX.25 connection by just typing
 a disconnect command... Instead of typing disconnect commands over and over,
 you should try the following: type: ax25 status
                      and then type: ax25 reset <'&AXB'-address>

 You should ONLY use these commands, when the state of the connection is (and
 remains) 'Conn pending', otherwise the remote-station will never know, that
 you have dropped the connection.




Read previous mail | Read next mail


 16.10.2026 12:25:31lGo back Go up