-=PCTechTalk=- Re: odd problem
- From: "Mikey" <mtg1021@xxxxxxxxxxxxx>
- To: <pctechtalk@xxxxxxxxxxxxx>
- Date: Tue, 17 Sep 2002 07:28:46 -0500
WHOA HORSE!!! dang I don't even understand most of the terms here let
alone what they mean sheesh I am only a lowly trader in commodities which
I can explain easily but the stuff is like reading ancient Hebrew or some
thin so please explain in dog and cat terms what this means
----- Original Message -----
From: "GuitarMan" <PCTech@xxxxxxxxxxxxxxx>
To: <pctechtalk@xxxxxxxxxxxxx>
Sent: Tuesday, September 17, 2002 1:27 AM
Subject: -=PCTechTalk=- Re: odd problem
>
> Mikey,
> Well, that's not going to be so easy to describe or understand even if
I
> get the description perfect. LOL
>
> They don't affect RAM directly, but they directly affect how Windows
is
> able to handle and divide system resources among various device drivers.
> Indirectly, this does include the allocation of RAM. Upon receiving a
> hardware interrupt, Windows allocates one of its stacks to handle the
> communication between the system (software and or the operating system)
and
> the hardware device. Below is Microsoft's description of how to take
> control of the stack allocation under WinXP.
>
> **********************************************************
>
> Stacks:
> Supports the dynamic use of data stacks to handle hardware interrupts. To
> use this environment variable, place it in your Config.nt file.
>
>
> Syntax
> stacks=n,s
>
>
>
> Parameters
> n
> Specifies the number of stacks. Valid values for n are 0 and numbers in
> the range 8 through 64.
> s
> Specifies the size, in bytes, of each stack. Valid values for s are 0
and
> numbers in the range 32 through 512.
> Remarks
> Default settings
> The following table shows the default settings for the stack command.
> a.. Computer Stacks
> IBM PC, IBM PC/XT, IBM PC-Portable 0,0
> Other 9,128
>
> b.. Special cases for stack allocation
> Upon receiving a hardware interrupt, Windows XP allocates one stack from
> the specified number of stacks. When you specify 0 for the n and s values,
> Windows XP allocates no stacks. If the values are 0, each running program
> must have enough stack space to accommodate the computer's hardware
> interrupt drivers. Many computers operate correctly, saving some memory
for
> programs, with n and s values of 0. If, however, your computer becomes
> unstable when you set these values to 0, return to the default values.
>
> Examples
> To allocate eight stacks of 512 bytes each for hardware-interrupt
handling,
> add the following command to your Config.nt file:
>
> stacks=8,512
>
> Formatting legend
> Format Meaning
> Italic Information that the user must supply
> Bold Elements that the user must type exactly as shown
> Ellipsis (...) Parameter that can be repeated several times in a
> command line
> Between brackets ([]) Optional items
> Between braces ({}); choices separated by pipe (|). Example:
> {even|odd} Set of choices from which the user must choose only one
> Courier font Code or program output
>
>
> **********************************************************
>
> Hopefully, you can make heads or tails out of the above. I'm not sure
> if the formatting will survive the copy/pasting. If not, I'll redo it
> manually and resend it into the group. LOL
>
> Peace,
> G Man
>
> PCTechTalk Owner
>
> ----- Original Message -----
> From: "Mikey" <mtg1022@xxxxxxxxxxxxx>
> To: <pctechtalk@xxxxxxxxxxxxx>
> Sent: Monday, September 16, 2002 8:04 PM
> Subject: -=PCTechTalk=- Re: odd problem
>
>
> what are stacks and do they affect ram at all
>
> To unsub or change your email settings:
> //www.freelists.org/webpage/pctechtalk
>
> To access our Archives:
> http://groups.yahoo.com/group/PCTechTalk/messages/
> //www.freelists.org/archives/pctechtalk/
To unsub or change your email settings:
//www.freelists.org/webpage/pctechtalk
To access our Archives:
http://groups.yahoo.com/group/PCTechTalk/messages/
//www.freelists.org/archives/pctechtalk/
Other related posts:
