HDTenEightyP/NetNews huggingface dataset:
From: dale@mkseast.uucp (Dale Gass)
Subject: Re: POSIX interface/Access to WIN32 calls
Organization: Mortice Kern Systems, Atlantic Canada Branch
Date: Mon, 25 Jan 1993 19:05:39 GMT

johnhall@microsoft.com (John Hall) writes:
>I am not an official MS Spokesbeing.  However, This is
>how I view the problem:
	.
	.
	.
>All in all, it is probably easier for MS to provide improved
>libraries and a little extra functionality (if necessary)
>in Win32 instead of trying to support mixing subsystems.

I can see your point, but I don't think it would have been as difficult
to extend the NT API in a Posix-compliant way, as it would have been to
create a whole new subsystem.

MicroSoft is going to have to add support for the Posix primitives anyway
in their new subsystem; adding these to the NT API would have made the
whole picture a lot tidier, IMHO...

(Instead, no doubt, they are adding the support required for the Posix
primitives in the subsystem via another raft of undocumented NT API's...)

-dale
-- 
 Dale Gass, Mortice Kern Systems, Atlantic Canada Branch
Business: dale@east.mks.com, Pleasure: dale@mkseast.uucp
Newsgroups: comp.os.ms-windows.programmer.win32
From: jallard@microsoft.com (James 'J' Allard)
Subject: Re: How to start up TCI/IP at boot time?
Date: 22 Jan 93 03:31:31 GMT
Organization: Microsoft Corporation

In article <1993Jan8.144909.24196@solaris.rz.tu-clausthal.de> hochstae@allfiwib1.wiwi.uni-marburg.de (Christoph H. Hochstaetter) writes:
>In <KEVIN.93Jan6171502@calamityjane.edscom.demon.co.uk> kevin@edscom.demon.co.uk (Kevin Broadey) writes:
>>I know this can be done, but I've forgotten the magical incantation...
>>
>>Using the Registry Editor you can modify an attribute in
>>
>>    HKEY_LOCAL_MACHINE/SYSTEM/ControlSet001/Services/TcpipSvc
>>
>>that starts up TCPIP at boot time, just as if you'd typed
>>
>>    net start tcpipsvc
>>


The more "friendly" way to achieve the same results would be:

o Log in as "administrator"
o Start the "Services" control panel applet
o Select the "Tcpip" service
o Choose "Configure..." and select "Automatic"

This goes for other services as well. HTH.

-- 
_______________________________________________________________
J. Allard                                 jallard@microsoft.com
Program Manager of TCP/IP Technologies    work: (206)882-8080
Microsoft Corporation                     home: (206)860-8862
From: ar364@cleveland.Freenet.Edu (Jim Shaw)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: NT not multiuser, then Unix is not a competing OS
Date: 23 Jan 1993 14:34:41 GMT
Organization: Case Western Reserve University, Cleveland, Ohio (USA)
NNTP-Posting-Host: slc10.ins.cwru.edu


Perhaps, instead of being a multi user O/S, NT is being designed
for a peer-to-peer LAN/WAN environment.  Take a step back and 
look for strategic threads running thru all of Microsoft's 
products.

----------------------------------------------------------------
Jim Shaw
Figgie Technology Center
Strongsville, OH
shaw@bronto.wariat.org
-- 
shaw@thorr.wariat.nshore.ncoast.org
In the valley of the blind, the one-eyed man is king!
Newsgroups: comp.os.ms-windows.programmer.win32
From: edm@wrs.com (Ed McClanahan)
Subject: Re: 16-bit Windows 3.1 vs Win32s thunking
Organization: Wind River Systems, Inc.
Date: Fri, 22 Jan 1993 23:45:45 GMT

alistair@microsoft.com (Alistair Banks) writes:

>                             Well no, because we set the 16-bit
>segment registers to zero, so cs=ds=es=gs=fs=0, and we just use
>32-bit addressing - this is a portable concept, particularly to
>RISC systems which don't have "segment" registers a la x86

First, let me be another to say thanks to Alisair for the frequent
postings and uploads - and presumably a stong Internet evangelist
inside the WinNT/Win32 Microsoft community...

I think Microsoft has made the correct choice of going with a
straight flat 32-bit address space.  However, most of the confirmed
or potential targets for NT that I have heard suggested ALL support
a larger than 32-bit address space:

  x86     - 48 bits
  Pentium - 64 bits
  Alpha   - 64 bits
  Mips    - 64 bits
  PowerPC - 64 bits (???)
  SPARC   - 32 bits (soon to be extended to 64?)
  HP-PA   - 48 bits

My impression is that most new "general purpose" processors are
headed for greater than 32 bits, while "embedded systems" processors
top out at 32 bits (e.g. i960, Hobbit, ARM).

Still, I agree that sticking with 32-bits helps "portability".
However, having been formally at HP for 8 years, I have to
point out that HP-PA is a 48-bit SEGMENTED RISC processor,
where the segment registers are specified as 32-bits but
currently all implementations allow only 16-bits.  Even HP,
however, sets these segment registers based on a processes'
context so that "short" 32-bit addresses may be used.

Once again, thanks for the Internet "support", Alistair!

Ed "CM are me" McClanahan
-- 

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

  Edward McClanahan
Newsgroups: comp.os.ms-windows.programmer.win32
From: zrepachol@cc.curtin.edu.au
Subject: Re: REQUIREMENTS TO RUN NT - HELP
Organization: Curtin University of Technology
Date: Sun, 24 Jan 1993 17:30:51 GMT

In article <1993Jan22.224431.25788@microsoft.com>, johnhall@microsoft.com (John Hall) writes:
...
> a 16-bit bus  (ISA for Industry Standard Architecture, the IBM AT
> bus) has 16 data bits and 24 address bits.  Yes, you can add memory
> to 16Mb but you may have to replace your current memory entirely
> depending upon your computer design.
> 

Interesting you should say this. Let me make a few preliminary comments on
memory and some system boards. We recently when to expand some 386DXs to 8MB
to run the Oct beta. They trashed ever few minutes. A quick look-see points
to several problems in the memory area: 1 not enought decoupling caps for the
SIMMS and driver, 2 power plane has too high an impedence to source the several
amps needed for the ?? nsec as the memory access starts. 3 undershoot in the
RAS/CAS lines. Result is flaky memory system. BTW, this is not just on NT,
you can't run DOS either.

Anyone else seen this?

~Paul
From: brian@jaguar.cs.utah.edu (Brian Sturgill)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: REXX, OS/2, and NT
Date: 27 Jan 93 23:20:54 GMT
Organization: University of Utah Computer Science

In article <3132.1101.uupcb@satalink.com> bert.tyler@satalink.com (Bert Tyler)  writes:
>  brian@jaguar.cs.utah.edu (Brian Sturgill) writes...
>
>BS>OS/2 does have one feature that NT doesn't that you might need... REXX.
>BS>If you need an imbedded scripting language, then REXX fills that
>BS>niche rather well, NT will eventually have ObjectBasic to fill this
>BS>need, but it's not there yet.
>
>Brian and everybody, just out of curiosity - is there anything
>(technically or legally) that prevents someone from implementing
>REXX under Windows NT?  How about the same question for the variant
>of REXX I've been hearing described as "visual REXX"?

Apparently not, the Microsoft catalog of win32 apps shows several such products
already.  (You can ftp the catalog from the site in my .sig.)

>
>(Note that I've never seen *either* variant of REXX in action, but
>that I've seen lots of approving comments about them in the OS/2
>conferences.)

Not to knock REXX, but it's not the language that I find so great, it's
the idea of having a system-wide embeddable macro/scripting language.
Users only have to learn one language and developers don't need to implement
their own, but rather simply add extentions to the embedded language.

What I'd really like to see is the same sort of hooks that REXX provides,
but in a manner that different users can use different languages for
the control structures.  An IBM mainframe person might prefer REXX, I'd
prefer a C-like one as in Brief, and DOS people might prefer a BASIC-like one.
The idea here is that the underlying OS would provide an API that calls
the embedded language specifed by the user, and has a system defined ability
to add extentions to any embedded language that follow its guidelines.
Unfortunately I've not seen this done.

My understanding is that Microsoft will provide a version of BASIC called
ObjectBasic that will provide the same sort of function that REXX does in
OS/2, but it would be nice if they did not limit the embedding API only
to ObjectBasic.

>                   Bert Tyler   (bert.tyler@satalink.com)
>---
> . DeLuxe./386 1.25 #343sa . Did you expect mere proof to sway my opinion?

Brian
-- 
C. Brian Sturgill                  Windows, WfW, Windows NT and some OS/2 2.0
University of Utah                 information available via anonymous ftp to
Center for Software Science        easy.cs.utah.edu. Also all my Tidbits posts.
brian@cs.utah.edu; CIS: 70363,1373     Windows NT SDK: $69; (800) 227-4679
From: jeff@claw.clearpoint.com (Jeffrey J. Griglack)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: Windows Tools Sampler
Date: 28 Jan 93 13:52:40 GMT
Reply-To: jeff@claw.clearpoint.com
Organization: Clearpoint Research, Hopkinton, MA

On 27 Jan 93 18:18:52 GMT, jmalloy@itsmail1.hamilton.edu (Joseph T. Malloy) said:

J> In article <1k3eofINNctj@umbc5.umbc.edu> themos@umbc.edu (Mr. Themos Pentakalos) writes:
>Hi everyone,
>
>I assume most of you who have been using NT received a letter from
>MS about a "free offer" for something called the Tools Sampler.
>There is a fax number which we are supposed to reply to but I have not
>been able to get through. I believe the fax is probably turned off
>because I have tried to send throughout the 24 hour day. 
>
>Anyone have any input on this?
>
>-Themos

J> I did get through, but it wasn't easy.  In fact, I ended up using a copy
J> of the form in Word through WinFax Pro...which just kept redialing and
J> redialing and redialing...

J> Don't give up!

I did the same thing, but, it was the stupidest FAX setup I have ever
seen.  It would answer after about 8 rings, then play a recorded
message telling you that this was a FAX line and that you should stay
on the line if you want to send a FAX.  By this time, my modem had
timed out and hung up (actually, the modem hung up after the 5th or
6th ring, but I picked up the phone).  Anyway, it was finally sent
last night at around 9:00, almost 12 hours after my first attempt.
--

-------------------------------------------------------------------------------
|Jeff Griglack             |"The role of the large woman in horn-rimmed glases|
|jeff@claw.clearpoint.com  | was played by Arlene Carmichael."                |
|jeff@fang.clearpoint.com  |                                                  |
-------------------------------------------------------------------------------
From: jmalloy@itsmail1.hamilton.edu (Joseph T. Malloy)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: Windows Tools Sampler
Date: 27 Jan 93 18:18:52 GMT
Organization: Hamilton College - Clinton, NY

In article <1k3eofINNctj@umbc5.umbc.edu> themos@umbc.edu (Mr. Themos Pentakalos) writes:
>Hi everyone,
>
>I assume most of you who have been using NT received a letter from
>MS about a "free offer" for something called the Tools Sampler.
>There is a fax number which we are supposed to reply to but I have not
>been able to get through. I believe the fax is probably turned off
>because I have tried to send throughout the 24 hour day. 
>
>Anyone have any input on this?
>
>-Themos

I did get through, but it wasn't easy.  In fact, I ended up using a copy
of the form in Word through WinFax Pro...which just kept redialing and
redialing and redialing...

Don't give up!

Joe
From: jmbrown@netcom.com (John M. Brown)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Novell Requester for NT x86
Keywords: IPX NT NOVELL NETWARE
Date: 26 Jan 93 22:21:01 GMT
Organization: Netcom - Online Communication Services  (408 241-9760 guest)

Available at ftp.novell.com in novlib/01  file called NWNT.ZIP

THis file contains the basic stuff to have a NT x86 box connect to 
a Novell File Server.  Beware there ARE some gotcha's!!!

Read the README file FIRST!!!

This is also mirror'd on Compu$pend

jmbrown@netcom.com
Newsgroups: comp.os.ms-windows.programmer.win32
From: yikes@netcom.com (Michael Brill)
Subject: Memory management from Unix to Win32
Organization: Netcom Online Communications Services (408-241-9760 login: guest)
Date: Sat, 23 Jan 1993 04:18:08 GMT


I'm developing an app on the NeXT that I'd like to take the bulk
of to either Windows and/or Macintosh.  I think I know how to 
port everything but the UI and memory management.  Note that the
pieces of the app I want to port are just plain old ANSI C.

As far as the UI goes, I'm not going to worry about now.  What I
am worried about is memory management.  I've scanned through the
Windows docs and understand how memory management works there
(getting handle, locking, operating, unlocking) and I'm looking
for an established scheme to make the port seamless between Unix
and Windows/Mac.

Does targeting Win32 make life any easier for me?

Thanks, ...Michael Brill (yikes@netcom.com)
-- 
----
Newsgroups: comp.os.ms-windows.programmer.win32
From: harp@martha.utcc.utk.edu (harp)
Subject: Re: Next SDK drop
Organization: University of Tennessee Computing Center
Date: Wed, 27 Jan 1993 02:13:12 GMT

In article <1993Jan27.012754.15020@ttinews.tti.com> terence@tanru.tti.com ( Terry) writes:
>
>I spoke with our NT Beta contact today.  He didn't have an official
>date but said the next SDK drop should occur in late February.  This is
>Microsoft we're dealing with so we'll have to see!?
>
>
>Terry (terence@soldev.tti.com)

An article in last week's PCWEEK said that the next drop would be between 4
and 6 weeks from then.  Sounds about right to be the end of february.
Doesn't sound like a heck of a lot of time to beta test it for it's release
in May, but who knows.  What I've seen so far doesn't look to bad.

Sean Harp
University of Tennessee

Newsgroups: comp.os.ms-windows.programmer.win32
From: instm@helios.rz.tu-clausthal.de (Stefan Mueller)
Subject: Re: New ATI NT drivers on Compuserve
Organization: Techn. Univ. Clausthal
X-Newsreader: Tin 1.1 PL5
Distribution: na
Date: Thu, 28 Jan 1993 08:31:29 GMT

Today I got a Mail that version 6 is said to be wacko ! 
It can end in reinstallation. So, if you try it out, you should
take a backup first ...


 Ciao, Stefan

instm@helios.rz.tu-clausthal.de
From: 90sra@eng.cam.ac.uk (S.R. Atkins)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: Q: Joining Beta Program
Date: 25 Jan 93 23:53:00 GMT
Organization: cam.eng

gary@nshade.uah.ualberta.ca (Gary Ritchie) writes:

>> >How do I join the NT beta program?  I have the requisite hardware,
>> >now I want the fabled CD-ROM.
>> 
>> Call Microsoft Developer Services at (800) 227-4679.  The CD only is  
>$69,
>> CD plus docs is $399.

>Does that number work in Canada as well?  I'd try it, but I can't dial any  
>numbers starting with 1 from my phone here...

I've been given +1 206 882 8080 as Microsoft Sales US......why is there no
way for the rest of the world to dial 800 numbers (even if we had to pay for
them)?
Newsgroups: comp.os.ms-windows.programmer.win32
From: msw@world.std.com (Mark S Warren)
Subject: Windows NT boot failure: 0x0000004E
Organization: The World @ Software Tool & Die
Distribution: usa
Date: Mon, 25 Jan 1993 16:06:45 GMT

My October Beta refuses to boot, failing with a

	*** Fatal System Error: 0x0000004E
	*** The Memory management PFN list is corrupt

	Kernel debugger using COM2:

I haven't yet received my package from Compuserve, so I'm hoping
someone in Usenet land can lend sm some advice.

The system is a Hawk 486, 25MHz, 16Mbytes, internal cache only,
Adaptec 1542b.

Previosly, I was getting error 0x00000069, but that one was cured (?) when
I upgraded the BIOS and MCODE proms on my Adaptec board.

Thanks in advance...
-- 

 == Mark S. Warren    msw@world.std.com     (508) 772-6045 ==
Newsgroups: comp.os.ms-windows.programmer.win32
From: jai@cs.albany.edu (Jai Kumar)
Subject: GNU Make for NT ??
Originator: jai@karp.albany.edu
Organization: The University at Albany, Comp. Sci. Dept.
Date: Fri, 22 Jan 1993 23:13:19 GMT

I would like to know if GNU-make has(latest version) 
been ported to NT.  If anyone has pointers to this 
please post it to this newsgroup or e-mail to 
"jai@cs.albany.edu".
Any info. about other GNU or UNIX tools port to NT
would also be welcome. 

Thanks
Newsgroups: comp.os.ms-windows.programmer.win32
From: johnhall@microsoft.com (John Hall)
Subject: Re: POSIX interface/Access to WIN32 calls
Date: 22 Jan 93 23:20:51 GMT
Organization: Microsoft Corporation

In article db@argon.Eng.Sun.COM (David Brownell) writes:
| I'm not after a "because that's the way it's built" answer, but rather
| one that explains why that's a supposed to be good thing.

I am not an official MS Spokesbeing.  However, This is
how I view the problem:

Think of NT as a virtual operating system where three different
subsystems (at present) take the primitive objects and proceedures
available in NT and implement their own particular ideas of
security, process structure, and system capabilities.

Each subsystem is internally consistant.  However, mixing
calls between internally consistant but diverse operating
systems (their ideas on process structures, for example)
would lead to an explosion of permutations and special cases.
Said increased complexity would undermine the quality
standards MS is striving for.

All in all, it is probably easier for MS to provide improved
libraries and a little extra functionality (if necessary)
in Win32 instead of trying to support mixing subsystems.



-- 
-------------------------
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: schiers@mcshh.Hanse.DE (Carsten Schiers)
Subject: Re: High color resolution graphics cards
Organization: Point of Presence & MCS Hamburg
Date: Thu, 21 Jan 1993 22:24:04 GMT

TI Ultra +/pro will offer you:

Win 3.1 24 bit BETA
Win NT  16 bit BETA

24 is max. 800x600, 16 is max. 1024x768.

Win NT will only work with ISA machines that have max. 12 MB.

Let me say: they work, somehow. They are BETA. It takes some time to
shuffle 24 bits per pixel, but as I said, it works.

CU Carsten.
From: mizo@sevax1.cse.canon.co.jp (Hideo Mizoguchi)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Win(NT) SCSI device driver
Date: 26 Jan 93 01:09:08 GMT
Distribution: comp
Organization: Canon Inc., Kawasaki , JAPAN

Hello,
Would someone please tell me what is a good starting point to learn
how to write a windows SCSI device driver. I am complete novice in
writing device drivers for whatever OS. Does it make any difference
if the target is Win or WinNT?
I browsed through Developer Network CD-ROM (Pre-release 1) but could not
get much information.
Please send any info or a reference to a good book or an article to:
	mizo@sevax1.cse.canon.co.jp
Thanks in advance

Hideo Mizoguchi
Newsgroups: comp.os.ms-windows.programmer.win32
From: sasbxc@tadpole.unx.sas.com (Brian Corcoran)
Subject: CreateProcess for Dos sessions
Originator: sasbxc@tadpole.unx.sas.com
Date: Thu, 28 Jan 1993 20:56:28 GMT
Organization: SAS Institute Inc.
Keywords: CreateProcess


  I have a question regarding CreateProcess invoking 
CMD.EXE.  How to you get parameters to the newly created
DOS session?  In the code I am working on, they seem to
be ignored.  I want to invoke the command processor to
send DOS commands to a newly created session.

  I also need to find a way to wait for the session action
to complete.  I can use WaitForSingleObject to wait on the
created process to exit, but I would rather wait on some
kind of user input after the DOS command was executed.

  Thanks in advance.

 - Brian Corcoran             sasbxc@tadpole.unx.sas.com

   SAS Institute
   Cary, NC
From: fn@junior.mathtok.polymtl.ca (Francois Normant)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: SQL-Server available for NT?
Date: 26 Jan 93 16:59:15 GMT
Organization: Mathematiques Appliquees - Ecole Polytechnique - Montreal

In article <1993Jan25.111419.8508@solaris.rz.tu-clausthal.de> hochstae@allfiwib1.wiwi.uni-marburg.de (Christoph H. Hochstaetter) writes:
>
>Microsoft has announced SQL-Server for NT
>
>Christoph

Do you have any pointer to the official annoucement ?
Microsoft Canada (Ontario) does not knwo anything about this product.

Thanks in advance.


-- 
Francois Normant (francois_normant@mathappl.polymtl.ca)
Departement de Mathematiques Appliquees - Ecole Polytechnique
C.P. 6079 - succursale A
Montreal - Quebec - Canada - H3C 3A7
Newsgroups: comp.os.ms-windows.programmer.win32
From: johnhall@microsoft.com (John Hall)
Subject: Re: REQUIREMENTS TO RUN NT - HELP
Date: 22 Jan 93 22:44:31 GMT
Organization: Microsoft Corporation

In article eng10056@nusunix1.nus.sg (LAU YIN CHENG) writes:
| I am currently haveing a 486DX-33 system with 4MB memory and the system
| is of 16-bit bus structure.
| 
| Can NT run on a 16-bit bus structure?
| Does Win32 need a 32-bit structure?

a 16-bit bus  (ISA for Industry Standard Architecture, the IBM AT
bus) has 16 data bits and 24 address bits.  Yes, you can add memory
to 16Mb but you may have to replace your current memory entirely
depending upon your computer design.

NT runs just fine on an ISA bus.


-- 
-------------------------
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: instm@helios.rz.tu-clausthal.de (Stefan Mueller)
Subject: NT-Crash ! What Can I Do ?!?!?!
Organization: Techn. Univ. Clausthal
X-Newsreader: Tin 1.1 PL5
Date: Thu, 28 Jan 1993 08:39:33 GMT

Hello Friends !

Today my NT crashed in a very strange way : at boot-time, there had been
a disk in drive a: that didn't let the system boot. (OK, that's not strange...)
I pulled the disk out but since that, NT won't boot anymore !!!!!

At boot-time I can only see : 00001677 00A6CFEF 00000D00 00003000
After that, the system hangs or loops the colons ...

Please HELP me soon !!!!

Thanks in advance, Stefan

instm@helios.rz.tu-clausthal.de
instm@139.174.2.11

Newsgroups: comp.os.ms-windows.programmer.win32
From: johnhall@microsoft.com (John Hall)
Subject: Re: 16-bit Windows 3.1 vs Win32s thunking
Date: 22 Jan 93 22:39:24 GMT
Organization: Microsoft Corporation

I'm just adding my $.02 to what alistair said.

In article jagrant@emr1.emr.ca (John Grant) writes:
| So what's the difference?
| -------------------------
| If the NT app is still doing the same thing as the 16-bit app compiled
| under Windows 3.1, i.e. switching pointers back & forth between linear
| and segmented values, then what is the point of Win32s at least for
| the memory stuff.

Huge pointers are 16:16 addresses with compiler support for 
increasing the offset (the upper 16bits) when necessary.
This means that incrementing a huge pointer is a function call.

Win32s lets you use, essentially, real 32bit pointers.  This
means that when you increment a pointer in Win32s code, you
add one to a variable.

For code that manipulates in memory structures a lot, the
code speadup between the two models is very large.  It more
than offsets for the overhead of switching from the 32bit
address to a 16:16 address when calling a Windows 3.1 function.

There are other advantages to a Win32s process.  I believe
sparse memory will be supported in the final release, 
for example.



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