Note that <ch> refers to Virtual Advanced Channel Number,
and that <x> refers to the NETWORKID #, as defined by file
DATA\NETWORKS.LST.
As a DOOR:
VQWK.EXE <ch>
(Example: VQWK %1)
The default Virtual Advanced set-up already includes references
to VQWK.EXE in the default function blocks provided. Knowing
the commandline usage is important, though, if you wish to
customize how the QWK door is accessed on your system, such
as running it from a script (example: DOOR "VQWK %1").
As a NETWORK INTERFACE:
Step 1. Generate Packet To Exchange (Send To) Other QWK net BBS
VQWK 0 /EXPORT=<path and filename>,<user #> NETWORKID=<x>
<path and filename> QWK Format File To Be Created
<user #> Dummy User # Assigned To This QWK Net Connect
Step 2. Get Packet From Remote BBS
Send Packet Created In Step 1 to Remote BBS
How this part is accomplished is up to you and the remote sysop.
Typically, this is done by using a script-driven comm program
such as Telix or Telemate to call, login, and download a QWK
packet. After that, the packet created in step 1 is uploaded.
Step 3. Get The Messages Onto Your BBS
VQWK 0 /IMPORT=<path and filename>,<user #> NETWORKID=<x>
<path and filename> QWK Format File To Be Imported
<user #> Dummy User # Assigned To This QWK Net Connect
Note: The <user #> dummy account is used for its "new-scan"
pointers, allowing your BBS and another BBS to exchange QWK
mail without duplicates, so long as each QWK net BBS you
exchange mail with has its own, consistent dummy account to use.
|