| Get this A+ OS CertiGuide for your own computer. |
Click Here! Use coupon code "SAVE50" to get it half price! |
|
|
Booting
(Page 2 of 2)
Windows NT/2000 Memory Model
NT/Windows 2000 differ in
many ways from DOS/Windows 3.x/9.x/Me. One huge difference is the fact
that NT 3.x/4/W2K are true 32-bit Operating Systems that use
a flat model for memory. That is to say there is
no HIMEM.SYS or EMM386.EXE, as there was in DOS and earlier
versions of Windows, because there is no real and extended
memory. All memory starts at zero and just goes
up. Applications that are written to operate in a 32-bit memory mode
always run in their own separate memory space.
Even with this strong distinction
between different processes, NT sometimes tries to take a few little
short-cuts in the name of efficiency. One of these is that all the Windows
Explorer windows you have open, potentially viewing many folders at
once, are managed by the same copy of the Windows Explorer program.
This is done because its faster to open a window if youre
not ALSO starting up a new copy of a program at the same time. Alas,
if Windows Explorer locks up due to a problem in one window, your other
Windows Explorer windows also lock up. This is not good for reliability.
So, Microsoft provides the option to run each folder window with a separate
copy of the Windows Explorer, if youre willing to trade a bit
of speed for increased reliability.
To enable this go the Control
Panel , open the Folder Options applet, click the View
tab and check the Launch folder windows in a separate process
box, as shown in Figure 147.
Figure 147: The Launch folder windows in separate process option

|
Separate Memory
Try running an application it in its own separate (protected) memory, if the application is misbehaving. |
![[spacer]](1p.gif) Shared Memory
16-bit applications can run in shared or protected memory. The challenge with running some applications in protected memory is they may be unable to dynamically share data with another program, say from Word to Excel. |
Sharing Downside
The down side of 16-bit programs that run in shared memory is if one application crashes, it will take down all applications that are sharing that memory. |
| If you find CertiGuide.com useful, please consider making a small Paypal donation to help the site, using one of the buttons below. You can also donate a custom amount using the far right button (not less than $1 please, or PayPal gets most/all of your money!) In lieu of a larger donation, you may wish to consider buying an inexpensive PDF equivalent of the CertiGuide to A+ (Operating Systems) from StudyExam4Less.com. (Use coupon code "SAVE50" to save a full 50% off the already low price!) Thanks for your support! |
|
|
Home -
Table Of Contents - Contact Us
CertiGuide to A+ (Operating Systems) (http://www.CertiGuide.com/apluso/) on CertiGuide.com
Version 1.0 - Version Date: January 7, 2005
Adapted with permission from a work created by Tcat Houser.
CertiGuide.com Version © Copyright 2005 Charles M. Kozierok. All Rights Reserved.
Not responsible for any loss resulting from the use of this site.
|