Create a file called startup.cmd in the root directory of your boot drive and
put the NET USE command in there.
--
Trevor Hemsley, Brighton, UK
Trevor dot Hemsley at ntlworld dot com
There was a series of posts in comp.os.os2.networking.misc on
11-June-2006 titled "Network (PEER) drive alias: how to make it
stick?". In one of those, Paul Ratcliffe wrote, "Use the 'Shared
Resources and Network Connections' or 'Sharing and Connecting'
object (depending on which version of OS/2 you're running) and
create a connection using that."
--
Fred Blau
(Remove SPAM-STOP from e-mail address)
Put the following commands into the file: \tcpip\bin\tcpexit.cmd on
the boot drive:
logon userid /p:password
net use x: \\whatever
substituting as necessary.
You can put it in \startup.cmd, but I have seen occasional timing
problems. If you put it in tcpexit.cmd then you can be sure it's all up
first.
(there is a form of networking protocol where this is not necessary, but
it does no harm to sequence it like this).
--
Bob Eager
That's assuming that he's using Netbios over TCP/IP, and not
plain Netbios. If using just Netbios, there's no reason to
start up tcpip.
Bob Plyler IBM 3890/XP Engineering
(not an official IBM spokesperson)
> > You can put it in \startup.cmd, but I have seen occasional timing
> > problems. If you put it in tcpexit.cmd then you can be sure it's all up
> > first.
> >
> > (there is a form of networking protocol where this is not necessary, but
> > it does no harm to sequence it like this).
>
> That's assuming that he's using Netbios over TCP/IP, and not
> plain Netbios. If using just Netbios, there's no reason to
> start up tcpip.
That was what I was (badly) attempting to say in the last paragraph. But
I hadn't thought of the situation where TCP/IP wasn't running at all, I
must admit. Having said that, he could be running separate NETBIOS and
TCPIP, as a mixed network.
--
Bob Eager
> I need to permanently map a network drive on a machine that is running
> OS/2 Warp 4. The problem that I am having is that I can map it using
> the Net Use command from the command line interface, but it won't
> recognize the /persistent:yes switch that always works Microsoft
> operating systems.
The equivalent switch under OS/2 is: /PERM
You can also use the "Shared Resources and Network Connections", which
under Warp 4 is (I think) somewhere under the "Connections" folder.
(On my W4 system, it's in the "Connections" -> "Network" -> "Network
Services" folder, but I may have moved things around a bit.)
There's an option on the connections page to make a connection
persistent. (Note: if you don't have the PEER service started, this GUI
may give you annoying error popups about the server not being started, but
you can treat those as harmless.)
This should cause the connection to be reattached whenever the REQUESTER
service is (re)started. This probably happens after bootup, assuming your
setup is fairly generic. If the NET START REQ command is in STARTUP.CMD,
you can of course take Trevor's suggestion and put the explicit NET USE
command in the same file, after the NET START command (as an alternative to
using /PERM or the GUI; I don't suggest doing both).
--
Alex Taylor
Fukushima, Japan
http://www.cs-club.org/~alex
Please take off hat when replying.