HDTenEightyP/NetNews huggingface dataset:
From: jrs@barracuda.kodak.com (Jeff Szczepanski)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: Can the NT CD be read under SunOS 4.1.1
Date: 24 Jul 92 20:42:01 GMT
Reply-To: jrs@barracuda.kodak.com
Organization: Eastman Kodak Company

In article l70hjjINN259@exodus.Eng.Sun.COM, silber@orfeo.Eng.Sun.COM (Eric Silber) writes:
>In article <1992Jul23.013920.674@vine.cp10.es.xerox.com> hamilton@vine.cp10.es.xerox.com (Bruce A. Hamilton) writes:
>>I haven't yet bought a CD-ROM drive for my PC, but I just ordered the NT CD-ROM.  Will I be able to read it under SunOS 4.1.1b?  Yes I have /pcfs in the kernel.  If I can read it under SunOS, it will be easier to print the documentation on various high-sp
>>eed PostScript printers at work.
>>
>>Thanks,
>>-- 
>>--Bruce
>>BHamilton.LAX1B@Xerox.COM
>>310/333-3538
>
> Well, I don't think that having pcfs filesystem support in your kernel
> relates to being able to read the cdrom.  The cdrom filesystem format
> that used to be standard was 'hsfs' (high sierra), now there is
> 'rockridge' which is (correct me if I am wrong) the common name for
> ISO9xxx (whatever the number is).
>
> I supsect that you WILL be able to read the NT CDROM on your 4.x
> SPARCSTATION, but you may need to recheck your kernel configuration
> for the support for the 'rockridge' filesystem type.
>
> (again note: the 'pcfs' filesystem type (the dos floppy format) 
>  IS NOT the filesystem type of the cdrom)

As you say,

The pcfs support is not relevant for this. In general ISO9660 disks are very
interchangeable with most (if not all) platforms. High sierra and ISO9660 are
basically the same thing....very minor differences.

Anyway, I have mounted the July 1992 Win NT SDK release on a SparcStation 2
under SunOS 4.1.1 using the command "mount -rt hsfs /dev/sr0 /cdrom"
or what ever path you want. Actually, I just noticed that the man page on
fstab says that "hsfs" supports both ISO9660 and high sierra.

This worked fine and I printed all ~3000 pages of NT documentation on our hearty
Postscript printer. (Overview, API 1 & 2)

-Jeff


-------------------------------------------------------------------------------
Jeffrey R. Szczepanski                                Eastman Kodak Company
Digital Technology Center                             901 Elmgrove Road
Electronic Imaging Research Labs                      Rochester, NY 14653-5324
							
Email: szczepan@dtc.kodak.com              My other car is a SOLAR CAR....
                                               RIT SpiRIT Solar Raycing!

-------------------------------------------------------------------------------
From: Robert_Salesas@mindlink.bc.ca (Robert Salesas)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: Recursive folders?
Date: 22 Jul 92 21:20:32 GMT
Organization: MIND LINK! - British Columbia, Canada
Distribution: world

> CIVENBAH@mizzou1.missouri.edu writes:
> 
> Considering the fact that the Windows 3.0 interface has been
> around for a couple of years now, it could be tought of as "a
> bit stale". Also considering the fact that OS/2 has a new
> object-oriented shell, it is apparent that the Windows interface
> will be considered by many as somewhat lacking when NT is released.
> Would you care to comment on this and/or perhaps provide some
> sort of time frame for when MS would *like* (as opposed to
> committing to a firm target date) to have "Cairo" implemented
> on Windows?
> 
> Brian.


Well, I for one, like the Windows 3.x interface with separate PM and FM.  I'm
glad that NT will offer this, and I hope it will keep offering it.  I don't
like systems like the Mac or Amiga that use the disk layout as a representation
of my "work groups".  I also don't like the way the WPS works.  However, I'm
sure that if MS changes the PM/FM combination, they'll do a good job.

Rob

--
\------------------------------------------------------------------------/
\ Robert Salesas             | Internet: Robert_Salesas@mindlink.bc.ca   /
\ Eschalon Development Inc.  | CIS:    76625,1320  Tel/Fax: 604-520-1543 /
\------------------------------------------------------------------------/

Newsgroups: comp.os.ms-windows.programmer.win32
From: charlesb@berkeley (Charles Brauer)
Subject: Help: install NT
Summary: Install problem with Windows NT
Keywords: Windows NT 
Reply-To: uunet!fai.com!charlesb
Organization: Fujitsu
X-Newsreader: Tin 1.1 PL4
Date: Tue, 21 Jul 1992 04:54:30 GMT

When installing the Windows NT SDK, I get:

    Copying CANYON.MID
    to C:\WINNT

    A error has occured
    Could not open the file named: 'D:\I386\CANYON.MID'

If I "ignore" I get a similar message for a series of files.
I thought it was a bad CD so I ordered a new one.  When it 
came in I re-tried the installation and I got the same error, so
I don't feel it is a bad CD.  My CD drive is a new CD Technology
drive that was in the vendor's exhibit at the conference.  I 
am running on a Toshiba 5200 with 12MB and a 100 MB disk. When
installing, I told it to reformat the FAT (I don't care about
saving anything on the disk).  I am curious about the reference
to the D drive.  I don't have one, unless that is the CD drive.

Any help will be greatly appreciated.

Charles Brauer

--
NAME Charles Brauer
EMAIL uunet!fai.com!charlesb
SNAIL Fujitsu, 3099 North 1st Street, San Jose, California 95134
PHONE (408) 456-7852
Newsgroups: comp.os.ms-windows.programmer.win32
From: jc@puff.esd.sgi.com (Joe Chien)
Subject: Re: NT Development Platform Possibilities
Organization: Silicon Graphics, Inc.
Date: Tue, 21 Jul 1992 19:05:54 GMT

In article <98160002@hpcuhe.cup.hp.com>, edwardm@hpcuhe.cup.hp.com (Edward McClanahan) writes:
|> I'm trying to put together a Windows NT development system (for a reasonable
|> amount of money) and have run into several difficulties with would-be vendors.
|> 
|> Problem 1 - S3 video
|>             Not currently supported in the NT SDK, but RSN
|>             Do the S3 cards have a VGA-compatible mode which NT can use?
|> 
If you have a V7 VRAMII card, you can have a 1024x768x4 display mode by
doing this "copy \winnt\system\v7_1024.dll \winnt\system\vga.dll"
or "copy \winnt\system\v7_800.dll \winnt\system\vga.dll" for 800x600x4.

Do this "copy \winnt\system\xga.dll \winnt\system\vga.dll", if you are using
a XGA card.

-------------------------------------------------------------------------
Joe Chien
Silicon Graphics Inc.
jc@esd.sgi.com
Newsgroups: comp.os.ms-windows.programmer.win32
From: alistair@microsoft.com (Alistair Banks)
Subject: Re: New Microsoft Developer Network News
Date: 23 Jul 92 05:18:43 GMT
Organization: Microsoft Corporation

In article <CHUCK.PHILLIPS.92Jul21003451@colorado.FtCollinsCO.NCR.COM> Chuck.Phillips@FtCollinsCO.NCR.COM (Chuck Phillips) writes:
>
>Are the updates (CD ROM and docs) free?  If not, then approximately how much?
>For me, if the updates are free, it would be worth it to go ahead and spring
>for the whole shebang.  Otherwise, I'll probably wait for the beta.

I really though my posting made this clear - "You get..." implies
"as part of the up-front cost" - i.e. not free, for $69 or $399 for
all updates until & including final -- Alistair
From: joiner@cs.umn.edu (Jay Joiner)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: Recursive folders?
Date: 22 Jul 92 18:55:59 GMT
Article-I.D.: cs.1992Jul22.185559.28919
Organization: University of Minnesota, Minneapolis, CSci dept.

In <1682C66B3.CIVENBAH@mizzou1.missouri.edu> CIVENBAH@mizzou1.missouri.edu writes:

>Considering the fact that the Windows 3.0 interface has been
>around for a couple of years now, it could be tought of as "a
>bit stale". Also considering the fact that OS/2 has a new
>object-oriented shell, it is apparent that the Windows interface
>will be considered by many as somewhat lacking when NT is released.

I'll bet Hewlett-Packard (NewWave) and Xerox (Rooms) will be one of the
first on the block to release their products for NT, giving it the object-
oriented capability of WPS.

Jay Joiner
Newsgroups: comp.os.ms-windows.programmer.win32
From: jonka@microsoft.com (Jonathan Kagle)
Subject: Re: NT display drivers?, Debugging C++
Date: 22 Jul 92 19:36:45 GMT
Organization: Microsoft Corporation

In article <4561@balrog.ctron.com> patman@olympus.ctron.com () writes:
>Also, how do you debug C++ code under NT?  The only way we've been
>able to get it to work even a little is with ntsd, and even that's
>painful.  Windbg is what we'd like to use, but it gets *real* confused
>after the first method gets called, and you can't see any local vars.

Unfortunately, the version of WinDbg supplied with the first prerelease
SDK does not support C++. Future releases will provide C++ support
along with many other features that are currently disabled. Be patient, 
the tools also are in prerelease form! :-)

       -Jonathan
Newsgroups: comp.os.ms-windows.programmer.win32
From: alistair@microsoft.com (Alistair Banks)
Subject: Re: New Microsoft Developer Network News
Date: 21 Jul 92 21:59:15 GMT
Organization: Microsoft Corporation

In article <1992Jul20.132358.12321@cam-orl.co.uk> thg@cam-orl.co.uk (Tim Glauert) writes:
>
>Sorry to re-post the same question, but this seems too good to miss so I want
>to get it completely clear:
>
>If I buy the ($69) SDK on CD now, will I get a final release of NT plus a
>final release of the SDK, including the C/C++ compiler, free of charge?
>
>If this is true, it seems like it would be worth buying the SDK now and just
>putting it on the shelf until January, since I can't imagine that NT will cost
>less than $69, even without the C/C++ compiler and SDK. I realise that I may
>have to buy an NT book or two, but it's still a pretty good deal, even
>allowing for the purchase of a CD-ROM drive! Is there an official Microsoft
>document which states this policy? (just to be sure!)

I hope I don't have to say the same thing too many times...

If you buy the Preliminary Win32 SDK for Windows NT you will
receive updates up to and including the final releases. The
final OS & final SDK are simple to understand, the final
C/C++ compiler will be supported, but won't have a matching
"boxed" product. The Microsoft Languages group intend to
ship a different technology mix in their retail 32-bit
C/C++ compiler product

It is of course very true that $69 without hardcopy, or $399
with hardcopy represents superb value, and will likely be
cheaper than any other packaging of these technologies at a
later date

You may quote my above paragraphs as an official document. I
do not include and disclaimers in my postings, in general. Otherwise
you should simply treat this as an explanation of the offer which
has been sent to previous purchasers of our development tools. I
would expect you could also receive a glossy sheet containing the
details of this offer if you were to call Microsoft's Sales
number, 800-227-4679

Having aquired the SDK, I hope that you don't simply put it on the
shelf. Rather I hope that you use it to develop great Win32 apps!

-- Alistair
Newsgroups: comp.os.ms-windows.programmer.win32
From: pbrooks@mentorg.com (Phil Brooks)
Subject: Re: DLL questions
Date: Wed, 29 Jul 1992 19:02:08 GMT
Organization: Mentor Graphics Corporation
Keywords: 
Followup-To: 

In article <Bs5wsE.H5@fmsrl7.srl.ford.com>, vscarafi@eccdb1.pms.ford.com (Vincent F. Scarafino) writes: 
|> My understanding of DLLs doesn't have any hierarchy involved.  If the
|> DLL is specifyed via a full pathname, then that determines the only
|> DLL that will be checked for the external reference.  If only the
|> name of the DLL is used, then DLLs are searched in the order specified
|> in the PATH statement until the first one that meets the criteria is
|> found.  I believe this to be the case, but I haven't extensively tested
|> it.

|> >                 main()
|> >                 /    \
|> >              aa.dll   bb.dll
|> >              /    \       \
|> >            cc.dll   \     dd.dll
|> >                       \    /
|> >                        ee.dll

The hierarchy I am trying to portray has to do with link time, not anything
to do with where things are found or how.  The above diagram implies that
when aa.dll is built, cc.dll and ee.dll are specified on the linker command
line and used to satisfy external references in aa.dll.  Likewise, when main() is
linked, aa.dll and bb.dll are specified on the linker command line and used
to satisfy external references in main().  I don't have an NT system in front
of me, so I can't experiment yet to find this out.  I am just working from
documentation and an understanding of SVR4 Unix dynamic linking and shared
libraries.  Given that setup, the manuals say that the libraries are loaded
at invoke time and LibMain() is called for each one.  My question is what order
are the LibMain() functions called in.  In particular if aa.dll LibMain() 
calls something in cc.dll and the function in cc.dll requires that its LibMain()
function be called before any of its internal functions are called, then 
aa.dll's LibMain should be called after cc.dll's LibMain().  Is this in fact
the case with Windows/NT?

The first question just has to do with scoping rules with regard to dlls.
Is the scoping for dlls different than it is for objects that are linked
monolithically for functions?  for data? for dll's loaded using LibMain()?
for dll's specified at link time?
  
-- 
Phil Brooks
phil_brooks@mentorg.com
Newsgroups: comp.os.ms-windows.programmer.win32
From: mba@tandon.com (Michael Ben-Ari (mba@tandon.com))
Subject: Re: Microsoft Systems Journal on NT
Keywords: Systems Journal NT
Organization: Tandon Corporation, Moorpark, CA
Date: Fri, 24 Jul 1992 20:25:39 GMT

In article <BrpzzM.1HJ@undergrad.math.waterloo.edu> debeaupr@cayley.waterloo.edu (David Beaupre) writes:
>Someone mentioned a few days ago, that an issue of the Microsoft
>Systems Journal was dedicated to Windows NT.
>
>What month and volume number was that issue??
>

It should be at your neighborhood magazine rack/bookstore by now....

It is the July/August 1992 issue.

Nice articles/ very good overviews!

-Mike

>Type to ya later...
>Dave
>
>=====================================================================
>David Beaupre					| "Think HONK iF
>University of Waterloo				|    you are a 
>debeaupr@descartes.waterloo.edu			|   telepath!"
>debeaupr@descartes.uwaterloo.ca			|
>CompuServe-> 71201,1176				|
>
>
>


-- 
------------------------------------------------------------------------------
Mike Ben-Ari    		Tandon Corporation 	(805) 378-7889
mba@tandon.com  		609 Science Drive	(805) 529-9033 Fax 
70523.3605@compuserve.com	Moorpark, CA 93021 USA 
Newsgroups: comp.os.ms-windows.programmer.win32
From: msdos1@nic.funet.fi (Petri Hartoma)
Subject: Re: MIPS NT and old apps
Organization: Finnish University Network Information Centre, Finland
	<1992Jul10.205504.1365@terminator.cc.umich.edu>
Date: 24 Jul 92 09:42:16

In article <1992Jul10.205504.1365@terminator.cc.umich.edu> potts@itl.itd.umich.edu (Paul Potts) writes:

> True - none of the Windows 16 apps on my hard drive would execute at all
> under the NT developer's release. Even Word for Windows 2.0 - when you launch
> it, it just exits - no dialog or anything. Better than crashing though... : )

That's strange, because I tried WfW on Monday and it loaded just fine
- slowly of course, but it worked. I was also amused to see BigDesk
(the virtual desktop program) run fine under Win NT. The only app I
couldn't get to run was Win 3.1 Write. No wonder MS guys didn't get it
ported. ;) Try incrreasing your swap file, maybe the 20 MB minimum is
too little. I have a 24 MB paging file now.

&& Petri
--
(* Petri Hartoma - moderating MSDOS material in nic.funet.fi *)
(* msdos1@nic.funet.fi,Petri.Hartoma@cc.tut.fi *)
Newsgroups: comp.os.ms-windows.programmer.win32
From: hamilton@vine.cp10.es.xerox.com (Bruce A. Hamilton)
Subject: Can the NT CD be read under SunOS 4.1.1 ?
Organization: Xerox Corp., El Segundo, CA, USA
Date: Thu, 23 Jul 1992 01:39:20 GMT

I haven't yet bought a CD-ROM drive for my PC, but I just ordered the NT CD-ROM.  Will I be able to read it under SunOS 4.1.1b?  Yes I have /pcfs in the kernel.  If I can read it under SunOS, it will be easier to print the documentation on various high-speed PostScript printers at work.

Thanks,
-- 
--Bruce
BHamilton.LAX1B@Xerox.COM
310/333-3538
Newsgroups: comp.os.ms-windows.programmer.win32
From: kung@kung32.b11.ingr.com (Michael Kung)
Subject: Internationalization Win32/NT
Organization: ISGS 
Date: Tue, 21 Jul 1992 17:11:08 GMT


The Win32/NT developer release do not contain any modules for localization.

What will be the tools I can use for the Asian market?

Michael
From: SXMRP@orca.alaska.edu (Michael R. Platzke)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: uupc-nt location?
Date: 27 Jul 92 21:58:06 GMT
Organization: University of Alaska Computer Network

About a week ago it posted that uupc was available for NT.  I wrote the
author and he told me it was available at ftp.uu.net in the /tmp directory.
However, since that time, the file has been moved.  Does anyone know the
location of the file now?  If not, would it be possible to get the file
uploaded to CICA?  CICA now has a nt directory in the win3 section, I assume
that it is intended for MS windows NT program.

I appreciate any help.

-Michael R. Platzke (sxmrp@orca.alaska.edu)
Newsgroups: comp.os.ms-windows.programmer.win32
From: doc@garfield.catt.ncsu.edu (Jeffrey Smith)
Subject: Telling Win NT that Sound Blaster Pro is on IRQ 5, How?
Organization: North Carolina State University
Date: Tue, 28 Jul 1992 15:51:02 GMT

How do I tell NT that my SB Pro is on IRQ 5.
I looked at the INI files but didnt see any why to set it up.
Any info would be greatly appreciated.

Thanks,
Jeff 
Romana: "I thought you said we were coming here for May week?"
Doctor: "I did, May week's in June."
	                **Shada and The Five Doctors**
        Jeffrey Smith   --KD4AYH--  doc@catt.ncsu.edu
From: vscarafi@eccdb1.pms.ford.com (Vincent F. Scarafino)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: write this down!!
Date: 29 Jul 92 18:12:50 GMT
Organization: Ford Motor Co.
Originator: news@pms001

rion@Ingres.COM (Rion Cassidy (x3357) OGT) writes:
> Some of the warnings from the NT linker are routed to stderr, not stdout.
> This means that you cannot redirect these warning to a file UNLESS you add
> the following:
> 
> 2>&1
> 
> Add it anywhere on your command line where you are also redirecting output
> to a file.  Apparently this is some kind of UNIX trick brought over to NT.
> 
This is a DOS feature (copied from Multics).  Errors are supposed to go to
stderr to give you the capability to route standard output to a file and still
see errors on your terminal.  Is the NT linker the first piece of software
to do this right?

Vince
Newsgroups: comp.os.ms-windows.programmer.win32,comp.os.ms-windows.misc
From: alistair@microsoft.com (Alistair Banks)
Subject: Re: LAN Man/NT beta test?
Date: 21 Jul 92 20:46:21 GMT
Organization: Microsoft Corporation

In article <G#R-s6B@engin.umich.edu> spexet@engin.umich.edu (Dennis Robert Spexet) writes:
>Now that the Windows NT test copies are out, I can stop complaining about the
>lack of a NT test copy that I can buy.
>
>However, I am wondering:  Is there a beta test program for LAN Manager/NT?  It
>would be great to obtain test copies of LAN Manager for NT.

The Win32 SDK that you can buy today has very significant portions of
Lan Manager built in - the last few pieces (domain replication,...) will
be made available in later releases. If you can be specific about
which piece that you need is _not_ in the prelim. Win32 SDK, then the
question would be easier to answer -- Alistair
Newsgroups: comp.os.ms-windows.programmer.win32
From: robertk@rkrajewski.lotus.com (Robert Krajewski)
Subject: 32-Bit API and default int size
Organization: Lotus Development Corporation
Distribution: comp
Date: 21 Jul 92 14:55:40

When Microsoft defined the 32-bit API for Windows, were 
any assumptions made about sizeof(int) ? The 3.1 header files
have been modified to hide many of the size dependencies of
standard Windows API types, but I noticed that ExtTextOut()
still takes an int FAR * (not LPINT). Does this mean that
int is still 16 bits when compiling for Win32, or is there
another explanation ?
From: guy@Auspex.COM (Guy Harris)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: Can the NT CD be read under SunOS 4.1.1 ?
Date: 26 Jul 92 23:44:53 GMT
Organization: Auspex Systems, Santa Clara

> The cdrom filesystem format
> that used to be standard was 'hsfs' (high sierra), now there is
> 'rockridge' which is (correct me if I am wrong) the common name for
> ISO9xxx (whatever the number is).

High Sierra and ISO 9660 are, as noted, similar.  "Rock Ridge" refers to
some stuff added to the ISO standard in order to support more capable
file systems; I believe there is both a general extension mechanism, and
a set of UNIX extensions using that mechanism.  There may be extensions
for other OSes as well (Mac System, NT); they may also share some
extensions (e.g., less unpleasantly restrictive file name conventions)
with UNIX.

4.1.1 doesn't have Rock Ridge support in its "hsfs" implementation,
although "hsfs" supports both High Sierra and 9660.  4.1.2's "hsfs"
includes the UNIX extensions, at least....
Newsgroups: comp.os.ms-windows.programmer.win32
From: CIVENBAH@mizzou1.missouri.edu
Subject: Re: Recursive folders?
Organization: University of Missouri
Date: Wed, 22 Jul 1992 12:17:42 GMT

In article <1992Jul21.200758.28760@microsoft.com>
alistair@microsoft.com (Alistair Banks) writes:
 
>But it is our design intent that Windows & Windows NT have
>a consistant UI - and therefore the first release of Windows NT
>will have the same shell features as Windows 3.1. (more accurately
>Windows for Workgroups) We have talked a little about Windows
>Cairo - this is the work where we will improve the shell. This
>work will be seen in later Windows releases
 
Considering the fact that the Windows 3.0 interface has been
around for a couple of years now, it could be tought of as "a
bit stale". Also considering the fact that OS/2 has a new
object-oriented shell, it is apparent that the Windows interface
will be considered by many as somewhat lacking when NT is released.
Would you care to comment on this and/or perhaps provide some
sort of time frame for when MS would *like* (as opposed to
committing to a firm target date) to have "Cairo" implemented
on Windows?
 
Brian.
Newsgroups: comp.os.ms-windows.programmer.win32