• Subject: RE: Windows NT and RUNRMTCMD
  • From: Buck Calabro <mcalabro@xxxxxxxxxxxx>
  • Date: Wed, 28 Jul 1999 09:08:21 -0400

It sounds as if the CWBRXD command is started before the I: drive is
assigned.  I know practically nothing about NT, but I would suggest changing
the order of the commands in the startup folder.  Barring that, don't
automatically run CWBRXD during startup - let the startup finish (and assign
the I: drive) then manually run CWBRXD.

Buck Calabro
Billing Concepts Albany, NY
mailto:mcalabro@commsoft.net

> -----Original Message-----
> From: fkolmann@revlon.com.au 
> Sent: Tuesday, July 27, 1999 9:43 PM
> To:   midrange-l@midrange.com
> Subject:      Windows NT and RUNRMTCMD
> 
> I am not sure if this is the right place to ask.
> We have a PC running Win NT and are connected via TCP-IP on a Novelle
> network using IBM Client Access.
> I am sending a RUNRMTCMD to the PC (the appropriate CX?? pgm is active
> on thePC) and the PC runs the command.
> My problem is that I have I : defined to go to the AS400 shared folders
> on the PC but in the ?emulation/dos? box that the command executes I
> cannot get access to the I:.  Its as if the PC expects me to assign the
> I: and log on to the AS400 again, even though I am already giving it
> commands from the AS400.
> 
> Does anyone know of what is needed to get this to work.  TIA. Frank
> 
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact [javascript protected email address].