Xref: utzoo comp.sys.ibm.pc.misc:187 comp.os.msdos.programmer:201 Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!mcgill-vision!snorkelwacker!ira.uka.de!smurf!gopnbg!tmpmbx!netmbx!cosheff From: cosheff@netmbx.UUCP (Charles Shefflette) Newsgroups: comp.sys.ibm.pc.misc,comp.os.msdos.programmer Subject: Re: 4DOS Aliases Keywords: 4DOS Message-ID: <943@netmbx.UUCP> Date: 22 Jul 90 01:04:04 GMT References: <1303@tuewsd.win.tue.nl> Organization: netmbx, Berlin, West Germany Lines: 36 mju@mudos.ann-arbor.mi.us (Marc Unangst) writes: >wsinpp@lso.win.tue.nl (Peter Peters) writes: >> -> /l:c:\system\4dos /e:1024 /a:2048 /s:n /p >> >> in my environment >> >> -> set 4dshell=/l:c:\system\4dos /a:2048 /e+128 /s:n >This is your second problem. There is a known bug in 4DOS v3.01A relating >to swapping and alias passing: When 4DOS is in memory-resident mode >(no swapping, or /s:n), aliases are not passed correctly from the >parent shell. Actually, this isn't a bug per se. In the 4DOS manual, page 24 (of the current manual) it states (although not explicitly) that when 4DOS is loaded in the resident mode: "Aliases will not be inherited from a previous shell." My experience shows this to be true. I suggest, as was suggested before, try using the /S:B switch, or none at all, let it figure out what the best method of swapping is. Chuck =========================================================================== Off Switch??? What Off Switch???? =========================================================================== Charles O. Shefflette, System Engineer cosheff@netmbx (US Mail) (International Mail) Box 9086 USAFSB Herbergerweg 1 APO New York, NY 09742-4824 D 1000 Berlin 37 - West Germany ===========================================================================