Block controller

Rev. January 1998

Software

I have built a simple basic program for testing blockp.bas:

10 REM *---------------------------------------------------------"
20 PRINT "-------------------------------------------------------"
30 PRINT " Block control tester for printer port - IOBCP v 1.0 6 jun 97"
40 PRINT "-------------------------------------------------------"
50 PRINT "init port 1a og 1b (control 0-255)"
100 INPUT "BLOCK POKE 001 ", a%
200 OUT &H378, a%
300 OUT &H37A, 255
400 INPUT "ok", b$
500 OUT &H37A, 0
600 OUT &H378, 0
1000 GOTO 100

This program works if priter port is at adress 378h and 37ah. For more info about Printer Port adresses look at my 8255 block poke value are sent on line 200
and then - the correct block are latched on line 300
LINE 400 are included to make it easier to test - remove it if everything works ok
line 500 - 600 are used to reset ports after user enters (return)

This program is usefull if you have a 8255 card blockt.bas:

10 REM *---------------------------------------------------------
20 PRINT "-------------------------------------------------------"
30 PRINT " Block control tester - IOBCT v 1.0 6 jun 97"
40 PRINT "-------------------------------------------------------"
50 PRINT "init port 1a og 1b (&h100- data og &h101 control 0-255)"
60 OUT &H103, 128
100 INPUT "BLOCK POKE 001 ", a%
200 OUT &H100, a%
300 OUT &H101, 255
400 INPUT "ok", b$
500 OUT &H101, 0
600 OUT &H100, 0
1000 GOTO 100

I have connected an 8255 io card on adress 100H
Initiating of 8255 are done in line 60
block poke value are sent on line 200
and then - the correct block are latched on line 300
LINE 400 are included to make it easier to test - remove it if everything works ok
line 500 - 600 are used to reset ports after user enters (return)

Using IOEXEC

Sample setup for dos version using QBASIC interface
This version of ioexec.com have support of BLOCK POKE command. However this is only a testversion. The main limitation is that addresses is hardcoded as port 100h (as in basic example), and that 8255 ic is initiated for each command (bad performance)

This has been solved by this version:
A newer version from January 1998 Documented in Automation

This page hosted by get your own Free Home Page

Hosted by www.Geocities.ws