Xref: utzoo comp.windows.ms.programmer:2170 comp.os.msdos.programmer:4975
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!sdd.hp.com!caen!kuhub.cc.ukans.edu!maverick.ksu.ksu.edu!matt.ksu.ksu.edu!rogerhef
From: rogerhef@matt.ksu.ksu.edu (Roger Heflin)
Newsgroups: comp.windows.ms.programmer,comp.os.msdos.programmer
Subject: Re: What to do about stdin, stdout, and stderr under Windows 3.0?
Keywords: Missing in action
Message-ID: <1991May1.180526.28683@maverick.ksu.ksu.edu>
Date: 1 May 91 18:05:26 GMT
References: <1991Apr30.162028.7771@sq.sq.com>
Sender: news@maverick.ksu.ksu.edu (The News Guru)
Organization: Kansas State University
Lines: 14
Nntp-Posting-Host: matt.ksu.ksu.edu

In <1991Apr30.162028.7771@sq.sq.com> dak@sq.sq.com (David A Keldsen) writes:

>On reading through the includes for the SDK, I see that std{in,out,err} are
>not supported under Windows.  While this isn't entirely surprising, what do
>you do to substitute for them?  (On Unix, I'd consider opening /dev/null,
>but there isn't one that I can find for DOS/MS-WINDOWS.)

I just tried it, it is not /dev/null it is /dev/nul under dos.


--
Rogerhef@Matt.ksu.ksu.edu                        Roger Heflin
                                                 EECE Grad Student
                                                 (913) 532-5600