
                  OS/2 Lan discussion              (Fidonet)

                 Saturday, 27-Nov-1999 to Friday, 03-Dec-1999

+----------------------------------------------------------------------------+

From: David Calafrancesco                               25-Nov-99 09:33:29
  To: Bryan Rubingh                                     27-Nov-99 15:42:15
Subj: Warp 3 Logon prompt

Bryan Rubingh wrote in a message to Don Guy:

 BR> Exact same problem I had.  Took me a couple years before I
 BR> stumbled across the solution.  You need to edit the
 BR> config.sys file.  You have a line which looks like:

 BR> SET AUTOSTART=TASKLIST,FOLDERS,LAUNCHPAD,CONNECTIONS

 BR> Remove the ",CONNECTIONS" from the list.  Then the logon
 BR> prompt will no longer appear when you boot the machine.  You
 BR> do need to leave the logon command in your startup.cmd.

 BR> (Note:  I think it is "CONNECTIONS".  I removed it from mine
 BR> so I'm going by memory.)

It is exactly the CONNECTIONS item. Also, remember to remove any start peer
services or similar ICONs from the startup folder. Use a simple 

net start requester
net start server                        # if it is a peer server
logon UserName /d:domain /p:password    # the /d:domain is not required for a  
                                       # single domain

 BR> The problem is that OS/2 attempts to autostart the LAN
 BR> connections as they were when you powered down.  To do that
 BR> it needs to logon.  Thus, that pops up before the "net
 BR> start" has even finished.  It is NOT "net start" which is
 BR> bringing up the logon window.

No, but a net use would bring up the logon prompt if run before the logon. 

 BR> One other tip I found that may assist you.  We have some
 BR> machines which we want logged on all the time.  We have a
 BR> rexx program which updates some files on the server every
 BR> ten minutes.  If they encounter an error accessing the
 BR> server, they logoff and logon again.  I don't have the rexx
 BR> code here, but as I recall there is a parameter we added to
 BR> logon so it doesn't display an error if it can't logon. 
 BR> That way if an error occurs while trying to logon, it won't
 BR> bring up the logon window, the program will continue and try
 BR> again in 10 minutes.  If you are interested, let me know and
 BR> I'll try to get the code.  Could be a couple weeks before I
 BR> get over there though.

I would be very interested in such code myself. Email it to me at any of my
addresses please. 

Dave Calafrancesco, Team OS/2
dave@drakkar.org

... They got the library at Alexandria, they're not getting mine! 
--- 
 * Origin: Druid's Grove BBS - (914)/876-2237 (1:2624/306)

+----------------------------------------------------------------------------+

From: Peter Knapper                                     28-Nov-99 11:28:10
  To: David Calafrancesco                               28-Nov-99 00:48:02
Subj: Warp 3 Logon prompt

Hi David,

 BR> One other tip I found that may assist you.  We have some
 BR> machines which we want logged on all the time.  We have a
 BR> rexx program which updates some files on the server every
 BR> ten minutes.  If they encounter an error accessing the
 BR> server, they logoff and logon again.  I don't have the rexx
 BR> code here, but as I recall there is a parameter we added to
 BR> logon so it doesn't display an error if it can't logon. 
 BR> That way if an error occurs while trying to logon, it won't
 BR> bring up the logon window, the program will continue and try
 BR> again in 10 minutes.  If you are interested, let me know and
 BR> I'll try to get the code.  Could be a couple weeks before I
 BR> get over there though.

 DC> I would be very interested in such code myself. Email 
 DC> it to me at any of my addresses please. 

You can actually do this without using REXX, I add the /R parameter to my
non-REXX .CMD files and the LOGON function returns to the command prompt
without notification boxes appearing when an Error occurs.

NOTE: In case you go looking for it, the LOGON command is NOT described in the 

Networking folder under "File and Print" help, but in the main OS/2 CMD
Reference help. Now why LOGON and the NET command are not considered Network
type commands but conventional commands beats me.........;-(

Cheers..........pk.


--- Maximus/2 3.01
 * Origin: Another Good Point About OS/2 (3:772/1.10)
2320/38

+----------------------------------------------------------------------------+

From: Don Guy                                           28-Nov-99 12:06:27
  To: Peter Knapper                                     28-Nov-99 22:30:22
Subj: Warp 3 Logon prompt

Greetings Peter!

   A long time ago, in a galaxy far, far away, a coded message from Peter
Knapper to Don Guy was intercepted...

 PK> 1. From an icon titled "File and Printer Sharing" (Warp 4 name, Warp
 PK> 3 is called "Start OS/2 Peer"), in the Startup Folder,

Have that one, but I'm not using it.  If memory serves, it was placed in the
startup folder, as well as "net start req" in StartUp.Cmd when I set the box
up.  The "Start OS/2 Peer" object appeared to be doing the same thing as the
StartUp.Cmd entry, so I removed it.

 PK>   2. Via a command line action that can be either -
 PK>      1. An explicit Networking command such as -
 PK>         NET START REQ           (or similar)
 PK>      2. The use of a NETWORK function that forces the network to start up
 PK> -        LOGON userid /p:password /r /s

You've probably seen my reply to Robin I. by now, but that is essentially what 
I use.  More precisely,

    @Echo Off
    Echo Starting Requester Service
    Net Start Req
    if errorlevel 2 C:\IBMLAN\NETPROG\lserr.exe

    Echo Logging on to Network
    logon username /p:pwd /v:local /r

    Echo Updating clock from \\Earth
    net time \\earth /set /yes

    Exit


The Startup folder contains nothing other than a shadow of the messaging
service, and a little program I use for monitoring system resources.  After
removing everything from the Startup folder, and commenting out the contents
of StartUp.Cmd, the logon prompt is still appearing.  I would assume at this
point that something in the system's Config.Sys is doing the deed.  I'll post
a chunk of the system's Config.Sys in another message...

-Don



... File found but don't want to run: <A>bort <R>etry <F>ail
---
 * Origin: EI/2 [Carleton Place, Ontario, Canada] (1:249/176)

+----------------------------------------------------------------------------+

From: Don Guy                                           28-Nov-99 11:41:27
  To: Bryan Rubingh                                     28-Nov-99 22:30:22
Subj: Warp 3 Logon prompt

Greetings Bryan!

   A long time ago, in a galaxy far, far away, a coded message from Bryan
Rubingh to Don Guy was intercepted...

 BR> SET AUTOSTART=TASKLIST,FOLDERS,LAUNCHPAD,CONNECTIONS

 BR> Remove the ",CONNECTIONS" from the list.  Then the logon prompt will
 BR> no longer appear when you boot the machine.  You do need to leave the
 BR> logon command in your startup.cmd.

Worked like a charm... thanks!

 BR> One other tip I found that may assist you.  We have some machines which
 BR> we want logged on all the time.
<snip>
 BR> If you are interested, let me know and I'll try to get the code.
 BR> Could be a couple weeks before I get over there though.

I like the sound of that.  If you don't mind...  :-)

-Don



... Captain! The UARTs cannot take this speed any more!
---
 * Origin: EI/2 [Carleton Place, Ontario, Canada] (1:249/176)

+----------------------------------------------------------------------------+

From: Don Guy                                           28-Nov-99 12:05:05
  To: Peter Knapper                                     28-Nov-99 22:30:22
Subj: Warp 3 Logon prompt

Greetings Peter!

   A long time ago, in a galaxy far, far away, a coded message from Peter
Knapper to Don Guy was intercepted...

 PK> Hmmmmm. Perhaps you could post the entire contents of your CONFIG.SYS and
 PK> STARTUP.CMD files. We might see something there that is triggering things
 PK> off.

No need to do that now--looks like Bryan R. nailed it.  My thanks in any case
though!

-Don



... CCITT: Can't Conjure Intelligent Thoughts Today
---
 * Origin: EI/2 [Carleton Place, Ontario, Canada] (1:249/176)

+----------------------------------------------------------------------------+

+============================================================================+
