We have been buying a lotof laptops lately, primarily Thinkpads with Docks.
Most of these machines run Windows 3.1, with TCP/IP.  We have ADSM installed,
and they run quite nicely.

The problem is a group of people that are using a product named Shieva to let
them remotely access a server while they are at home.  (I believe they are
either going after NetWare files, applications on the NetWare Servers, or
Lotus Notes.)  The problem is that when the machine is booted, Shieva routines
are loaded, and communications are established with the server via the modem.
When Windows starts, ADSM is in the Startup folder, and immediately tries to
kick off.  Because a communications method is present, ADSM tries to establish
communication with his server, and succeeds, although very slowly.  According
to the guys working on the Shieva support, thet can't get out of ADSM quickly;
their answer is to remove ADSM from the Startup folder.  This concerns me, as
my experience is that if ADSM isn't in the startup folder, people don't run it
offen enough to justify it.

I can think of several ways to solve this problem under OS/2, but am not
enough of a windows guru to come up with a solution.  Does anyone have any
suggestions?

Jerry Lawson