Re: Guru help needed: How to do sockets in DOS

I really don't think so - if you come across an example, I'd like to see it.
Perhaps you mean the QuickWin library?

According to Wikipedia (not that it is always correct):

http://en.wikipedia.org/wiki/Win32_console

"In earlier versions of Windows, there were no native support for consoles.
To simplify the task of porting applications to Windows, Visual C++ was
supplied with QuickWin, a library that implemented basic console
functionality inside a regular Window. Since Windows 3.1 and earlier was
merely a graphical interface for MS-DOS, most text applications that ran on
earlier Windows versions were actually MS-DOS applications running in "DOS
boxes"."

And

http://en.wikipedia.org/wiki/QuickWin

"Since the release of Windows NT, Microsoft has included support for console
windows in the Windows operating system itself, eliminating the need for
QuickWin."


"Alexander Nickolov" <agnickolov@xxxxxxxx> wrote in message
news:%23j$ElhkuGHA.2036@xxxxxxxxxxxxxxxxxxxxxxx
Windows 3.1 did have console applications for sure. These
could not be run under plain DOS as they contained the DOS
stub stating they require Windows. Not sure when they have
been initially introduced (perhaps in Windows 3.0?). You can
check for yourself if you have VC 1.52 or earlier...

--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@xxxxxxxx
MVP VC FAQ: http://www.mvps.org/vcfaq
=====================================

"JJ" <jj@xxxxxxxxxx> wrote in message
news:uIHR18PuGHA.1272@xxxxxxxxxxxxxxxxxxxxxxx
It's been a while, but I didn't think there was such as thing as a
"console 16-bit application".

I thought "console applications" where not introduced until Windows NT.

I thought under 16-bit Windows, "console" applications were just DOS
programs.

Since Windows Sockets was implemented as a DLL (winsock.dll) and DOS
programs cannot use DLL's, there was not a standard way to use TCP/IP
functions under 16-bit Windows. You could use a 3rd party TCP/IP stack
that provided DOS libraries, but then the program was tied to that
stack - there was no similar DOS standard. Although I sort of recall
seeing some code that allowed DOS programs to use the Microsoft WfWG
TCP/IP stack.

"Alexander Nickolov" <agnickolov@xxxxxxxx> wrote in message
news:u3aRbkntGHA.452@xxxxxxxxxxxxxxxxxxxxxxx
Consider using Windows for Workgroups 3.11 and a console
16-bit application. This is _not_ DOS, but pretty close.
Otherwise you need to find a TCP stack for DOS and
program against it - DOS doesn't provide one. Now, I'm
not an expert on Win16 networking, I have some vague
recollection (which may be false), that WfW included a
TCP stack, whereas older Windows versions (3.1 and
previous) didn't. I'm sure others will correct me if I'm wrong.

--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@xxxxxxxx
MVP VC FAQ: http://www.mvps.org/vcfaq
=====================================

"DaleBert" <DaleBert@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0AF1F418-8EEC-4CEC-B0CE-EC3100FFFADB@xxxxxxxxxxxxxxxx
Hi,

Does anyone know how to do sockets in DOS? I have been assigned to save
a
16-bit DOS program that can't be updated. The customer wants me to make
a
static library that intercepts the I/O driver calls and send the data
out and
reads back over a TCP socket to a Windows host. Then the program will
then
run in a DOS box in a Windows machine (the host may or may not be on
the same
machine).

Sounds good in theory, but I have no idea how to do this and neither
does
anyone else around here. The code is set up to compile in Visual C++
1.52 and
uses several libraries that weren't brought over into the 32-bit world,
so it
would be hard to update. I tried to set up a simple example DOS program
using
WINSOCK functions, but it won't compile (probably because it is
including
files like windows.h in DOS).

I suppose I could use something other than TCP, but I am not sure what
would
be supported any better. I need synchronous and asynchronous sockets to
simulate both function calls and interrupts (or find a way to get the
host to
create real interrupts in the DOS box).

If anyone knows where you would go to get this kind of info, please let
me
know!
(This may be the wrong discussion group, but I couldn't find a DOS one)

Thanks,
Dale









.

Relevant Pages

  • Re: Linux syscalls
    ... > A device driver or a rewrite of DOS could permit this, ... really "DOS inside Windows" or "Windows inside DOS"? ... > DOS interrupts are revectored... ... if you re-write DOS to use the _Windows device drivers_ ...
    (alt.lang.asm)
  • Re: How To Determine if EXE is Windows 32-bit console application
    ... the .EXE is a 16-bit DOS program, ... and 7 for a Win 32 Console app. ... 4DOS can run only DOS programmes, and doesn't know what DOS extender is ... When I run a Windows 32-bit console application in plain ol' 4DOS, ...
    (comp.os.msdos.4dos)
  • [Full-Disclosure] ron1n phone home, episode 4
    ... Hacking from Windows 3.x, 95 and NT ... Use secret Windows 95 DOS commands to track down and port surf computers ... Download hacker tools such as port scanners and password crackers designed ... Now you have the option of eight TCP/IP utilities to play with: telnet, ...
    (Full-Disclosure)
  • Re: Terminal server client and old dos programs
    ... At the console it works in windowed and in full mode, ... The program dos not reference to any ini file on the client side. ... Since DOS doesn't see Windows Printers, ...
    (microsoft.public.windows.terminal_services)
  • Re: Detect mouse click and coordinates (C++)
    ... Early Windows was run from DOS. ... My understanding was that Windows now simulates DOS (console) for backward ... "Ron Francis" wrote: ...
    (microsoft.public.win32.programmer.ui)
Quantcast