Lab 5-7 Exploring Operating System Functions
Observing 16-bit
and 32-bit applications in Windows Task Manager
1. Click
Start, and then click Run.
The Run dialog box appears.
2. In
the Open drop-down list, type \\nettech05\labfiles\lab1, and then click OK.
The Lab1 window appears.
3. Double-click
the following icons: Badapp32, Spind16, and Spind32.
The Bad App, SpinDIB:32, and
SpinDIB:16 applications appear.
4. Minimize
the Lab1 window, and arrange the
desktop so that you can see the three applications you started in the previous
step.
5. In
the SpinDIB:32 application, click the Open
button.
The Open dialog box appears.
6. Double-click
the Mcsekit.bmp file icon.
The Mcsekit.bmp image appears in
the SpinDIB:32 window.
7. In
the SpinDIB:16 application, click the Open
button.
The Open dialog box appears.
8. In
the File Name text box, type \\nettech05\labfiles\lab1\mcsekit.bmp, and then click OK.
The Mcsekit.bmp image appears in
the SpinDIB:16 window.
9. Verify
that the SpinDIB:32 and SpinDIB:16 applications are running by clicking the Spin! button in each application.
10. Click Start, and
then click Run.
The Run dialog box appears.
11. In the Open
drop-down list, type taskmgr, and
then click OK.
The Windows Task Manager window
appears.
Four applications appear on the Applications tab: two SpinDB
applications, Bad App, and Lab1 (the Lab1 window).
12. Open the Processes
tab, and then scroll down to the bottom of the list.
Many processes, including Badapp32.exe, Spind32.exe, and Spind16.exe
appear in the list.
13. Why is Spind16.exe,
along with Wowexec.exe, indented below Ntvdm.exe while Badapp32.exe
and Spind32.exe are not?
.
14. Open the Applications tab.
15. In the Task column, right-click SpinDIB:16 - Mcsekit.bmp, and then
click Go To Process.
The Processes tab becomes active, and Spind16.exe is selected.
The last two steps demonstrated
that Spind16.exe is the active
process of the SpinDIB:16 application.
16. Repeat the last two steps to complete the Process Name column of the following table:
|
Application name |
Process name |
Application type |
|
SpinDIB:16 |
Spind16.exe |
Windows 16-bit |
|
Bad App |
|
Windows 32-bit |
|
SpinDIB:32 |
|
Windows 32-bit |
17. Open the Processes tab.
18. On the Option menu, click Show
16-Bit Tasks to clear this option.
The Spind16.exe process and the Wowexec.exe process disappear from the list on the Processes tab.
19. On the Option menu, click Show
16-Bit Tasks again so that 16-bit applications appear in the list on the Processes tab.
Testing the
effects of a halted 32-bit Windows application
1. On
the Options menu, click Always On Top to clear this option.
2. In
the Bad App application, on the Action
pull-down menu, click Hang.
The fuse burns down, and the bomb
explodes.
3. Move
the mouse pointer over the Bad App window.
The mouse pointer changes to an
hourglass, demonstrating that Bad App is busy.
4. In
Windows Task Manager, open the Applications
tab.
Bad App shows a status of Not Responding.
5. In
the SpinDIB:32 and SpinDIB:16 windows, click the Flip! buttons.
Why do both applications continue
to respond normally even though the Bad App application is not responding?
6. In
Windows Task Manager, verify that Bad
App is selected, and then
click the End Task button.
The End Program - Bad App dialog
box appears, warning you that ending the application this way will cause the
loss of any unsaved data.
7. Click
the End Now button.
The Bad App application closes.
8. Leave
the SpinDIB applications running, and continue to the next procedure.
Observing the
results of GPF and halted applications
1. Restore
the Lab1 window, and
double-click the Badapp16 icon.
The Bad App application appears.
2. On
the Action menu, click GP-Fault.
When the fuse burns down, the bomb
explodes and a Badapp message box appears, stating that an
application error occurred.
3. Do
not click the Close button or
the Ignore button.
4. In
the SpinDIB:32 window, click the Spin!
button.
The application responds to the
spin request.
5. In
the SpinDIB:16 window, click the Spin!
button.
The application does not respond.
6. In
the Badapp message box, click
the Close button.
An Application Error message box appears.
7. Click
the Close button.
8. In
the SpinDIB:16 window, click the Spin!
button.
The application is now able to
respond.
9. In
the Lab1 window, double-click
the Badapp16 icon again.
The Bad App application appears.
10. On the Action menu,
click Hang.
When the fuse burns down, the bomb
explodes and the application halts.
11. Move the mouse pointer over the SpinDIB:16 window.
SpinDIB:16 does not respond.
12. Move the mouse pointer over the SpinDIB:32 window.
The application is running
normally.
13. Using Windows Task Manager, close Bad App.
14. Move the mouse pointer over the SpinDIB:16 window.
m
The application
is running normally.
m
After you halted
Bad App, SpinDIB:16 was no longer responsive but SpinDIB:32 was.
m
After you closed
Bad App by using Windows Task Manager, SpinDIB:16 responded normally.
m
Why did hanging
Bad App affect SpinDIB:16 but not SpinDIB:32?
15. Leave the SpinDIB:16 and
SpinDIB:32 windows open for the next procedure.
Running shared
and exclusive Windows On Windows Virtual DOS Machines (VDMs)
1. Click
Start, and then click Run.
The Run dialog box appears.
2. In
the Open drop-down list, type cmd, and then click OK.
A command window appears.
3. At
the command prompt, type start /separate
\\nettech05\labfiles\lab1\spind16.exe,
and then press Enter.
4. In
Windows Task Manager, open the Processes
tab.
A number of processes appear,
including two ntvdm processes.
5. Why
are there two ntvdm processes running?
6. Close
the copy of SpinDIB:16 that you opened in step 3 of this procedure.
7. Close
the command window.
8. Verify
that the SpinDIB:16 and SpinDIB:32 applications you opened in Exercise 2 are
still running.
9. Restore
the Lab1 window.
10. Select the Spind16 icon.
11. On the File menu,
click Create Shortcut.
A Shortcut message box appears, stating that a shortcut cannot be
created in the Lab1 window but
it can be created on the desktop.
|
Note |
You cannot create a shortcut in
the Lab1 window because your student account does not have write access to this
folder.
12. Click the Yes button.
The Shortcut To Spind16 icon appears on the desktop.
13. Right-click the Shortcut To
Spind16 icon, and then click Properties.
The Shortcut To Spind16 Properties dialog box appears, and the Shortcut tab is active.
14. Select the Run In Separate
Memory Space check box and the Run
As Different User check box, and then click OK.
15. Double-click the Shortcut
To Spind16 icon.
The Run As Other User dialog box appears.
16. Why did this dialog box appear?
17. Select the Run The Program
As serverxx\administrator radio
button, and then click OK.
18. Verify that two ntvdm processes appear in Windows Task Manager.
19. In the Lab1 window,
double-click the Badapp16 icon.
The Bad App application appears.
20. On the Action menu,
click Hang.
The fuse burns down, and the bomb
explodes.
21. Check the status of both running copies of SpinDIB:16.
22. Why is one copy of SpinDIB:16 not responding while the other is?
23. In Windows Task Manager, close Bad App.
24. Close Windows Task Manager, the SpinDIB applications, and the Lab1 window.
Attach screen shots and the
answers to the questions to your lab report.