HDTenEightyP/NetNews huggingface dataset:
From: beame@maccs.dcss.mcmaster.ca (Carl Beame)
Subject: Re: DuplicateHandle -- passing handles to other processes
Organization: Department of Computer Science, McMaster University
Date: Wed, 11 Nov 1992 01:28:54 GMT

In article <BxI8o0.6K@unx.sas.com> sasdxk@skyhawk.unx.sas.com (Dave Kolb) writes:

Stuff delete
>
>My questions/suggestions are two:
>
>- Does the pipe that CreateFile is opening already exist?  If not you
>  don't have a valid handle to pass.

	The pipe named in the CreateFile already exists, and communication has
already taken place between this process and the pipe creator.

>
>- You need to set the inherit flag in the lpsa security attributes
>  data structure when creating the remote handle.

I do actually call the CreateFile with the following security attributes:

SECURITY_ATTRIBUTES sa;

	sa.nLength=sizeof(sa);
	sa.bInheritHandle=TRUE;
	sa.lpSecurityDescriptor=NULL;
>
>P.S. How does the created process open the local pipe if the remote# is part of
>the pipe name and that's what you're trying to pass it?  And why pass it if it
>already knows it?  Or why not just have the created process open up the remote pipe?

	I am passing the name of the local pipe in the command line to the 
remote process so it can connect back to the creator process to receive
the value of the newly created handle.

>
>I guess this is a contrived fragment???

	Not really, I just changed the name of the pipes used.

>
>Let us know...
>
>-- 
>Dave Kolb                     Opinions are mine not SAS'
>SAS Institute, Inc.           EMAIL:      sasdxk@unx.sas.com
>SAS Campus Drive - J206       Phone:      (919) 677-8000 x6827
>Cary, NC  27513-2414 USA      FAX:        (919) 677-8123
>

- Carl Beame

Newsgroups: comp.os.ms-windows.programmer.win32
From: cohen@mips2.ma30.bull.com (Steve Cohen)
Subject: NT and DCE
Reply-To: cohen@mips2.ma30.bull.com (Steve Cohen)
Organization: Bull Worldwide Information Systems  (Billerica, MA)
Date: Mon, 9 Nov 1992 17:38:57 GMT
Keywords: Naming Services, Security

I have been reading the "Inside NT book" and it is a very good book.

According to the book NT has its own security, and LANManager
Naming services; but NT supports OSF DCE RPC's.


How can you do OSF DCE RPC's if there is no CDS (Cell Directory Service)
for naming services or KERBEROS for security?

Steve Cohen
Bull


Newsgroups: comp.os.ms-windows.programmer.win32
From: RFowler@kelvin.jpl.nasa.gov (Robert A. Fowler)
Subject: NT config probs, was: Re: S3 Pprobles [was Re: ATI ultra drivers]
Organization: Jet Propulsion Laboratory
Date: Sat, 14 Nov 1992 02:50:04 GMT

In article <JKF.92Nov13133111@frisky.Franz.COM> jkf@Franz.COM (Sean Foderaro) writes:


>>>      I have a greater concern. When I switched to 1024x768 I could no longer
>>> see anything. Since the NT setup is 100% graphical I had no choice than
>>> reinstalling ALL of NT.

> I had this problem too but rather than reinstalling NT I just booted dos,
>found the et4000 driver file in the nt drivers area and copied the vga driver
>on top of it and rebooted nt.  viola, it was now running in vga mode.

BUT, THIS ONLY WORKS IF YOU ARE RUNNING ON A FAT, if you installed NT on to 
a NTFS partition (like I did) you can't access it from dos, to change 
drivers, or to install the SDK of of a non-supported CD drive.  (Ba Humbug!)

PS:

Is there a way to convert a NTFS partition back into a FAT with out 
reformating & reinstalling NT?

Is there a way to allow (device driver/TSR) DOS to access an NTFS partition?
    _________________________________________________________________
                        
                        HONDA -- The only way to fly
    o          
  _/\_>   -A proud owner (just wish they were made in the USA)
 O,> / O   [with all respects to Ohio MINE were made in Japan]
           
                           CM400T/XL500R/VF500F
                             '79   '82    '84
                           
     Slower trafic keep right (SUCKzukies, HDs, etc.) ->->->->->->->
    _________________________________________________________________

Newsgroups: comp.os.ms-windows.programmer.win32
From: trevorl@ise.canberra.edu.au (Trevor Lawrence)
Subject: Re: Info on NTFS internals ?
Reply-To: trevorl@ise.canberra.edu.au
Organization: Info. Sci. and Eng., University of Canberra, AUSTRALIA
Date: Thu, 5 Nov 92 22:10:29 GMT

In article <1992Nov04.053326.643@microsoft.com> Alistair writes:
>Please will you be much more specific about what things in NTFS
>you are trying to learn
>
>Features? These are surfaced in the published Win32 API (though I
>could summarise them again, as I have done before on this forum)
>
>On-Disk sector layout? This is not publicly available at this time
>
>Mechanisms involved in implementing its features? These live in the
>code of the OS, and as such are competitive advantage for the OS, and
>like other parts of the source code, are only available to licensees
>
>I think I am missing something, so please explain extactly what you
>want to know, but don't have access to - and importantly, why (so that
>I could make a case, if I need to get things changed)
>
>-- Alistair

In the September 1989 issue of Microsoft System Journal a 13 page
article by Ray Duncan was published giving the rationale and
disk layout info for HPFS. That's the kind of information I'd
like to see on NTFS. But it looks like Microsoft's going to
clam up this time. Pity, but I won't be able to put details of a
good example of a file system (if it is) before the hoards of
Operating Systems students who pass by me each semester.

Trevor
From: groening@sdsc.edu (Chris Groening)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Icon image format
Date: 6 Nov 1992 22:33:04 GMT
Organization: San Diego Supercomputer Center @UCSD.
Distribution: world
Reply-To: groening@sdsc.edu
NNTP-Posting-Host: sluggo.sdsc.edu
Keywords: Icon

I'm writng an image file translator and Icon will be included.

I got a files that has multiple icons in it.
According to the Programmers Guide vol 4 for window 3.1
the first word in an icon format is reserved to be 0 and
the next word should be a one.  This is not the case for this
file.  The header is totally different from what it should
be, what gives?

thanks in advance

Newsgroups: comp.os.ms-windows.programmer.win32
From: johnhall@microsoft.com (John Hall)
Subject: Re: Dialog instance data...
Date: 10 Nov 92 23:22:26 GMT
Organization: Microsoft Corporation
Distribution: na


In article carty@ists.ists.ca (Ed Carty) writes:
| 
| 9 Nov. 1992
| 
| Anyone walked this road before...
| 
| I'd like to encapsulate instance data with a modeless dialog.  

SetProp(hDlg, "MyInstanceData", 32bit DataValue);

Use the property functions to associate a data structure with
a dialog, and *don't* forget to release it when the dialog
exits!

-- 
-------------------------
My comments are my own.  They are independent and unrelated to the
views of my company , relatives or elected representatives.
From: turpin@cs.utexas.edu (Russell Turpin)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Is anyone using the Viper S3 video controller?
Date: 13 Nov 1992 11:12:04 -0600
Organization: U Texas Dept of Computer Sciences, Austin TX
NNTP-Posting-Host: im4u.cs.utexas.edu
Summary: Is it compatible with Oct. Beta release of NT?

-*----
Is anyone successfully using the Viper S3 video controller with
Windows NT?  (This is a local bus video card using the S3 chip
set.)

Do you like it?

Russell
Newsgroups: comp.os.ms-windows.programmer.win32
From: tpradeep@cs.tamu.edu (Pradeep K Tapadiya)
Subject: Converting MSC 7.0 code to MSC 8.0 - Help
Organization: Computer Science Department, Texas A&M University
Distribution: usa
Date: Fri, 6 Nov 1992 17:00:46 GMT

Howdy netters,

Finally managed to install NT and the new `C' compiler on my machine.

After playing around with one of the examples, sample.c, I realize
that a program compiled with the new version is not limited to 640K
under the new dos-box. Now I wish to recompile our existing "dos-based"
`C' code for the new environment so that I can happily do some
more mallocs without worrying about any limitations. 

Chapter 1 in PROGTECH notes interchangeably talks about 16 bit and
32 bit compilation, which is kind of confusing. Can someone please
enlighten me on the following questions?

1.I don't see any support for the old graphics functions (graphics.lib).
  Are there any equivalent functions for them? The on-line help still
  provides help on these functions (drawing lines and rectangles, etc).

2. Can I produce 16 bit code with the new version and use the old
  graphics.lib? This way I can get some more memory for my application. 

3. Or can I use the old 16 bit compiler and linker and do "something"
  so that the application doesn't choke on 640K limit and still everything
  else remains the same?

4. Any other suggestions?

Thank you for your help. If need be, I'll summarize the responses on
the net.

Pradeep
tpradeep@cs.tamu.edu
Newsgroups: comp.os.ms-windows.programmer.win32
From: joiner@myria.cs.umn.edu (Jay K. Joiner)
Subject: Re: October Beta: comments and questions
Organization: University of Minnesota
Distribution: na
Date: Wed, 11 Nov 1992 22:46:08 GMT

In <1658@applix.com> jim@applix.com (Jim Morton [ext 237]) writes:

>I've gotten the October Beta installed on both x86 and Mips, and
>have a few comments/questions.

>2) "RMDIR /S has been disabled in this release" - ARGGGGGGGHHH!!!!!
>   I may keep the July release on disk just for this feature. Is
>   there any other good way to recursively delete directories?

If you can stand using the mouse...

You can do it in File Manager by selecting the directory and then selecting
delete.  You'll probably want to turn off confirmations in the Options/
Confirmations dialog first. 

Otherwise, you might look for GNU's rm utility.  You might find it in
the GNUFUTIL package.  This stuff has been ported to OS/2 2.0, so it
shouldn't be long here.

Please no flames about WIMP/GUI interfaces or OS/2.

Newsgroups: comp.os.ms-windows.programmer.win32
From: sasdxk@skyhawk.unx.sas.com (Dave Kolb)
Subject: Re: NT on a TriStar...DISAPPOINTED!!!
Originator: sasdxk@skyhawk.unx.sas.com
Date: Fri, 13 Nov 1992 19:39:19 GMT
Organization: SAS Institute Inc.


In article <1e0q44INNom6@gazette.bcm.tmc.edu>, bsteiner@mbcr.bcm.tmc.edu (Brian W. Steiner) writes:
...
|>
|> -Screen redraws are very slow.
|> -Mouse tracking is very jumpy (ie. you can tell the system is very over burdend).

Per release notes - 16M is recommended for this release altho it runs on 8M.

|> -Frequently run out of memory (although my swap file is 15Mb)

Page file should be bigger and can run across more than one disk.

|> -NT<-->LM 2.1 not fully supported (cannot "see" the LM file servers)

This works if you set up WNT to use a workgroup same as the LM domain.
An WNT domain is something different - for use with LM for NT only.
Some more doc on this distinction would be nice.

|>
|> If there is something I missed in the setup that would correct these problems
|> then I'll turn off my flame.  Otherwise I will caution my collegues against
|> what I thought was going to be a great OS...

This is still beta code.

|>
|> Disclaimer: All opinions expressed are mine and mine alone.
-- 
Dave Kolb                     Opinions are mine not SAS'
SAS Institute, Inc.           EMAIL:      sasdxk@unx.sas.com
SAS Campus Drive - J206       Phone:      (919) 677-8000 x6827
Cary, NC  27513-2414 USA      FAX:        (919) 677-8123

Newsgroups: comp.os.ms-windows.programmer.win32
From: hosken@spss.com (Bill Hosken)
Subject: Re: Logitech
Organization: SPSS, Inc.
Date: Wed, 11 Nov 1992 21:09:49 GMT

In article <139760001@hpcupt1.cup.hp.com>, fenwick@hpcupt1.cup.hp.com (John Fenwick) writes:
> 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?

I have a Logitech mouse.  I think I called it a PS/2 Bus Mouse at 
intall time.  It seems to work fine.

Newsgroups: comp.os.ms-windows.programmer.win32
From: stevea@xvt.com (Steve Archuleta)
Subject: Version Control under Windows NT?
Organization: XVT Software Inc.
Distribution: usa
Date: Thu, 5 Nov 1992 23:44:13 GMT
X-Disclaimer: The views expressed in this message are those of an
	individual at XVT Software Inc., and do not necessarily
	reflect those of the company.

Has anyone had any experience running a version control system under 
Windows NT (beta)? Specifically, I am interested in PVCS from InterSolv.
I need to know about reliability or specific problems encountered with such
a setup. 

Responses via email would be appreciated.

Thanks,
Steve Archuleta
stevea@xvt.com


-- 
sldkfjlskdjflskdfj sdgarbage
Newsgroups: comp.os.ms-windows.programmer.win32
From: sasdxk@skyhawk.unx.sas.com (Dave Kolb)
Subject: GetLastError() return values???
Originator: sasdxk@skyhawk.unx.sas.com
Date: Mon, 9 Nov 1992 21:53:19 GMT
Organization: SAS Institute Inc.


Although I've found Appendix B in the Overviews manual, how is one
supposed to relate the many possibilites for rc's that GetLastError()
returns after a particular WNT function returns FALSE?

E.G. How am I supposed to know the actual values GetLastError() will
return after CreateFile fails?  I think many of the values are the
same as OS/2 such as ERROR_PATH_NOT_FOUND, ERROR_FILE_NOT_FOUND or
ERROR_PIPE_BUSY but I sure as heck can't test for all the values in
Appendix B each function call.  I don't even want to look thru the
100's of calls to even GUESS what they might be!

And indeed, most of the return values I could care less about, an
error is an error and I'll print out a message and the user can look
it up and modify his or the program's behaviour somehow :-)

But what if I want to deal with certain types of errors?  How does
one find out the possibilities for a given function?

In OS/2 the rc's were listed with each function and when porting
software it would be nice to know the likely rc candidates.  Or even
if not porting an OS/2 app.

Thanks,

-- 
Dave Kolb                     Opinions are mine not SAS'
SAS Institute, Inc.           EMAIL:      sasdxk@unx.sas.com
SAS Campus Drive - J206       Phone:      (919) 677-8000 x6827
Cary, NC  27513-2414 USA      FAX:        (919) 677-8123
From: perkins@tallis.enet.dec.com (Eric Perkins)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: RE: Link out of memory:
Date: 12 Nov 92 16:37:55 GMT
Reply-To: perkins@tallis.enet.dec.com
Organization: Digital Equipment Corporation, Littleton MA


I have seen the linker (coff) get the out of memory message on
the MIPS platform when I have forgotten to convert the object
files to coff format. Could this be the cause of the problem?

===============================================================================
-- Note: All views questions, and thoughts are my own and in no way represent
--       those of my employer. I can be reached by the following means:
--
-- perkins@tallis.enet.dec.com
-- (508) 952-3144
===============================================================================
From: trevorl@ise.canberra.edu.au (Trevor Lawrence)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: Getting DOS TCP/IP software to work with NT
Date: 8 Nov 92 21:56:21 GMT
Reply-To: trevorl@ise.canberra.edu.au
Organization: Info. Sci. and Eng., University of Canberra, AUSTRALIA

Ushomirskiy Gigory writes:
>I remeber reading here that Win NT's network drivers are similar to NDIS.  In
>this case it seems to be easy to get any dos TCP/IP software that uses packet
>drivers or NDIS to work with NT.  Since the above programs rely on a packet
>driver (or NDIS driver) to communicate with the ethernet board and if NT 
>does provide NDIS services to DOS VDM's then it probably would not mind
>the program (say QVT/NET or an X server) to write to the packet driver.
>There is a program called dis_pkt that is supposed to provide a packet driver
>interface to an NDIS driver, so QVT/NET should work (it just needs a packet
>driver).  
>
>Is this just a lot of wishful thinking or has anyone tried it?
>I don't have any NDIS software and am having trouble tracking down dis_pkt
>(my archie client is having problems) so I haven't tried this yet.
>
>It would be interesting to know what kind of network services does NT 
>provide to programs in a DOS VDM or Win-16 sybsystem?
>
>Greg.
>

Since QVT/NET is a Win16 program it doesn't run in a standard DOS VDM anyway.
In which case you might have trouble getting the Dis_Pkt TSR loaded.

The QVT/NET people recently told me they were working on producing a WinSock
API compatible version, and were also installing a machine to load NT to 
work on an NT version as well.
From: sasdxk@skyhawk.unx.sas.com (Dave Kolb)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: WNT hangs when viewing LM/X Server
Date: 10 Nov 92 18:36:30 GMT
Organization: SAS Institute Inc.
Originator: sasdxk@skyhawk.unx.sas.com


We finally got LM/X installed on our HP/UX system for a trial but my
WNT machine can't seem to "net view \\hpmachine".

I'm trying to figure out why the Workstation is bound both to "Netbeui"
and to "NBT Netbios TCP/IP" at the same time and which transport is
chosen when.  I'm presuming I could actually use this to access LM/X
servers over tcp/ip and OS/2 servers over Netbeui.  Right?

The HP/UX manual says that the Lan Manager "dynamic name resolution"
requires that the PC workstation and the server be on the same logical
subnet and have the same subnet mask.  And that if you use the "addname"
command to resolve computer names to their internet address, they can
be on different subnets.  So I figure that's my problem as my WNT and
HP server are on two subnets between a Cisco router.  But WNT seems
to not have an "addname" command.

Then I discovered \winnt\system\drivers\etc\lmhosts and added my LM/X
server ip address to that file (is this documented?).  But now when I
do a "net view \\hpmachine" my PC locks up solid - not even my cursor
will move so I have to power off.  I've read other users on CIS getting
some sort of GP fault I think when they try to "net view".
 
Should I be using the lmhosts file since my LM/X server is on a different
tcpip subnet than the WNT machine?

Any advice to keep if from locking up?

Thanks,


-- 
Dave Kolb                     Opinions are mine not SAS'
SAS Institute, Inc.           EMAIL:      sasdxk@unx.sas.com
SAS Campus Drive - J206       Phone:      (919) 677-8000 x6827
Cary, NC  27513-2414 USA      FAX:        (919) 677-8123
Newsgroups: comp.os.ms-windows.programmer.win32
From: sinyaw@starbright.smsc.sony.com (Sin-Yaw Wang)
Subject: no C++ for RISC?
Organization: Sony Microsystems
Distribution: comp
Date: 11 Nov 92 22:32:10


The Win32/SDK release note stated, "There is no C++ suport for the RISC
platform in this release."  We did found the CL front-end compiler on the
CD-ROM, and, rightly so, it does not accept any C++ programs.

How are we supposed to port MFC based programs to the RISC platform?  I
guess the better question is, "When are we...".

Is Microsoft committd to have full C/C++ 7.0, MFC included, supported
when NT is released?

    Sin-Yaw Wang, sinyaw@smsc.sony.com
    
    Sony Microsystems Company
    651 River Oaks Pkwy
    San Jose, CA 95134
    TEL: (408)-944-4076
    FAX: (408)-954-0849
Newsgroups: comp.os.ms-windows.programmer.win32
From: stonecypher@star.enet.dec.com ()
Subject: Naming Convention for Named Objects?
Reply-To: stonecypher@star.enet.dec.com ()
Organization: Digital Equipment Corporation
Date: Fri, 13 Nov 1992 18:45:16 GMT


Has Microsoft published a spec detailing naming conventions for named
objects? Names for named objects are system-global, so it is possible that
two different applications will (unintentionally) conflict, choosing the
same name for an object.

A naming convention would act as a gentleman's agreement across application
developers about global object names. I realize that a naming convention
doesn't prevent malicious action on the part of a developer, but it is a
necessary step for prevention of unintended name conflicts.

I imagine Microsoft intends developers to embed the organization and
application names in the object's name. For example, imagine that
Microsoft App1 and Digital App2 both want to create a named pipe:

	\MICROSOFT\APPLICATION\APP1\MYNAMEDPIPE
	\DIGITALEQUIPMENT\APPLICATION\APP2\MYNAMEDPIPE

This type of naming convention would prevent unintended collisions. Is
there an official Microsoft spec detailing a naming convention?

I'm not asking about object domains -- just plain objects, like a named pipe
which is used as a generic service request channel, for server/client
session startup. Nor am I asking about access tokens -- I realize they are
important for some classes of objects.

Thanks!

-----------------------------------------------------------------------------
Tom Stonecypher, Digital Equipment Corporation, stonecypher@star.enet.dec.com
-----------------------------------------------------------------------------
Newsgroups: comp.os.ms-windows.programmer.win32
From: alistair@microsoft.com (Alistair Banks)
Subject: Re: Info on NTFS internals ?
Date: 09 Nov 92 04:35:11 GMT
Organization: Microsoft Corporation

In article <1992Nov5.155204.19448@decuac.dec.com> baker@westsd.dco.dec.com (Art Baker) writes:
>
>It would be possible, I believe to desribe the algorithms/methods used
>by the NTFS driver without revealing anything that would put Microsoft
>at a competitive disadvantage.
>
>My own employer, Digital Equipment, has published an entire book
>describing both the on-disk block structure *and* the interaction of the
>Files-11 XQP for VMS. Similar documentation exists for OSF/1 and most
>other flavors of UNIX.
>
>As to why:  Because it's nearly impossible to write high-performance
>code that treats the entire disk-subsystem as a black box. This is going
>to be particularly true if/when WNT becomes the OS of choice on large
>server-machines.  In these kinds of disk-intensive environments,
>information about the disk-subsystem's allocation strategies, locking
>policies, buffering schemes, etc, becomes crucial to squeezing the greatest 
>number of I/O's out of the system.  A simple list of file-system features
>does not meet this need.

Thank you for the description - I understand much better what you're asking
for now. As someone later refers to, we did previously write such an article
about the mechanisms of HPFS. There are many articles yet to be written
about Windows NT, even though Inside Windows NT is out! This certainly
appears to be one such article - To my knowledge, this hasn't
been written yet, so I'll ask that it does get written and published

-- Alistair
Newsgroups: comp.os.ms-windows.programmer.win32
From: storm@cs.mcgill.ca (Marc WANDSCHNEIDER)
Subject: Fatal Error: 0x0000001E
Organization: SOCS - McGill University, Montreal, Canada
Date: Sat, 7 Nov 1992 22:37:58 GMT


About 70% of the time, when I try to switch a shell prompt (MS DOS Prompt)
from windowed to full screen, I get the following error:

Fatal Error: 0x0000001E

Mode Exception not Handled.


Any idea whud up...?

Toodlepip!
Marc 'em.
-- 
  storm@cs.mcgill.ca           McGill University         "-- Attack ships on
  Marc Wandschneider           Montreal, CANADA             fire "
	Any opinions expressed are not mine, but those of the Demon Lord
      Yeegeheeegenogohugu who possessed me whilst I munched on Raisin Bran.
Newsgroups: comp.os.ms-windows.programmer.win32