On Mon, 28 Oct 2002, Lars Bjørndal wrote: > Bart Oldeman <[EMAIL PROTECTED]> writes: > > > On Sun, 27 Oct 2002, Lars Bjørndal wrote: > > > >> I've noticed that if I use dosemu-1.0.1, the mem-command gives, in the > >> line "largest executable program size" 617K, 1.1.3.5, the same command > >> and config gives 611K. Why, do you think? > > > This problem was caused by that thing that 1.1.3.5 will not use the > autoexec.emu. I've replaced it with autoexec.bat now, and then it's > ok. Why will not .emu work? > > My config.emu's last lines is: > > SHELL=C:\DOS\COMMAND.COM C:\DOS\ /e:1024 /p > > install=c:\subst.exe i: c:\ > install=c:\lredir.exe c: linux\fs/dos > > Witn dosemu-1.0.1, it is the autoexec.emu on the new drive c: that is > executed.
Well you can use SHELL=C:\DOS\COMMAND.COM C:\DOS\ /e:1024 /p /k C:\AUTOEMU.BAT and use AUTOEMU.BAT instead of AUTOEXEC.BAT. The problem with $_emubat, is that while it seems to work using some OS'es, some COMMAND.COM's and some types of AUTOEXEC.BAT it is really a hack and can be confusing. All kinds of weird things were possible such as: * command.com simply crashing DOSEMU (this is what the FreeDOS command.com did) * command.com executing autoexec.emu for the first half and autoexec.bat for the second half if the number of estimated "fakes" was not correct. * you doing "type autoexec.bat" and getting the contents of autoexec.emu. * potentially deleting or renaming the wrong file. $_emusys is a hack too, but it's more predictable what the DOS does (only one fake is needed) and it cannot be worked around so easily (only using bootmenu's and keystrokes or a separate boot directory). BTW if /K doesn't work you can use isemu.com in autoexec.bat: isemu if errorlevel 1 goto native_dos call autoemu.bat exit :native_dos Bart - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
