U.EXE (for DOS) and U2.EXE (for OS/2) are enhanced versions of the NET USE
command intended to make linking and unlinking network resources simpler
(especially changing multiple connections simultaneously).
The syntax is similar to that used by NET USE, except that multiple connections
can be specified on a single command line. For example:
K:\> U J: \\SERVER\DOSAPPS K: PROJ LPT1: LASER1
would link the drive J: to the DOSAPPS share on SERVER, k: to the PROJ share
on SERVER, and LPT1: to the LASER1 share on SERVER.
U will attempt to force closed any connections on existing links before
relinking, so it is not necessary to delete a connection before assigning
it to another resource. For example, with the command:
F:\PROJ> u f: \\SERVER2\PROJ2
U would first remove the connection on the F drive (even though it is the
current drive) and then create the new link on drive F with this one
command (unless the NO FORCE option was specified). Note that on OS/2
workstations U will be unable to delete a connection which is currently in
use in another session.
U uses the last server name it was given as the default server name for
creating a link. To link to resources on different servers on the same
command line, simply specify a new server name, as in:
K:\> U J: \\SERVER\DOSAPPS K: \\SERVER2\DOSAPPS
Typing U with no arguments will show your existing links as NET USE does.
U can be especially useful when linking resources during a logon from a
floppy-only workstation, since it has a small load size, and can make multiple
connections while only having to load itself once.
U does not support supplying passwords to access resources. If you run share
level security or have different passwords on different servers, U will not
be able to link to these drives. I may add password support if there is enough
interest. Since I wrote U primarily for my own use, error messages are terse
or non-existant. Do not be alarmed.
The syntax for a U command line is as follows:
Usage: u [-vfhx] [[local remote]...]
local = local resource (drive or LPT or COM port)
remote = remote resource (need only specify server first time)
/d to delete the local connection
v = verbose (show links as they are made or deleted)
f = no force (default is to force deletions)
x = delete all connections
h = show this help
Now for the legal stuff:
U is provided without any warranty as to its fitness for a particular
application. Although U has been tested extensively, neither the author nor
Cracchiolo & Feder, Inc. will accept responsibility for its performance or
U is copyright 1991 (c) by Sean Purcell and Cracchiolo & Feder, Inc.,
all rights reserved. U is provided free of charge, with the understanding that
it will not be resold or used for commercial purpose without explicit permission
in writing from the author.
The author, Sean Purcell, can be reached at:
73650,372 on CompuServe ([email protected]
from the Internet)
Cracchiolo & Feder, Inc.
4400 E. Broadway, Suite 600
Tucson, AZ 85711
Cracchiolo & Feder, Inc. is a network integrator based in Tucson, Arizona.
C&F specializes in high end network support, and is a Microsoft Network
Specialist and a Novell authorized reseller.
C&F also produces the RightFAX network fax server for LAN Manager and
Please write if you have any comments, suggestions, or bugs to report.
Fixed a problem where the list resources command failed because
of a memory allocation error. The symptom was the error message:
Unable to read link information 2: 234
This should only have occured on networks using share security with
long server names or passwords.
fixed a problem in the documentation, namely, this README specified the syntax :
U -d x:
to delete a resource, rather than the correct syntax:
U x: -d
Added the -x option to delete all existing connections, and
removes the requirement that a ':' follow the name of a local
printer resource (i.e., U will now accept 'LPT1' as well as 'LPT1:')
U will not work on a Basic Workstation, because it uses API calls
that the Basic Redirector does not support.