Xref: utzoo comp.protocols.tcp-ip.ibmpc:3709 comp.windows.ms:5060
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!usc!snorkelwacker!bloom-beacon!eru!hagbard!sunic!news.funet.fi!ousrvr!daemon
From: TKOP-ML@finou.oulu.fi (Mikko Laanti)
Newsgroups: comp.protocols.tcp-ip.ibmpc,comp.windows.ms
Subject: FTP Inc. TCP/IP and MS-Windows 3.0 in 386 enhanced mode
Message-ID: <90251.141244TKOP-ML@finou.oulu.fi>
Date: 8 Sep 90 11:15:23 GMT
Sender: daemon@ousrvr.oulu.fi
Organization: University of Oulu, Finland
Lines: 25


-------
I have made an interface for FTP Inc. TCP/IP, so that it will work in
Windows protected mode.  While everything works fine in 286 (WIN /2)
I have not managed to get the program to work in 386 mode (WIN /3).
The functional description of this Client/Server:

-  FTP's network is loaded in real mode
-  Our protected mode Windows application program copies
   needed data into real mode memory area
-  network interrupt is called through DPMI (simulating real mode
   interrupt
-  when the interrupt returns, data needed is copied into
   protected mode data segment

In 386 mode all goes fine until I try to send my first message
to server (network program solves addresses etc.).  Is there
any special I/O restrictions in DPMI ?

Any ideas ?

   Mikko Laanti

P.S. I applied same method to BTRIEVE (Novell Inc.) and it works
     well in both 286 and 386 mode.