Xref: utzoo comp.sys.ibm.pc.misc:196 comp.os.msdos.programmer:204 Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!ucsd!sdd.hp.com!cs.utexas.edu!yale!ox.com!mudos!mju From: mju@mudos.ann-arbor.mi.us (Marc Unangst) Newsgroups: comp.sys.ibm.pc.misc,comp.os.msdos.programmer Subject: Re: 4DOS Aliases Keywords: 4DOS Message-ID: Date: 24 Jul 90 02:41:09 GMT References: <943@netmbx.UUCP> Organization: The Programmers' Pit Stop, Ann Arbor MI Lines: 27 cosheff@netmbx.UUCP (Charles Shefflette) writes: > 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. Well, J.P. Software may not consider it a bug, but I do. Things like alias passing should not be affected AT ALL by the swapping mode selected. The problem with using /S:B is that it will use disk swapping if EMS or XMS isn't available, meaning that 4DOS will take longer to start up, because it has to write the disk file. I *know* that I don't have EMS or XMS on this system, and sometimes I don't want to have to wait the few seconds if all I need to do is do a DIR A: or something. I use disk swapping now, because the 80K that the shell took up in memory-resident mode was just too much, but I still think it's a bug. -- Marc Unangst | "A foolish consistency is the hobgoblin of little mju@mudos.ann-arbor.mi.us | minds." ...!umich!leebai!mudos!mju | -- Samuel Johnson