BBS: Inland Empire Archive
Date: 02-25-93 (02:24)             Number: 388
From: MICHAEL LOWE                 Refer#: NONE
  To: DAVE CLEARY                   Recvd: NO  
Subj: QB/QBX 16550 PROBLEMS          Conf: (2) Quik_Bas
 >ML> But if Telix loads and accesses the 16550 and exits, my program
 >ML> I have eliminated all other possibilities, leaving ONLY the 16550 as
 >ML> conmmon culprit.

 DC> Some programs have problems if the 16550 buffers are left enabled when
 DC> a prior program ends. QB may be one of them. Another problem code be in
 DC> resseting the IRQ. If Telex doesn't do it, that could cause a crash.
 DC> Prodigy does not reset the IRQ, causing someone to power down if they
 DC> want to use a different port on the same IRQ.

 Thanks for the input, Dave.  I've seen your name here and other places, and
 respect your opinion.
 One of the people that was having the lockup problem, used a program that
 turns off the 16550 fifo.  This cleared up the lockup problem.

 Now I know the beast, and I know the antidote.  The problem is that I think
 it's unprofessional to distribute a program which requires someone else's
 program to make it function properly.

 I know that if anyone knows what to do, you should.
 How do I go about Detecting/Disabling (More important) 16550 FIFOs
                                Mike Lowe

... RAM DISK is NOT an installation procedure!
___ Blue Wave/QWK v2.12

--- TMail v1.31.3
 * Origin: * 20/20 TBBS * 312-769-2020 @2400 * 275-1785 @9600 (1:115/769)
Outer Court
Echo Basic Postings

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