HDTenEightyP/NetNews huggingface dataset:
From: kenyee@sneakers (Ken Yee)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: error 0x69 kills NT boot!!
Date: 29 Sep 92 08:59:09 EDT

In article <BvBM7o.2AH@huey.jpl.nasa.gov> brad@huey.Jpl.Nasa.GOV (Brad  
Hines) writes:
> In article <16245@ksr.com>, kenyee@ksr.com (Ken Yee) writes:
> >Using dos2nt to install the NT beta, I get the following message:
> >
> >Fatal System Error: 0x00000069
> >Phase 1 I/O initialization failed.
> 
> There are apparently a whole slew of things that can cause this.
> 
> In my case, the problem was caused by outdated disk BIOS ROMs in 
> my Ultrastor 12F ESDI disk controller.  It works fine now.

    Some other person suggested making NT the one and only partition
    on the drive.  That didn't work.
    And my system is relatively new (1.5 years old).  At least OS/2
    never had any problems :-(

So anyways, is there a gripe line to Microsoft?  The local fidonet
echo doesn't carry the win32 conference.

 ken
Newsgroups: comp.os.ms-windows.programmer.win32
From: tim@boxhill.com (Timothy Jones)
Subject: Comtrade Systems & NT
Organization: Box Hill Systems Corporation, New York, NY
Date: Tue, 6 Oct 1992 14:59:40 GMT

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.

Also, has anyone tried running Windows/NT on them?  They're not listed in the
latest hardware compatibility list I have, and NT compatibility is a
requirement.

Thanks,
Tim
--
Timothy Jones, Engineer                                 e-mail: tim@boxhill.com
Box Hill Systems Corporation                                voice: 212-989-4455
161 Avenue of the Americas, New York, NY, 10013               fax: 212-989-6817
From: darrylo@hpnmdla.sr.hp.com (Darryl Okahata)
Date: Mon, 28 Sep 1992 05:25:25 GMT
Subject: Re: Sigma Legend II (ET4000) and hi-res
Organization: Looking for a new job
Newsgroups: comp.os.ms-windows.programmer.win32

In comp.os.ms-windows.programmer.win32, bbrown@infonode.ingr.com (Bailey Brown) writes:

> Are you using the default 60hz refresh or 72hz?  I was using 72.

     To be perfectly honest, I have no idea what the refresh rate is.
When I installed the drivers, I was given a choice of resolution, number
of colors, and large or small fonts.  I'm using an ancient NEC Multisync
II monitor, and I do not notice any flicker at 800x600x256.

     -- Darryl Okahata
	Internet: darrylo@sr.hp.com

DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion or policy of Hewlett-Packard or of the
little green men that have been following him all day.
Newsgroups: comp.os.ms-windows.programmer.win32
From: johnhall@microsoft.com (John Hall)
Subject: Re: NT Win32 DLL building problem
Date: 01 Oct 92 22:43:30 GMT
Organization: Microsoft Corporation

In article rion@Ingres.COM (Rion Cassidy (x3357) OGT) writes:
| You are only half right Sean.  The printf does not make sense in a windows
| application, but when you link his stuff with "subsystem:console" where
| printf should work, you still get "_main undefined".  Why does a library
| routine expect there to be a "_main"?  Using  "strlen" causes the same
| problem.  I have never understood the problem that Windows has with the
| standard library functions.

I think this usually happens if you are accidentally linking in
more than one c runtime library.  Personally I always use
crtdll.lib (not libc.lib or libcmt.lib) and you need to compile
with -D_MT and -D_DLL

Also, make sure your executable has the right entry: flag in the
link line.  One CRT entry calls _main, the other calls _WinMain

-- 
-------------------------
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: mikee@seas.gwu.edu (Mike Me)
Subject: Re: EISA vs local bus
Keywords: EISA VL
Organization: George Washington University
Date: Fri, 2 Oct 1992 13:37:45 GMT

In article <BvGyJH.1D6@huey.jpl.nasa.gov> brad@huey.Jpl.Nasa.GOV writes:
>In article <1992Oct1.134613.1581@netfs.dnd.ca>, rosenqui@ncs.dnd.ca (E. Rosenquist) writes:
>
>>#1 - I can't decide between a machine with an EISA bus or one with a
>>VESA local bus (VL).
>
>These are not mutually exclusive.  Most local bus machines only have
>one or two local bus slots; the rest can be EISA or ISA.  I believe
>the new Gateway 486/66DX2 machine (with the new Micronics motherboard)
>is a EISA VL-bus machine.
>
>But I may be wrong.
>
>-- 
>Brad Hines
>Internet: brad@huey.jpl.nasa.gov
>Jet Propulsion Lab, Pasadena, California

I believe this is wroung....
They sell a local BUS machine && an EISA machine... (october add)

later,
	MikeE


Newsgroups: comp.os.ms-windows.programmer.win32
From: alistair@microsoft.com (Alistair Banks)
Subject: Re: Is it time to split this newsgroup?
Date: 30 Sep 92 14:46:58 GMT
Organization: Microsoft Corporation

In article <1992Sep29.140006.13908@cam-orl.co.uk> thg@cam-orl.co.uk (Tim Glauert) writes:
>In article <2PoTRB4w165w@underg.UUCP>, max@underg.UUCP (Max Cray) writes:
>|> Actually since a lot of the traffic in this newsgroup is not about
>|> win32 programming at all, but about nt, I think what we need is a

I would stongly suggest that Win32 programming is kept in one place
and win16 in another. Please remember that Win32 programming includes
Win32 on Windows 3.1, and later on enahnced version of Windows - so please
dont split up the programming parts between Windows NT and Windows.

Also, please remember that "NT" is Northen Telecom - its a registerred
name, and not the name of any Microsoft Operating system. Our OS is
called "Windows NT" and today has alot in common with Windows, in
commn GUI, common shell, common apps,...

I'd seperate setup issues between windows nt and windows

So I think comp.os.ms-windows.nt.setup or comp.os.ms-windows.setup.win-nt
might be appropriate - we should think ahead and design a hierarchy that
can handle windows 3.x series, windows nt, "Modular Windows" series,
and be ready for other future versions of Windows. In general I
think its probably best to keep the .setup's together, and the
programmers sections together, rather than seperate things by the
particular product packaging, since the product packaging will change
more often than the pieces of technology contained within those
products - and I just left our "Windows for Workgroups", how could I?

-- Alistair

Newsgroups: comp.os.ms-windows.programmer.win32
From: tad@wrq.com (Tad Marshall)
Subject: Re: ///// .WAV file format??? \\\\\\\\\\
Organization: Walker Richer & Quinn, Inc., Seattle, WA
Date: Mon, 5 Oct 1992 23:44:36 GMT

In article <1992Oct1.141707.202945@uctvax.uct.ac.za> arcpau02@uctvax.uct.ac.za (Paul Archer) writes:
>
>Does anybody know the .WAV file format?
>
> I assume it is basically 8-bit data, but what is the format of the
> header? Any info would be greatly appreciated.
>
>Thanks in advance 
>
>  Paul Archer   (ARCPAU02@uctvax.uct.ac.zx)
>
> University of Cape Town

.WAV files are a type of RIFF file.  RIFF (Resource Interchange File Format)
files are composed of "chunks" which can be of different types, and can
include other chunks.  The files such as TADA.WAV that come with Windows each
contain a single chunk which is a "WAVE" type.

The WAVEfmt header gives the format of the data which follows.  There are
several supported formats, varying in sample rate, bits per sample, and
number of channels (mono or stereo).  8-bit sounds are, as you suggest, raw
data preceded by a header.  8-bit sounds are interpreted as having a minimum
value of 0x00 and a maximum value of 0xFF, with 0x80 as the "null" level.
16-bit sounds are in two's complement, so 0x8000 is the minimum value, 0x7FFF
is the maximum, and 0x0000 is the "null" (quiet) level.

This is pretty well documented in chapter 8 of the Multimedia Programmer's
Reference that comes with the Windows 3.1 SDK, and even better documented in
a separate Multimedia Programmer's Reference and Multimedia Programmer's
Workbook available from Microsoft Press (order codes MMPRRE and MMPRWO).

-- Tad Marshall
Newsgroups: comp.os.ms-windows.programmer.win32
From: alistair@microsoft.com (Alistair Banks)
Subject: Re: Instance data in Win32s
Date: 30 Sep 92 14:26:19 GMT
Organization: Microsoft Corporation
Distribution: usa

In article <CRAIGM.92Sep28182655@egnext1.SLAC.Stanford.EDU> craigm@egnext1.SLAC.Stanford.EDU (Craig Markwardt) writes:
>
>
>, does anyone know the Win32s subsystem
>will handle memory?  It would be convenient if it kept the stack out
>of the way and only allocated stack/data pages upon demand.  

The Win32s exetensions for  Windows 3.1 will indeed provide stacks
which grow as used, and will also provide the sparse memory allocation
you refer to -- Alistair
Newsgroups: comp.os.ms-windows.programmer.win32
From: mikee@seas.gwu.edu (Mike Me)
Subject: Re: Beginner question....
Organization: George Washington University
Date: Mon, 28 Sep 1992 01:16:48 GMT

Hi I am a beginner when it comes to NT, and just joined this 
group.

Quick question:

	I just ordered my CD and am looking forward to getting BUT!...
I have a TIGA graphics card. Its actually a Hercules graphics station
card, but with the tigacd prog. it turns tiga compatible.
Do I have to look forward to 640 * 480 * 16 for now?

Or is there a way to run the TIGACD programs? Its kinda like the same 
problem the TSENG diamond speedstar people were having with V-MODE.

Thanx,
From: kenyee@ksr.com (Ken Yee)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: error 0x69 kills NT boot!!
Date: 27 Sep 92 20:59:45 EDT
Organization: Kendall Square Research Corp.

Using dos2nt to install the NT beta, I get the following message:

Fatal System Error: 0x00000069
Phase 1 I/O initialization failed.

I copied the CDROM directories dos2nt, mstools, and q_a to the D:
partition and tried to install to the c: partition (I don't have a
CDROM player).

Has anyone seen this problem?  If not, could someone post this
message to compuserve or tell me how to e-mail or call Microsoft
tech support?

NT has a wd33c93.sys driver which looks like it will work with my
WD7000FASST SCSI card.  Does anyone else use this card?
The system also has 24Meg of RAM and a 200Meg drive with a 386/40 motherboard.

 thanks,

  ken  (kenyee@ksr.com)

Newsgroups: comp.os.ms-windows.programmer.win32
From: ch@sg1502.chemie.uni-marburg.de (Christoph H. Hochstaetter)
Subject: Re: How to run net cmds at boot time?
Organization: Philipps-University Marburg
Date: Thu, 1 Oct 1992 15:00:22 GMT

In article <1992Sep30.202724.21003@u.washington.edu>, tad@wrq.com (Tad Marshall)
writes:

|> >Seems like sometime I can do a "net view" and don't see the 
|> >other machines and later I can.  Could be my own problem but I haven't
|> >figured out what I'm doing wrong if it is :-).
|> 
|> My experience is the same as yours ... sometimes things show up and
|> sometimes
|> they don't, and I haven't discovered a pattern yet.  I can generally mount
|> a remote volume even when the machine doesn't show up in the list, however,
|> assuming that everything is up-and-running.
|> 

Servers announce themselves via unACKed broadcast packets, so other machines
sometimes don't get those packets, especially on ethernet segments with a
large number of machines. In addition, when NET VIEW is entered a broadcast
request is sent that servers should answer, similar to UNIX rup.

So don't be surprised, if NET VIEW doesn't always show up all servers. On the
other hand, this works quite reliable with LAN-MAN 2.x, so I think, that it
will work with the same reliability in the retail version.

Christoph
-- 
Internet: ch@sg1502.chemie.uni-marburg.de
BITNET: HAMPE2@DMRHRZ11
Fido: 2:243/660
Newsgroups: comp.os.ms-windows.programmer.win32
From: ch@sg1502.chemie.uni-marburg.de (Christoph H. Hochstaetter)
Subject: Re: Perr to Peer File Sharing Problem
Organization: Philipps-University Marburg
Date: Mon, 28 Sep 1992 16:52:12 GMT

In article <BvALqx.L8M@unx.sas.com>, sasdxk@skyhawk.unx.sas.com (Dave Kolb)
writes:
|> So I added another shared directory "c" path "c:\" and now I can see
|> and connect to my own shared directory using the fm/disk/connect menu.
|> 
|> My new shared directory seems to be defined exactly like the default
|> directories that were already defined (e.g. C$ and ADMIN$).  Is there
|> something special about the $ sign in the name?
|> 
|> Anyone have any ideas why the other machiens in the workgroup can't
|> see either the default shares or the new share I setup but can
|> detect the other machines active in the workgroup?

The $-sign by itself is not special in any way. But the default shares
are "Admin-only" shares. You must have administrative privileges on
the NT-machine to see and use these shares.

To use shares from an NT machine on another machine without administrative
privileges, define them via NET SHARE (e.g. NET SHARE ROOTC=C:\) on your
NT machine. Then you can use it from other machines with 
NET USE \\<NT-machine name>\ROOTC.

Christoph
-- 
Internet: ch@sg1502.chemie.uni-marburg.de
BITNET: HAMPE2@DMRHRZ11
Fido: 2:243/660
Newsgroups: comp.os.ms-windows.programmer.win32
From: sasdxk@skyhawk.unx.sas.com (Dave Kolb)
Subject: How to run net cmds at boot time?
Originator: sasdxk@skyhawk.unx.sas.com
Date: Tue, 29 Sep 1992 18:02:57 GMT
Organization: SAS Institute Inc.


Is there anyway to run things like "net start tcpipsvc" and
"net share ..." and "net use ..." commands at initial boot time?

I.E. Something like DOS' autoexec.bat or OS2's startup.cmd?

Does anyone else have consistency problems w/ the NT File Manager
and net commands in regards to sharing/using directories on other
machines?  Seems like sometime I can do a "net view" and don't see the 
other machines and later I can.  Could be my own problem but I haven't
figured out what I'm doing wrong if it is :-).

Can you share a cdrom on another machine?  I haven't tried this yet.

Thanks,

-- 
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: ch@sg1502.chemie.uni-marburg.de (Christoph H. Hochstaetter)
Subject: Re: Question about supporting CD ROM?
Organization: Philipps-University Marburg
Date: Mon, 28 Sep 1992 15:46:27 GMT

In Article <1992Sep22.162445.2740@tamsun.tamu.edu>, tpradeep@cs.tamu.edu
(Pradeep K Tapadiya) writes:

|> I have a SCSI adapter on my PC which drives my harddisk. Often
|> I unhook an optical drive from a Mac at our place and hook it up
|> to my PC through the SCSI adapter. This setup works fine. Therefore
|> I have a feeling that I can probably use the Apple CD-ROM presently
|> hooked to the Mac with my PC successfully.
|> 
|> The NT handout gives a list of supported CD-ROMs and Apple is not on
|> the list. My question is shouldn't the list of supported devices be
|> a function of supported adapters? In my case, if my SCSI adapter is
|> supported by NT, then shouldn't any device I attach to the adapter be
|> supported by NT? Can someone enlighten me on this subject?
|> 

We have two different Apple CD-ROMs here. They identify as Sony CDU-8001 and
Sony CDU-8002, if you query their SCSI-Ids.
Both work perfectly with NT with AHA-1542B.

regards,

Christoph
-- 
Internet: ch@sg1502.chemie.uni-marburg.de
BITNET: HAMPE2@DMRHRZ11
Fido: 2:243/660
Newsgroups: comp.os.ms-windows.programmer.win32
From: philipla@microsoft.com (Phil Lafornara)
Subject: Re: product name 
Date: 01 Oct 92 19:13:54 GMT
Organization: Microsoft Corporation

In article <1992Sep30.190350.160@pony.Ingres.COM> rion@Ingres.COM  writes:
>In article <1992Sep30.003620.15924@microsoft.com> philipla@microsoft.com (Phil Lafornara) writes:
>>
>>     I disagree - The product is not called NT - it's called Windows NT.
>>
>>					-Phil
>
>I don't know Phil.  This news group is called win32, not winnt.  But then,
>you ARE a Microsoft employee, so you SHOULD know.  Seems like I've heard
>Bill Gates state that the operating system was NT, the environment is Win32.

     The product name is Windows NT - the name of the main interface
to that product is Win32.  This makes comp.os.ms-windows.nt.setup an
appropriate name, since you set up the operating system, while
comp.os.ms-windows.programmer.win32 is also appropriate, since you
program to the interface and not to the operating system itself.


>Could someone clarify the official name of this product??

       Windows NT.

					-Phil
-- 
-------------------------------------------------------------------------
Phil Lafornara         				1 Microsoft Way         
philipla@microsoft.com				Redmond, WA 98052-6399 
Note:  Microsoft doesn't even _know_ that these are my opinions. So there.
Newsgroups: comp.os.ms-windows.programmer.win32
From: ben@sgi.com (Ben Passarelli)
Subject: Fault-tolerance (Was: NT Peer to Peer File Sharing)
Organization: Silicon Graphics, Inc., Mountain View, CA
Date: Fri, 2 Oct 1992 16:28:38 GMT

In article <1992Sep29.071105.8337@microsoft.com> alistair@microsoft.com (Alistair Banks) writes:
>"Lan Manager for Windows NT" will be desirable when administering
>networks with large numbers of Windows NT machines, or when
>server fault-tolerance is desired -- Alistair

What features are planned in the area of fault-tolerance?  Does this
include disk mirroring?  -- Ben
  


Newsgroups: comp.os.ms-windows.programmer.win32
From: kevin@edscom.demon.co.uk (Kevin Broadey)
Subject: isdigit('0') returns FALSE!!
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: Thu, 1 Oct 1992 16:31:34 GMT

I'm running Windows NT on an Olivetti PWS4000 (MIPS R4000 processor).
I'm porting a Windows 3.1 application so I'm using the MCL compiler.

One of my validation routines flags an error when it's given valid data.
It turns out that

	isdigit('0') == 0
	isdigit('1') == 0

Have I managed to wheel in a unicode library or something?


Heeeeeeeeeeeeeelp!!

Kevin
Newsgroups: comp.os.ms-windows.programmer.win32
From: jason@alpha.ee.ufl.edu (Jason Nadrowski)
Subject: Having a shell more like X Windows
Keywords: Posix, shell, nt, x
Organization: HSDAL
Date: Thu, 1 Oct 92 19:39:04 GMT

The preliminary version (july '92) did not, as I know of, have a shell
where the active window was the one with the mouse pointer over it as in
X Windows.  With NT the user would have to click on the window to make it 
active and consequently bring the window to the front.  With the addition 
of Posix in Oct/Nov can I expect to see a shell more like X, where I can 
have the mouse pointer on an underlapping window (opp of overlapping window) 
and be the active window?

If the above will not happen I would suggest you consider it.  I and everyone
that I have talked with would prefer an active window permitted to be
below other nonactive windows.

jason
From: kkt@philabs.philips.com (Kim-Kiat Tan)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: win16 & dos programs in nt
Date: 2 Oct 92 14:20:16 GMT
Distribution: usa
Organization: Philips Laboratories, Briarcliff, New York

In article <1992Sep30.145155.7566@microsoft.com> alistair@microsoft.com (Alistair Banks) writes:
>In article <1992Sep21.022934.14464@philabs.philips.com> kkt@philabs.philips.com (Kim-Kiat Tan) writes:
>>
>>	What is the status of running current dos and window 3.1 programs
>>in NT (final official release version) ? If there are exceptions, what are
>>they ?
>
>Windows NT will run the major Windows and MS-DOs programs. It will not run
>those which would compromise its security rating or robustness, such as
>those which re-program hardware or access "non-standard PC" devices. The

	I have a thunder board card and a Music Quest PC-MIDI card, can I run
dos and window 3.1 programs that uses that or do I need a different driver ?
I would appreciate also if you can give some examples of what you mean by 
"non-standard PC" devices.
	Like to get into developing software in NT but not ready to buy another
pc just for that (that's the case if I couldn't use my MIDI and sound card, I
need those). 
	I guess it boiled down to do we have NT drivers for those cards and also
for 24 bits color graphic card.
Newsgroups: comp.os.ms-windows.programmer.win32
From: kevin@edscom.demon.co.uk (Kevin Broadey)
Subject: _ctype values are wrong!
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, 2 Oct 1992 10:48:40 GMT

I am building an application on an Olivetti PWS4000 running the July
release of Windows NT using the MCL compiler.

I linked my application with the following libraries and isdigit('0')
returned zero (which it shouldn't).  I relinked it with libcmt.lib at
the start of the list and isdigit('0') returned a non-zero value (which
it should).

The libraries were:-

win32libs=	$(LIB)\gdi32.lib $(LIB)\kernel32.lib $(LIB)\user32.lib \
		$(LIB)\userrtl.lib $(LIB)\crtdll.lib $(LIB)\ntdll.lib

I ran MCL with -E -C and checked the preprocessor output.  The macro
version of isdigit() was being used, so I put in a MessageBox call to
wsprintf the value of

	(int)(_ctype+1)['0']

It said 0xE1.  The 0x04 bit ought to be set for a digit.


So the question is, which of the above libraries defines "_ctype" and
gives it the wrong values?
From: perkins@sousa.ltn.dec.com (Eric Perkins)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: EISA vs local bus
Keywords: EISA VL
Date: 5 Oct 92 16:33:15 GMT
Article-I.D.: sousa.1869
Reply-To: perkins@sousa.ltn.dec.com (Eric Perkins)
Organization: Digital Equipment Corporation, Littleton MA


The original question for this article stated that 16MB was a limit
for ISA systems.

I would like to point out that this is not the case. After
posting a question and having Microsoft point out that
NT can handle more than 16MB on an ISA system I can
state that in fact it does. We currently have two ISA systems
one with 32MB and the other with 28MB and Windows NT has no problem
seeing and using all of the memory installed in the system.

It also appears that Windows 3.1 is making good us of the 
extra memory as well.

===============================================================================
-- Note: All views questions, and thoughts are my own and in no way represent
--       those of my employer. I can be reached by the following means:
--
-- perkins@tallis.enet.dec.com                  -- (508) 486-6085 (Voice)
--                                              -- (508) 486-6014 (Fax)
-- Eric R. Perkins                             
-- Digital Equipment Corporation                
-- 295 Foster Street                            
-- LTN1-2/H09                                  
-- Littleton, MA 01453                          
===============================================================================
   
Newsgroups: comp.os.ms-windows.programmer.win32
From: mo@gizmo.bellcore.com (Michael O'Dell)
Subject: Re: SUN SPARC CD-ROM
Keywords: 
 
Reply-To: mo@bellcore.com
Organization: Center for Chaotic Repeatabilty
Date: Thu, 1 Oct 92 14:15:45 GMT

i missed the first of this, but i installed NT on a 486/33 with
an adaptec 1542B using a borrowed SunCD drive with no problems.
in fact, it's running right here right now.
	-mo
Xref: sparky comp.os.ms-windows.programmer.win32:1284 comp.unix.questions:11704