Windows 3.11 and TCP/IP
MalcolmCox
several motors and data aquisition subsystems.
The main program is written in Dos QBasic 7.0, with liberal chunks of
assembler for the quick stuff. This ONLY just fits inside Dos memory.
When customers demanded windows and network interconnect, we supplied Win
3.11 and Alt/Tabbed between DOS and Windows (was it real mode or standard?,
I cant remember) Win 95,98 cannot do that, so we are stuck with Win 3.11.
Now we are under a lot of pressure to support TCP/IP protocol, but I am
told that Win3.11 can ONLY handle Netbui.
Not always believing the first quick anser I get, I am seeking a second
opinion.
Does anyone know of ANY available product we can use to get Win 3.11 to
talk TCP/IP?
Malcolm
Thomas Buchner
wrote:
>
>
>Now we are under a lot of pressure to support TCP/IP protocol, but I am
>told that Win3.11 can ONLY handle Netbui.
>Not always believing the first quick anser I get, I am seeking a second
>opinion.
>
>Does anyone know of ANY available product we can use to get Win 3.11 to
>talk TCP/IP?
>Malcolm
>
>
>
Look for this:
TCP32B.EXE: TCP/IP-32 v. 3.11b for Windows for Workgroups
Microsoft TCP/IP-32 version 3.11b for Windows for Workgroups is
a 32-bit TCP/IP network protocol for Windows for
Workgroups only. ...
URL: support.microsoft.com/support/downloads/dp1096.asp
Hope this helps
--
Thomas Buchner
Lucent Technologies Network Systems
Deutschland GmbH
Thurn-und-Taxis-Strasse 10
90411 Nuernberg
Germany
mailto:tbuc...@lucent.com
Zorallin
Follow the link
http://www.stardust.com/cgi-bin/wsdir/display_holding.pl?category920
If it's broken just go to
Cheers
-------------------------------------------------------------------
"If you think you know the answer,
then you don't understand the question !"
-------------------------------------------------------------------
MalcolmCox <mal...@napanet.net> wrote in message
news:3BOo4.1642$Zh4.1...@newshog.newsread.com...
> We make a machine, which uses a current desktop motherboard, controls
> several motors and data aquisition subsystems.
> The main program is written in Dos QBasic 7.0, with liberal chunks of
> assembler for the quick stuff. This ONLY just fits inside Dos memory.
> When customers demanded windows and network interconnect, we supplied Win
> 3.11 and Alt/Tabbed between DOS and Windows (was it real mode or
standard?,
> I cant remember) Win 95,98 cannot do that, so we are stuck with Win 3.11.
>
David Brown
MS (if you cannot find the latest version on MS website, I may have an old
copy I could send you). Alternatively, get hold of a web browser (old
Netscape, IE, Opera, or whatever) - the Win16 versions invariably had their
own TCP/IP stack in the distribution, since it does not come as standard.
Of course, far and away the best system for running DOS programs is OS/2.
When I ran Warp 3 (before I started having to run Win32 programs), I ran DOS
programs in a DOS box with 768k conventional memory. I ran DOS-based
compilers and emulators up to 50% faster than in pure DOS 6.2 on the same
machine. The DOS sessions were multi-tasked far more efficiently and
smoothly than under Win NT (I need hardly mention the drivel known as
Win9x). And of course OS/2 has TCP/IP built-in, and runs anything Win3.11
runs, only better.
As another alternative, have you thought of DOSEmu under Linux? I don't
know how well this might work, but it would solve the TCP/IP problems.
It may also be possible to get TCP/IP access for DOS, if you search hard
enough. I believe there are a few DOS-based web browers available (possibly
a port of Linx, the UNIX text-based browser), so they must have TCP/IP
support.
MalcolmCox wrote in message <3BOo4.1642$Zh4.1...@newshog.newsread.com>...
Thomas Buchner
wrote:
If its only for DOS and networking, search the web for Caldera, I
think they have overtaken DR DOS, it should support networking also.
I recently saw it on:
http://archive.nat.bg/pub/systems/dos/Caldera%20DOS/
Mark D'Sylva
MalcolmCox wrote:
> We make a machine, which uses a current desktop motherboard, controls
> several motors and data aquisition subsystems.
> The main program is written in Dos QBasic 7.0, with liberal chunks of
> assembler for the quick stuff. This ONLY just fits inside Dos memory.
> When customers demanded windows and network interconnect, we supplied Win
> 3.11 and Alt/Tabbed between DOS and Windows (was it real mode or standard?,
> I cant remember) Win 95,98 cannot do that, so we are stuck with Win 3.11.
>
> Now we are under a lot of pressure to support TCP/IP protocol, but I am
> told that Win3.11 can ONLY handle Netbui.
> Not always believing the first quick anser I get, I am seeking a second
> opinion.
>
> Does anyone know of ANY available product we can use to get Win 3.11 to
> talk TCP/IP?
> Malcolm
Malcolm,
you may find a solution from "Trumpet" here's the URL:
http://www.trumpet.com/products.html
Mark D'Sylva
Steve Goodwin
<mds...@interlog.com> writes
>
>
>MalcolmCox wrote:
>
>> We make a machine, which uses a current desktop motherboard, controls
>>
>> Now we are under a lot of pressure to support TCP/IP protocol, but I am
>> told that Win3.11 can ONLY handle Netbui.
>> Not always believing the first quick anser I get, I am seeking a second
>> opinion.
>>
>> Does anyone know of ANY available product we can use to get Win 3.11 to
>> talk TCP/IP?
>> Malcolm
>
>Malcolm,
> you may find a solution from "Trumpet" here's the URL:
>http://www.trumpet.com/products.html
>
>Mark D'Sylva
>
MS do/did a 32 bit TCP/IP stack for (at least) WfWg 3.11 providing a
WinSock interface. Sorry, can't remember the file name or URL but note
there was also an earlier TCP/IP stack for the same platforms which was
not 32. IIRC, I would not use the earlier one.
However, are you implying that you need access to TCP/IP from DOS. If
so, you may have problems because I would guess that you will need a DOS
stack such as that from FTP Software who also supply an SDK to allow you
to integrate socket access into your code. (Much memory needed IIRC).
Finally you could look for WatTCP (or is it WaTCP), Waterloo TCP, source
code available on the net I believe and maybe a book?. I had trouble
with it when multi-tasking under DOS but that was probably me and I have
seen many people refer to using it. You should find something via
Altavista or deja I guess.
HTH
--
Steve Goodwin... De-spamming active, remove any _DSPM from address
Michael Ellis
> The main program is written in Dos QBasic 7.0, with liberal chunks of
> assembler for the quick stuff. This ONLY just fits inside Dos memory.
> When customers demanded windows and network interconnect, we supplied Win
> 3.11 and Alt/Tabbed between DOS and Windows (was it real mode or
standard?,
> I cant remember) Win 95,98 cannot do that, so we are stuck with Win 3.11.
>
> told that Win3.11 can ONLY handle Netbui.
> Not always believing the first quick anser I get, I am seeking a second
> opinion.
>
> Does anyone know of ANY available product we can use to get Win 3.11 to
> talk TCP/IP?
Three answers:
1) WfW 3.11 supports the TCP/IP protocol. Look for tcp32b.exe for this
protocol.
2) MSDOS supports TCP/IP using the Microsoft Network Client for DOS (no
Windows required). This will provide client access to other servers but
your DOS machine cannot publish network resources (can't act as a server).
You seem to indicate that your existing application uses all the available
memory, so this may not work in your particular application.
3) Win95/98 allows you to run a DOS session and <alt-tab> between the
desktop, the DOS box, or any other application that you have running. How
well the DOS application runs under Win95/98 depends on what the application
does and how well behaved it is. Some DOS apps work well under Win95/98,
others fail miserably.
AFAIK both (1) and (2) are available at no charge from MS for anyone who
owns the appropriate OS (WfW or DOS).
--
Michael Ellis
first initial last name at pesa commercial domain