HDTenEightyP/NetNews huggingface dataset:
From: shanny@snake20.cs.wisc.edu (Nicholas Shanny)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: sockets
Date: 5 Nov 92 15:19:39 GMT
Article-I.D.: daffy.1992Nov5.151939.1880
Distribution: usa
Organization: U of Wisconsin CS Dept

Hello,

I am in the process of trying to get a simple socket program to work
under NT, character mode. (i.e. not as a WINDOWS program ) The same
software worked fine under unix, but I receive an error when the sender
attempts to do a 'sendto'. The error number is 10022. The receiver
works fine and if I run netstat -a , the server is seen with the
correct port number. Has anyone else been able to get sockets working
under NT?

Nick Shanny
shanny@bc.cs.wisc.edu
Newsgroups: comp.os.ms-windows.programmer.win32
From: brad@huey.Jpl.Nasa.GOV (Brad Hines)
Subject: Re: Device Driver Questions
Reply-To: brad@huey.Jpl.Nasa.GOV
Organization: JPL Spatial Interferometry Group
Date: Sat, 7 Nov 1992 04:18:07 GMT

>In article <1992Nov05.222315.29019@bnr.ca>, ctjones@bnr.ca (Clifton Jones) writes:

>When I start NT, the printer never sends data. It seems to be waiting forever.
>(I think that its looking on IRQ7.)
>The soundblaster driver will not install on IRQ7 because it says its already
>in use.  (Thats why I think that the print driver is on IRQ7).
>
>This setup is a result of soundblaster needing IRQ7 for historical
>compatibility.  This setup works for SCO Unix, MSDOS 5.0, OS/2 2.0.

I had the same problem.  The problem is that LPT1 uses IRQ7, and so does
the Soundblaster.  I'm not sure why NT cares about this when other
multitasking environments don't (for robustness, I guess?), but you
need to change one of the devices to make things work.

At first, I changed the Soundblaster to IRQ5 (normally used by LPT2),
but, for the historical reasons you mentioned, that wasn't so great.

So I changed my parallel port card to be LPT2 (changed it to be
what the card refers to as LPTB, and changed it from IRQ7 to IRQ5).
That made everything work great.  Now the soundblaster is happy and so
is printing under NT (you have to use print manager to reconfigure your
printer to be on LPT2 instead of LPT1).

When you go back to DOS, however, LPT2 exists but is not the default
printer (that is, the PRN device does not refer to LPT2).  So, the first
time you run the print command, when it asks "Output device [PRN]:" or
some similar thing, you should answer "LPT2".  Then printing will be fine
from then on.  Alternatively, use "print /D:LPT2" the first time you run
print.  I have added the line "loadhi print /D:LPT2" to my autoexec.bat
file to load the TSR portion of print and initialize it to LPT2 at boot
time.

Of course, if you are already using LPT2 in your system, then none of this will
work.

[BTW, this message is being sent by both email and by netnews, since you
asked for it by mail but others might find this useful.]

-- 
Brad Hines
Internet: brad@huey.jpl.nasa.gov
Jet Propulsion Lab, Pasadena, California
Newsgroups: comp.os.ms-windows.programmer.win32
From: mo@gizmo.bellcore.com (Michael O'Dell)
Subject: Problems loading Word for Windows 2 under NT
Keywords: 
 
Reply-To: mo@bellcore.com
Organization: Center for Chaotic Repeatabilty
Date: Tue, 10 Nov 92 20:15:07 GMT

thought i'd install word for windows v2 on my nt system
so i could look at .doc files and print them readily.

well, i launched a:install from the first diskette
and it whirred away just fine until just after starting
the last diskette.  then everything stopped.  i could
use the dask switch to switch to other jobs, but
the installer seem to have croaked, taking the 
floppy with it. when i tried to "dir" the floppy
from a newly-launched file manager, touching
the floppy drive was the kiss-o-death for that
copy of the file manager.

the weird part is that even after gunning down the
errant processes from the task list, the DOS windows from
which I had launched the a:install STAYED BEHIND no matter what!
Nothing about it worked except the title bar
which would highlight, but couldn't be dragged or anything.
more amazingly, after logging out, when i logged-in again,
the undead window frame came back!

at that point i rebooted.  clearly the installer died
in such a way that the win32 window server didn't hear
about it and hence kept updating the decorations on the
base window. this would seem to be a serious bug.

at any rate, has anyone successfully installed WinWord2 under
NT, and then did it run reliably after you did?? I tried
running it and got all sorts of angry dialog boxes about
how I killed the Win16 subsystem, etc, etc.

not very nice, i'twasn't atall.

anyone within a lightyear of a clue on this??

	-mo

Bellcore?? Bellcore isn't allowed opinions.  Any seen here
are purely accidental.

Newsgroups: comp.os.ms-windows.programmer.win32
From: alistair@microsoft.com (Alistair Banks)
Subject: Re: DLC Transport and Driver
Date: 09 Nov 92 07:13:15 GMT
Organization: Microsoft Corporation

In article <Bx7Dqv.40A@unx.sas.com> sasdxk@skyhawk.unx.sas.com (Dave Kolb) writes:
>
>When I go to control panel/advanced/configure software to setup TCP/IP,
>one of the "network sotware" choices is "DLC transport and drivers".
>
>I guess I know what it is in general but who needs it as it was not
>already selected.  Does TCP/IP need it? 

No, tcp/ip does not need dlc - dlc is used by various SNA transports

-- Alistair
From: wintert@wl.com (Tom Winters)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Excluding areas of memory in NT
Date: 9 Nov 92 20:27:23 GMT
Article-I.D.: wl.1992Nov9.202723.1187
Organization: Warner Lambert / Parke-Davis

I have managed to install the Oct release of the Windows/NT SDK on my Everex
Step 386/20, with 8 Meg of memory.  Things seem to be working overall pretty
well except for my Network installation. That however is to be expected since
I am running Lantastic NOS 4.1, on their early AE-2 ethernet boards.  I don't
wish to change my LAN over to LanManager at the momment, but I would like
to be able to access my other Peers on the network, if nothing else via the
MSDOS command line interface. The problem is I can't load my NetBios onto the 
card as I would under regular MSDOS.  When I attempt to do so the LANBIOS pro
program indicates that there is no card at the address normal for the card.  
Again thats no problem as this happened also under WINDOWS 3.1 untill I told
it to exclude - EMMexclude=D000-DFFF under the [386enh] section of the 
system.ini file.  As far as I can acertain Windows/NT doesn't allow this sort
of behavior. 

I have taken a look at the REGEDIT program and the registration database is
quite meaningless to me without any detailed DOCS, Any Idea where they are 
located on the CD? 

So far my experences have been pretty good with this release.  It seems to 
run much of my software pretty well, including quite a lot of Windows 3.0 and
Windows 3.1 shareware.  I have also found that if I replace the HIMEM.SYS  
driver that comes with Windows/NT with the one shipped with Windows 3.1 (the
version number is later) I am able to run quite a few very old MSDOS programs 
that wouldn't work with the Windows/NT version of HIMEM.SYS.  Unfortunately 
this results in not being able to load WOWEXEC.EXE.  So I have switched back
to the NT version.

I would welcome any comments anyone might have in how to solve the problem I 
am having with the Lantastic Adapter card.  I can see that this might also be a
problem for someone else that might be running Data acquisition hardware that 
might also map some of its memory into the systems address space.

Tom. 
Newsgroups: comp.os.ms-windows.programmer.win32
From: sjr@dartac.demon.co.uk (Simon Roberts)
ReplyTo: sjr@dartac.demon.co.uk
Subject: Re: Getting DOS TCP/IP software to work with NT
Distribution: world
X-Mailer: cppnews $Revision: 1.19 $
Organization: Dartacross Limited
Date: Wed, 11 Nov 1992 11:18:07 +0000


In article <1992Nov09.073534.14267@microsoft.com> alistair@microsoft.com
(Alistair Banks) writes:

> Windows NT includes netbeui & tcp/ip trasnports - We've demoed
> most SNA transports on Windows NT now, also appletalk. DEC are
> working on DECNet, and various vendors are starting OSI work.

Interesting. However, it would be good to see an ISO TC0,2,4 transport
bundled with NT.

Is there an XTI or TLI type transport interface as well as the socket
interface?

Simon

--
Simon Roberts
Dartacross Limited - Open Systems Consultancy
sjr@dartac.demon.co.uk (preferred)
sjr@cix.compulink.co.uk
Newsgroups: comp.os.ms-windows.programmer.win32
From: johnhall@microsoft.com (John Hall)
Subject: Re: OS/2 to NT port question
Date: 06 Nov 92 01:29:42 GMT
Organization: Microsoft Corporation


I've done so -- and I plan on uploading the source code before next
Tuesday.  I wasn't faithful to the OS/2 syntax because it looked
really strange.  Mine should be easier to use.

It sits on top of shrmem.

I was going to post this to compuserve along with other updates
on all my OS/2 -> Windows NT porting tools.  Do you want it on
the ftp server, too?

In article <2615@cronos.metaphor.com> eli@Metaphor.COM (Eli Lauris) writes:
| 
| Does anyone know how to port OS/2 queuing calls (DosCreateQueue, DosOpenQueue, DosWriteQueue, DosReadQueue, DosPeakQueue) to NT ?
| 
| Thanks,
| 
| Eli
| 


-- 
-------------------------
My comments are my own.  They are independent and unrelated to the
views of my company , relatives or elected representatives.
From: joiner@pico.cs.umn.edu (Jay K. Joiner)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: Problems loading Word for Windows 2 under NT
Date: 11 Nov 92 16:31:16 GMT
Article-I.D.: pico.joiner.721499476
Organization: University of Minnesota

I also tried to install WfW 2.0 from diskette under NT with no
success.  My symptom was the system doing essentially a no-op
when running A:SETUP from either the Program Manager or an
MS-DOS prompt.  I even tried running the Win16 "executive" from
the command line before trying SETUP.
Newsgroups: comp.os.ms-windows.programmer.win32
From: tpradeep@cs.tamu.edu (Pradeep K Tapadiya)
Subject: How to reinstall flexboot? Help
Organization: Computer Science Department, Texas A&M University
Distribution: usa
Date: Mon, 9 Nov 1992 15:58:03 GMT


Howdy netters,

Because of some unrecoverable errors, I had to reformat my c-drive.
Now flexboot doen't exist on my drive. Is there a way to 
reinstall just the flexboot part without reinstalling the whole NT
system again?

Thank you for your help.

Pradeep
tpradeep@cs.tamu.edu
Newsgroups: comp.os.ms-windows.programmer.win32
From: beame@maccs.dcss.mcmaster.ca (Carl Beame)
Subject: Re: DuplicateHandle -- passing handles to other processes
Organization: McMaster University, Hamilton, Ontario, Canada.
Date: Tue, 10 Nov 1992 06:04:32 GMT

|> Forgive me if this has already been answered ... but ...
|>
|> I am trying to pass a handle to a named pipe to a process which I have just
|> created. After reading the docs :-), I called DuplicateHandle with
|> the GetCurrentProcess() as the source process handle, the handle returned
|> to me from the create process call as the destination handle and
|> the pipe as the handle to duplicate. The call returned TRUE and filled in
|> the new handle ... I passed this new handle to the new process via another
|> named pipe ... Using the new handle in the created proceedure fails.
|>
|> Help ... What am I doing wrong ... (if anything :-) ).
|>
|> - Carl Beame
|> beame@bws.com
>
>Post your code fragment.  I've coded this but not tested it yet.
>-- 
>Dave Kolb                     Opinions are mine not SAS'

Well here is the code fragment. This code tries to pass the handle 
"Remote" to the created process. The interprocess communication does work and
the duplicated handle value is correctly passed to the new process, but when
the handle is used in the new process it fails:

{
	STARTUPINFO  sui;
	PROCESS_INFORMATION pi;
	HANDLE	Local,Remote,newh;
	char	my_pipe[40];
	int	ret;

/* Remote is handle to pass */
	Remote = CreateFile("\\\\.\\PIPE\\somepipe", GENERIC_WRITE, 0, NULL, 
			OPEN_EXISTING, FILE_ATTRIBUTE_NORMAL, NULL);
/* Create unique name pipe for this process */
	wsprintf(my_pipe,"\\\\.\\PIPE\\myipipe%d",Remote);
	Local = CreateNamedPipe (my_pipe, 
       	       PIPE_ACCESS_OUTBOUND               // 1 way pipe.
       	       | FILE_FLAG_WRITE_THROUGH,        // Use write through.
	       PIPE_WAIT                         // Wait on messages.
               | PIPE_TYPE_BYTE,
               PIPE_UNLIMITED_INSTANCES,         // Unlimited instance limit.
               0,                                // Buffer sizes.
               0,
               5000,                         // Specify time out.
               NULL);                            // No securities specified.


	memset(&sui,0,sizeof(sui));
	sui.cb=sizeof(sui);
	sui.wShowWindow=SW_SHOWMINNOACTIVE;

/* command_line contains the program to run and the string my_pipe to get
   the passed handle from. */

	CreateProcess(NULL,command_line,NULL,NULL,TRUE,DETACHED_PROCESS,
			NULL,NULL,&sui,&pi));
	ConnectNamedPipe(Local, NULL);
	DuplicateHandle(GetCurrentProcess(),Remote,pi.hProcess,&newh,
		GENERIC_READ,TRUE,DUPLICATE_SAME_ACCESS);
	WriteFile(Local,&newh,sizeof(HANDLE),&ret,NULL);
	CloseHandle(pi.hProcess);
	CloseHandle(pi.hThread);
	CloseHandle(Local);
	DisconnectNamedPipe(Local);
}

- Carl Beame
Newsgroups: comp.os.ms-windows.programmer.win32
From: francis@csli.stanford.edu (Straw Man Dude)
Subject: Windows NT beta or info
Organization: CSLI, Stanford University
Date: Wed, 11 Nov 1992 01:38:15 GMT

I would like to get some information on how to become a Windows NT
beta site or get some detailed information on the software library
support the operating system provides.

If anyone can help please mail me at
francis@csli.stanford.edu

Thank you,
dave francis
From: fenwick@hpcupt1.cup.hp.com (John Fenwick)
Date: Wed, 11 Nov 1992 00:00:19 GMT
Subject: Re: Logitech
Organization: Hewlett-Packard, Cupertino
Newsgroups: comp.os.ms-windows.programmer.win32

Same problem - can't get Logitech mouse to work at all.

I heard a rumor that Microsoft has removed from NT all support 
for either mouse or soundboard that is not a Microsoft product.
Any comments anyone?
Newsgroups: comp.os.ms-windows.programmer.win32
From: strobl@gmd.de (Wolfgang Strobl)
Subject: Re: LINK: out of memory
Organization: GMD, Sankt Augustin, Germany
Distribution: comp
Date: Thu, 12 Nov 1992 08:35:29 GMT

In <SINYAW.92Nov11223705@starbright.smsc.sony.com> sinyaw@starbright.smsc.sony.com (Sin-Yaw Wang) writes:


>I attepmted to link a simple MFC based program, not very far from "hello"
>from the MFC samples directory, under Win32/SDK.  I have debug options all
>turned on and linked to the debug version of the librareis (e.g.
>safxcwd.lib).

>I did it on a DOS-PROMPT window, with "nmake".   The linker refused to
>link, complaining "out of memory".

>It is a 486DX/33 with 16MB of memory I was using.

>Any insight, anybody?

My experience (on a similar machine, using the July PDK) is that
this error is most probably the result of having the DOS and/or
Win16 subsystem started, due to some prior use of a non-NT program
during the current session (==login). 

Because of that, I avoid using non-NT programs during development
sessions.  I only suffer from spurious "out of memory" errors 
from the "cvpack" (or some similar name, my machine is at home) utility.
That's the last step, after the link step. 

If I get that error, I simply apply the utility to the newly created
.exe file again, manually.

Wolfgang Strobl
#include <std.disclaimer.hpp>
Newsgroups: comp.os.ms-windows.programmer.win32
From: alistair@microsoft.com (Alistair Banks)
Subject: Re: Lanman 2.1 with Starlan 3.4
Date: 06 Nov 92 02:56:26 GMT
Organization: Microsoft Corporation

In article <JONES.92Nov4001815@sadye.uvm.edu> jones@sadye.uvm.edu (Mike Jones) writes:
>
>I haven't been able to get my netcard configured, so I can't answer
>this question for myself.
>
>Does anybody know.... does Lanman 2.1 (supplied with NT) work with
>AT&T's Starlan 3.4 package ?

Ughmmmm - Its somewhat more than LanMan 2.1 in Windows NT, but disregarding
that, Windows NT using its tcp/ip transport should indeed interoperate
with AT&T's Starlan, with its tcp/ip transport -- Alistair
From: potts@oit.itd.umich.edu (Paul Potts)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: Any known problems with Borland C++ 3.1 / Windows NT
Date: 11 Nov 1992 20:53:10 GMT
Organization: Instructional Technology Laboratory, University of Michigan
NNTP-Posting-Host: helen.oit.itd.umich.edu

In article <19122@ucdavis.ucdavis.edu> hughes@madrone.eecs.ucdavis.edu (S. Hughes) writes:
>I too am unable to run the Borland C++ IDE.  It seems NT is convinced
>that it is an OS/2 program.  Anybody know how to tell NT to execute as
>DOS??

Apparently the DOS IDE will not run. A Borland person told me that I should
try to create a makefile and use the command-line compiler if I want to
use Borland C++ under NT, but I was unable to get that to work either.
"MAKE" crashes my machine; so does the "EMSTEST" executable. PIF settings
don't seem to help.

I'm pretty irritated by this; I realize this is only the first beta, but
one would think that Microsoft would have tested BC++ with NT. I realize
that Borland is a competitor, but an OS that doesn't support competitor's
software just won't fly. Borland C++ is simply a more usable environment
for what I'm doing; besides, I need the TurboVision library for C++. Not
what I'd be using for pleasure, ideally, but when you're developing something
that has to run on a 640K DOS machine there isn't much pleasure in your life.
I was hoping to use NT as a crash-barrier for testing the app as I work on it,
otherwise every crash causes a painful reboot.

BTW, NT also doesn't know that "BC.EXE" (the Basic Compiler for Visual BASIC
for DOS) is not the same as "BC.EXE" (The Borland C++ 3.1 DOS IDE). They
are both put into the applications group with the same icon. So it doesn't
look like they are even testing NT internally with their own software...



-- 
"What good is a computerized nose?" - Lou Reed - potts@oit.itd.umich.edu
From: max@underg.ucf.org (Max Cray)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: SLIP/PPP Software
Date: Sat, 07 Nov 92 01:27:25 CST
Organization: Underground Computing Foundation

Anybody working on SLIP or PPP software for Windows NT? If so, please
send me mail. Thanks.

                                          -= Max =-

---------------------------------------------------------------------
 I try to be my own moderator...
Newsgroups: comp.os.ms-windows.programmer.win32
From: joiner@myria.cs.umn.edu (Jay K. Joiner)
Subject: Re: How do I load mep online help?
Organization: University of Minnesota
Date: Thu, 5 Nov 1992 18:29:57 GMT

In <Bx91s2.AID@unx.sas.com> sasdxk@skyhawk.unx.sas.com (Dave Kolb) writes:

>Is there a way to globally do this for all users?  The best I've seen
>is editing the set variables via control panel/systsem icon for each
>user individually after they log on.
>Seems like the July release used to have this alread set.

I don't remember the July release being different in this respect.  One
difference in the Oct release is the inheriting of env variables from
autoexec.bat files.  Could you set the init variable in autoexec.bat
and have it apply for all users?
From: potts@oit.itd.umich.edu (Paul Potts)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Any known problems with Borland C++ 3.1 / Windows NT
Date: 6 Nov 1992 15:01:59 GMT
Organization: Instructional Technology Laboratory, University of Michigan
NNTP-Posting-Host: helen.oit.itd.umich.edu
Summary: Can anyone run the DOS IDE under Windows NT?

I've got the NT beta up on my system on drive D: with NTFS installed;
drive C: is a FAT volume with Borland C++ 3.1 and a lot of development that
I've done for DOS.

I was hoping to use NT to run the Borland C++ DOS IDE. When I test half-
baked programs under DOS, I often have to reboot. I was hoping NT would 
help this problem and let me work on my DOS development without crashing
all the time. I've successfully run other DOS apps under NT (including some
that I wrote) with no problems. When I try to run the Borland C++ DOS-based
IDE, I get a message saying something like "An OS/2 application has caused
an exception and must be halted," or words to that effect. 

I'm running an AMI 386/40 with 20 megs of RAM, if that helps. If this is
in the docs somewhere, please don't flame, but point me in the write direction.
I haven't had the opportunity to read through everything on the CD yet.
(no surprise there!) Keep in mind I'm referring to the DOS-hosted IDE; the
Windows-based Borland C++ compiler runs fine.

-Paul-
I've got Juan Valdez on my back... Espresso! Espresso!  

-- 
"What good is a computerized nose?" - Lou Reed - potts@oit.itd.umich.edu
Newsgroups: comp.os.ms-windows.programmer.win32
From: PVossler@cen.ex.ac.uk (P.J.Vossler)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: NT progs under 3.1
Date: 12 Nov 92 15:30:01 GMT
Distribution: comp
Organization: Computer Unit. - University of Exeter. UK


I have heard that Windows NT applications will be able to run under 3.1 
with a piece of additional software. Is this true and if it is what
software will be required ?
--
	

===============================================================================
P.J.Vossler, Dept of Physics,	|	Email:p.j.vossler@ex.ac.uk 
University of Exeter		|	Tel  : +44-392-264100
Exeter, Devon, England EX4 4QL  | 	Fax  : +44-392-264111
===============================================================================
-- 
	

===============================================================================
P.J.Vossler, Dept of Physics,	|	Email:p.j.vossler@ex.ac.uk
From: lfosdal@falcon.no (Lars Fosdal)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: NT October beta - Which one ?
Date: Fri, 06 Nov 92 10:24:32 MET
Organization: Falcon Information Services AS

Several netusers have recently posted that they have received the
October Beta of Win NT.  I still have only the July '92 prerelease,
and these postings made me call the Norwegian MS rep.

After the standard "Yes, it's coming", I kept on pushing and he
then stated that "the NT OS _only_ was out, but that the NT/SDK still
was in production, and he couldn't give me a date".

Could somebody tell me if you have received the NT/SDK October beta
or if it's only the NT OS ?    I had never heard before that there
were supposed to be to "versions" of the NT CDROM's.

I just _don't_ like salesmen that doesn't tell it to me straight...

--
/ Mr.Lars Fosdal, Software Developer, Financial Analysis Systems  /
/ Falcon Information Services AS, Stranden 1, N-0250 Oslo, Norway /
/ E-mail:lfosdal@falcon.no  Tel:(47-2) 831310  Fax:(47-2) 831290  /
-- All opinions are personal and does not reflect company policy --
Date: Sun,  8 Nov 92 20:26:00 +0100
From: Bernhard_Weichel@ccwn.fido.de (Bernhard Weichel)
Subject: Re: HELP ME!!!
Newsgroups: comp.os.ms-windows.programmer.win32
X-Comment-To: (Kenneth Yoder)
Organization: Discover the Point of Life 

Hallo Kenneth!

 Am <04 Nov 92> hast Du zu > HELP ME!!! < geschrieben:

 >> Can I have a triboot feature where NT,OS/2,&DOS are chosen at power on
 >> and thus pick either of the three to go into?  If so how?

I intend to do the same thing with NT, OS/2, LINUX an DOS. I think I will 
switch activ partitions on my harddisk. I've done this earlier when I worked 
with DOS and XENIX.

Could you do the same or are there some problems to expect?

Yours
Bernhard

Newsgroups: comp.os.ms-windows.programmer.win32