HDTenEightyP/NetNews huggingface dataset:
From: ee0n+@andrew.cmu.edu (Eric James Ewanco)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Windows 3.1 & Processor Mode Swap
Date: 12 Sep 92 16:52:24 GMT
Article-I.D.: andrew.Iegd38G00WB98APb1X
Organization: Carnegie Mellon, Pittsburgh, PA

Hi. I've been having a discussion with someone about WInodws over DOS, and I
had some questions about how Windows behaves when DOS and BIOS calls are made.

Suppose a Win32 application mades a DOS call  First, does the trap go into
Windows in Protected mode, or into DOS (in 21h)?  I assume it goes into Windows
and stays in protected mode.  When Windows executes the call, what processor
mode does it go into when it transfers to DOS? Real mode (i.e. it switches out
of protected mode) or virtual 8086 mode?  When DOS executes, does Windows
maintain memory and I/O protection, or is the machine unprotected when it
executes the DOS call? For example, let's say I did a DOS call that causes
other process memory to be mangled (assuming it's in the lower 640k) -- will it
be mangled or will Windows trap?  Now DOS, as it is wont to do, will often call
BIOS in the execution of a call.  Will this 1) Trap into protected mode,
Windows code, which Windows will then switch into real/virtual 8086 code before
it makes the actual bBIOS call; 2) Trap into the BIOS directly in real mode?

Hence, the big question, how many times does Windows switch between real and
protected mode (protected and virtual 8086?) in a Win32 DOS call? Six is my
guess.

Next question, related: what happens when a DOS program does a DOS call?  Does
the processor switch to protected mode, and then do what a Win32 program does?
Or does it run in virtual 8086 mode all the way?
Does a similar process happen with a Win32 or DOS program calls BIOS?

Final question: DOS is still non-reentrant under Windows, right, so only one
DOS call may be executing at any given time?

Basically I am trying to convince someone that Windows NT will be much more
efficient and less crash-prone than Windows on top of DOS.  I am trying to show
how awkward DOS compatibility makes Windows execution.

Thanks for the help in understanding.

Eric
Newsgroups: comp.os.ms-windows.programmer.win32
From: storm@uriel (Marc WANDSCHNEIDER)
Subject: Problems with LINK386 and ET4000
Organization: SOCS, McGill University, Montreal, Canada
Date: Sun, 13 Sep 1992 22:03:16 GMT


Got the NT PreRelease SDK, and have been fiddling with it to try and see 
how things are.

I have noticed a couple of things that are driving me kinda batty though:

The Release Notes in Appendix A talk about adding Drivers for the ET4000
chip to driver highe resolutions.

Following the instructions given there just caused my screen to garble
stuff up big time though -- as if the frequency was all hosed.  I am curently
using my SpeedStar with my AAMAZING monitor in High-Res (60Hz) without
troubles.

Has anybody else experienced this?

The other big problem I've had is with linking.

cl386 complains that it can't find link386, and the link.exe just doesn't
seem to like me.

A simple program to printf"hello" just won't link, even though it compiles
file.

There are usually problems with about 20 undefined symbols errors.

How do I go about just getting it to link Character based applications.



(P.S.  I can't really afford a Compu$crew account, so I have to ask these
things here -- sorry)

Toodlepip!
Marc 'em.

-- 
  storm@cs.mcgill.ca           McGill University         C program run.  Run  
  Marc Wandschneider           Montreal, CANADA          Program run! PLEASE!
      "When 900 years old you reach, look as good you will not." - Yoda
				"Ow!" -J.F.K.~
From: dww2@po.CWRU.Edu (David W. Woodward)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: Reading *.ps files
Date: 15 Sep 1992 02:36:38 GMT
Organization: Case Western Reserve University, Cleveland, OH (USA)
Reply-To: dww2@po.CWRU.Edu (David W. Woodward)
NNTP-Posting-Host: slc12.ins.cwru.edu


I should have made it clear in my first post that the system I need to read
the *.ps docs files on does not have WIN NT on it.  It doesn't have a CD
ROM drive on it, so we installed parts of it on the machine that does (at
work) and backed up the docs and we are trying to read them at home.  It is
a 386-33, 8 megs, Win 3.1 etc, just not Win NT.

Thanks again!

Dave
From: "peter gottlieb" <peter.gottlieb@channel1.com>
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: ddk price too high??
Date: 11 Sep 92 02:23:53 EST
Reply-To: "peter gottlieb" <peter.gottlieb@channel1.com>
Distribution: comp
Organization: Channel 1 Communications

DM>Question for all of you. Would you buy a CD only version of the
DM>NT DDK??

YES!!

Many of us developers have tight budgets, but have the printers to
print out what we need.  A CD only version would be exactly what I
would need!!

Thank you very much for taking the time to ask!

---
  OLX 2.2  My mouse has only one ball, but a 6' tail.
--
Channel 1 (R)   Cambridge, MA

From: mike-b@hpfcso.FC.HP.COM (Michael Bishop)
Date: Fri, 4 Sep 1992 15:29:30 GMT
Subject: Re: Experiment in booting NT
Organization: Hewlett-Packard, Fort Collins, CO, USA
Newsgroups: comp.os.ms-windows.programmer.win32

Just to followup on this thread:  All you need to do to save/restore the
boot sector on your hard disc is to look at the dos2nt script on the
CD-ROM.  In that script are the steps (using DEBUG which is also on the
CD-ROM) to both save and restore the boot sector.  I used this
information to create a little toolkit that I put on a bootable floppy
for when I need to excise or reactivate NT on my system.  Works great.

Michael Bishop
Newsgroups: comp.os.ms-windows.programmer.win32
From: jkf@Franz.COM (Sean Foderaro)
Subject: PE and lib format
Organization: Franz Inc., Berkeley, CA
Date: Fri, 11 Sep 1992 17:06:42 GMT

 I'd like to write some windowized browsers for NT .exe files and .lib files. 
I can't find any .h files that describe the format of these files. 
I'd appreciate a pointer to the correct include files or a published spec
for these files.    


Newsgroups: comp.os.ms-windows.programmer.win32
From: ebergman@nyx.cs.du.edu (Eric Bergman-Terrell)
Subject: Re: setjmp/longjmp
X-Disclaimer: Nyx is a public access Unix system run by the University
	of Denver for the Denver community.  The University has neither
	control over nor responsibility for the opinions of users.
Organization: Nyx, Public Access Unix at U. of Denver Math/CS dept.
Date: Tue, 8 Sep 92 21:47:25 GMT

In article <1992Sep8.202606.13762@xanadu.com> ravi@xanadu.com (Ravi Pandya) writes:
>The July NT x86 toolset does not include setjmp/longjmp - the header
>file is ifdef'ed out, and it is not in the library. It is a fairly
>straightforward piece of assembly code to write, but before I do it,
>I'd like to know if there are any subtle reasons why the obvious
>approach won't work. Does NT do any odd messing around with stacks,
>privilege levels, etc that would make it hard? I have a suspicion that
>something like this is the reason it is not in the library.
>
>Unfortunately, our port from UNIX to NT cannot proceed without it, or
>some facsimile, since it is used in our own exception handling
>package, which is used everywhere. We could move it over to the MS
>exception handler, except that it doesn't seem to be available nor
>documented yet... Any suggestions?
>
>Furthermore, the compiler insists on treating a function in which some
>control paths do not return as an error. Since a lot of our functions
>might terminate by raising an exception and doing a longjmp, there are
>hundreds of places in our code that provoke this error message. Is
>there any way to turn it off, or at least downgrade it into a warning?
>
>Thanks!
>	--ravi
>
>	Ravi Pandya
>	Xanadu Operating Company
>	1891 Landings Drive
>	Mountain View CA 94043
>	415 903 1316
>	415 903 1399 fax
>	ravi@xanadu.com


Ravi:

You might want to read about Catch() and Throw() in the Windows API docs.

Terrell
From: bagwill@swe.ncsl.nist.gov (Bob &)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: multiple threads per window?
Summary: multiple threads per window?
Keywords: threads
Date: 9 Sep 92 15:28:31 GMT
X-Newsreader: Tin 1.1 PL4

With NT, you can have multiple threads per process and multiple windows
per process.  Am I correct in assuming you can have at most one thread
issuing WIN32 calls per window?

--
Bob Bagwill	NIST/Computer Systems Lab/Distributed Systems Engineering Group
Newsgroups: comp.os.ms-windows.programmer.win32
From: assela@aix.rpi.edu (A. Andre Asselin)
Subject: Re: fatal error 0x69 on first boot
Keywords: 69 boot install 
Date: Mon, 14 Sep 1992 04:19:59 GMT

After I posted this, I found the FAQ and the entry on this.  I will try out
the suggestions there and see if it helps....
       - Andre Asselin (assela@rpi.edu)
Newsgroups: comp.os.ms-windows.programmer.win32
From: alistair@microsoft.com (Alistair Banks)
Subject: Re: Process Security in NT
Date: 12 Sep 92 03:08:28 GMT
Organization: Microsoft Corporation

In article <sxjcb-100992122022@sxjcb.uacn.alaska.edu> sxjcb@orca.alaska.edu (Jay C. Beavers) writes:
>
>I'm surprised to find that NT requires you to log in.  This brings up the next
>question which I haven't found an answer to, does NT have user security
>restrictions on processes?  I.E.  does this process run in the background
>with this security level while a separate process runs with a different
>security level? 

Windows NT requires you to login, since it is a secure system which controls
access to reseources by user-id/password pairs, locally, and accross a
network

Yes, Windows NT runs background processes (which we call services) with
different security contexts

>If so, why all the moaning about lack of multi-user
>support in NT?  All the basics are more than present and a telnetd is
>nothing more than a background daemon that hasn't been written yet.

Agreed

>BTW, is anyone thinking of writing a GUI version of telnet or rlogin?  Is
>it going to be necessary or is RPC and peer-to-peer networking going to
>totally replace the command-line login metaphor?

Windows NT comes with "a GUI telnet" - telnet is provided as a comm
driver, and you can simply use Terminal and select the "telnet" port
instead of com1, com2, etc

Net Manage have already shown their Telnet for Windows ported to Windows NT,
and I'm sure that rlogin and the rest will follow

>Are daemon and process bad words for NT that have been replaced with more
>'MC (Microsoft Correct)' jargon?  Threads means processes, but how about
>daemon?  Background thread?

Threads dont mean processes at all - Daemons may well be compared to
services, unix processes to Windows NT processes, but threads are
multiple paths of execution within the same code and dataspace in
a single process - ie, a register set and unit of execution - some
unixes have threads, but threads arent Microsoft jargon

-- Alistair
From: jyl@burgess.eng.sun.com (Jacob Levy)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: Re: NT problems with logitech bus mouse?
Date: 9 Sep 92 10:01:40
Organization: State Retirement Home for Retarded Slugs
Reply-To: jyl@toss.eng.sun.com
NNTP-Posting-Host: burgess
In-reply-to: act@softserver.canberra.edu.au's message of Wed, 9 Sep 92 03:35:44 GMT


>I thought I saw mail on compuserve/winnt that suggested that at the moment
>only the uSoft mouse was supported at present??

I'm using logitech serial mouse. It's usable but not ideal.

--JYL
From: perkins@sousa.ltn.dec.com (Eric Perkins)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Found functions that might give CPU time?
Date: 8 Sep 92 18:26:39 GMT
Reply-To: perkins@sousa.ltn.dec.com (Eric Perkins)
Organization: Digital Equipment Corporation, Littleton MA


Well, I sort of answered my last question. By using the COFF
utility that was provided with the SDK, I dumped out the imported
functions, and sure enough there is a set of them, from the 
ntdll.dll module, which I am sure has the information that I 
need to get the amount of CPU time a process/thread is taking. Fuctions
like NtQueryInformationProcess might be useful.

Is Microsoft going to make these calls public? Here is the list of 
calls that I found PVIEW.EXE making:

=========================================================================
            ntdll.dll

               700E8 characteristics
                   0 time date stamp Sat Feb 05 22:28:16 2106
                 0.0 version

                 25   NtClose
                 4E   NtGetContextThread
                 68   NtOpenThread
                 76   NtQueryInformationProcess
                 7C   NtQueryObject
                 83   NtQuerySystemInformation
                 87   NtQueryVirtualMemory
                 8C   NtReadVirtualMemory
                12A   RtlExtendedIntegerMultiply
                138   RtlFreeAnsiString
                151   RtlInitAnsiString
                162   RtlLargeIntegerAdd
                164   RtlLargeIntegerDivide
                168   RtlLargeIntegerSubtract
                1B6   RtlTimeToTimeFields
                1B8   RtlUnicodeStringToAnsiString
                1CB   RtlZeroMemory
                1C1   RtlUnwind

=========================================================================


-- Eric Perkins
-- perkins@tallis.enet.dec.com
-- Views and comments are my own and not those of my employer.

Newsgroups: comp.os.ms-windows.programmer.win32
From: RAICER@LSTC2VM.stortek.com (Bob Raicer)
Subject: Re: : DDK Price too high??
Organization: StorageTek SW Engineering
Date: Fri, 11 Sep 1992 14:52:32 GMT

I and the others I work with would definitely buy the DDK if it
and the doc were available on CD-ROM.  The format isn't terribly
important, but I do agree with the others who would prefer the
Windows help file format.  Having the doc in Word for Windows
format would also be very acceptable (at least the doc could
be selectively printed on a variety of printers).  The Postscript
format would be ok, but definitely not preferred.
 
Whatever format you choose, I encourage you to continue to give
your customers a choice about documentation - hardcopy or CD-ROM.
Having the doc in a machine processable format makes it much easier
to use.
 
Thanks for listening and giving us the opportunity to help you
make NT a success.
----------------------------------------------------------------------
Bob Raicer  (raicer@lstc2vm.stortek.com)
Storage Technology Corporation
2270 South 88th Street
Louisville, Colorado 80028-6100
(303) 673-5087
----------------------------------------------------------------------
Newsgroups: comp.os.ms-windows.programmer.win32
From: johnhall@microsoft.com (John Hall)
Subject: Re: Getting the Process/Thread CPU Time:
Date: 14 Sep 92 06:55:34 GMT
Organization: Microsoft Corporation

In article perkins@sousa.ltn.dec.com (Eric Perkins) writes:
| 
| Has anyone seen any API which will give the amount of CPU
| time a thread or process has used up? The program Pview that
| comes with the SDK can do this so there must be a way with the 
| API to do this, right?

Mostly, you need to use the API's already there in new and
interesting ways.  On the ftp server under OS2toWindows
[sort of where I hang out] I placed a *rough* example of how
to do this with the PDC build.

Yes, Perfmon does use a few Nt calls because not everything
of interest was exposed through the official mechanisms by
the PDC build date.  Those Nt calls are not (according to
the designer) necessary in future versions but no word on
when it will be cleaned up.

Brief how to:

The counters available can vary from system to system, and
theoretically the index number of the counters can as well.
You find the counters for a given system by looking at:
HKEY_LOCAL_MACHINE\\Software\\Microsoft\\CurrentVersion\\
Perflib\\<Lang ID -- '409' for now>\\Counters as a set
of MULTI_SZ data which looks like:
"2" "% Process Time" "4" "Processes" etc.
There is also a Help value with odd numbers which explains
each counter string.
"5" "List of Processes active in the local machine"

The perf2.zip I uploaded contains a program called
'perf1.exe' which dumps all this in a useful manner
(as #define's).  For reasons I explain, at the current state
of the system you probably want to hard code these values
[after figuring out what they are].

Then, armed with values for: Processes, Threads, Total Process
time, Total thread time, User thread time, Privlidged thread time
the algorithm looked like this:

Query HKEY_PERFORMANCE_DATA\\Global.  You probably have to get
it multiple times till you grow your buffer big enough.

When this exceeds, you have all the performance data (as a snapshot)
that anyone could want -- you just need to interpret it.

Interpretation:

Basically, you walk the structures contained in winperf.h.
Loop through all objects looking for the objects of interest
(Processes and Threads) save pointers to them.

Examine the Process Object and Thread Object looking for
counter definitions (type, offset).

Loop through all process instances:
  [Instance 0 is special, it has no threads by definition]
  print the process name [it is in unicode!]
  output Process Time data.
  For every THREAD instance, see if the thread parent is this
     process instance.  If it is accumulate the info.
  output thread data.

This yields a simple output.  I discuss some extentions to
make this a true time() system.  Again, this is rough but
I hope it helps.






-- 
-------------------------
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: c263-ah@cs.berkeley.edu (Class Account)
Subject: GetClipRgn and DCs
Organization: CS Dept. Snakepit - Do Not Feed.
Date: Sat, 5 Sep 1992 09:35:49 GMT

The help file says only certain DCs have valid regions accessible to
GetClipRgn.  But all the DCs I've created from GetDCEx and even BeginPaint
have caused GetClipRgn to return an error status.  Does this call work at
all or am I missing some vital clue?

							Jeffrey
Newsgroups: comp.os.ms-windows.programmer.win32
From: toddy@uni-paderborn.de (Thomas Rose)
Subject: Windows NT Beta on CD Rom in Germany
Organization: Uni-GH Paderborn, Germany
Date: Wed, 9 Sep 1992 11:02:49 GMT

Hi !

A few days ago, i have read that you can get Windows NT on a CD Rom from
Microsoft Bielefeld for 168 DM. What does this offer include (the final
product ???), and which CD-Rom do i need ? In which way works the 
installation, and is my machine (486-33, 16MB, 540MB Conner SCSI, 
Adaptec 1542B, ET4000 1MB VGA, Wangtek Streamer) supported by NT.

Are there Drivers for 1024x768 in 16/256 Colours ?


           Thanks for helping !

                        Tom


toddy@uni-paderborn.de





P.S.: Is these offer good, does NT work properly ?

Newsgroups: comp.os.ms-windows.programmer.win32
From: leehart@microsoft.com (Lee Hart)
Subject: Re: Loading device drivers before Flexboot
Date: 11 Sep 92 12:26:51 GMT
Organization: Microsoft Corp.
Keywords: NT

In article <1992Sep10.174706.9513@utdallas.edu>, paschall@utdallas.edu (Dwayne Paschall) writes:
> I have a couple of questions that someone may have solutions. I need to 
> load a couple of device drivers before the Flexboot load NT (or DOS). I 
> tried putting them in config.nt and autoexec.nt. Soem of them loaded, 
> but the last one or two did not (this also prevented Flexboot from loading). 
> 
> Does anyone have suggestions for work-arounds (other than "ask the 
> Compu$erve forum")?
> Let me know direct if you do!!

Let me guess what you are really trying to do:  You have either a strange 
partitioning scheme that requires a device driver, or you are using a
disk compression utility to compress your data on your drive.  You want to
put Windows NT on this partition.  At this time, this will not work.

NTLDR (and NTDETECT.COM) are not MS-Dos apps - they are 'BIOS' apps, since
the only APIs they call are the BIOS APIs, to read from the disk, query
the system, etc.  As a result, they do not support device drivers, with
the exception of NTBOOTDD.SYS, which is the SCSI miniport driver for
your SCSI card (this file is optional in most cases)

And yes, Compuserve is the best place to get support at this time.

Lee
I can't always speak for myself; how could I speak for Microsoft?
Newsgroups: comp.os.ms-windows.programmer.win32
From: alistair@microsoft.com (Alistair Banks)
Subject: Re: Does NT provide the Windows for Pen extensions?
Date: 10 Sep 92 03:11:48 GMT
Organization: Microsoft Corporation
Keywords: windows pen NT extensions

In article <18j99tINNk0p@agate.berkeley.edu> gwm@bravo.berkeley.edu (Garry Martin) writes:
>Are the Windows for Pen extensions that are part of the Windows 3.1 SDK 
>supported/included as part of Windows NT?

No, the Windows for Pen extensions are not supported on the first release
of Windows NT. We think that the Pen-based market will favour the features
of rom-based ms-dos & windows 3.1 and other "portable" features over
those of Windows NT in the short term, and have decided to expend our
finite resources on further developping other features for Windows NT
in this first release.

If you can define a particular market need for the features of Windows NT
and the Pen extensions, we'd be interested in that feedback - do send it
to me

-- Alistair
Newsgroups: comp.os.ms-windows.programmer.win32
From: paschall@utdallas.edu (Dwayne Paschall)
Subject: Loading device drivers before Flexboot
Keywords: NT
Reply-To: $USER@utdallas.edu
Organization: The University of Texas at Dallas
Date: Thu, 10 Sep 1992 17:47:06 GMT

I have a couple of questions that someone may have solutions. I need to load a couple of 
device drivers before the Flexboot load NT (or DOS). I tried putting them in config.nt 
and autoexec.nt. Soem of them loaded, but the last one or two did not (this also prevented 
Flexboot from loading). 

Does anyone have suggestions for work-arounds (other than "ask the Compu$erve forum")?
Let me know direct if you do!!
-- 
---------------------------------------------------------------------------
  //\    //\\\                 M3    "The ULTIMATE Driving Machine"
 //  \  //  \\\                M5          paschall@utdallas.edu
//    \//    \\\otor Sport     M7            
---------------------------------------------------------------------------
From: sxjcb@orca.alaska.edu (Jay C. Beavers)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Process Security in NT
Date: 10 Sep 92 20:28:27 GMT
Followup-To: comp.os.ms-windows.programmer.win32
Organization: University of Alaska Computer Network


As I impatiently await the arrival of my very backordered NEC CDR-84, I've
been perusing the documentation that comes with the NT pre-beta SDK and I'm
surprised to find that NT requires you to log in.  This brings up the next
question which I haven't found an answer to, does NT have user security
restrictions on processes?  I.E.  does this process run in the background
with this security level while a separate process runs with a different
security level?  If so, why all the moaning about lack of multi-user
support in NT?  All the basics are more than present and a telnetd is
nothing more than a background daemon that hasn't been written yet.

BTW, is anyone thinking of writing a GUI version of telnet or rlogin?  Is
it going to be necessary or is RPC and peer-to-peer networking going to
totally replace the command-line login metaphor?

Are daemon and process bad words for NT that have been replaced with more
'MC (Microsoft Correct)' jargon?  Threads means processes, but how about
daemon?  Background thread?

______________________________________________________________________________
                                        |    jay@seaspray.uacn.alaska.edu
Jay C. Beavers                          |    sxjcb@orca.alaska.edu
University of Alaska Computer Network   |    sxjcb@alaska.bitnet
________________________________________|_____________________________________
Newsgroups: comp.os.ms-windows.programmer.win32