08-14-96 INTRODUCTION ------------ The purpose of this document is to give a brief overview of the advantages of running PCBoard under Windows 95 versus Windows 3.1. In addition to discussing the benefits, essential information about configuring PCBoard to operate under Windows 95 is also included. One of the major advances with Win95 is that is it a 32-bit operating system -- not just a 16-bit or 32-bit add-on to DOS like the old Windows. As a 32-bit operating system, it can do something that the old Windows can't: provide device driver support at the (32-bit) operating system level. Device drivers reside in extended memory, and do NOT take up any conventional memory resources. Why should I try to free conventional (lower) memory? Conventional memory is where programs are actually executed. The more memory available, the bigger the program you can run. THE OLD WINDOWS --------------- Let me illustrate this with an example: Suppose you have a system with a CD-ROM drive. Under the old DOS/Windows combination, you'd have a CONFIG.SYS that would look somewhat like the following: device=c:\dos\setver.exe device=c:\dos\cdrom.sys And in the AUTOEXEC.BAT: c:\dos\mscdex.exe /d:mscd001 /v When you boot the example system under the old Windows, and you open up one or more DOS sessions, Windows assigns a separate conventional memory space for each session. If you run MEM /C within the DOS session, you'll see that the device drivers and TSRs you've got loaded are "duplicated" in each session's conventional memory space, reducing the amount of free conventional memory available to that session. THE NEW WINDOWS --------------- Windows 95, however, has ways around that problem. To get around the problem, use either a 32-bit Windows driver, or a Windows virtual device driver instead of using old DOS drivers. For example, the CD-ROM drive is most likely plug'n'play recognizable by Win95 without the need for the old drivers you used to use under the old DOS/Windows set-up. How do you tell the difference between a DOS driver, and a Windows driver? DOS drivers usually have a .SYS or .COM (when a TSR) extension, and load either through the CONFIG.SYS or AUTOEXEC.BAT. Windows drivers usually have a .386 or .VXD extension, and they almost always load through the SYSTEM.INI file. To find out if you've got unnecessary drivers loading, simply REM out the old, possibly unnecessary, statements from your CONFIG.SYS and/or AUTOEXEC.BAT and reboot. CD-ROMs: Win95 *should* recognize these automatically. If not, go to Control Panel, Add New Hardware, and try to add it. Sound cards: Win95 *should* be able to support it using the stock drivers included with Win95 LAN cards: A bit trickier. Win95 auto-detect of LAN boards is not reliable, and can cause lock-ups. It is perhaps better sometimes to select the hardware yourself. Use Control Panel, Network, to change LAN set-up. With Win95, you'll need to configure: - an Adapter This is the physical hardware... IE.. "NE2000" or other network board. - a LAN Protocol This is something like TCP/IP, NETBEUI, LANBIOS, or some other Protocol. The "language" to be used. Must be "bound" to the adapter. - a Client This is something like "Novell NetWare" or "Artisoft LANtastic" or "Microsoft Windows." The client software allows for use of shared hard disk, printer, and other network resources. Must be "bound" to one or more Protocols. PCBoard under Windows 95 ------------------------ PCBsetup In PCBsetup | Node configuration answer Y to the Running a Network / Multitasker System question. BOARD.BAT NODEx.BAT Locate a SET PCB= line and Add the following. SET PCB=/NOGIVEUP Win95 Add the following to your SYSTEM.INI file. Under [386enh] UniqueDOSPSP=1 Under [NonWindowsApp] CommandEnvSize=768 In program properties change the following settings. Under PROGRAM [X] Close in exit (Checked) ADVANCED [X] Prevent MS-DOS-based programs from detecting Windows [ ] Suggest MS-DOS mode as necessary [ ] MS-DOS mode Under MEMORY Conventional Memory Total: Auto Initial Environment: Auto [X] Protected (Checked) Expanded [EMS] memory: Auto Extended [XMS] memory: Auto [ ] Uses HMA (Not Checked, unless you have a door that can use the high memory area) MS-DOS protected-mode [DPMI] memory: Auto It is also recommended that you run PCBoard in a FULL SCREEN, not a window. The reason, windowed sessions take up to 64k more than a full screen session. And full screen sessions are faster because Win95 doesn't have to virtualize the textmode screen and convert it into a windows font. Under MISC [ ] Allow Screen Saver (Not Checked) [ ] Always suspend (Not Checked) [X] Warn if still Active (Checked) Idle sensitivity Low High *--------------------------- ^ This setting was found to be VERY important to the function of PCBoard under Win95. It was found that if this setting was not full to the left, the background node(s) would freeze! A great way to check priority is to window two sessions side by side and adjust the idle sensitivity. Watch the system clock, the updates will go faster or slower depending on the setting you choose. CONCLUSION ---------- As explained, Win95 was designed so that you could still use your old device drivers and TSRs with it, but if you do you could pay a penalty in memory, performance, and stability. Windows drivers are preferred because they: 1. Reside in Extended Memory as 32-bit Extensions to the OS 2. Multitask Better 3. Do NOT Consume Conventional Memory 4. Do NOT Use VM386 Virtual Machines 5. Provide Universal OS Access to Your Hardware (IE..hardware accessible by both Windows and DOS apps) You should be able to get very large conventional memory spaces under Win95, if you eliminate the unnecessary DOS device drivers and TSRs. 580k and up per conventional memory space should be fairly easy to attain.