SERDIA WHAT TO DO IF...? 8.1.2 INTERFACE CONFIGURATION WITH ISETUP On PCs, the COM1 interface may already be occupied by the mouse. In this case, the interface must be connected to the other serial interface (COM2). This port can then be configured with ISETUP to allow it to communicate with the interface. Proceed as follows : Start the ISETUP.EXE program. Select the other COM port and click OK. The initialisation file ISODRV.INI is modified automatically. Re-start Windows. Note: On many PCs, the second serial interface is the 25-pin type. In this case, a hardware adapter (25-pin to 9- pin) must be inserted to allow connection of the 9-pin diagnostic interface.
8.1.3 ACCESS CONFLICTS IN WINDOWS 3.1 The ISODRV.386 interface driver can only be loaded statically. In the Windows SYSTEM.INI file, the ISODRV.386 driver is entered in the [386Enh] section (with the working directory path). This may cause problems with other programs that ac- cess the same serial interface. Remedy: Start the ISETUP.EXE program. Delete the driver entry from the SYSTEM.INI file. Re-start Windows 3.11. 8.1.4 ERROR MESSAGE IN WINDOWS 3.11 WHEN STARTING SERDIA When starting SERDIA in Windows 3.11, the following error message may appear: This is because the VXDLDR.386 driver is not activated. Remedy: Start the ISETUP.EXE program.
Check the "Device VXDLDR.386 enabled“ checkbox and click OK to confirm.The appropriate driver entry is made au- tomatically in the SYSTEM.INI file. Re-start Windows 3.11. 20-304