I just don't know enough about the real (nitty-gritty) things with which Win$(9x) works; but here I have a question, Ben:
> All DOS apps have the ability to overwrite all but a very small part of > COMMAND.COM in the RAM; this is because COMMAND.COM is split into two parts, > the permanent part loaded by the OS at boot and the transient part (command > line, internal commands etc.). Isn't it so that the Win$-"DOSbox" is just some _arbitrary_ RAM/mem area designated for that purpose at that moment ? As far as I could make up from what I read (in certainly not highly precise and/or reliable writings) about it, opening a DOS-"box" in Win$ only seizes an area of RAM/mem (appropriate to DOS conditions) but that area is not (necessarily) the same as the "real" low memory area of the unit, and this is not congruent (maybe at best partly overlapping) with what you'd occupy with a "naked" DOS-booting. (I wouldn't konw how it's done but one thing could be simply remapping mem-addresses.) (At least there are some indications for this in the circumstance that you cannot "get at" some of the "real" low-mem addresses when using a DOSbox. Or it would explain why memory managers like QUEMM wouldn't work in such a DOS-"box".) Or am I completely wrong here ? If not, then the conclusion is quite simple - there _has_ to be the command.com shell to be reloaded each time. -heimo
