Mail Archives: opendos/1997/05/25/05:48:16
I have several observatons, wishs and questions about
Novell/OpenDos including interaction with MS-Windows (WFW 3.11)
and QEMM (I tested QEMM 7.51).
1. Some configuratons of CONFIG.SYS with QEMM makes UMBs
visible for QDK LOADHI.COM and MFT but not for DOS (MEM, HILOAD
etc). At result, then that is impossible some with
QDK LOADHI high-loaded programs (e.g. Norton Commander) to
normally unload (interrupts restore, but memory not releases).
If UMBs are visible for DOS utilities they can become invisible
after starting of WFW 3.11 with MS network drivers (and not
restore after exit Windows). To prevent this effect, CONFIG.SYS
for some reason must have a line HISTORY=ON,... But why?
2. I found a serios conflict between NWCache (all updates of
NW7 and OD7.01) and Norton Commander 4.0. If DPMS not loaded and
NWcache loaded then a trying to set at one panel of NC a floppy
disk and at the another Info (^L) causes non-normal NC behavior
and system crash. I found this interacton between NC 4.0 and
all these NWcache also under MS-DOS 6.22 but never under DRDOS
6.0. I think, this "compability with MS-DOS" is not useful!!!
3. QEMM cannot optimize OD 7.01 (release conv. memory) equal
good as NW7. CONFIG.SYS created with QDK OPTIMIZE under NW7 may
work under OD7.01 but free memory is less. Therefore a best
solution for today is Novell update 15 on OpenDOS and copying
OPENDOS.INI to NWDOS.INI. But why?
4. Some full-screen DOS utilities work not normally without /N
switch. E.G. I cannot use mouse with UNDELETE (mouse cursor
moving area is invalid). My be, it is a bug of the mouse driver
(LCS/Telegraphics IMOUSE.COM 8.20h) or video card
(CL-GD54M30/5440)?
5. DRDOS6/NWDOS7/OpenDOS do not support MS-DOS multi-config
syntax. Yes, all these OSs have another features instead ("?",
SWITCH, GOTO, GOSUB/RETURN...) but all these features are
unknown for QEMM OPTIMIZE (and GOSUB and CHAIN not only not
responsible but cause errors while optimizing). That may also
make some problem if everybody installs OpenDOS over MS-DOS and
wishs use old system configuration.
6 LOADHIGH not supports MS-DOS switches (/R etc). But these are
essential for using MS-DOS .BAT files (even though as
non-functional "dummies").
7. IF WFW 3.11 32-bit disk access is on, after exiting from
Windows all current directories on all drives always become root
even if I started Windows with other current directory.
8. TIMEOUT statement in CONFIG.SYS works also with all (not
only "?") next CONFIG.SYS commands if F8 boot trapping and
"automatically" sets "N". That is not any serios problem, but
not always convenient.
9. What and why is a MS-Windows driver, NW/OPENDOS.386?
BUT I USE THIS DOS because it has: 1. A good system for
undeleting of erased files and directories (preserves first
letter); 2. Very beautiful CONFIG.SYS syntax; 3. Runs very safely
(only DR DOS 6 was more safely but it was not compatible with WFW
VSERVER.386 and some other programs); 4. Good understands QEMM
UMBs if those are "visible" (then I can without any problem use
HIDEVICE and HILOAD instead LOADHI.SYS and LOADHI.COM, this
makes my CONFIG and AUTOEXEC very simpler if I use
multi-configuration with or without QEMM); 5. "honest"
CONFIG.SYS line-by-line executing (unlike MS-DOS!!!);
6. Good interactive memory management utility, MEMMAX (partial
compatible with QEMM) that solves some conflicts between
applications.
--
Pavel V. Ozerski | Inst. of Evolutionary Physiology & Biochemistry,
office +7 (812)552-6870(291)| Russian Academy of Sciences,
FAX +7 (812)552-3012 | Thorez pr. 44, St.Petersburg, 194223, Russia
home +7 (812)528-5576 | E-mail: pavel AT insect DOT ief DOT spb DOT su
- Raw text -