Looking 4: I/P DOS Emulator

[Guest.Visitor]

In an attempt to get one communication protocol on our network. We're looking for an as/400 emulator that is DOS based and runs on an I/P configuration. It is my understanding that IBM no longer supports their Client Access for DOS. (We're trying to avoid having to put Win95 on PC's that are being used for simple connection to the 400). thanks, Mike

[J.Wells]

I thinks Mochasoft might have what you need (www.mochasoft.dk).

[Guest.Visitor]

On Wednesday, June 02, 1999, 02:29 PM, mike essig wrote: In an attempt to get one communication protocol on our network. We're looking for an as/400 emulator that is DOS based and runs on an I/P configuration. It is my understanding that IBM no longer supports their Client Access for DOS. (We're trying to avoid having to put Win95 on PC's that are being used for simple connection to the 400). thanks, Mike We use to buy real mode DOS TCP/IP drivers and the 5250 emulators from FTP software and Net Manage. These companies have merged and can be found at WWW.FTP.COM. I don't know if they still sell real mode dos but they did in 1994. Until 1996, I worked with TCP/IP on DOS computers. One problem with TCP/IP on DOS computers was that TCP/IP requires 50 to 70 kb of low memory ram. Another problem was that TCP/IP did not come with DOS, you had to purchase it from a 3rd party and pay a fee. I remember always fighting ram cram. Having to get DOS applications, network drivers and DOS to all fit in the 640kb of low memory. Usually, I could not do it with TCP/IP. Most of our DOS computers had to use a device to convert IPX or Netbeui to TCP/IP. These protocols used only 8 to 12kb of low memory. To communicate with the AS/400, we usually used SNA server to convert these protocols to SNA. You could use the MOCHA terminal emulator, but it requires you to install windows 3.11. When Windows 3.11 came out, it had virtual device drivers. These were loaded into high memory so the lower 640k could be used for DOS programs. However, virtual drivers only work when windows is loaded. If you quit windows and returned to DOS, the virtual device drivers quit working. Many "DOS" TCP/IP drivers were virtual drivers. It does not sound like this is what you want. You want real mode drivers that work with DOS. If all you want is a terminal consider an NC computer from IBM or a 5250 terminal that uses Ethernet and IP. Thats what we do. JHicks@SUZ.com