sgs@rand.mel.cocam.oz.au (Stuart Szabo) (03/25/91)
Does anyone know if there exists a set of clarkson packet drivers that will run under windows 3? Do you also need a specific telbin and ftpbin to run with windows 3 ? If so, where can I get a hold of these files. Thanks,
carroll@ssc-vax (Jeff Carroll) (03/26/91)
In article <205@rand.mel.cocam.oz.au> sgs@rand.mel.cocam.oz.au (Stuart Szabo) writes: > >Does anyone know if there exists a set of clarkson packet drivers >that will run under windows 3? Do you also need a specific telbin >and ftpbin to run with windows 3 ? If so, where can I get a hold >of these files. Do the "vanilla" packet drivers not work under Windows 3 for some reason? This could explain some problems that I have back-burnered as being more complicated than I have time to tackle right now... Mr. Nelson, would you care to clear this up for us packet driver novices? -- Jeff Carroll carroll@ssc-vax.boeing.com
nelson@sun.soe.clarkson.edu (Russ Nelson) (03/27/91)
In article <3748@ssc-bee.ssc-vax.UUCP> carroll@ssc-vax (Jeff Carroll) writes: In article <205@rand.mel.cocam.oz.au> sgs@rand.mel.cocam.oz.au (Stuart Szabo) writes: > >Does anyone know if there exists a set of clarkson packet drivers >that will run under windows 3? Do you also need a specific telbin >and ftpbin to run with windows 3 ? If so, where can I get a hold >of these files. Do the "vanilla" packet drivers not work under Windows 3 for some reason? This could explain some problems that I have back-burnered as being more complicated than I have time to tackle right now... The problem with Windows 3, in fact with any DOS 386 multitasker, is that you don't know what memory is mapped in at interrupt time. What the multitaskers do is remap interrupt controllers so that they use interrupts other than normal. Then they provide interrupt handlers that map the correct memory in. This lets you run a terminal emulator in one window and handle serial interrupts, yet still start up other DOS sessions. That's what happens if you run the packet driver in a window. Everything works, hunky-dory. But what happens if you want to run Novell at the same time? You have to run the packet driver *outside* of a window. But then when the packet driver receives an interrupt, and tries to hand the packet up to the TCP/IP stack (upcall), that DOS session isn't necessarily mapped in, and BOOM! The -w switch tries to avoid the BOOM part by ensuring that the same code that attached to the packet driver is also present during the upcall. The only real solution to using TCP/IP and Windows is to use a TCP/IP stack *written* for windows. -- --russ <nelson@clutx.clarkson.edu> I'm proud to be a humble Quaker. It's better to get mugged than to live a life of fear -- Freeman Dyson I joined the League for Programming Freedom, and I hope you'll join too.
luwsm@vax1.cc.lehigh.edu (03/27/91)
In article <NELSON.91Mar26195522@sun.clarkson.edu>, nelson@sun.soe.clarkson.edu (Russ Nelson) writes: > In article <3748@ssc-bee.ssc-vax.UUCP> carroll@ssc-vax (Jeff Carroll) writes: > > In article <205@rand.mel.cocam.oz.au> sgs@rand.mel.cocam.oz.au (Stuart Szabo) writes: > > > >Does anyone know if there exists a set of clarkson packet drivers > >that will run under windows 3? Do you also need a specific telbin > >and ftpbin to run with windows 3 ? If so, where can I get a hold > >of these files. > > Do the "vanilla" packet drivers not work under Windows 3 for some > reason? This could explain some problems that I have back-burnered as being > more complicated than I have time to tackle right now... > > The problem with Windows 3, in fact with any DOS 386 multitasker, is that > you don't know what memory is mapped in at interrupt time. What the > multitaskers do is remap interrupt controllers so that they use > interrupts other than normal. Then they provide interrupt handlers > that map the correct memory in. This lets you run a terminal emulator > in one window and handle serial interrupts, yet still start up other DOS > sessions. > > That's what happens if you run the packet driver in a window. > Everything works, hunky-dory. But what happens if you want to run > Novell at the same time? You have to run the packet driver *outside* > of a window. But then when the packet driver receives an interrupt, > and tries to hand the packet up to the TCP/IP stack (upcall), that DOS > session isn't necessarily mapped in, and BOOM! > > The -w switch tries to avoid the BOOM part by ensuring that the same code > that attached to the packet driver is also present during the upcall. > > The only real solution to using TCP/IP and Windows is to use a TCP/IP stack > *written* for windows. > > -- > --russ <nelson@clutx.clarkson.edu> I'm proud to be a humble Quaker. > It's better to get mugged than to live a life of fear -- Freeman Dyson > I joined the League for Programming Freedom, and I hope you'll join too.