HDTenEightyP/NetNews huggingface dataset:
From: sg@monsoon.com (Sunil Gupta)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: Recursive folders?
Date: Thu, 23 Jul 92 12:11:42 EDT
Organization: Monsoon Software, Inc.

CIVENBAH@mizzou1.missouri.edu writes:

> 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.

From the impression I got from talking to Jim Allchin (the project
leader for Cairo), the current intended delivery date for Cairo is
somewhere in 1994, but there are so many unexplored issues, that
date should be viewed as a best-case scenario.

Sunil Gupta
Monsoon Software, Inc.
sg@monsoon.com
Newsgroups: comp.os.ms-windows.programmer.win32
From: alistair@microsoft.com (Alistair Banks)
Subject: Re: NTFS features
Date: 21 Jul 92 20:21:28 GMT
Organization: Microsoft Corporation
Distribution: comp

In article <1992Jul20.173150.20682@news.mentorg.com> pbrooks@mentorg.com (Phil Brooks) writes:
>
>I don't want to make a big deal out of this or anything.  I am just curious
>as to the behavior of NTFS and would like to find out exactly what sort of 
>POSIX compliance Microsoft is claiming.  I don't really care much for the
>ability to create a file named '\' or ' ' or '<carrige return>' etc, but it 
>appears that POSIX specifies that they indeed are legitimate filenames.  
>
>Here are some of the pertinent statements from Posix 1003.1-1990 from my copy:

We are claiming (and delivering) POSIX 1003.1 compliance with NTFS & the
POSIX subsystem in Windows NT 

We are therefore conforming with any POSIX 1003.1 section you quote
as mandatory. I'm no POSIX expert - if you're disputing our compliance
and could give details, then I'll take that to our POSIX developers, but
otherwise please understand that we understand what compliance is! -- Alistair
Newsgroups: comp.os.ms-windows.programmer.win32
From: msdos1@nic.funet.fi (Petri Hartoma)
Subject: Re: Full installation Reqs of NT
Organization: Finnish University Network Information Centre, Finland
Date: 24 Jul 92 09:16:33

In article <BrtJHx.E7r@undergrad.math.waterloo.edu> debeaupr@cayley.waterloo.edu (David Beaupre) writes:
>   What is the disk requirements (MBs) of a full installation of Windows NT?

Windows NT: 32 MB (FAT drive), C/C++ 8.0: 29MB, swap file: min. 20MB.
There is about 250 MB stuff in that Win32 SDK CD-ROM, mostly the
documentation as Postscript files.

>   Does that include the full SDK with compiler?

Yes.

>   Also is the compiler both C/C++ compliant?

Yes, but with a quick look to the manuals I couldn't find what
versions of C++ and ANSI-C are supported, sorry.

&& 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: rion@Ingres.COM (Rion Cassidy (x3357) OGT)
Subject: write this down!!
Reply-To: rion@Ingres.COM (Rion Cassidy (x3357) OGT)
Organization: Ask Computer Systems Inc., Ingres Division, Alameda CA 94501
Date: 29 Jul 92 00:39:53 GMT

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.

Newsgroups: comp.os.ms-windows.programmer.win32
From: johnhall@microsoft.com (John Hall)
Subject: Porting Tools for OS/2 to Windows NT
Date: 23 Jul 92 01:23:14 GMT
Organization: Microsoft Corporation


On the Compuserve Win32 forum, the library upload section
for 'Porting From OS/2' now has a new updated set of
utilities.

os2port -- Help setting up an NT environment, then some
	   translation tools to move your C code to NT.
sedgnu  -- A NT version of Sed courtesy of Gnu
annote  -- NT version of source code annotation system
	   shipped with the 'OS/2 to Windows Conversion Kit'
resconv -- NT version of .rc file converter.
helpc   -- Original kit version of help (IPF) format conversion.
imagc   -- Image conversion (Ptrs, Bitmaps, etc)
apicnt  -- Tools for counting what API's you are using on OS/2,
	   some simple estimation techniques for the port.
winhlp  -- Conversion kit help file with hotlinks to the
	   32bit and 16bit Windows help files.
root    -- The root readme for the entire kit.

The original OS/2 to Windows conversion kit is still around,
but they are going fast.


-- 
-------------------------
My comments are my own.  They are independent and unrelated to the
views of my company , relatives or elected representatives.

Newsgroups: comp.os.ms-windows.programmer.win32
From: kcurtis@inthehat.engin.umich.edu (Keith Curtis)
Subject: Re: Postscript manual viewer
Date: Wed, 22 Jul 92 20:15:05 EDT
Organization: University of Michigan Engineering, Ann Arbor
Originator: kcurtis@inthehat.engin.umich.edu


 >As an asside, the manual pages are also on the win32 sdk in
 >WinHelp format, so reading them is no problem. The postscript 
 >formats are there purely for printing

Dwight Matheny and others at MS have been saying that there is some stuff in the docs that is not included in the online help.
From: keogh@sc.sni.ie (Paul Keogh)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Windows NT developers conference
Date: 30 Jul 92 13:55:25 GMT
Article-I.D.: sc.145
Organization: Siemens Nixdorf Software Center, Dublin, Ireland
Keywords: nt

Does anyone have the UK and Europe dates for the Windows NT developers'
conferences ?

Thanx,
Paul Keogh

-- 
Paul Keogh, 			
SNI Software Center 
Dublin, Ireland.	
		
Net: p.keogh@sc.sni.ie
From: lothar@cyrcle.uucp (Bob Trembley)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: Windows NT and SoundBlaster Pro CD-ROM
Summary: Creative Labs will be writing an NT driver for the SBP CD
Keywords: SoundBlaster CDROM CD-ROM DRIVER Creative NT
Date: 26 Jul 92 11:25:10 GMT
Reply-To: lothar@angus.mi.org
Organization: Cyrcle Systems

> >In article <3LT9NB1w165w@cyrcle.uucp> lothar@angus.mi.org writes:
> >>He informed me that the install crapped
> >>out with a message like: "No SCSI CD-ROM detected, Install aborted."
> 
> The SB Pro CD isn't SCSI
> 

Alright Folks!

I have carved "The SB Pro CD isn't SCSI" onto my forehead!  :(

To date, only 2 people had actually sent a response that has been helpful, the
rest want to make sure I know that it isn't SCSI.  Ok.  Fine.  I now know...

I had heard that it was SCSI, but used a proprietary connector to the SB Pro.
If I was mislead, sorry.  Please don't waste any more bandwidth to inform me
that it isn't SCSI!  Ok?  :)

For your information: I got ahold of a *very* helpful tech support person at
Creative Labs who told me that they *will* be working on an NT driver to
support the SoundBlaster Pro CD-ROM drive.  I asked if I could be a
beta-tester for that driver and was told that I wouldn't even get the time
of day from Developer Support unless I was a "Registered Creative Labs
Developer."

To register as a C.L. Developer, call C.L Developer support @ 408-428-6644
and request a form.  You can also try faxing them @ 408-428-6655, but I was
told faxes have a tendency to vaporize. :)  The person I talked to wasn't
sure, but he thought that you *might* also have to buy some sort of
development kit. :(  (Again, I stress he wasn't sure since this is not for
DOS development).

Lastly, I asked if Creative Labs had a presence on the Internet and was told
that they are talking with Compu$erve about opening a forum, and one of the
tech support persons is thinking about getting on the Internet.

--
lothar@angus.mi.org (Bob Trembley)
From: martin@minster.york.ac.uk
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: Running NT with more than 16MB
Date: 30 Jul 92 21:13:06 GMT
Organization: Department of Computer Science, University of York, England

jvert@microsoft.com (John Vert) says:
> >My question concerns what happends on an ISA machine with disk controllers
> >or other expansion boards which might try to access memory above the
> > 16Mb limit of the ISA expansion bus. Does this even happend in todays
> >systems?
> 
> Yes, it happens all the time.  However, Windows NT will take care of the
> messy details and you can use all your memory just fine.

OS/2 v2.0 *still* has trouble with this! I believe - perhaps they should
have done less of the OS/2 v2.0 development on PS/2s :-)

> 
> >
> >For instance, what if some software wants to DMA a block of memory to a disk
> >or video or other type of card? If the source or destiation of the DMA
> >transfer is above 16Mb what happends? Do the DMA controllers automaticall
> >handle this case? Is there some system software which will detect this and
> >possibly do a transfer to low memory (below 16Mb) and then transfer it
> >above 16Mb to its destination?
> 
> The disk driver requests DMA transfers through the HAL (Hardware Abstraction
> Layer)  The HAL figures out that the DMA controller cannot see the memory
> above 16Mb, performs the DMA into a buffer below the 16Mb line, then copies
> the result to its final destination.  (and vice-versa when memory above
> 16Mb is the source of the DMA))
> 

What is the performance penalty of
1)	The extra copying
2)	The (presumably) limited size of the intermediate buffer
?

In particular, if I'm using the *wonderful* CreateFile option which does
the I/O directly into my address space, without going through the cache
(that is the FILE_FLAG_NO_BUFFERING option), with big reads (>100Kbytes, say)
and the memory happens not to be in the low 16Mbytes, will there be a
horrendous (and rather unpredictable) penalty?

(Actually, this *is* quite important to me!)

Thanks,

Martin
PS
  Microsoft is going to regret calling it `CreateFile'... :-)

INTERNET: martin@minster.york.ac.uk
surface:
        Dr. Martin C. Atkins
        Dept. of Computer Science
        University of York
        Heslington
        York YO1 5DD
        ENGLAND
From: silber@orfeo.Eng.Sun.COM (Eric Silber)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: Can the NT CD be read under SunOS 4.1.1 ?
Date: 24 Jul 1992 18:05:39 GMT
Organization: Sun Microsystems, Mt. View, Ca.
NNTP-Posting-Host: orfeo

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)


Newsgroups: comp.os.ms-windows.programmer.win32
From: bonneau@hyper.com (Paul Bonneau,,)
Subject: Re: network configuration?
Reply-To: bonneau@hyper.UUCP (Paul Bonneau,,)
Organization: HyperCube Inc.
Date: Fri, 31 Jul 1992 16:06:12 GMT

In article <1992Jul31.002611.17830@pony.Ingres.COM> rion@Ingres.COM (Rion Cassidy (x3357) OGT) writes:
>We have found that the network cards will not work on IRQ3 unless you 
>disable COM2.  This will be the case even if your network card will work
>under DOS or OS/2 with IRQ3 with COM2 enabled!!  Don't ask why!
>
I use IRQ 5 as suggested, and still am unable to get things
to run.  A big problem is thatr without using the graphical
install you apparently do not have access to the net stuff in
the control panel.

>I would not recommend even starting regedit, as I can make the system
>crash completely very easily with regedit.  Regedit is not for novices.
>
According to the release notes, you will have to run regini
against /winnt/tcpip./ini, to update the registry.  This means
editing the tcpip.ini file.  Be warned that you will gets
lots of warnings apparently because regini can't handle the
comments in the file.

cheers - Paul.
Newsgroups: comp.os.ms-windows.programmer.win32
From: c2s4027@tamsun.tamu.edu (Cedric Sims)
Subject: Re: Recursive folders?
Organization: Texas A&M University, College Station
Date: Wed, 22 Jul 1992 22:40:20 GMT

In article <13642@mindlink.bc.ca> Robert_Salesas@mindlink.bc.ca (Robert Salesas) writes:
>> 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 /
>\------------------------------------------------------------------------/


What is Cairo?

Ced.
From: martin@minster.york.ac.uk
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: NT not to be generally available in the UK
Date: 29 Jul 92 11:20:43 GMT
Organization: Department of Computer Science, University of York, England

Hi,
  I phoned Microsoft UK this morning, trying to find out how to get a copy
of the PDK, and was told that it is not going to be available to anyone who
wants a copy, as it is in the US. In the UK there are three ways to get a PDK

1)	Be a Microsoft Registered Developer
2)	Attend one of the (4?) NT conferences goming up soon.
	(Anyone know the details?)
3)	Write to some guy at Microsoft, and `make a case'

I must say I'm disappointed, although if (1) is not terribly expensive it
would probably be a good way to go. (3) suggests that (1) *is* expensive,
and why should I bother to go to a conference? I've already read all the
slides from the conference in San Francisco!

Martin
INTERNET: martin@minster.york.ac.uk
JANET:  martin@uk.ac.york.minster
surface:
        Dr. Martin C. Atkins
        Dept. of Computer Science
        University of York
        Heslington
        York YO1 5DD
        ENGLAND
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: printing the docs from the CD
From: yaturner@picard.agames.com (D'arc Angel)
Date: 21 Jul 92 01:04:15 GMT
Organization: The Houses of the Holy


has anyone succeeded in printing the postscript fromat docs from the
CD? my postscript printer (QMS 410) drops out of postscript and into
text mode about 1/2 thru anything I print

help!

-- 

James M. Turner     yaturner@agames.com       

Those who feel the breath of sadness, sit down next to me
From: Robert_Salesas@mindlink.bc.ca (Robert Salesas)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: Recursive folders?
Date: 23 Jul 92 01:43:52 GMT
Distribution: world
Organization: MIND LINK! - British Columbia, Canada

> Cedric Sims writes:

Two FULLY quoted messages deleted...

> What is Cairo?
> 
> Ced.
> 



This ticks me off.  WHY do people insist on quoting 1) whole articles when only
pieces are relevant 2) quoting whole articles when NONE of it is relevant!!!!!!

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: joel@vthvax.tamu.edu
Subject: Installing NT
Organization: Veterinary Teaching Hospital, Texas A&M University
Date: Mon, 27 Jul 1992 15:13:12 GMT

I'm having trouble installing WNT.  One problem is that I have to let
OS/2 remain on a bootable partition.  I know this is unsupported but
I have no choice.  I also only have 8 meg of ram.  Will NT install with
only 8 meg of ram?  Here's what i did:

- I partitioned the disk with a 1 meg primary boot partition, a primary 135 meg
  os/2 partition, and 2 135 meg extended dos partitions.

- Installed os/2 with it's (flexboot) program.

- Rebooted.  Selected dos from os/2's bootloader. 

- Used dos2nt to install NT on C drive and edited the ini files.

- Rebooted.  Selected dos from os/2's boot manager, which brought
  up NT's boot manager.  Selected NT...

Windows NT
Portable Bootloader
(c) Microsoft

Warning! - Incorrect EISA memory configuration info.
Windows NT will use the ISA memory configuration information.

Loading...

MS Windows NT
MnInit: 8192 Kb Available memory
*** Fatal system error: 0x00000069
*** Phase 1 i/o init failed.
(hang)

I seems to me like os/2 and it's bootloader is not my problem.  Is it my 
memory or is it really the EISA configuration?  Since dos and os/2 work 
correctly,  I would think the EISA configuration sould work under NT.

I know this is a bit of a kludge but could someone point out any invalid 
assumptions i have made?

Joel

Newsgroups: comp.os.ms-windows.programmer.win32
From: jvert@microsoft.com (John Vert)
Subject: Re: Installing NT
Date: 30 Jul 92 07:37:20 GMT
Organization: Microsoft Corporation

In article <Bs5v9D.3p@fmsrl7.srl.ford.com> vscarafi@eccdb1.pms.ford.com (Vincent F. Scarafino) writes:
>joel@vthvax.tamu.edu writes:
>> I'm having trouble installing WNT.  One problem is that I have to let
>> OS/2 remain on a bootable partition.  I know this is unsupported but
>> I have no choice.  I also only have 8 meg of ram.  Will NT install with
>> only 8 meg of ram?  Here's what i did:
>> 
>> - I partitioned the disk with a 1 meg primary boot partition, a primary 135 meg
>>   os/2 partition, and 2 135 meg extended dos partitions.
>> 
>> - Installed os/2 with it's (flexboot) program.
>> 
>> - Rebooted.  Selected dos from os/2's bootloader. 
>> 
>> - Used dos2nt to install NT on C drive and edited the ini files.
>> 
>> - Rebooted.  Selected dos from os/2's boot manager, which brought
>>   up NT's boot manager.  Selected NT...
>> 
>> Windows NT
>> Portable Bootloader
>> (c) Microsoft
>> 
>> Warning! - Incorrect EISA memory configuration info.
>> Windows NT will use the ISA memory configuration information.
>> 
>> Loading...
>> 
>> MS Windows NT
>> MnInit: 8192 Kb Available memory
>> *** Fatal system error: 0x00000069
>> *** Phase 1 i/o init failed.
>> (hang)
>> 
>> I seems to me like os/2 and it's bootloader is not my problem.  Is it my 
>> memory or is it really the EISA configuration?  Since dos and os/2 work 
>> correctly,  I would think the EISA configuration sould work under NT.
>> 
>> I know this is a bit of a kludge but could someone point out any invalid 
>> assumptions i have made?
>> 
>> Joel
>> 
>I get the same EISA memory configuration error when I bring up NT.  It doesn't
>cause me any problems.  I have 12 meg of memory, though.  Is your swap file
>at least 20 meg in size?  That was documented as requirement for NT to come
>up.
>
>Vince


The EISA memory warning is just that, a warning.  On EISA machines, NTLDR 
scans the EISA bus in order to determine how much memory is available.
This usually works, but we have found a number of systems that do not 
update the EISA configuration information automatically when memory is
added to the system.  So NTLDR also checks the ISA memory configuration
with the standard BIOS call.  This ALWAYS works (probably because this is
the one DOS uses, so PC makers actually test it!)

So this warning just means that the ISA BIOS call says 8Mb (or 12Mb) but
the EISA configuration reports less.  (probably 4 or 1Mb)  You can make
this warning go away by running the EISA configuration disks and manually
updating the entry for installed memory.  I think this is in the release
notes.

When NTLDR detects this incorrect EISA configuration, it just
ignores the EISA data and uses the ISA data.  It is not responsible for
your system failing to boot.

(Why use the EISA at all if it's not always right?  It allows us to 
support EISA machines with more than 64Mb of RAM, and it allows us to 
support EISA machines with discontiguous chunks of RAM.  The ISA BIOS
call will not handle either of these cases.)

    jvert@microsoft.com
    Not a Microsoft Spokesperson
    I just work here
From: abeals@autodesk.com (Andrew Scott Beals -- KC6SSS)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: More TCP/IP install problems
Keywords: Windows NT, TCP/IP
Date: 31 Jul 92 01:41:57 GMT

Acutally, I'm following up to my own article which is still spooled.  )-:

So, I figured "Why not" and ran regini tcpip.ini again.  And it picked
up the missing item from before.

Now the amazing disappearing window says:

	BUILD down from tcp
	open("\Device\Streams\tcp", O_RDWR) => 0
	DOWNSTREAM to ip
	open("\Device\Streams\ip", O_RDWR) => 0
	DOWNSTREAM to loop
	open("\Device\Streams\loop", O_RDWR) => 0
	ioctl(0, I_LINK, 0)
	failed to link stream 0 under driver 0AnnounceServiceStatus: Currenstate 1
	[blahblah]
	Win32ExitCode: 4294967295

And an entry appears in the System event log saying that the device
Elnkii01 is incorrectly configured, but not what it doesn't like about
it.  It isn't memory mapped [flag is set to 0], and all the other parameters
are correct...
--
Andrew Scott Beals	abeals@autodesk.com, kc6sss@n6ldl.#nocal.ca.usa.na
50.115MHz
Vivu libere a>u mortu!
Newsgroups: comp.os.ms-windows.programmer.win32