🚀 go-pugleaf

In article <26158@hydra.gatech.EDU>, go3@prism.gatech.EDU (OLIVE JR,GEORGE A) writes:
> 
> We are trying to use GlobalDosAlloc to allocate a block of memory to be
> shared by a Windows application and a DOS application which has been
> started using WinExec.  The following code shows the basic calls that
> we are using.  wDosSeg is the real mode segment which is being sent as
> a parameter to the DOS program.  hDos is a global memory handle which
> is created from the selector in the LOWORD of the value returned by
> GlobalDosAlloc and is used to access the memory from within Windows.
> Unfortunately, this doesn't seem to work.  Data written to the memory
> area pointed to by lpDos doesn't appear in the memory area wDosSeg:0000
> when read by the DOS application.  We would be extremely grateful to 
> anyone who can point out what we are doing wrong.

Sorry, but this is not going to work.  GlobalDOSAlloc only allocates memory
addressable in the Windows context.  This complete context is swapped
when you run a DOS application.  The name 'Global' in GlobalDOSAlloc is
misleading in this case.

So now you ask, how can memory be shared between a DOS application
and Windows.  The only way I know of is to write a TSR which is run
BEFORE Windows is started.  This TSR reserves the memory required
and passes the memory address via some private interface to either
Windows or DOS applications.

There is a DPMI call to allocate DOS memory in protected mode.
This is unlikely to succeed since Windows takes all the DOS memory
it can find.  Don't bother trying to use this.

Tony Gosling,
aka tonyg@microsoft

The above are my opinions only and may not agree with those of Microsoft.