skl@van-bc.UUCP (11/11/87)
For those of you who had been pulling your hair out wondering why
UUPC works on one IBM-PC clone but refuse to talk to the serial
ports on another, this might be good news for you...
On some combinations of IBM-PC clones, third-party BIOS, and internal
Hayes-compatible modems, the low-memory serial port addresses table
maintained by the BIOS at 47:0 does not get initialized by the BIOS
correctly during the power-up self-test initialization, and therefore
pointing to incorrect addresses for the serial ports. In this case,
UUPC will happily use the values provided by the BIOS table as the
serial ports' base addresses, and consequently gets no where when
trying to talk to the serial ports.
To check if your PC/XT/AT clones have this problem, go into DEBUG and
use the command 'D 40:0 7' to examine the values of the BIOS' serial
port addresses table. If the output looks like
0040:0000 F8 03 00 00 (for a 1-serial-port system)
0040:0000 F8 03 F8 02 (for a 2-serial-port system)
then your table is fine. Otherwise, this could be the problem that
has been preventing you from using UUPC on your system.
The fix to this problem is fairly straight forward, all you need to
do is write a small program (in whatever language you like) to poke
the appropriate port addresses back into the port table, and invoke
this program in your AUTOEXEC.BAT file. As a fast and very short-term
fix, you could also hand-patch the correct port addresses in using
DEBUG, but this fix will only last until you turn off your machine.
Good luck, and send me e-mail if you have further questions on this.
...Sam
--
Samuel Lam <Samuel.Lam@van-bc.UUCP> or
{ihnp4!alberta,watmath,uw-beaver}!ubc-vision!van-bc!skldennis@rlgvax.UUCP (Dennis.Bednar) (11/13/87)
One question: Is UUPC a version of UUCP that runs on the IBM-PC?
Second question:
Is UUPC only to be used interactively to send files between your
UNIX mainframe and your PC (I would imagine that you use it much
like kermit, you start up a terminal emulator program that allows
you log into UNIX via the PC serial com port, then start up a remote
uucico program on UNIX, then tell the local program to start chatting
with the UNIX uucico program, to do the file transfer, but this
is only a guess. Some overviews on UUPC please?)
--
FullName: Dennis Bednar
UUCP: {uunet|sundc}!rlgvax!dennis
USMail: CCI; 11490 Commerce Park Dr.; Reston VA 22091
Telephone: +1 703 648 3300broehl@watdcsu.UUCP (11/18/87)
In article <1512@van-bc.UUCP> skl@van-bc.UUCP (Samuel Lam) writes: >On some combinations of IBM-PC clones, third-party BIOS, and internal >Hayes-compatible modems, the low-memory serial port addresses table >maintained by the BIOS at 47:0 does not get initialized by the BIOS >correctly during the power-up self-test initialization, and therefore >pointing to incorrect addresses for the serial ports. >... >The fix to this problem is fairly straight forward, all you need to >do is write a small program (in whatever language you like) to poke >the appropriate port addresses back into the port table, and invoke >this program in your AUTOEXEC.BAT file. You don't even need to write a program. Just use any text editor to create a debug script consisting of the following two lines: e 40:0 f8 03 f8 02 f8 01 q (this provides for three serial ports; if you only have two, it would be "e 40:0 f8 03 f8 02", and for only one it would be "e 40:0 f8 03") Assuming this file is called "comfix.dbg", just put the following line in your autoexec.bat file: debug <comfix.dbg >nul That's all, folks. -- Bernie Roehl, University of Waterloo Electrical Engineering Dept Mail: broehl@watdcsu.waterloo{.edu,.csnet,.cdn} BangPath: {allegra,decvax,utzoo,clyde}!watmath!watdcsu!broehl Voice: (519) 745-4419 [home] (519) 885-1211 x 2607 [work]