HDTenEightyP/NetNews huggingface dataset:
From: dwightm@microsoft.com (Dwight Matheny)
Subject: Re: Windows NT October Beta
Date: 11 Jan 93 21:07:24 GMT
Organization: Microsoft Corp.

>>Wow! I'm still waiting for my copy!! MS in Sweden are not TOO interested
>>in the developers. I'v phoned them three times last year, and everytime
>>they just answered that I would get my October release in 2 weeks! Well,
>>right now I have been waiting about 10 weeks!
>>Why dosen't the developers in Sweden get their copy?

Tomas, I asked the SDK product manager in Sweden to respond to your 
concerns. Both of us have tried to send you email without success. 
His response is below.

Thanks,
Dwight (MS)

Hej Tomas!

Jag maste brja med att be om ursakt for att du int fatt din NT SDK
annu.

Tyvarr gick det lite fort i juli nar de forsta utgavan kom. Da visste vi
i Sverige inte annu att de senare betorna skulle skickas ut gratis. Darfor
gjorde vi inte nagon speciell forteckning pa dem som bestallde da.

Nar vi senare skulle skicka ut uppdateringen i oktober (som av olika
skal, for oss mycket pinsamma, inte kom hit forran i slutet av novenber)
upptackte jag att vart datasystem inte inneholl nagra speciella rutiner
for att halla reda pa gamla kunder.

Darfor har det for oss inneburit manuellt arbete med varje order (och
de ar ju som du forstar ganska manga). For att dessutom inte behova
gora omm detta misstag och for att det inte skall ta nagon extra tid att
skicka nasta uppdatering till dig, har vi redan nu lagt in de tva framtida
uppdateringarna i ordersystemet.

Jag vill an en gang be om ursakt for det intraffade och hoppas att det
ar en liten trost att vi eliminerat nagra felkallor till nasta forsok.

Med vanliga halsningar
Microsoft AB

Michael Buczek
Produktchef, utvecklingsverktyg
From: tad@wrq.com (Tad Marshall)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: Installation adveNTures with NT
Keywords: Speedstar 24x, ET4000
Date: 4 Jan 93 22:30:07 GMT
Article-I.D.: shelley.1iadpfINN2lg
Organization: Walker Richer & Quinn, Inc., Seattle, WA
NNTP-Posting-Host: elmer.wrq.com

In article <47888@ogicse.ogi.edu> rogere@ogicse.ogi.edu (Roger Ellingson) writes:
>In article <EBROWN.92Dec29120203@bud_light.kodak.com> ebrown@tap.kodak.com writes:
>>
>>The ET4000 drivers do work for the Diamond Speedstar 24. That
>>is what I am using.
>>
>Could someone point me to where these et4000 drivers are located?
>I think I have tried all et*.* sys and ts*.* dll files on both
>July and Oct releases of NT and have not been able to get a 
>24X to run at high res on Oct NT.
>
>Are the correct drivers the Oct NT ET4000.sys drivers?
>Is it still necessary to copy files to vga.sys and vga.dll?

The Diamond SpeedStar 24 and 24X use different accelerator chips.  The
24X uses the Western Digital 90C11 (I may have the model number wrong,
but this is close), not the ET4000.  The October CD doesn't have any
driver for the Western Digital chip.

On a goof, I tried using a Compaq driver for the WD chip in their new
(ProLinea?) machines and it mostly worked in 800x600x16 mode, though there
was a lot of funky looking video noise on the screen.  I was unable to get
the Compaq driver to drive the SpeedStar 24X at 1024x768x16 -- it looked
like the monitor wasn't syncing up right, though it's a 5FG and can sync
at pretty high rates.

Bottom line -- you are stuck in VGA mode on your 24X until someone makes
a SpeedStar 24X compatible driver.

-- Tad
Newsgroups: comp.os.ms-windows.programmer.win32
From: jinho@iti.gov.sg (Tan Jin Ho)
Subject: NT Object Manager parse method
Organization: National Computer Board, Singapore
Date: Mon, 11 Jan 1993 15:30:33 GMT

Hi, I'm looking for more information on NT's Object Manager,                    
but don't have access to NT Oct SDK (yet).                                      
Could someone please tell me what argument(s) the Object Manager
parse method take in addition to the partial object name ? It                   
seems that NT's parse method is very similar (in concept) to 
DCE CDS's junction point. Any ideas how junction point
is done too ?                                         

Thanks,
Jin-Ho
jinho@iti.gov.sg

Newsgroups: comp.os.ms-windows.programmer.win32
From: hochstae@allfiwib1.wiwi.uni-marburg.de (Christoph H. Hochstaetter)
Subject: Re: X-Windows and NT
News-Software: IBM OS/2 PM RN (NR/2) v0.16 by O. Vishnepolsky and R. Rogers
Reply-To: hochstae@allfiwib1.wiwi.uni-marburg.de (Christoph H. Hochstaetter)
Organization: Techn. Univ. Clausthal
Date: Fri, 8 Jan 1993 14:21:35 GMT

In <1iecr4INN5n5@news.uni-paderborn.de> toddy@uni-paderborn.de (Thomas Rose) writes:
>Is it possible to install and run X11R5 Libarys and programs on a NT
>machine. Is there an implementation up to now ?
>
>I don't like the program mananger, and i think the best desktop would
>be X-Windows !
>

I uploaded W32CAT.ZIP to cica. It contains a Winword 2.0 Document with
available Software for NT. You'll find an X-Windows Server there too.

Christoph
-------------------------------------------------------+-----------------------
Christoph H. Hochstaetter, Philipps-University Marburg | Universitaetsstr. 25
Internet: hochstae@allfiwib1.wiwi.uni-marburg.de       | D-W-3550 Marburg
Bitnet  : HOCHSTAE AT DMRHRZ11                         | Germany
Fido    : 2:243/660                                    | Phone +49-6421-28-7092
Fax     : +49-6421-28-4858                             |
Newsgroups: comp.os.ms-windows.programmer.win32
From: hochstae@allfiwib1.wiwi.uni-marburg.de (Christoph H. Hochstaetter)
Subject: Re: How to start up TCI/IP at boot time?
News-Software: IBM OS/2 PM RN (NR/2) v0.16 by O. Vishnepolsky and R. Rogers
Reply-To: hochstae@allfiwib1.wiwi.uni-marburg.de (Christoph H. Hochstaetter)
Organization: Techn. Univ. Clausthal
Date: Fri, 8 Jan 1993 14:49:09 GMT

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
>
>What is the attribute and what is its value?
>

Don't use ControlSet001, but CurrentControlSet. The attribute you need
to change is the START attribute. Set it to 0x1 to start at boot time.

Christoph
-------------------------------------------------------+-----------------------
Christoph H. Hochstaetter, Philipps-University Marburg | Universitaetsstr. 25
Internet: hochstae@allfiwib1.wiwi.uni-marburg.de       | D-W-3550 Marburg
Bitnet  : HOCHSTAE AT DMRHRZ11                         | Germany
Fido    : 2:243/660                                    | Phone +49-6421-28-7092
Fax     : +49-6421-28-4858                             |
From: tad@wrq.com (Tad Marshall)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: Registry woes
Date: 7 Jan 1993 02:08:02 GMT
Organization: Walker Richer & Quinn, Inc., Seattle, WA
NNTP-Posting-Host: elmer.wrq.com

In article <1993Jan6.183252.3612@berlioz.nsc.com> mcdan@berlioz.nsc.com (Eric McDaniel) writes:
>I'm having a problem making changes to the registry on my machine.
>I can log in as administrator and use regedit to make changes, but
>when I reboot all the changes are gone.  I've tried to change
>permissions, add & delete keys, add and delete values -- nothing
>seems to persist across reboots.
>
>This is on a Dell System 425E with 12MB RAM, running the October
>Beta release.  It is extremely slow running NT, but I see no
>reason for the problems I'm having.  I have no problems doing
>all the above operations on my other machine, a Compaq 486/50L.
>
>Any suggestions?

The MACHINE section of the registry is rebuilt on each reboot.  It is supposed
to contain current actually found stuff, rather than configuration info.

Which sections are you editing?

-- Tad
Newsgroups: comp.os.ms-windows.programmer.win32
From: hochstae@allfiwib1.wiwi.uni-marburg.de (Christoph H. Hochstaetter)
Subject: Re: Two beginner's questions
News-Software: IBM OS/2 PM RN (NR/2) v0.16 by O. Vishnepolsky and R. Rogers
Reply-To: hochstae@allfiwib1.wiwi.uni-marburg.de (Christoph H. Hochstaetter)
Organization: Techn. Univ. Clausthal
Date: Fri, 8 Jan 1993 14:43:17 GMT

In <1993Jan6.223149.403@emr1.emr.ca> jagrant@emr1.emr.ca (John Grant) writes:
>In article <1993Jan6.135141.11288@solaris.rz.tu-clausthal.de> hochstae@allfiwib1.wiwi.uni-marburg.de (Christoph H. Hochstaetter) writes:
>>In <1icf97INNf7i@flop.ENGR.ORST.EDU> gunnelj@curie.CS.ORST.EDU (John A. Gunnels) writes:
>[...stuff deleted...]
>
>>In the registry, there is also a section called INI-File Mapping, which
>>causes that Windows 3.x apps, that issue WriteProfileString or
>>WritePrivateProfileString to write the data in the registry. You can
>>choose between storing on a per user basis or per machine basis. This
>>causes, that Win 3.x apps store certain things on per user basis.
>
>       Oh no!  Is this true!  In Windows 3.1, I've been using the
>       ...PrivateProfileString functions to maintain a script file
>       of data descriptors, rather than a *.INI file for the app.  The
>       file is not in the windows directory and is not used for the
>       app config.  Instead it resides with the data files used by the app
>       and contains various info about the files.  I want it to
>       remain ASCII, so it can be edited and I want it to remain in
>       the directory where my data resides.
>
>       When I move to NT, does this mean that even the ...Private...
>       stuff will go into the registry in the NT directory!?!?!?
>       If this is true, I will have to write my own replacement
>       for these functions and stop using them altogether.
>

You can still write to ASCII Files. The only thing is, that when you
make an INI-File-Mapping entry in the registry, WritePrivateProfileString
writes into the registry, of you don't make an entry, you still write
in ASCII-Files. It's really your choice.

Christoph
-------------------------------------------------------+-----------------------
Christoph H. Hochstaetter, Philipps-University Marburg | Universitaetsstr. 25
Internet: hochstae@allfiwib1.wiwi.uni-marburg.de       | D-W-3550 Marburg
Bitnet  : HOCHSTAE AT DMRHRZ11                         | Germany
Fido    : 2:243/660                                    | Phone +49-6421-28-7092
Fax     : +49-6421-28-4858                             |
Newsgroups: comp.os.ms-windows.programmer.win32
From: claest@imec.be (Tony Claes)
Subject: Registry woes
Organization: IMEC V.Z.W,Interuniversitair Micro Electronica Centrum, Belgium
Date: Thu, 7 Jan 1993 17:27:23 GMT



Hello,


I have used the last NT Beta, and think it is not usefull in practice
for the moment. In Theory it is a nice system, but I am afraid that this
is of no use for the real life;

Lets face it that OS/2 is for the moment the best PC operating system. The main
objectives we have against OS/2 are temporary.

  - It will run all Windows 3.1 programs in version 2.1 [ this spring ]
  - It will have system input queues for every process in version 2.2 [ fall ]
  - It will have a distributed object model ( SOM2 ) comforming the
    emerging CORBA standard in version 2.2 [ fall ]

  - It will be micro-kernel based in version 3.0 [ ??? -> '94 ]
    The result of this is that it is at that moment platform independant.

I want to compare NT with the corresponding version of OS/2. This comparison is
possible at the end of the Year, when both are running on enduser machines.

As I see it both will have pro's and contra's. The major points for the 
desktop market are :

KERNEL ;

  NT
  --
     pro  : micro kernel based.
	    platform independent.
     contra : new, buggy ?

  OS/2
  ----
     pro  : stabel
     contra : platform dependent.

FILE SYSTEM ;

  NT
  --
     pro : file protection between users.

  OS/2
  ----
     contra : no file protection between users.

COMPATIBILITY

   NT
   --
     contra : compatibility with dos/ windows  is restricted.

   OS/2
   ---- 
      pro   : very compatible with dos/windows.

GUI

   NT
   -- 
      pro : same as Windows 3.1 --> users are familiar with it.
      contra : not OO.

   OS/2
   ----
      pro : a distributed object oriented environment.
	    easy to use.
      contra : unfamiliar for windows users.

HISTORY

   NT
   --
      pro : very good marketing. Most people are pro NT although they never
	    saw it.

  OS/2
  ---
      contra: previous versions.

NEAR FUTURE

  NT
  --
     contra : Will have to prove that it is as good as Microsoft promisses
	      in the marketing.

  OS/2
  ----
     pro : can be a discovery for people who are negative about it without
	   having used this version.

PROGRAMS

  NT
  --
    pro : Many native programs will be available
    contra : compatibility with dos/windows

      [ Will this compatibility be that important at the end of the Year ? ]

  OS/2
  ----
    pro : Compatibility
    contra : Will there be many native progams available ?


NON DESKTOP ITEMS.

  With both OS's it is possible operate as server in a network. If the features
  needed to do this are in the base package, is irrelevant.



MY CONCLUSION

I do not understand why there is so much fuss about NT vs OS/2. Both are 
operating systems with a potential promissing future. Which of the two will
be dominant in 2 -3 Years is something the future will tell . 



Newsgroups: comp.os.ms-windows.programmer.win32,comp.os.ms-windows.misc
From: reimert@mamacass.etdesg.trw.com (Scott P. Reimert)
Subject: Re: Help unistalling Windows NT
Organization: TRW Inc., Redondo Beach, CA
Date: Mon, 4 Jan 93 21:57:59 GMT

In article <1993Jan1.205854.6450@murdoch.acc.Virginia.EDU> rwb@Turing.ORG (Robert W. Bingler) writes:
>Hey,
>	Can someone please help with unistalling Windows NT?  We've
>tried deleting it but it remains in the boot equence, therefore
>it locks the machine up.
>
>Any help would be great!
>
>Thanks,
>Rob
>
>+--------------------------+----------------------+--------------------------+
>|   o    \ /  <o>    o     |  Robert Bingler      |  .sig Virus Disenfector  |
>| _/|-'   |    |   _/|-'   |->rwb@turing.org      |                          |
>|  / \,  /o\  / \   / \,   |  dwb4h@virginia.edu  |  To envoke type:         |
>| `                `       |                      |  rm .sig                 |
>+--------------------------+----------------------+--------------------------+

WindowsNT (tm) has several hidden files that it deposits in the root directory
of the C: drive, even if you are using the flexboot option and the C: drive is
DOS (or something else). You'll need to get rid of all the NT files in the
root directory on C:. Some of the NT files are not hidden, so just poke around
and nuke files that don't belong there. 

If you wanted to be REALLY sure, you could do a backup of your disk (which is
good to do anyway), and exclude the NT files. Then reformat the disk.

		Scott

-- 
-------------------------------------------------------------------------------
  Scott Reimert  \    reimert@mamacass.etdesg.trw.com     /Standard disclaimer:
Redondo Beach, CA \______________________________________/"Blah blah blah ... "
__________________|Always store beer in a cool dark place|_____________________
Newsgroups: comp.os.ms-windows.programmer.win32
From: JBaird@rm42.ucc.uconn.edu (James Baird)
Subject: Help! Dos programs with Token-Ring Still don't work
Organization: University of Connecticut Computing Center
Date: Tue, 12 Jan 1993 15:09:03 GMT

The title just about says it all - I loaded up Microsoft's "Bug fix" on my
Model 80 with IBM Token Ring Adapter/A, and I still get this error whenever 
I try to run a DOS or 16-bit Windows program:
The instruction at "0x0101fd54" referenced memory at "0x000e2051". The 
memory could not be "read".  

I thought the fix was supposed to address this, but apparently I am 
"special".  Anybody have any ideas?

Jim Baird
From: Alistair Banks <alistair@microsoft.com>
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: 16-bit Windows Sockets for Oct '92 Win32 SDK for Windows NT
Date: 5 Jan 93 11:33:53 GMT
X-MSMail-Message-ID:  6F8CBAD8
X-MSMail-Conversation-ID:  6F8CBAD8
X-MSMail-WiseRemark:  Windows for Workgroups Mail
To: winsock@microdyne.com


The file wsock16.zip is available now via anonymous ftp, from 
ftp.uu.net[192.48.96.9], in the 
~ftp/vendor/microsoft/windows-sockets-api directory

ftp% ls -l wsock*
total 701
-rw-r--r--  1 ms-isv     599359 Jan  5 06:18 wsock16.zip
-rw-r--r--  1 ms-isv       1180 Nov  3 13:01 wsock16.zip.readme

ftp% cat wsock16.zip.readme

This directory contains the necessary files for 16-bit Windows Sockets
support for the Windows NT October Beta release.  These files have not
received the thorough testing that the released Beta received, and should
be used cautiously.  In particular, you are encouraged to make backup
copies of the Beta files that these overwrite in case you need to revert
to the Beta.

To use these files, go to the "system" subdirectory of the NT tree and
rename wow32.dll to wow32.sav, wsock32.dll to wsock32.sav, and
wshtcpip.dll to wshtcpip.sav, then copy in the four files included here.
Reboot and you'll be ready to run 16-bit Windows Sockets applications.
If you experience problems running non-Windows Sockets 16-bit applications
or with 32-bit Windows Sockets applications, revert to the original files
included with the beta.  The files included herein work on either free
or checked(debug) builds.

Known problems with the 16-bit Windows Sockets code include:

    - WSASetBlockingHook() does not work.
    - WSACleanup() doesn't close open sockets.

A fully tested implementation of 16-bit Windows Sockets support will be
included in the next NT Beta release.

Feedback and bug reports to the mswin32 forum on Compuserve, please

-- Alistair
Newsgroups: comp.os.ms-windows.programmer.win32,comp.os.ms-windows.setup
From: poffen@sj.ate.slb.com (Russ Poffenberger)
Subject: Re: Can I use this CD-ROM drive with Windows or NT ?
Followup-To: comp.os.ms-windows.programmer.win32,comp.os.ms-windows.setup
Organization: Schlumberger Technologies, ATE division, San Jose, Ca.
X-Newsreader: TIN [version 1.1 PL7]
Date: Tue, 12 Jan 93 21:23:58 GMT

Dwayne Paschall (paschall@utdallas.edu) wrote:
: I have successfully used a Toshiba TXM-3201 CD-ROM drive connected to a 
: Future Domain SCSI-I controller. The NT setup program recognized my FD 
: controller as a FD-845 SCSI board (mine is, I believe, a Future Domain 
: 860 board).
: 
: It seems that all access to the CD-ROM drive worked fine for the setup 
: of NT. The only thing that didn't work was the Audio CD utility that 
: came with NT.
: 

This is true for Audio access. NT currently only supports audio on CDROM's
with SCSI-II interfaces. Apparently, on SCSI-I, there is no standard for
audio control, so all CDROM drives are different, and need different drivers.

Russ Poffenberger               DOMAIN: poffen@sj.ate.slb.com
Schlumberger Technologies ATE   UUCP:   {uunet,decwrl,amdahl}!sjsca4!poffen
1601 Technology Drive		CIS:	72401,276
San Jose, Ca. 95110             Voice: (408)437-5254  FAX: (408)437-5246
From: fmh@monsoon.com (Francis Hogle)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: Determining path of loaded DLL from debugging process
Date: Mon, 11 Jan 93 22:31:05 EST
Organization: Monsoon Software, Inc. +1 (410) 235-2365

saswta@terrapin.unx.sas.com (Bill Arnette) writes:
> Does anybody know how I can get the path name of the loaded DLL, or
> failing that, how I can get the name of a file given a file handle?

Look at the GetModuleFileName() function (Win32).
Newsgroups: comp.os.ms-windows.programmer.win32
From: chrisl@quip.eecs.umich.edu (Chris Lang)
Subject: Spawning programs from POSIX subsystem
Organization: University of Michigan EECS Dept., Ann Arbor, MI
Date: Fri, 8 Jan 1993 16:02:17 GMT

In NT, a Win32 program can use CreateProcess() to execute another program,
without worrying about whether it is a POSIX, Win32, DOS, or whatever,
program.  Does a similar facility exist for a POSIX program?  I have tried
the exec?() family, but they seem only able to execute another POSIX
program, and return with an error if the program is a Win32 or DOS program.

Is there another function that will do what I want, or is it just not
something that is possible to do from within the POSIX subsystem?

Thanks.

 -Chris
-- 
Chris Lang   |   Univ. of Michigan Engineering   |   chrisl@umich.edu
WORK: National Center for Manufacturing Sciences, 
      900 Victors Way, Suite 310, Ann Arbor, MI, 48108        +1 313 995 0300
"I hate quotations.  Tell me what you know."  - Ralph Waldo Emerson
Newsgroups: comp.os.ms-windows.programmer.win32
From: martin@iastate.edu (Martin R Calsyn)
Subject: Re: NT not multiuser, then Unix is not a competing OS
Organization: Iowa State University, Ames, IA
Date: Mon, 11 Jan 1993 17:13:05 GMT

In article <1993Jan11.031254.14628@ryn.mro4.dec.com> Peter.Mayne@cao.mts.dec.com writes:
>
>In article <0T5DVB1w165w@gnct.com>, garyng@gnct.com (Gary Ng) writes:
>>NT is not multiuser in the sense that it do not allow more than 1 person to
>>logon and use it simultaneously(in the way one logon to unix or ibm mainframe).
>
>Despite the fact that telnet servers have been/are being written for NT that
>allow just that?

I wouldn't be too sure about those telnet servers (telnetd) for NT.  I
embarked on such a project, only to be thwarted.  If there's interest,
I'll post the official reply from MicroSoft, but essentially, a crucial
API call set is not available.

When you log on through WINLOGON, you get an access token which is the
basis for all further security interactions with NT.  That is, WINLOGON
takes your cleartext username and password and produces an access token.

In order to produce a true telnetd application giving you all of the
same system, file, and network access rights, your telnetd must be able
to accept a cleartext username and password and use them to obtain an
access token.  WNetAddConnection2() accepts a name & password, but only
gives you access to NT file shares -- it does not give you all of the
security components necessary for generalized interactive computing.

This is not so much of a problem for NT<-->NT interactions since one NT
system can pass security information to another based on the user
authentication already performed at logon to the first system.  Named
pipes, etc do this.  But, the components necessary for authenticating
users originating on foreign (non-NT) systems is not available.  Using
`fake' logons is not sufficient - they might get you past your telnetd
logon, but you still wouldn't have the security objects you need to get
anything useful done in NT.

I have campaigned MS on this issue (on CI$ forum MSWIN32) and recieved a
response which indicated that MS considers it insecure to allow the
calls to be made other than in a communications session layer (I'm not
entirely sure what they meant by that).  The note did mention the
possibility of some future extensions to the security API but was quite
fuzzy and noncommital on this point.

Barring any back-door, undocumented-API efforts (I have no idea whether
any would be successful), this would appear to put a serious roadblock
in the way of porting/implementing telnetd, rshd, or any other service
requiring acquisition of generalized access from cleartext
authentication.  (ftpd is an exception -- WNetAddConnection2() is
sufficient for this application)

-- 
Martin R. Calsyn                                   martin@iastate.edu
Software Innovations Incorporated                  voice: (515) 232-9196
P.O. Box 644                                              (800) 728-1525
Ames, Iowa 50010                                   fax:   (515) 233-6209
Newsgroups: comp.os.ms-windows.programmer.win32