The Major BBS Forums (Archive)

I've been working on this pretty much all day, trying to get certain variables to work with my DOS 5 system so that a batch file could be made for daily backups, but I couldn't get anything to work. I got the variables to work but didn't know how to convert them, despite using a few batch files/variables from the web that were suppose to do it (maybe for dos 6 or win nt?)

Why did I need variables? The date format on my copy of DOS is DD-MM-YYYY, which ends up being over the 8 character DOS filename format.

I eventually found a program called XSET, which is considered shareware but is suppose to be uncrippled and it will actually change the date format very easily, with the "XSET datevar DATE" command. After you use this command in a batch file, you can also use the variable in a batch file like this:

xcopy . d:\backups\%datevar%\

When that batch file is called from MBBS/WG's nightly cleanup routine, it will automatically name the directory the date on which the backup is made. Why is this important? It allows you to backup copies for for an extending period of time with no user intervention. You don't have to replace tapes, zip disks, etc every day. Of course, if you don't want a daily backup, it may not be something you'd like!

How to access wg/mbbs's dos batch program... Strange that there's no wgsclean.mdf file in the directory when you install it (at least not in the mbbs 6.26 or wg 1.1 I have) - so, guess what? You have to make it.

The wgsclean.mdf file:

; WGSCLEAN.MDF
Module Name: Offline Cleanup & Events
UNCONDITIONAL
INTERNAL
; Add "Cleanup:" or "Event-X:" lines specifying applications to run, and
; the applications will be executed in that order, during cleanup or the
; specified event.
Cleanup: \TAPE\TAPEBACK.EXE \Program Files\Galacticomm\Worldgroup Server /L- /D+ /SNU
Cleanup: WGSCLEAN.BAT
Event-1: COPY *.DAT \BACKUP
Event-1: WGSEVT1.BAT
Event-2: WGSEVT2.BAT
Event-3: WGSEVT3.BAT
Event-4: WGSEVT4.BAT

This isn't my file. I actually stumbled across it on another site, which made me try to make my own. My copy actually looks a bit more like this:

; WGSCLEAN.MDF
Module Name: Offline Cleanup
UNCONDITIONAL
INTERNAL

Cleanup: WGSCLEAN.BAT


Now, I don't know what the UNCONDITIONAL or INTERNAL things are, if they even need to be there, but I copied them into my file just to be sure.

Now, you have to make a wgsclean.bat file, to call up other batch files. Since I'm only doing one task: backing up the bbs, I only needed one entry: backit.bat

My backit.bat looks like this:

xset datevar date
xcopy . d:\backup\%datevar%\

Make sure to put the slash behind the %datevar% of the program will ask you whether or not it's a file or a directory it's being copied to.

When it's done, it copies to DD-MM-YY format, which is 8 characters as opposed to 10.

This will minimize backup downtime, and you'll have a backup for each day, which may be important if something went wrong in one or more of the files and it went unnoticed for several days. You don't have to settle with just the last backup but could go back for as long as you wanted.

To find xset, just google it.. it should be the first page that comes up.

Just a note - I've also tried this in ms-dos 7.10, and none of the cleanup events seem to occur, not even the built in trade wars cleanup on my TW2002 demo.

It would be nice if the backup event could actually copy the files to a network hard drive, and I believe it's possibly possible, but I can't get the 3c905b drivers to unload after they've been loaded. It'd be nice if, on cleanup, the batch file could unload the network driver, let the MS network use its own driver, copy the files over, unload itself, load the 3290x drivers back up, and then restart worldgroup as normal, all automatically.

when I do the "3c90xpd /u /i=0x60" command, it just shows a list of commands.

Here's one of my thoughts for doing daily maintance...

Depending on your system, why not have it to a backup when the computer first loads, then for cleanup, have a command to reboot the computer??

This will also allow for easier control of when certain network options (or drivers) run...

Just a thought, I don't do this, but might once i get my bbs on a different computer because the one it's running on now has boot issues:)

Thanks!
--James

Since I couldn't get the driver to unload, I guess there should be a way to actually create a group of batch files that change the config.sys, autoexec.bat, reboot, copy the files to a network drive, change the config.sys and autoexec.bat files back, and reboot again, back into wg.That way, I wouldn't have to worry about unloading drivers, as each config.sys change and reboot would change the drivers which are loaded anyway.

That may be something worth checking into later...

Malakai wrote:Since I couldn't get the driver to unload, I guess there should be a way to actually create a group of batch files that change the config.sys, autoexec.bat, reboot, copy the files to a network drive, change the config.sys and autoexec.bat files back, and reboot again, back into wg.That way, I wouldn't have to worry about unloading drivers, as each config.sys change and reboot would change the drivers which are loaded anyway.

That may be something worth checking into later...

Maybe this will help it mentions a bit about unloading the driver manually, found this in dos odi help area of the 90xxx driver files

3Com (R) Corporation
3C90x EtherLink PCI NIC Family
3Com NIC Configuration and Diagnostic Program for DOS


Overview
--------
The configuration portion of the 3Com NIC Configuration and Diagnostics
program for DOS allows you to change the configuration parameters
for the NIC to fit the specific environment in which the NIC is
installed.

The diagnostics portion of the program is designed to make sure that
the NIC is installed correctly and functioning properly in the PC.
It consists of the following tests:

The Group 1 tests check the physical components, connectors, and
circuitry of the NIC and require only that the NIC be installed in
the PC.

The Group 2 tests check the ability of the NIC to transmit data on the
network; these require that the NIC be connected to a loopback plug
or to a network (for 3C900-COMBO or 3C900-TPC NICs).

The Group 3 tests check the ability of the NIC to correctly transmit and
receive data over the network; these require that the NIC be connected
to a network on which an echo server has been set up.

The PC that contains the NIC to be configured or tested must be running
DOS only (reboot with a DOS-only diskette) and must have at least 505KB
of free memory.

NOTE: If the PC is an operating server, notify all users of the
server to save their work and to log out from the network before
running the Configuration and Diagnostics program. The program
disrupts the normal operation of servers and workstations,
and work that is not saved may be lost.


Starting the 3Com NIC Configuration and Diagnostics Program for DOS
------------------------------------------------------------------

There are two ways to start the program:

1. Automatically (from INSTALL.EXE) by selecting
Configuration and Diagnostics Program on the main menu.

2. Manually, from the root directory of the EtherCD or EtherDisk diskette 2,
by typing the following command:

3C90XCFG [command keyword] [parameter list]

3C90XCFG represents the 3Com NIC Configuration and Diagnostics program
name.
The brackets indicate that the command keyword and parameter list are
optional.

3C90XCFG without any arguments invokes the program in full Windows
mode. This includes mouse support and context-sensitive help.
Press [F1] for help at any time.


Command Line Keywords
---------------------
You can use the first two characters of any command or parameter as a
shortcut. For example, 3C90XCFG HE RU means 3C90XCFG HELP RUN.

The command keywords and parameters are not case-sensitive (for
example, CONFIGURE, configure, and Configure, will all work).


CONFIGURE
Configures a NIC in one of three ways:
1. Automatically with the /auto parameter
2. Using a specified NIC configuration file
3. Using command line configuration parameters

ECHOSERVER
Enables a designated NIC to function as an echo
server.

HELP
Displays general or command-specific help information.
To get command-specific help, type:

3C90XCFG HELP [command keyword]

LANGUAGE
Invokes the program in full Windows mode using a
specified external resource file. This option provides
support for multiple languages through a different resource
file for each language supported.

LIST
Displays a list of installed NICs and their recognized
NIC numbers.

RUN
Executes the diagnostic tests (which can also be specified
from a file) on a selected NIC and writes the results
to the screen, a file, or a printer.


Configuration
-------------
The NIC can be configured in either full-screen Windows mode or
command line mode.


Full Screen Windows Mode
------------------------
To configure the NIC using full-screen windowing, type:

3C90XCFG [Enter]

Then select the Configure NIC option from the Install menu.


Command Line Mode
-----------------
Command Line Mode Defaults
--------------------------
Defaults: CONFIGURE has /AUTO and /ADAPTERNUM:1 as defaults.
So, for example, if only 3C90XCFG CONFIGURE is used, NIC
number 1 is automatically configured.

ADAPTERNUM:N and /SLOT:S parameters can be used with any of the
CONFIGURE options that follow. They are both intended for use
whenever multiple NICs are present in the PC and
recognized by the Configuration and Diagnostics program.

/ADAPTERNUM:N specifies the number of the NIC to be configured for
PCI computers. Run the LIST command separately to determine the
NIC number to use here.

There are three different ways to configure the NIC using
command-line mode:

1. Command line with auto configuration

2. Command line with explicit parameters

3. Command line with configuration file


Command Line with Auto Configuration
------------------------------------
Command syntax: 3C90XCFG CONFIGURE /AUTO

The /AUTO parameter configures the NIC media type
automatically. All other options settings are left unchanged.

NOTE: The program attempts to detect what media type is being
used. Therefore, connect to the network first and then run
3C90CFG CONFIGURE /AUTO. The program configures the
media type for you.


Command Line with Explicit Parameters
-------------------------------------
Command syntax: 3C90XCFG CONFIGURE [ /BSTATE:N /XCVR:N /TR:N
/FULLDUPLEX:N /OPTIMIZE:N /LINKBEAT:N ]

Command line configuration parameters are used to configure the
NIC using only the option settings you specify. Some
parameters are for all NICs; some are for PCI only. For
example, /BSTATE:N is a PCI-only parameter. In most cases, any
combination of parameters can be used. Therefore, it is possible
to modify only a few settings if needed.

/BSTATE
Boot PROM state
Possible values - disabled, enabled

/TR (or /XCVR)
Transceiver
Possible values - Auto, 100BASE-TX, 10BASE-T, COAX, AUI,
100BASE-T4, 10BASE-FL, and 100BASE-FX

/OPTIMIZE
Network Driver Optimization
Possible values - NORMAL, NETWORK, CPU

/LINKBEAT
Link Beat disable/enable (pre-10BASE-T standard only)
Possible values - disabled, enabled

NOTE: Try this setting ONLY if pre-10BASE-T standard hubs
are in use.

/FULLDUPLEX
Full Duplex disable/enable
Possible values - disabled, enabled

NOTE: Enable this setting ONLY if the NIC is
connected to a 100BASE-T or 10BASE-T repeater
that supports full duplex. Otherwise, it will bring
down the network.


Command Line with Configuration File
------------------------------------
Command syntax: 3C90XCFG CONFIGURE /CONFIGFILE:filename

/CONFIGFILE:filename is used to configure a NIC with the
settings specified in an ASCII configuration file that can be
created and modified by any text editor. The filename can be
a fully qualified DOS filename including a path. A standard
format for the file must be used, as follows:

- Variable names and values match the wording in the
full-screen Configure window in most cases.

- Begin each variable/value line with an "at" symbol (@),
followed by a variable name, a colon (:), and the value.

Example: @Media type: 100BASE-TX

- Blank lines and other white spaces are allowed between
variable lines.

- Start any comment lines with a semicolon (;).

- The variable names allowed are:
Boot PROM state
Media type
Network driver optimization
Full duplex
Link beat

- The values allowed are the same as those shown in the
full-screen Configure window.

Example 1: @Network driver optimization:Normal
Example 2: @Media type:On-board Coax


Diagnostics
-----------

Full-Screen Windows Mode
------------------------
To run the diagnostic tests using full-screen windowing, type:

3C90XCFG [ENTER]

Then select the Run Tests option from the Tests menu.


Command Line Option - RUN
-------------------------

Command syntax: 3C90XCFG RUN [/TESTFILE:filename] [/RESULTS:[filename
| PRN | PRNHP]] [/ADAPTERNUM:N]

The RUN parameter executes the diagnostic tests on a selected NIC
and displays the results on the screen. The defaults are NIC
number 1 and Group 1 tests. The parameters below are all optional.

/TESTFILE:filename
Specifies a test file that contains a specific test setup
description.

/RESULTS:[filename or PRN or PRNHP]
Specifies an alternative location to store the test results.
This location can be a DOS path and filename, PRN printer port
(same as LPT1), or PRNHP, which is an HP LaserJet printer
connected to LPT1.

/ADAPTERNUM:N
Specifies the NIC number to be tested, in the case of
multiple NICs installed in the PC and recognized by
this program. Run the LIST command separately (see LIST below)
to determine the NIC number to use.


Other Command Line Options
--------------------------

HELP
Command syntax: 3C90XCFG HELP [Command Keyword]

HELP is an on-line summary of commands. Without a command keyword
specified, it gives a summary of the command keywords. With a command
keyword specified, it gives the parameter choices for that particular
command. For example, 3C90XCFG HELP CONFIGURE gives details about the
parameter options for the CONFIGURE command.

LANGUAGE
Command syntax: 3C90XCFG LANGUAGE /LANGFILE:filename

LANGUAGE invokes the program in full Windows mode using a specified
external resource file. This option provides support for multiple
languages through a different resource file for each language supported.

/LANGFILE:filename is a required parameter with this command.
The filename is the name of the resource file that is loaded by the
program. The filename can be a fully qualified DOS filename.

NOTE: At this time, there are no alternative resource files included
on the EtherCD or EtherDisk diskette.

LIST
Command syntax: 3C90XCFG LIST

LIST displays a list of currently installed NICs (and their
assigned NIC numbers) that are recognized by this program. The
NIC number is then used as the N value for the /ADAPTERNUM:N
parameter when multiple NICs are installed. There are no
parameters associated with the LIST command keyword.

ECHOSERVER
Command syntax: 3C90XCFG ECHOSERVER [/ADAPTERNUM:N]

ECHOSERVER enables a NIC to function within an echo server.
/ADAPTERNUM:N specifies the NIC to be configured in the
echo server, in the case of multiple NICs.


Further Assistance
------------------
If the NIC fails any of the diagnostic tests, see the TROUBLE.TXT file
in the \HELP directory on the EtherCD (or EtherDisk diskette 2) for
troubleshooting procedures.

The SUPPORT.TXT file in the \HELP directory on the EtherCD (or EtherDisk
diskette 2) provides information about obtaining product support for
the NIC.


3Com, EtherDisk, and EtherLink are registered trademarks of 3Com
Corporation. All other trademarks are the property of their respective
owners.


(%VER DOSDIAG.TXT - Configuration and Diagnostic Program Instructions v5.1.0)

Malakai wrote: I eventually found a program called XSET, which is considered shareware but is suppose to be uncrippled and it will actually change the date format very easily, with the "XSET datevar DATE" command. After you use this command in a batch file, you can also use the variable in a batch file like this:

xcopy . d:\backups\%datevar%\

BTW, Don't run this batch command on the same drive you're backing up, as it will make an infinite loop in the directory structure, and there will be no way to delete the x:\backups\%datevar%\ directory it created.

If you're going to run it on the same drive (for testing purposes, etc), it would be safer to run:

xcopy *.* x:\backups\%datevar%\

The difference between "." and "*.*" is that "." backups up everything on your hard drive, while "*.*" backs up just the worldgroup directory.

If there are subdirectories in the worldgroup system, then you'd also add a switch like /s, for example:

xcopy *.* x:\backups\%datevar%\ /s

In DOS 5, the /e switch doesn't seem to work, but I highly doubt you'd need to copy empty directories (I haven't so far). The /s switch copies all directories but empty ones.

I believe that DOS 5 uses just slightly less RAM than dos 6.22. That's why I use it, but there are probably more advantages to run DOS 6.XX, because for example, it has the DELTREE command, which is useful for wiping complete directory structures out, including the files. In DOS 5, you have to manually delete each file in every subdirectory before the directories can be removed. This can be a hassle when there are tons of subdirectories.

DOS 6.xx also has memmaker, which is good for getting having the system auto-configure all of your drivers, etc and getting the most RAM out of the system.

Some device drivers for tape drives seem to call for DOS 6.0 or higher as well. Does that mean they won't work DOS 5? Who knows, unless some one tries...

I believe that switching from an IDE Hard drive rack to a tape drive for daily backups will be in the future, for the DMA server. The tapes are a lot more expensive, as much as $10 per, but there are some that will hold 1gb uncompressed or 2gb compressed, and that would probably give me 5-10 days worth of backups before having to change out the tape, and I wouldn't have to take the server down to copy the contents to a cd or dvd.

How possible would it be to run two nics in DOS, one with MS networking loaded and the other with worldgroup DOS? I believe multiple NICs can be loaded, but what determines which one worldgroup would use and which one ms client would use?

If possible, could both NICs be on the same network, or would the 2nd NIC have to be connected to a 2nd network?

Malakai wrote:How possible would it be to run two nics in DOS, one with MS networking loaded and the other with worldgroup DOS? I believe multiple NICs can be loaded, but what determines which one worldgroup would use and which one ms client would use?

If possible, could both NICs be on the same network, or would the 2nd NIC have to be connected to a 2nd network?

It is possible but you need to have the second card on differnt init, some of the old network card have jumper for init A/B. Set one for A the other B or you could probably set this in the nram settings on a newer card.

Looks like none of my network cards have any jumpers.. Wonder if it can be done through the 3c90x configuration software... most of my test pcs are gone after putting up another makeshift dos server temporarily... might have to dig out one of the old old dos systems..