"MODEM BURNING" scripts (auto setup a modem)

From: Jim Agnew [agnew@hsc.vcu.edu]
Sent: Friday, January 19, 2001 4:33 PM
To: Everhart, Glenn (FUSA)
Subject: Re: What succeeds TSM?

Glenn,

Here are the modem scripts and a manual for practical peripherals modems
that is very thorough.  

Here is a little ditty...

These *.in and *.out files program dialin and dialout modems for use on a
DECserver 550.  The typical terminal server setting for a dialin modem
follows...

Some may need to be set to filetype STREAM.

Local> show port 81

Port 81: Dialin_01                     Server: ADVIL

Character Size:            8           Input Speed:        9600
Flow Control:            XON           Output Speed:       9600
Parity:                 None           Modem Control:   Enabled
Stop Bits:           Dynamic

Access:                Local           Local Switch:       None
Backward Switch:        None           Name:          Dialin_01
Break:              Disabled           Session Limit:         1
Forward Switch:         None           Type:               ANSI

Dedicated Service:  ANACIN

Authorized Groups:  0-5
(Current)  Groups:  0-5

Enabled Characteristics:

Autobaud,  Autoprompt,  Broadcast,  Dialup,  Inactivity Logout,  Lock
Loss Notification,  Message Codes,  Password,  Verification

the terminal server settings for DIALOUT modems follows...
(warning, has not been used for years...)


Port 7: DSNPORT                        Server: ADVIL

Character Size:            8           Input Speed:        2400
Flow Control:            XON           Output Speed:       2400
Parity:                 None           Modem Control:   Enabled
Stop Bits:           Dynamic

Access:               Remote           Local Switch:       None
Backward Switch:        None           Name:     DSN$MODEM_PORT
Break:              Disabled           Session Limit:         1
Forward Switch:         None           Type:               SOFT

Preferred Service:  None

Authorized Groups:  0-5
(Current)  Groups:  0-5

Enabled Characteristics:

Dialup,  DTRwait,  Loss Notification,  Remote Modification


Good luck!!!

Sincerely, Jim Agnew



 > From: Jim Agnew [mailto:agnew@hsc.vcu.edu]
 > Sent: Friday, January 19, 2001 11:04 AM
 > To: Info-VAX@Mvb.Saic.Com
 > Subject: Re: What succeeds TSM?
 >
 > Would anyone be interested in my Kermit modem-burner floppy?
 >
 > a bootable DOS floppy that runs kermit and then you put in a script you've
 > edited with qed, (included), and it "burns" a modem for
 > you.  I've had it for YEARS, but this is the first time i've thought of
 > giving it out...  no doccos, but if you're into burning
 > modems, it should be figurable out.
 >
 > jim
 >
 > Christoph Gartmann wrote:
 > >
 > > In article <3A6718FA.557E5333@Omond.net>, Roy Omond <Roy@Omond.net>
 > writes:
 > > >Ask yourself if you *really* need TSM.  It oesn't sound to me like
 > > >an awful lot of terminal servers to configure.  Unless they're spread
 > > >out over a large geographical area, you're best just going to each server
 > > >and configuring it on the spot.  I doubt if you'll need to do it very
      often in any case.
 > >
 > > Yesterday I advised one of my employees to add a special kind of modem to
 > a
 > > DECserver700. We had already one of these modems connected to this server.
 > So
 > > all he needed to do was to copy the configuration of the old modem to the
 > new
 > > one. As there was no tool available (like TSM for servers) he printed the
 > > configuration (with some hassle, again no tool) and typed it into the new
 > > modem. Of course there were some typos, then he missed a few settings
 > because
 > > he didn't think of the commands to review these,... A whole day's work for
 > > a single stupid modem. I whish we have had "modem-TSM"...
 > >
 > > Regards,
 > >    Christoph Gartmann