HDTenEightyP/NetNews huggingface dataset:
From: ryanm@stein.u.washington.edu (Ryan Mcneilly)
Subject: Peoples Impatience!
Organization: University of Washington, Seattle
Date: Tue, 13 Oct 1992 22:47:14 GMT

I enjoy reading this news group very much.  However, I have seen small
wars getting started on features not in NT like Unix provides.  I think we
need to look at NT in perspective.  NT is thee first OS designed to
utilize high end machines created by MS.  You can't expect MS to provide
every single utility and feature into a product only 1.5 years (or is it 1
year?) old.

Unix has been around for a long time.  It has had years to develop the
favorite tools and features that I keep hearing about.  NT has had only a
few months (6 to 12) to develop these features and tools.  This is very
quick when they didn't just take unix and rework it.  They started from
scratch adding Unix (powerful) like features into it along with VMS and
Windows features.

I think the biggest heated discusion is on XWindows and Multi-user
interface.  From what I understand (no expert) X has plenty of problems (I
may be wrong) and the Multi-user capability is there just no interface or
daemon has been built to use it.

Another thing is that MS is trying to get competition going for third
party developrs (all of us) to develop what NT doesn't have.  Lets face
it, if MS provided everything where would we be?  I think MS has provided
a balance between base requirements and everything we need.  Also the
competition will provide better products than if MS creates a through
together.

I commend MS in there marketing approach and fairness to all involved in
development.  I think they have come up with a winner and like it (I do
like Unix a lot also!).  Lets keep this in perspective and have patience with
MS.

This is my $.02 worth.  Please no flames or wars.  This is only my
opinion.  Lets keep the discussions civalized!  I don't see the vord
advocacy in this group name!  --Ryan

==========================================================================
  Ryan McNeilly 

  Internet: ryanm@u.washington.edu
==========================================================================
From: Guy.Harris@f1.n100.z60.wlink.nl (Guy Harris)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: NT Under SCO Unix
Date: Mon, 12 Oct 1992 23:55:14 -0100

Organization: Auspex Systems, Santa Clara

>As you pointed out, 286 are cheap: and they are good for text based
>applications. That's why WNT should not restrict itself to graphical
>applications: a minimum to run a window GUI is a good 386

Umm, a minimum to run WNT, GUI or no, is a 386.  I don't think Microsoft
gives a damn about making it run on 286's, and frankly, I suspect
that's the correct decision on their part.
From: sanzgiri@bombay.metaphor.com (Ajit Sanzgiri)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: NT Win32 DLL building problem
Date: 12 Oct 92 19:57:27 GMT
Organization: Metaphor Computer Systems, Mountain View, CA

In article <KEVIN.92Oct1091818@loneranger.edscom.demon.co.uk> Kevin Broadey <kbroadey@edscom.demon.co.uk> writes:
>
>> undefined".  Why does a library routine expect there to be a "_main"?
>
>I had a similar problem a while ago.  I created a function called "main"
>which did a MessageBox() call to say when it was called and linked it in
>to the DLL.
>
>It has never yet announced that anyone called it...!

	I was plagued by the same problem. It went away when I started putting
	crtdll.lib before $(guilib) on the link command line.
	The way $(guilibs) is defined it links DLLs with the wrong libraries
	unles you stick crtdll.lib in ahead of the other libraries.

	Ajit Sanzgiri
-------------------------------------
CUTE EPIGRAM INSERTED TO KEEP NEWS SERVER HAPPY:
If you want to be successful all you need is lots of confidence coupled with
an equal amount of ignorance. -- Mark Twain (I think).
-------------------------------------
From: thg@cam-orl.co.uk (Tim Glauert)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: Multiuser NT???
Date: 9 Oct 92 10:40:10 GMT
Organization: Olivetti Research Ltd, Cambridge, England.

In article <1992Oct8.175157.16182@husc3.harvard.edu>, mendels1@husc4.harvard.edu (Andrew Mendelsohn) writes:
|> The recent articles about NT's multiuser capability have been confusing.

This is really addressed to the guys at Microsoft:

There really is *a lot* of confusion about this. I suggest that you take three
experienced NT programmers and give them the task of implementing telnetd,
rshd and ftpd respectively. Lock them all in a room with three NT machines and
don't let them out until they have finished. Then announce that these services
will form part of the base NT product, or release them into the public domain.
All the speculation would go away and the Unix users looking at NT would be
happy. Can't MS afford a few weeks of programmer time to tackle this problem
once and for all?

Failing that, how about an effort among some developers to get PD versions of
these services out as soon as possible?
Newsgroups: comp.os.ms-windows.programmer.win32
From: jones@hal.uvm.edu (Mike Jones)
Subject: Dialog Editor Question
Organization: University of Vermont, EMBA Computer Facility
Date: Wed, 7 Oct 1992 22:32:39 GMT

I have a question about the use of the .res file that the dialog
editor creates.   How do you use it ?

If I put all of the .dlg file into my master .rc file and skip using
the .res file, all works.

Seems like too much work.  Can I use the .res file directly somehow ?
I tried both "MyMenu"(after commenting out the approp #define) and
MAKEINTRESOURCE(MyMenu) for the parameter to DialogBox().

What I want is... a main.rc file with the titlebar menus, and write
all of my popups using the dialog editor.

thanks for all replies,
  Mike

=========================================================
Mike Jones		     | Mike.Jones@EMBA.UVM.EDU	   
EMBA-CF, 250 Votey Building. |
University of Vermont 	     |
Burlington, VT.    USA	     | Voice:  (802) 656-2926 	
		05405        | FAX:    (802) 656-8802
=========================================================
Newsgroups: comp.os.ms-windows.programmer.win32
From: leehart@microsoft.com (Lee Hart)
Subject: Re: Fatal System Errors
Date: 09 Oct 92 00:14:59 GMT
Organization: Microsoft Corp.
Summary: Arc is not quite dead - see boot.ini!

In article <1992Oct8.024618.17756@solaris.rz.tu-clausthal.de>, hochstae@allfiwib1.wiwi.uni-marburg.de (Christoph H. Hochstaetter) writes:
> This has also been discussed before, of course you can install NT after
> you have installed OS/2 2.0. NT's flexboot just gets a little confused
> about the drive letters. So change the x:\WINNT to
> multi(0)disk(0)rdisk(x)partition(y)\WINNT and flexboot will work perfectly.

It is probably a good idea to explain what all of the portions of the
path you show are:

multi(0)disk(0)

refers to the first WD1003 (AKA ATDISK, IDE, ST506, etc) controller in the
system.  For a SCSI drive you would use scsi(0)disk(n), where n is the scsi
ID of the drive.  rdisk(x) refers to the first (0) or second (1) disk attached
to the WD1003 controller, or to the appropriate SCSI Logical Unit Number (LUN)
at the given SCSI ID.  partition(n) refers to the nth partition (n>=1) on
that drive (partition(0) refers to the entire disk, w/o Filesystems, and
is used by chkdsk, etc.)  The partition numbers are assigned in the age old
manner of first active partitions, then non-extended partitions, and then
the partitions in the extended partition table.  BTW, SCSI()... notation
requires that your scsi miniport driver be copied into ntbootdd.sys in
the root of your booting drive (i.e. a:\ or c:\)

The above is a little on the brief side, but it does explain the ARCpaths
(I've also heard them called ARC names) that you see while the system is
booting.  Users of MIPS machines are a little more familiar with these,
since they are used by jzsetup.exe (the ARC refers to the machine spec
from the ACE initiative BTW)

Probably more than you ever cared to know about that naming convention.


Lee
Not a spokesman.
From: alistair@mits.com.au
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: NT slows down on memory upgrade
Date: 9 Oct 92 08:00:24 GMT
Nntp-Posting-User: alistair

Whenever we try to upgrade a PC (ISA, EISA, different brands,
configurations, etc) from 16 Mbyte to 32 MByte main memory, NT slows
down horribly (we do reconfigure the PC for the extra memory).

Has anyone else experienced this?

Thanks in advance,

Alistair Grant

Internet:     alistair@mits.com.au
Alternate:    alistair%mits.com.au@ucsvc.ucs.unimelb.edu.au
Newsgroups: comp.os.ms-windows.programmer.win32
From: kevin@edscom.demon.co.uk (Kevin Broadey)
Subject: Re: new Dell BIOS fixes 16meg limit problem
X-Disclaimer: These opinions are mine: others available on request.
Reply-To: Kevin Broadey <kbroadey@edscom.demon.co.uk>
Organization: EDS-Scicon, Milton Keynes, UK
Date: Fri, 16 Oct 1992 16:02:03 GMT

Hi Jim,

In newsgroup comp.os.ms-windows.programmer.win32 you wrote:

Jim> while the FAQ said that the Dell 486 A09 BIOS fixed the 16meg max
Jim> memory problem, it didn't. BUT: A10 is out and fixes the problem!
Jim> I am happily using NT on a 24meg Dell 486 now. For the others who
Jim> had the same problem:

Jim>     1) Call Dell's support BBS at 512-338-8528  (1200/2400/V.32)
Jim>     2) Download 486DA10.EXE or 486PA10.EXE depending on which
Jim>        model machine you have. You'll need binary download
Jim>        protocol support like X/Y/ZModem, Kermit, etc.
Jim>     3) Run the .EXE to unzip the Flash burner and ROM files
Jim>     4) Run FLASH.EXE to burn the new BIOS into your flash ROM
Jim>        (nice touch, Dell - BIOS chips suck!)
Jim>     5) Reboot and rejoice!

I don't suppose this is available on an anonymous ftp server?  If not,
would someone put it where I can get it?

TIA

Kevin
--
.signature: no such file or directory
From: hochstae@allfiwib1.wiwi.uni-marburg.de (Christoph H. Hochstaetter)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: NT and Network Cards
Date: 13 Oct 92 17:57:07 GMT
Article-I.D.: solaris.1992Oct13.175707.6935
Reply-To: hochstae@allfiwib1.wiwi.uni-marburg.de (Christoph H. Hochstaetter)
Organization: Techn. Univ. Clausthal
News-Software: IBM OS/2 PM RN (NR/2) v0.14 by O. Vishnepolsky and R. Rogers

In  <14045@ncrcan.Canada.NCR.CA>  rmeester@ncrcan.Canada.NCR.CA (Richard Meesters) writes:
> The System:  NCR 3433 (486 33MHz Micro channel)
>                 with an IBM T/R Adapter /A
>
> I've experienced a problem where the system was unable to run any dos programs
> under NT.  When running anything DOS, the system came back with a function
> failed message in a popup window.  This problem goes away when the IBM T/R
> card is removed from the system.
>
> This looks like a conflict in the 640K - 1Meg range of memory.  I had a similar
> problem with OS/2 2.0 (DOS sessions worked, but you couldn't get any Expanded
> memory) which was solved by making the memory settings as contiguous as
> possible in the D0000-DFFFF range (Leaving C0000 areas free for what I think
> must have been the necessary page frame, but I'm guessing).
>
> Does anyone have an explanation for what's happening here?
>
No, but I have exactly the same problem on an IBM Model 90 486/33 with an
IBM Token-Ring card. So we will have to wait for the next release.

Christoph
--
Internet: hochstae@allfiwib1.wiwi.uni-marburg.de
Bitnet  : HAMPE2 AT DMRHRZ11
Fido    : 2:243/660
Newsgroups: comp.os.ms-windows.programmer.win32
From: brad@huey.Jpl.Nasa.GOV (Brad Hines)
Subject: Compiler error (assertion)
Keywords: compiler error cl386
Reply-To: brad@huey.Jpl.Nasa.GOV
Organization: JPL Spatial Interferometry Group
Date: Tue, 13 Oct 1992 21:50:56 GMT

I was trying to port some Windows 3.1 code that I had written for
Borland C++ to NT over the weekend and ran into a couple of problems.

The one of most concern was something that appears to be come sort
of internal compiler error.  While successfully compiling most of
my project, the compiler gives errors something like this for two
of the files:

Compiler error (assertion) .... [stuff about compiler module names and line #'s]

Does anyone know what causes this or what a workaround is?  I haven't
been able to find anything obvious in these two source files that's
not in the other.

==

The other problem involves the compiler complaining about something
that is valid C++.  The following is legal (it's been simplified for
clarity), and both the Borland and Zortech compilers compile and run
it fine, but the NT version of cl386, at least, complains:

class ClassA;
typedef void (ClassA::*PCLASSAPROC)(int);

class ClassB {
  PCLASSAPROC pProc;
}

class ClassA {
  void SomeProc(int x);
  ClassB SomeMemberOfTypeClassB;
}

.
.
.


Basically, cl386 doesn't like the typedef when it hasn't yet seen the full
class definition and prints out an error message that basically says that
this is illegal.  This is legal, however.  Is there a fix for this
problem?

BTW, you can see that the structure of the application requires that
ClassB be defined before ClassA, since ClassA contains a member of type
ClassB.  But ClassB also needs to be able to store a pointer to a member
function of ClassA, so I need the forward declaration of ClassA to work.

Thanks for any help or info anyone can provide...

-- 
Brad Hines
Internet: brad@huey.jpl.nasa.gov
Jet Propulsion Lab, Pasadena, California
From: sasdxk@skyhawk.unx.sas.com (Dave Kolb)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: Fatal System Errors
Date: 7 Oct 92 19:21:09 GMT
Organization: SAS Institute Inc.
Originator: sasdxk@skyhawk.unx.sas.com


In article <16605@ksr.com>, kenyee@sneakers (Ken Yee) writes:
|> In article <30@hymir.mlb.dmt.csiro.au> gsl@mlb.dmt.csiro.au (Geoff Lamb)
|> writes:

|>     I have a WD7000FASST SCSI card.  The driver seems to load before I
|>     get this error.
|>     A couple of people who've gotten around it have suggested formatting
|>     the disk to one partition for NT only.  Another one got new ROMs for
|>     his Ultrastor controller.  Sounds like a generic "I'm clueless"
|>     error to me :-<
|>

I've had success after failure w/ SCSI drives if I formatted the drive
under OS/2 or DOS before letting NT see it.  The SCSI drives had originally
come from a UNIX system and caused NT to hang at boot time.
-- 
David Kolb                    Opinions are my own not SAS'
SAS Institute, Inc.           EMAIL:      sasdxk@unx.sas.com
SAS Campus Drive - J206       Phone:      (919) 677-8000 x6827
Cary, NC  27513-2414 USA      FAX:        (919) 677-8123
Newsgroups: comp.os.ms-windows.programmer.win32
From: jseidman@jarthur.claremont.edu (Jim Seidman)
Subject: Re: Comtrade Systems & NT
Summary: Don't buy Comtrade!
Organization: Cornfield Computing
Distribution: na
Date: Tue, 13 Oct 1992 19:02:48 GMT

tim@boxhill.com (Timothy Jones) writes:
>Does anyone out there have experience with these systems?  They run big ads in
>Computer Shopper and have pretty competitive prices.  Of particular interest
>is their combination EISA/local bus machine.

Comtrade is by far the worst company I have ever had to deal with.
I won't waste bandwidth with my tales of woe, but if anyone really
wants to hear, e-mail me.  Suffice it to say that Comtrade systems
are among the worst available, the support is incompetent, and the
owner has no sense of ethics.

I also know that my case is not an isolated one, since an insider
at Computer Shopper told me that they've received numerous complaints
about Comtrade besides mine.  Not to say they would actually *do*
anything about these complaints... Comtrade is, after all, a big
advertiser...

-- 
Jim Seidman, President
Cornfield Computing, Inc.
410 Hilltop Road
Champaign, IL 61821-7328
Newsgroups: comp.os.ms-windows.programmer.win32
From: brianmo@microsoft.com (Brian Moran)
Subject: Re: Win NT, some simple questions
Date: 09 Oct 92 18:01:42 GMT
Organization: Microsoft Corporation

Developers outside the  US may order the Windows NT prerelease development kit
from the MS office in their country.

-Brian K. Moran
Developer Relations Group
Microsoft Corp.

(Disclaimer: Yes I work for Microsoft. Sometimes I am even responsible for the
 things  that I  say! )
From: gsl@mlb.dmt.csiro.au (Geoff Lamb)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Fatal System Errors
Date: 7 Oct 92 05:06:08 GMT
Organization: CSIRO Division of Manufacturing Technology, Melbourne, Australia


I am trying to install Windows NT over our network using PC-NFS and a SUN Sparc CD-ROM and the dos2nt.bat file.

I get to the bit where it asks if I want to boot NT or DOS, I choose NT and I get the following errors:

	*** Fatal System Error : 0x00000069

	*** Phase 1 I/O initialization failed

Does anyone have any ideas? Or does anyone know what those errors mean?

Thanks in advance.

Geoff Lamb

-- 
Geoff Lamb, CSIRO Div of Manufacturing Tech,     Phone: +61 3 487 9295
Locked Bag No. 9, Preston, Vic, 3072, Australia. Fax: +61 3 484 0878
Internet: gsl@mlb.dmt.csiro.au                  
Newsgroups: comp.os.ms-windows.programmer.win32
From: mikee@seas.gwu.edu (Mike Me)
Subject: Re: Drivers for CD Technology with AHA-1542B
Keywords: driver, Toshiba, Adaptec AHA-1542B, CD Technology
Organization: George Washington University
Date: Fri, 9 Oct 1992 16:32:59 GMT

>|> 
>|>   - Does the software for the Microsoft Developer Network
>|>     CD-ROM work under Windows NT without the DOS drivers?
>|>     In other words, am I barking up the wrong tree? Can I
>|>     just forget about DOS drivers and rely on Windows NT
>|>     completely?
>|> 

>Yes.

>|>   - Are DOS drivers needed for use of the CD-ROM drive by
>|>     DOS programs running under Windows NT?
>|> 
>
>This won't work (currently).
>

An interesting twist on this is that they DO work... 
I was surprised myself...
I had borrowed an IBM CD_ROM and hhoked it to mny AHA1740.
Dos had NO clue as to what the E_DRIVE wassince I had no drivers,
but once I stated windows and shelled to dos, the E_drive was way
Happy.

I guess NT supplies the neccesary drivers for the CD_ROM both for
dos windows and OS/2.

Just my 2 cents,
	later,
		MikeE
Newsgroups: comp.os.ms-windows.programmer.win32
From: hochstae@allfiwib1.wiwi.uni-marburg.de (Christoph H. Hochstaetter)
Subject: Re: Future Domain 1680 driver missing?
News-Software: IBM OS/2 PM RN (NR/2) v0.14 by O. Vishnepolsky and R. Rogers
Reply-To: hochstae@allfiwib1.wiwi.uni-marburg.de (Christoph H. Hochstaetter)
Organization: Techn. Univ. Clausthal
Date: Thu, 15 Oct 1992 00:57:35 GMT

In  <miron.719058061@sfu.ca>  miron@beaufort.sfu.ca (Miron Cuperman) writes:
> I have a Future Domain 1680 SCSI card.  The setup diskette seems
> to be missing the driver for this card.  Windows NT itself fails
> to recognize the drives attached to the card.  Does anybody know
> why the driver is missing and where I might get it?
> --

There is a bugfix release available on ftp.uu.net in
/vendor/microsoft/compuserve-libs

Christoph
--
Realname: Christoph H. Hochstaetter
Internet: hochstae@allfiwib1.wiwi.uni-marburg.de
Bitnet  : HAMPE2 AT DMRHRZ11
Fido    : 2:243/660
From: saswta@terrapin.unx.sas.com (Bill Arnette)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: WndDbg problem
Date: 8 Oct 92 13:22:01 GMT
Organization: The Village
Originator: saswta@terrapin.unx.sas.com



You must specify the program you want to debug on the command line.  I beleive
that the greyed out 'Program' menu will be the mechanism by which programs can be
loaded after Windbg is running.  I assume this will be enabled in a later release.


Bill Arnette, SAS Institute Inc.    (919)677-8000    | saswta@unx.sas.com
SAS Campus Drive, Cary, NC 27513  (919)677-8123(fax) | ...!mcnc!sas!saswta
-- 
Bill Arnette, SAS Institute Inc.    (919)677-8000    | saswta@unx.sas.com
SAS Campus Drive, Cary, NC 27513  (919)677-8123(fax) | ...!mcnc!sas!saswta
From: vlj@hpfcso.FC.HP.COM (Victor Johnson)
Date: Wed, 14 Oct 1992 18:58:54 GMT
Subject: Re: Proaudio 16 + NEC CD-ROM
Organization: Dances with Hawks
Newsgroups: comp.os.ms-windows.programmer.win32

> Art Baker writes:
>
> > Michael Bishop writes:
> >
> >My question is:  Will the Windows NT Beta release (scheduled for this
> >October) have support for the Proaudio 16 soundcard?  Will this support
> >also include the SCSI portion of the soundcard so that I can get access
> >to my CD-ROM while running Windows NT?
> 
>  A call to Media Vision's technical folks reveals that Media Vision has
> no plans to support the PAS-16 under Windows NT.  It is their opinion
> that their customers should be able to get by with the SoundBlaster 
> emulation features of the PAS-16.
> 
>  If Trantor writes a driver for the SCSI controller, then at least the
> CD-ROM drive would work under NT.  I don't know what Trantor's plans
> are.
> 
>  You might want to give Media Vision a call and register your opinion on
> their decision:
> 
> 	BBS:	(510)770-0968
> 	voice:	(510)770-8600

  I did so to learn that they have recently changed their position.  They
  now claim that they *will* support the ProAudio 16 under Windows NT and
  expect to be releasing drivers in mid '93.

  They have also established a "waiting list" for those wishing to obtain
  the drivers as soon as they are released.  If you want to be put on this
  waiting list, call

	 1-800-638-2807

  and traverse the voice-mail menu labyrinth to get to Customer Support.
  They will take your name/address and ostensibly will provide the driver
  when ready for public consumption.

  Cheers,
  Victor Johnson
  --------------

Newsgroups: comp.os.ms-windows.programmer.win32
From: paulb@harlqn.co.uk (Paul Butcher)
Subject: Stripping debugging info from a Win32 binary
Organization: Harlequin Ltd, Cambridge, UK
Date: Tue, 13 Oct 1992 11:44:43 GMT

I'm sure this is just me being stupid, but I can't seem to find a way
to strip debugging information from a Win32 binary.  I know I can "just"
recompile, but I've got about a 2 hour recompilation time at the moment
:-(

Thanks in advance,

PaulB->msgCount++
Newsgroups: comp.os.ms-windows.programmer.win32
From: paulb@harlqn.co.uk (Paul Butcher)
Subject: Re: Stripping debugging info from a Win32 binary
Organization: Harlequin Ltd, Cambridge, UK
Date: Wed, 14 Oct 1992 08:26:13 GMT

In article <d0zz3c#@rpi.edu> assela@aix.rpi.edu (A. Andre Asselin) writes:
>paulb@harlqn.co.uk (Paul Butcher) writes:
>>I'm sure this is just me being stupid, but I can't seem to find a way
>>to strip debugging information from a Win32 binary.  I know I can "just"
>>recompile, but I've got about a 2 hour recompilation time at the moment
>
> [Stuff about shareware coff dumper deleted]
>   As an aside, can't you just relink instead of going through the whole 
>recompilation process?  I haven't looked closely at the options available for
>LINK/COFF, but with the old LINK, you'd only get debugging info in the .EXE
>if you specified /CO on the LINK command line.  I'd have thought that that
>was the way it still worked.  

Whoops!  My fault - I should have mentioned this in my original posting.

One of the first things I tried (of course) was linking without debug info
(this is still a pain in the arse - link time is about 10 mins!), but the
.EXE I ended up with wasn't recognised by the OS as an executable!  I tried
this a couple of times with the same result.

It seems that if I want an executable without debug info, I have to have a
load of objects without debug info :-(

If anyone has any idea what's going on here, I'd love to hear about it...

Ta.

PaulB->msgCount++