( SO Ê SC ,SU ¢SAVÒSADm SAP3 SAA¥SM ­SMB2FO 4FR ªFI ‹FIB‹FB IFM  PO ­"PA ­$PN 'PM ›)PB ,TO ‹.TM È0DO ø1DR Q4DI ¼6DE 9QO O;QY )=QYB)=QA ÿ>QABÿ>QN 5AQNB5AQM ¤BVO ¶DVM ‚FHO 4HHE ×IXE KKXR ÖLThe ÿ úSystem Overview ÿ øscreen shows the main components of your PC. Shown here are standard features most often used to describe a particular system: processor (CPU), manufacturer, video adapter type, number and type of I/O ports and memory capacity. This screen tells you if you have a numeric coprocessor. It tells you the developer and date of the BIOS firmware. This information is basic to any discussion of a computer system. It's what you would tell a friend if you were describing your system. Technical support personnel often need this information to resolve a problem. ÿÿThe ÿ úSystem CONFIGÿ ø screen shows the contents of your CONFIG.SYS file. Statements in this file extend your operating system in several ways. This file may load device drivers to support additional hardware. It is also used to increase the memory DOS uses to support disk and file access. A look at this file tells you how your system may differ from another system. It serves to remind you of the your system's special needs and capabilities. Many commands in CONFIG.SYS affect memory usage. A periodic review of this file gives you an opportunity to understand or fine tune your memory requirements. ÿÿThe ÿ úSystem AUTOEXEC ÿ øscreen shows the contents of your AUTOEXEC.BAT file. DOS executes statements in this file every time you start up your computer. These statements customize a PC in several ways. You can specify search paths, set up a helpful prompt and load useful Terminate and Stay Resident (TSR) programs. A periodic review of this screen serves to remind you how you have customized your system in the past. You may find obsolete utilities. Also, the TSR's you find here may be the source of problems with newly installed programs. ÿÿThe ÿ úSystem Video Display Adapterÿ ø screen shows details about the display adapter(s) you have installed. The type of adapter is given in industry standard terms (i.e. CGA, VGA). The area(s) of adapter memory used are shown, both ROM firmware and display memory. If the ROM contains a manufacturer's signature, it is displayed. If you have two display adapters, both are shown. With this information you know the capabilities of your display adapter(s). Check this screen to confirm graphics capability, or to verify that the system sees two adapters if two are installed or to determine resolution or color features based on the video type. ÿÿThe ÿ úSystem Disk Adaptersÿ ø screen identifies the disk drives installed in your system. It shows the number of floppy and hard disk units. For each of these it gives the drive characteristics, type and formatted capacity in tabular form. This display is useful to confirm a successful installation of new equipment, to easily and quickly determine the presence of a high density floppy, or multiple hard drives installed within the case. ÿÿThe ÿ úSystem Serial / Parallel Adaptersÿ ø screen shows the industry standard Port I/O adapters present in your system. The display shows the number and Port Address of each serial adapter and the number and Port Address of each parallel adapter detected. Standard signals and their current state are shown beside each device in tabular form. This information may be used to confirm the presence of such devices and to avoid clashes if you add devices using industry standard ports. Experienced users may find the state of the signals informative. Less involved users can relay this information to others. ÿÿThis ÿ úSystem Adapterÿ ø screen shows you the adapters installed on your microchannel machine according to information found in the Adapter Description Library (ADL) file. The information is presented in tabular form, showing: slot number, device type number in hexadecimal, identifying name, and the area of memory used by the adapter. This screen presents a convenient display of the your installed adapter equipment for problem solving, equipment inventory purposes and memory usage determination. ÿÿThe ÿ úSystem CMOSÿ ø screen shows the information in the CMOS memory of AT class and later PCs. The display is like your system's Setup program. CMOS memory is preserved by battery power when your machine is turned off. When you have to change your batteries, information here is lost. You can use this screen to capture CMOS settings before you change the battery. You can compare information on this screen with other screens reporting the same type of information. Other methods of equipment determination may show anomalies which show up in the way your programs behave. You should try to resolve such differences. ÿÿThis ÿ úSystem CMOSÿ ø screen shows the information in the CMOS memory of AT class and later PCs. The display shows each byte of the CMOS memory, gives a brief description of its meaning and shows the current value of the byte. Locations and values are shown in hexadecimal, except for the date and time bytes; these are in decimal. This screen offers convenient access to the contents of your CMOS memory. Viewing this information on different machines may reveal how different manufacturers use CMOS. ÿÿThe ÿ úFirst Meg Overviewÿ ø screen(s) show memory areas in the first megabyte of address space. The summary view is partitioned at the conventional memory boundary. Memory above that is usually devoted for hardware adapter use and BIOS ROM but may also have room for programs. The information is presented in tabular form, giving: the area used in hexadecimal, its size in K (K=1024 bytes), and how or by what it is being used. The information on these screens enable you to analyze your memory usage, to identify areas used but no longer needed, and to target opportunities for making better use of memory. ÿÿThe ÿ úFirst Meg Programs ÿ øscreen(s) show a breakdown of the memory areas used in the first megabyte of address space on your system. Con- ventional memory is always shown. If you have a memory manager, the area between conventional memory and the first megabyte boundary, which is nominally devoted for hardware adapter use and BIOS ROM, is also shown. The information is presented in tabular form, giving: the area used in hexadecimal, its size in K (K=1024 bytes), and the program owning the memory (or how it is used). The information on these screens enable you to analyze your memory usage further, focusing on programs and their memory usage. Opportunities for fine-tuning memory use may show up here. ÿÿThe ÿ úFirst Meg Interrupts ÿ øscreens present two detailed views of your PC's interrupt vectors. The first set of screens lists the programs providing interrupt services followed by the interrupt vector number(s) they service. The second set of screens list the interrupts by their number, giving also the name or purpose of the interrupt and the address and name of the program providing the service. Experienced users may find these screens helpful in determining conflicts among programs trying to provide interrupt services, during debug sessions for locating the routines, for finding a 'safe' interrupt to use or simply as a quick reference to the interrupt services defined. ÿÿThe ÿ úFirst Meg BIOS Dataÿ ø screens show the data area in RAM devoted for use by the ROM BIOS. Many application programs reference, and some change, the information contained in this memory area. The display consists of several screens showing the offset within the BIOS data area, the name or purpose of the data, followed by the current contents of the memory involved. Experienced users may find these screens helpful in a number of ways: as a database reference of the BIOS data structure, for quick access to port address values or the equipment and memory size bytes. Experimenters and students may find these screens helpful in confirming the effect of DOS and BIOS calls. ÿÿThe ÿ úFirst Meg Timingsÿ ø screen provide memory access times for various segments of memory in your system. The timings are presented in tabular form showing: the area of memory tested, the access time in K (K=1024 bytes) per second and a comparative index value relative to a PC/XT timing standard. In many systems, adapter memory and ROM memory may be significantly slower than either standard RAM or add-on memory. A system whose present memory capacity has been acquired over time may also show significant variations. A careful use of this screen may help you determine the benefit, if any, of shadow RAM, or of memory upgrades you may be considering. ÿÿThe ÿ úExpanded Overviewÿ ø screen shows information on any expanded memory installed in your system. If expanded memory is present, basic information is given, such as the driver name and version number supporting the memory, the location of the page frame and the amount and availability of the memory installed. Also important is the EMS level of support provided by the hardware and software as this determines the EMS capabilities you have. The version number gives you this information. ÿÿThe ÿ úExpanded Pagesÿ ø screen details the first megabyte of memory as it pertains to expanded memory. The vertical table lists sixteen 64K areas each of which has four 16K segments which are marked to indicate expanded memory usage. A legend describing the codes appears at the bottom of the screen next to this table. The horizontal table at the top of the screen lists Logical Page usage, showing the area of memory used, its size and the number of pages allocated to the area. Experienced users may use this display to confirm installation of memory boards and expanded memory drivers. ÿÿThe ÿ úExpanded Handlesÿ ø screen lists the handles allocated to requesting programs by the EMS driver installed in your system. The table lists the handle number, the amount of memory allocated in K (K = 1024 bytes) and, where possible, the name or identification of the program. You may use this list to determine which of your application programs make use of expanded memory and the amounts of memory they are using. In some cases (i.e. in DESQview, or by commands to the application itself), you may be able to limit the amount of memory the application is able to acquire if its expanded memory use is excessive for your purposes ÿÿThe ÿ úExpanded Timingsÿ ø screen shows memory access times for your system's expanded memory. The timings are in tabular form showing: the area of memory tested, the access time in K (1024 bytes) per second and a comparative index value relative to a PC/XT timing standard. When no application program is using expanded memory, the display shows only the timing for available memory. If expanded memory is being used, you will also see timings for each memory area. This list is sorted by handle number. Together with the other timing screens, this screen may pinpoint ways to improve your system performance. ÿÿThe ÿ úExpanded Benchmarkÿ ø screen provides a benchmark of the EMS manager in your system. Five sets of tests are performed, giving minimum, maximum and average timings in microseconds. These tests are repeated throughout the time this screen is selected. The tests show performance values for typical and heavily used memory management services. The time spent in an interrupt handler is also a critical factor. This figure is reported. Comparative results of this benchmark on the same or similar equipment using different memory managers can show the relative merits of the products under consideration. ÿÿThe ÿ úExtended Overviewÿ ø screen shows you a map of the extended memory in your system. You will see the range of memory addresses used, their size and whether that memory is in use or free. For areas in use, you will also see if the memory has been taken from the top or your extended memory or from the bottom. This screen can tell you if you have extended memory that is not being used. It can remind you of the presence of programs that use extended memory. It will often lead you to other screens to explore an opportunity or resolve a question. ÿÿ The ÿ úExtended XMSÿ ø screen shows you the XMS support available in your system. The level of support is indicated by the version and driver revision information. If you have applications which use XMS, this screen will help you determine if your XMS capability is sufficient for your needs. ÿÿThe ÿ úDOS Overviewÿ ø screen shows two views of your DOS Kernel. The view on the left gives general information about DOS code and resource usage, the view on the right breaks this information down to show the location in memory of these areas. The DOS version and the presence of an expanded memory manager will affect some of the details of this screen. A review of this screen is useful in checking or confirming the presence of required resources for your system, to pinpoint excessive allocation or to verify the effect of installing device drivers or buffers in high memory. ÿÿThe ÿ úDOS Driversÿ ø screen shows a list of the drivers installed in your system including the standard devices present in all DOS systems. For all devices listed, the name is given along with the device characteristics map. Standard devices are identified as belonging to DOS in the name column. Devices loaded from statements in the CONFIG.SYS file show the memory area they use and their size. Although this screen contains highly technical information, less experienced users may find it useful to determine which of several installed devices are contributing to a high device total memory use. ÿÿThe ÿ úDOS Filesÿ ø screen shows you information about your file usage. The box at the top shows you the number of file handles and FCBs currently open and the total number available for your use. The lower box lists all the files currently open. Three files are always open: AUX, CON and PRN. Other open files will be listed by name following the standard handles. Only files opened and left open for a considerable period of time will appear here. Experienced users may use this screen to help track down problems with lost handles or to determine the correct number of handles needed. ÿÿThe ÿ úDOS Environmentÿ ø screen shows the variable names and values for items in your Environment. Every program, while it's in memory has an environment. Some programs use environment variables to set configuration parameters. Probably more familiar to you are the PATH and PROMPT variables which COMMAND.COM uses. You can use this screen to see what variables are being set. If you want to see how your DOS prompt is formatted, look at this screen. If DOS can't find a program you want, check your PATH statement in your AUTOEXEC.BAT file. ÿÿThe ÿ úQEMM Overviewÿ ø screen shows you basic information about QEMM-386. A quick look at this screen will give you the version number for QEMM. You can tell if high RAM is in use and whether you have set your ROM to be mapped. The current mode and the location of the Page Frame is shown. Information on this screen is useful when you need help. It can guide technical support to other screens that might help to resolve any problems using expanded memory. ÿÿThe ÿ úQEMM Typeÿ ø screens show you a map and a list of your expanded memory usage. The map shows you how each 4K block of memory in your system is being used. The list shows multiple blocks of contiguous memory by type. You can use this screen to see how you or QEMM has organized your memory. You can check to see if there is high RAM and the size of each region. Information here, along with other screens can help you make better use of your memory. ÿÿThe ÿ úQEMM Accessedÿ ø screens show you a map and a list of your expanded memory patterns of access. The map shows you if any 4K block of memory in your system has been accessed since the memory was mapped. The list shows multiple blocks of contiguous memory that have been accessed or that have not been touched. Areas of memory that have not been accessed might be available for other uses. Areas in high memory could be mapped, perhaps. These screens alone will not tell you this definitely, but can point out possibilities for investigation. ÿÿThe ÿ úQEMM Analysisÿ ø screens show you a map and a list of an analysis of your expanded memory. The map analyzes each 4K block of memory. The list shows multiple blocks of contiguous memory by type. This information can help you to Include or Exclude memory, but only if you have carefully followed the guidelines specified in the QEMM-386 manual. ÿÿThe ÿ úQEMM Memoryÿ ø gives you an accounting of the expanded memory in your system that QEMM has converted from your extended memory. The screen shows what, if any, changes have been made to conventional and extended memory. It shows whether high RAM has been made available and the amount of expanded memory your system now has. The memory used by QEMM is detailed also. This information can tell you not only how memory is being used, but may point out opportunities for a better use of the memory you have. ÿÿThe ÿ úDESQview Overviewÿ ø screen shows you selected information about the window in which Manifest is now running. It tells you DESQview's version number, which is important when you contact Technical Support. You can experiment with Move and Resize using this screen. When you see a window position you like, you can use the information from this screen to start up an application by using Change a Program and copying the values you see here. ÿÿThe ÿ úDESQview Memory Statusÿ ø screen gives you convenient access to the infomation reported by DESQview's Memory Status program. Common memory shows how DESQview and DESQview programs are now using the memory set aside for internal use and program communicication. Conventional memory shows you how that memory is now being used. Expanded memory shows how much memory DESQview is managing and how it is being use now ÿÿThe ÿ úHints Overviewÿ ø screen shows how you might make better use of your system. This screen consists of short suggestions that Manifest has compiled as a result of gathering all the information about your PC for its reports. You should look at the detail screen if you find a suggestion that looks promising. If Manifest has not found any conditions to report, the Overview screen will tell you this. ÿÿThe ÿ úHints Detailÿ ø screens give you more information about the recommendations you saw in the Overview screen. The detail screen tells you why the recommendation is being made. It also attempts to point out circumstances where the suggested action should not be taken. If you decide to follow the suggestion, you are instructed about the changes necessary. ÿÿThe ÿ úExitÿ ø screen tells you how to quit Manifest: by entering ESC (the Escape key). Actually, you can quit Manifest from any screen by entering ESC twice (three times from a Help screen other than this one). Thank you for using Manifest. We hope it helps when you have a problem. Better still, we hope it helps avoid problems that keep you from your more productive tasks. ÿÿThe ÿ úExit Stay Residentÿ ø screen tells you how to quit Manifest, but keep it in memory so it can be "popped" back up later. You do this by entering one of the three key combinations listed. Then at the DOS prompt, run the program whose behavior you want to monitor. While this program is running, use the same key-stroke combination to bring the Manifest screens back. With this feature, you can see if a program provides interrupt services (First Meg Interrupts). Does the program use expanded memory (Expanded Handles)? Can I tell how much memory the program really uses (First Meg Programs - if it has an [Available] entry)? ÿÿ