PRB: Delta and Bad Command or Filename MessageID: Q111548 The information in this article applies to:
SYMPTOMSYou may receive two "bad command or filename" messages and a "command completed successfully" message when performing a Delta command. CAUSEDelta was not properly added to the path during set up, or the network login script has removed Delta from the path. RESOLUTIONFrom MS-DOS, verify that Delta was properly added to the path statement. to do this, exit Windows and type SET at the command line; Delta should be in the path. If it is, start Windows and create an MS-DOS session (MS-DOS Prompt) and repeat the SET command. If you find the Delta directory is missing from the path and you are on a network, the problem may be due to environment changes being made by your network login script. Change the login script appropriately or consult your network administrator for suggestions on how to repair your path. NOTE: MS-DOS versions 6.x do allow path statement lengths of greater than 128 characters when specified within the CONFIG.SYS file. However, once the path is declared in the CONFIG.SYS, the path may not be altered within the AUTOEXEC.BAT or any other batch file. Please consult your MS-DOS 6.x user s guide for more information. Additional reference words: 1.00 KBCategory: kbusage kbprb KBSubcategory: Delta |
Last Reviewed: June 13, 1995 |
