Home Page The Club Computers News Links Glossary EYAWTK
Before Amiga Background ICS OCS ECS AGA ??? PPC
U-Boot SLB Linux Amiga OS Dual Boot Motherboards Peripherals Other
Initialisation Installation OS4 Updates About OS4 File Systems Networking Printing Other
Introduction File System Workbench Preferences Commands Error Msgs Miscellaneous

AmigaOS 4.0 - About OS4 - Commands

NETLOGVIEWER Networking
Purpose: To capture any debug or notification network messages.
Format: NETLOGVIEWER [CX_POPKEY <key>] [CX_PRIORITY <priority>]
[CX_POPUP <yes | no>]
Template: CX_POPKEY/K, CX_PRIORITY/K, CX_POPUP/K
Path: C:NETLOGVIEWER
NETLOGVIEWER is used to capture any debug or notification messages sent by bsdsocket.library or its clients, and runs as a commodity.

NETLOGVIEWER must be started before you add the first networking interface (in order to capture any error output). Note, however, that if you shut down the bsdsocket.library (by using the NetShutdown command) the NETLOGVIEWER program will exit, too.

CX_POPKEY enables you to specify the hot key for the program. If more than one key is specified, be sure to enclose the entire argument in double-quotes (i.e. CX_POPKEY="Shift F1"). Default is "Shift Alt F8"

CX_PRIORITY sets the priority of BLANKER in relation to all other Commodity Exchange programs. All the Commodity Exchange programs are set to a default priority of 0.

CX_POPUP=no will prevent the BLANKER window from opening. (By default the program window opens when the command is invoked.)

The following window is displayed when NETLOGVIEWER is started and errors have been reported - in this instance the network cable was disconnected.

NetLogViewer Window

Notes:
At this time there is a slight complication when running NETLOGVIEWER from the Startup-Sequence. When it is run without CX_POPUP=no it immediately opens a window, which defaults to the current resolution. Therefore if NETLOGVIEWER is run prior to LOADWB, it will run in the wrong resolution and LOADWB will be unable to reset the window, so either CX_POPUP=no must be specified or NETLOGVIEWER and ADDNETINTERFACE must be run after the LOADWB command.

However, if CX_POPUP=no is used and an error is detected while the NETLOGVIEWER window is still hidden, NETLOGVIEWER will fail, so timing can be critical. Using CX_POPUP=no works fine as long as you use the CX_POPKEY or default (Shift Alt F8) to activate the window before the first error is detected. If, for some reason, this is not possible you must use the other option discussed above.

Example 1:

In this example we want to run NETLOGVIEWER from the Startup-Sequence using CX_POPUP=no, which means it must be run prior to the first networking interface being started.

   run >NIL: C:NetLogViewer >NIL: CX_POPUP=no
   run >NIL: C:AddNetInterface >NIL: DEVS:NetInterfaces/~(#?.(info|off))

In this instance you must activate NETLOGVIEWER using the CX_POPKEY or default (Shift Alt F8) once the Workbench is loaded and before any errors occur.

Example 2:

In this example we want to run NETLOGVIEWER from the Startup-Sequence using the default value for CX_POPUP which is 'Yes', which means it must be run prior to the first networking interface being started but after LOADWB being run.

   C:LoadWB
   run >NIL: C:NetLogViewer >NIL:
   run >NIL: C:AddNetInterface >NIL: DEVS:NetInterfaces/~(#?.(info|off))

NOTE, that by default, AddNetInterface is normally run earlier in the Startup-Sequence, and must be moved after the LOADWB command, together with the NETLOGVIEWER command, in order for it to work successfully.

Example 3:

In this example we want to run NETLOGVIEWER while the system is running.

   3.OS4:> NETLOGVIEWER

in this instance, NETLOGVIEWER is being run independently, and while this will load and run the program, it will not produce any output if the interface has already been started. The correct procedure is shown in Example 4.

Example 4:

In this example we want to run NETLOGVIEWER while the system is running.

   3.OS4:> NETSHUTDOWN
   3.OS4:> NETLOGVIEWER
   3.OS4:> ADDNETINTERFACE DEVS:NetInterfaces/ETH3COM

in this instance, we have shutdown the network interface, started NETLOGVIEWER and then restarted the network interface in order to log network errors.


Return to Commands Selection

Disclaimer: Amiga Auckland have prepared the above information for the use of its members based on our experiences and as such is subject to revision at any time. Amiga Auckland cannot guarantee any of the information and cannot be held accountable for any issues that may result from using it.


Copyright 2006 Amiga Auckland Inc. All rights reserved.
Revised: February 9, 2006.