Kingston Technology MC133PD manual OS/2 2.0 and higher, Solution

Appendix C: Troubleshooting 39

The Solution

The solution is to edit your CONFIG.SYS after the installation is done. Make the disk cache about half the size of the MCMaster memory.

Version 3.0 of SMARTDRV does not need to be as precisely "tuned" as it used to need to be. Previously, you had to balance the size of the disk cache against the memory needs of your Windows applications. (Microsoft's MEMSET did this for you.) With Windows 3.0, in 386 Enhanced Mode, Windows and SMARTDRV will share the memory dynamically, depending on current conditions. If Windows needs to grab more memory for other uses, it will be able to. To read more about this, consult your Windows 3.0 documentation.

For a MCMaster with 4 MBytes, the entry might read:

DEVICE = C:\WINDOWS\SMARTDRV.SYS 2048 512

The first parameter specifies a maximum cache size of 2 Megabytes; the second specifies a minimum of 512K. This should work for most users.

OS/2 2.0 and higher

For OS/2 2.x to work correctly with the MCMaster, the MCMaster's memory configuration must be set to "Unmapped." Since OS/2 2.0 is "aware" of the MCMaster and will load itself into the MCMaster's 32-bit memory, this does not cause the performance problems that it would with other operating systems. For more information on MCMaster memory modes, read "Memory Options".

MCMaster User’s Guide - Rev. B06 Kingston Technology Company