ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ» º º º Inboard 386/PC: Troubleshooting Windows Problems º º º ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ SOTA FLOPPY I/O PLUS S900 The SOTA Floppy I/O PLUS S900 device driver must be before the InBoard 386/PC device driver in the CONFIG.SYS for proper operation. Our installation procedure alters the CONFIG.SYS so the InBoard 386/PC device driver is first. The user must manually restore the correct order of device drivers (FLOPPYIO.SYS, then INBRDPC.SYS) for the SOTA card to work properly. DOS APPLICATION DOES NOT WORK Many DOS applications do not run under Windows 3.0 in 386 machines or in Inboard 386/PC systems. Try to make sure the DOS application is compatible with the Windows environment. If the application will not run in the ENHANCED mode, try running it in the STANDARD (WIN /S) or the REAL(WIN /R) mode. REFLECTION REFLECTION is a COMM package for communicating with mainframes. It has been noted that characters can be lost when running in virtual machine mode and doing very keyboard intensive actions. The solution to this is to start Windows in the REAL mode (WIN /R) or to run REFLECTION from DOS. SMARTDRV FEATURES Using SMARTDRV and a permanent SWAP file can allow Windows 3.0 for the InBoard 386/PC to run up to 4 times faster than running without the SWAP file. A permanent SWAP file is created by running SWAPFILE.EXE from the PROGRAM MANAGER. More information can be found in the Windows 3.0 manual under OPTIMIZING WINDOWS. WINDOWS DOES NOT COME UP IN THE ENHANCED MODE If Windows 3.0 for the InBoard 386/PC fails to come up in ENHANCED mode (from the Program Manager, choose HELP and ABOUT WINDOWS to see the operating mode), try using WIN /3 to invoke Windows instead of just WIN. This forces Windows to load in the ENHANCED mode and does not allow for mode arbitration. This problem may be caused by timing issues and timing varies from configuration to configuration. Forcing a mode may eliminate the timing issues. There are several files that MUST be present for Windows 3.0 to come up in ENHANCED mode. An XMS driver (HIMEM.SYS, QEMM386.SYS, or 386TTM.SYS) must be loaded at boot and the following files MUST be in the SYSTEM subdirectory: WIN386.EXE; KRNL386.EXE; WINO386.MOD; .GR3. THESE FILES ARE ESSENTIAL TO ENHANCED MODE. There are several things that may interfere with the installation of Windows 3.0 for the InBoard 386/PC. NORTON DESKTOP AND PC TOOLS VER 7 FOR WINDOWS These utility packages install Virtual DMA controller interfaces for use when Windows is running in the Enhanced mode. Their DMA controller interfaces were designed for systems with 2 DMA controllers built into the motherboard (16 bit machines). PC/XT systems only have one DMA controller and Intel's custom Virtual DMA controller interface (IBVDMAD.386) MUST be used, otherwise the system will lock during operations. Norton DeskTop installs VDMADX.386 and PC Tools installs VDMAD.386 into the [386 ENH] section of the SYSTEM.INI file. Remove the command line for their DMA controller interface and replace it with DEVICE=IBVDMAD.386 to get Windows for the Inboard 386/PC to in the Enhanced mode. NOTE: The Backup utilities for these packages depend on their DMA controller interface and will not work with the IBVDMAD.386 from Windows for the Inboard 386/PC. These programs do Hard Disk optimization, backups, and other Hard Disk operations under Windows. Both of these packages install a Virtual Machine DMA controller for use when Windows is running in the Enhanced mode. TROUBLE SHOOTING All Windows 3.0 applications work flawlessly with Windows for the InBoard 386/PC. Any problems encountered would also happen on 386 machines. Troubleshoot exactly as if Windows 3.0 for the InBoard 386/PC was not present. Try to narrow the field to a hardware issue or a software issue. Many DOS applications simply are not Windows 3.0 compatible. If the application does not work under Windows in the ENHANCED mode, try it under the STANDARD mode (WIN /S) or under the REAL mode (WIN /R). Some DOS applications will work under the ENHANCED mode, but trash the video under the STANDARD or REAL mode. This is usually true of systems with clone video boards. ENHANCED KEYBOARD PROBLEMS After market Enhanced Keyboards for XT/PC type systems are very non- standard. A typical problem with Enhanced Keyboards is one key will work and the other will not. This is a function of non-standard keyboard decoding and is not related to Windows 3.0 for the InBoard 386/PC. HIGH DENSITY FLOPPY CONTROLLERS Windows 3.0 for the InBoard 386/PC is very hardware-dependant. Many High Density FD Controllers will conflict with Windows when trying to bring up the ENHANCED mode. The user must modify the SYSTEM.INI 386ENH section to exclude the ROM of the controller from the Windows memory usage with EMMExclude=. Since Floppy accesses are Direct Memory Accesses in 8-bit machines, the 386ENH section should also include DMABuffer1MB=YES and DMABuffersize=064.Refer to the SYSINI2.TXT file in the WINDOWS subdirectory for more information on these parameters. in the 386ENH section of (usually during the SETUP process). IRQ 5 AND WINDOWS FOR THE INBOARD 386/PC Because there are few Interrupt Request Lines available in the PC/XT architecture, Windows 3.0 for the InBoard 386/PC DEMANDS that IRQ 5 is left for the Hard Disk. Scanners can be set to IRQ 2 (if open) instead. LANTASTIC BY ARTISOFT The user must either turn off the Server mode or run Windows in the REAL mode. The first time the LANtastic software under Windows, a Dialog Box will appear informing the user to increase the NETHEAPSIZE. Enter into the SYS.INI file and add NETHEAPSIZE=X (X is usually 140). This will allow LANtastic to run, but it will take X amount away from Conventional Memory (again, usually 140K). This CANNOT be loaded high. Artisoft has a faxable document about this problem. ATI MOUSE The ATI Mouse driver must be replaced with MicroSoft's Mouse driver. If the ATI Mouse driver is used and the customer opens a window, then leaves the window, and then re-enters the window (ie: swapping between windows) the video could either be incorrect (mouse droppings) or trashed. LOGITECH MOUSE The Logitech Mouse Driver MUST be loaded before entering Windows 3.0. If the customer does not load the Logitech Mouse driver before entering the Windows 3.0 environment and then opens a window, exits that window, and then re-enters that window (ie: swapping windows) the display will be incorrect or trashed. Loading the Logitech Mouse driver in the AUTOEXEC.BAT or CONFIG.SYS fixes this problem. NOVELL AND NETBIOS The problems associated with Novell and Net BIOS under Windows 3.0 for the InBoard 386/PC are the same problems encountered on true 386 machines. There are SEVERAL workarounds available on COMPUSERVE. This is a Novell issue and not a Windows 3.0 for the Inboard 386/PC issue. ÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ End of file Intel FaxBack # 2562 July 8,1992