BBS: Inland Empire Archive Date: 03-02-93 (16:33) Number: 357 From: MICHAEL LOWE Refer#: NONE To: DANIEL GURZYNSKI Recvd: NO Subj: COMM PORTS Conf: (2) Quik_Bas
-=> Quoting Daniel Gurzynski to All <=- DG> Here's a question for someone, I am unable to open com2 port in QB. I DG> can open and use comm1 just fine. Comm 2 has an internal modem and 1 DG> is a serial port. The program gets hung up on the open statement and DG> eventually I get a device time out. What might I be doing wrong here. This question might be more appropriate in the TECH or DR_DEBUG echo, but because I've had similar problems, using QB/QBX, I'll answer it. 1st, QBX and Telix seem to have a problem when Telix is loaded first. If you have a 16550 UART on that COM port and Telix is loaded first, Telix will leave the 16550 FIFOs turned on, which somehow causes a lock-up problem for QB/QBX Communications programs. I'm still waiting for an answer to the question, "How do you turn OFF the 16550 FIFOs?" 2nd, if you only have 2 com ports, most system reporting programs will report them as COM1 and COM2, even if they are something else. Check and make sure that the internal modem is setup for COM2, not for 3 or 4. ... Catch the Blue Wave! ___ Blue Wave/QWK v2.12 --- TMail v1.31.3 * Origin: * 20/20 TBBS * 312-769-2020 @2400 * 275-1785 @9600 (1:115/769)
Books at Amazon:
Back to BASIC: The History, Corruption, and Future of the Language
Hackers: Heroes of the Computer Revolution (including Tiny BASIC)
Go to: The Story of the Math Majors, Bridge Players, Engineers, Chess Wizards, Scientists and Iconoclasts who were the Hero Programmers of the Software Revolution
The Advent of the Algorithm: The Idea that Rules the World
Moths in the Machine: The Power and Perils of Programming
Mastering Visual Basic .NET