Date:	Thu, 8 May 1997 11:04:12 -0400 (EDT)
From:	randir <goehrigd AT gort DOT canisius DOT edu>
To:	opendos-support AT delorie DOT com
Subject:	More on that Word 6.0c problem
Message-ID:	<Pine.SOL.3.91.970508104747.1002A-100000@gort.canisius.edu>
MIME-Version:	1.0

After a few "helpful" hints I think I've come to a disturbing conclusion:

Here is the autoexec.bat file I used for BOTH  MS-DOS 6.22 & OPENDOS 7.01

		path=c:\;c:\windows;c:\opendos

And that is it...

Here is the config.sys files that I tried...

		device=c:\opendos\himem.sys

that is one

		device=c:\opendos\emm386.exe MULTI DPMI=ONN FRAME=NONE

and one last one just to be sure:

		device=c:\windows\himem.sys
		decive=c:\emm386.exe [noems was a tag I tried also]

Now here was the verdict:

With MS-DOS all three configurations worked just fine.  There were no memory
problem, files going "read only", or anything.. even with the OD memory
manager.. (I did try loading DPMS but it didn't have any effect on the
MS-DOS versions..read on)

With OPENDOS none of the configurations worked.  In fact I got a chain of
error messages as I fixed one problem new ones would appear.  For example
the first error with any configuration with opendos was what:

	SHARE.EXE must be loaded to run WORD..

This was not at all necessary for MS-DOS, but I figured what the hell,
so I loaded OD's share.exe (cause you can't load MS-DOS's)
and then tried again.. this time I got the

	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..

So I tried every combination of DPMI on DPMI off MULTI on MULTI off..
and so on.. to no avail.. Now I loaded up DPMS & then it would actually
load word however, after two or three file accesses it would start
loading everything as READ-ONLY...

	Also it gave me "drive full or locked" or "too many files open"
	errors whenever I tried to open or save even more files.

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)...

	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.

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.

- Raw text -