hfreedman@janus.mtroyal.ab.ca (01/15/91)
Many thanks to those that replied to my inquiry re communications and comm ports. Herewith a sample of the most common replies: ------------------------------------------------------------- From: ST%"efrethei@blackbird.afit.af.mil" 29-DEC-1990 17:31:39.52 I had the same problem for quite some time. I finally used one of those resource checker problems and found that the cause of the problem was a brain dead characteristic of windows. It seems windos goes out and assigns the first port it sees to COM1 the second to COM2 and so on. Since you have nothing on COM2 and COM3 windows thinks you only have COM1 and COM2, but the programs know you have COM4 the result is total confusion. Some people have suggested writing the COM3 and COM4 addresses into the BIOS, but this does not work. The only thing I have found that really works is to ensure that all com ports are sequentially used. Of course this is a stupid requirement but nothing else seems to do any good. I had to move my mouse to COM2, my second computer to COM1 and my modem to COM3. (They were on 1,2 and 4 respectively) This keeps the mouse interupts from interferring with the modem, but in general is not the ideal solution, only one that works. Good luck. erik ================================================ From: ST%"richark@fog.CS.ORST.EDU" 30-DEC-1990 02:22:38.53 The problem with getting win3 to see com4 has to do with how windows sets itself up. Upon start up it checks to see which com ports are active, once it finds a hole,(in your case com2) it stops looking. If you were to move the serial port at com4 to com2 your problems would probably go away. At least that is what MS has told me, and I have found it to be true in all of the cases I have run up against. Good luck...... -Kenny ==================================================== From: ST%"shuo@UCSD.EDU" 30-DEC-1990 22:17:27.18 In the "[386enh] section of "system.ini", add a line like: com3base=03e8h (for COM3) or com4base=02efh (for COM4). Windows 3.0 does not support COM3 and COM4. So you have to tell it the Address. Good luck! ShouqinFrom:ST%"KAHAI@ducvax.auburn.edu" 1-JAN-1991 13:50:28.47 Configure your computer system with mouse on COM1 and modem on COM2. Setting modem on any other COM port or even the mouse on any other COM port will cause problems and give "COM PORT USED BY DOS APPLICATION" messages. After doing that, use the WIN 3.0 text editor NOTEPAD and edit the WIN.INI file in the WINDOWS subdirectory. Get to the [Terminal] section and change the "Port" setting to COM2. That should solve the problem. I had similar problems, too. Let me know on my e-mail address if it works. Paramjit Kahai ============================================ From: ST%"SPR003@SATURN.UKC.AC.UK" 2-JAN-1991 03:13:02.38 Re: your problem with Com4 under Windows 3 I had similar problems with all comms packages; after one successful login to the mainframe all subsequent attempts would fail until a hardware reset was carried out. For me, the solution was to enter in System.ini the line Com2Irq=3 I have had no problems with Procomm, WinQvt, Kermit-PC or Terminal since then. I don't claim to understand all this stuff but hope this helps. By the way, adding four lines, each dealing with the Irq setting for one of the four Com ports on the machine, screwed it up again. The machine is a Viglen 386 LS running Windows in 386 enhanced mode, with a mouse on Com1, a mainframe link (3-wire to a PAD) on Com2, a Laplink cable on Com3 and a printer-sharer on Com4. -- ------------------------------------------------------------------------- Hy Freedman HFREEDMAN@JANUS.MTROYAL.AB.CA Mount Royal College Calgary, Alberta, Canada -------------------------------------------------------------------------