Mail Archives: opendos/2001/02/03/09:20:40.1
On 2001-02-02, Alan S. wrote:
> Ok, since 4DOS manages some level of integration with WinMe, I read the
> relevant 4DOS tech support page. It says to make NO changes to
> CONFIG.SYS or AUTOEXEC.BAT when using 4DOS.COM with WinMe ["WinMe will
> ignore/delete changes to CONFIG.SYS"]
Yes, but this is only true for the unmodified WinMe. As discussed earlier
(and I have to rely on other sources here), it is possible to reactivate the
normal DOS-only mode in WinMe, and then it should be possible to use
CONFIG.SYS/AUTOEXEC.BAT (with a few exceptions). Again, I donīt
use WinMe, so I havenīt tested this myself.
> [...] but when I moved/renamed [thanks to Matthias Paul for this suggestion]
> to C:\DRDOSCMD.COM, I was able to launch a DR-DOS 7.05 'DOS box'....
> BUT ONLY ONCE! [NOT repeatable...ARRRGHH!]
Very interesting behaviour... ;-)
Have you also tried the .EXE extension? Mind that (similar to MS-DOS 7.0+
COMMAND.COM) DR-DOS COMMAND.COM is actually an .EXE file,
not a true .COM file. Shouldnīt make a difference, but...
What happens if you start the shell with "/?" or "/C EXIT" or "/C DIR" or
"/K DIR" or "/P:" (including the colon) with or without /N (no critical error
handler), /D (no AUTOEXEC.BAT file) and possible other startup options.
One more thing to try: Instead of COMMAND.COM try the DR-DOS MEM
or CHOICE or XDIR (exactly the same way as you start COMMAND.COM),
just to see, if the problem is actually the shell, and not the DOS box.
> The failure mode in all cases is an empty DOS box [or full screen] with
> just a blinking cursor. [...]
Do you have a new "grace" launch after a reboot, or does the system
"remember" what you did in the last session?
In how far was your first launch successful? Do you got the DR-DOS prompt
and could for example run batchjobs or start applications. Did you kill
this session with EXIT, or by other means?
> I tried this only with the 7.05 COMMAND.COM [because it has integrated
> long file name processing].
???
Even the DR-DOS 7.02 COMMAND.COM has full LFN support built in.
Thatīs why I suggested to use the "offical" DR-DOS 7.03 COMMAND.COM
and not an OEM shell.
You should always keep in mind, that an OEM issue may be specifically
designed to fulfill special requirements by a particular OEM, and that these
may not always be appropriate for a general purpose or desktop OS. Also,
OEM issues could have been modified by the OEMs themselfs. There is no
DR-DOS 7.05 consumer release, unfortunately. The latest consumer version
is 7.03, still, and I suggest to use this instead of 7.05 whenever possible.
Matthias
------------------------------------------------------------
Matthias Paul, Ubierstrasse 28, D-50321 Bruehl, Germany
<Matthias DOT Paul AT post DOT rwth-aachen DOT de> <mpaul AT drdos DOT org>
http://www.rhrz.uni-bonn.de/~uzs180/mpdokeng.html
------------------------------------------------------------
- Raw text -