xeee02@mixcom.UUCP (Dean A. Roth) (08/31/90)
I would like to hear your experience using DesqView 386 (a 386 running in virtual 386 mode) and FTP Software's 2.x kernel. I am looking to determine the optimum configuration. I have tried running the kernel outside of Desqview and within a window. The former resulted in Desqview blowing up with exception 13. (I'm not pointing fingers at any product. I'm just saying something didn't work that way.) The latter has worked so far, but limits TCP/IP access to one window/process. (The version of the documents I have do not say anything about using the kernel with Desqview.) Thank you. Dean deanr@mixcom.uucp deanr%mixcom@uunet.uu.net
PIRARD%vm1.ulg.ac.be@CUNYVM.CUNY.EDU (Andr'e PIRARD) (09/03/90)
On Fri, 31 Aug 90 14:09:58 GMT Dean A. Roth said: >I would like to hear your experience using DesqView 386 >(a 386 running in virtual 386 mode) and FTP Software's >2.x kernel. I am looking to determine the optimum configuration. > >I have tried running the kernel outside of Desqview and within >a window. The former resulted in Desqview blowing up with >exception 13. (I'm not pointing fingers at any product. I'm >just saying something didn't work that way.) The latter has >worked so far, but limits TCP/IP access to one window/process. As a general rule, you *must* load the program grabbing the communication card interrupt *inside* the DESQview application. I. e. packet driver or/and FTP's kernel. Andr'e PIRARD SEGI, Univ. de Li`ege B26 - Sart Tilman B-4000 Li`ege 1 (Belgium) pirard@vm1.ulg.ac.be or PIRARD@BLIULG11 on EARN/BITNET