V123 V124 COMMDRV.IBM (AREV Specific) [Revelation On-Line Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
[[https://www.revelation.com/|Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community]]


==== V123 V124 COMMDRV.IBM (AREV Specific) ====
=== At 29 JAN 1998 12:54:00PM D E Arbogast wrote: ===
 
{{tag>"AREV Specific"}}
 
<QUOTE>
We have an appication that uses subroutines V123, V124 and TSR COMMDRV.IBM to handle serial port communications. This application has ran four years on a 386DX-33 class computer. When this appication was moved to a 486DX-33 class computer hardware serial port timing problems manifested themselves. A software vendor who has worked with this application had told us in advance that this problem would manifest itself of faster computers.



Is there a patch, upgrade or work for this problem?
</QUOTE>
----

=== At 30 JAN 1998 12:02AM Chris Vaughan wrote:  ===

<QUOTE>It was a long time ago now, but I seem to recall having to put a delay loop after (eg FOR X=1 TO N; NEXT N) after the V124 read. I think it needed about 50 milliseconds. I will see if I can remember client and find the code. 

</QUOTE>

----

=== At 30 JAN 1998 05:38AM Steve Smith wrote:  ===

<QUOTE>COMMDRV.IBM has timing loops imbedded in the code. There

has been no patch for this problem to my knowledge. As the 

code was originally released for 8250 UART chips (serial port)

and not 16550 chips (current), you might try:



(a) using a DOS MODE statement to slow things down at the port.

(b) switching the motherboard to a lower speed, or software

switching the TURBO to low speed if this is possible.

(c) matching the speed of the PC's at both ends a little more.

(d) introducing configurable timing loops in the code.



Steve



stsm@ozemail.com.au

</QUOTE>

----

=== At 18 FEB 1998 09:46AM D E Arbogast wrote:  ===

<QUOTE>I eventually had to write V123 and V124 replacement routines using strictly AREV itself.

</QUOTE>

----

=== At 02 MAY 1998 10:04PM Clyde Walker wrote:  ===

<QUOTE>What method did you use to Communicate without v124?

I have the same problem with Win95.

</QUOTE>


[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=NONWORKS_READ&SUMMARY=1&KEY=18A3AF7007ABAC2D8525659B00625415|View this thread on the  forum...]]