Mail Archives: opendos/1997/05/12/02:24:54
Once upon a time (on 8 May 97 at 11:04) randir said:
> the first error with any configuration with opendos was what:
>
> SHARE.EXE must be loaded to run WORD..
[snip]
> There isn't enough memory to run WORD..
>
> Funny, I thought 16 megs + 8 megs of swap should be enough, especially since
> I loaded share High (or upper I tried both) and MS-DOS without any memory
> managers didn't have a problem..
[snip]
> Meanwhile it filled up what ever directory I was in with .tmp files for no
> adequately explained reason (autosave was off and it never got past pick a
> name any name stage)...
That's because Word *always* works on a temporary copy of a document.
> This leads me to believe that the file handling of OPENDOS
> both in the kernel & share.exe have some problems compounded
> by the preportedly buggy emm386.
Hmm.. not quite so - read on
> If the kernel was 100% MS-compatible it shouldn't NEED to load share.exe in
> the first place, and that is what is really the big problem here. Something
> ain't kosher.
If Micro$loth documented 100% of their code and dirty hacks they use, we
wouldn't have probelms at all. Novell DOS was based on many compatibility
guesses and "Undocumented..." series of books. But that's not an issue here.
The problem is that M$ uses dirty tricks to make their programs work smoothly
(oh, well...) with M$-DOG only. Win 3.11 (and I think you said you're using
this version) has a built-in SHARE support - VSHARE.386. That's why M$-FOG
doesn't need to install SHARE.EXE. But the fact that under OD VSHARE.386
isn't active, proves that some M$-FOG specific, dirty hack is being used to
make it work. Something ain't kosher, true - but in M$ products. Same applies
to memory management - emm386 from OD is surely buggy, and I recommend not to
use it unless you know how to make it work in your particular setup (and you
need to use MultiTasker software), but Windoze/Word problems with memory are
not caused directly by a memory manager software. The problem, again, lies in
the way M$-Windoze cooperates with M$-FOG - Windoze patches both M$-DOG
kernel memory management (if, and only if, M$-FOG is detected beyond any
doubt) as well as *M$* memory managers (again, *only* when run on M$-FOG!)
I think that explains the nature of the problem. Why other advanced
multitasking environments, like DeskView/X, run with no problems? 'Cause they
play fair!
----------------------------------------------------------
Doctor said my liver looks like living with my lover -
needs another time-out now. Like any sort of hero turning
down to zero, standing out in any crowd. [snip]
Dr. Finlay: And my advice is if you maintain this lifestyle
you won't reach 30...
----
- Raw text -