Xref: utzoo comp.sys.ibm.pc.misc:135 comp.os.msdos.programmer:161
Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!samsung!umich!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: <yN9km4w162w@mudos.ann-arbor.mi.us>
Date: 20 Jul 90 04:24:45 GMT
References: <1303@tuewsd.win.tue.nl>
Organization: The Programmers' Pit Stop, Ann Arbor MI
Lines: 26

wsinpp@lso.win.tue.nl (Peter Peters) writes:
> ->  shell=c:\system\4dos\4dos.com @c:\system\4dos\4dos.opt

Well, here's your first problem.  Most versions of MS-DOS don't read
past the 32nd character on the SHELL= line.  Are you getting an
error message when 4DOS starts up; like, maybe, "error opening
c:\syst"?

> ->  /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.  You can either load your aliases from 4START.BTM, or
you can switch to swapping mode.  EMS or XMS swapping is recommended
if you have it, but even disk swapping is better than none.

And I don't think the history is passed anyway, although I could be
wrong on this one.

--
   Marc Unangst    mju@mudos.ann-arbor.mi.us    ...!umich!leebai!mudos!mju