Path: utzoo!utgpu!watserv1!watmath!att!att!pacbell.com!ucsd!sdd.hp.com!zaphod.mps.ohio-state.edu!rpi!crdgw1!ge-dab!peora!rtmvax!amigash!scot From: scot@amigash.UUCP (Scot L. Harris) Newsgroups: comp.sys.amiga.hardware Subject: Re: DiskFailure Message-ID: Date: 20 Oct 90 05:18:17 GMT References: <5145@crash.cts.com> Lines: 44 >In article <5145@crash.cts.com> hawk@pnet01.cts.com (John Anderson) writes: > >right where it plugs into it's port? Another by-the-way: After getting my >dual serial board to run a JX-100 color scanner from, I found out they won't >work together. The JX-100 software looks into the serial device to see if the >scanner is connected but when it transfers data it does not go through the >serial.device. It goes directly to the serial port. This makes it impossible >to change the serial.device to siosbx.device andn have the scanner send the >data to that device instead. I can't use the dual serial board for my modem >because A-max can't access that port either, not to mention my modem games >that i would have to try to get to work. Has anybody done anything to their >software for the JX-100 to get it to work with a dual serial board? How about >workbench 2.0? Does it have better support for multi-serial board in that it >might work then? Thanks ahead of time for any help. I have an A2232 multi-port board AND a JX-100. The scanlab software is hardcoded to use the internal serial port. This is done partially so it can talk at the 115,200 baud rate. To do this it apparently goes directly to the hardware(?). The problem I have is that the A2232 comes with a new preferences program that allows the selection of the default serial port. The default port is unit 0. The internal port is unit 1, with additional serial ports being designated unit 2 on up. By selecting unit 2 as the default port I am able to run all of my modem programs with no problem (including Handshake, uucp etc.). Now this is where it gets real strange and is what you ran into. Apparently the ScanLab software opens the DEFAULT serial port to check for the JX-100 being out there. Then it goes and hits the port directly to get the speed. I have exchanged a couple of messages with Aaron Avery and Perry of ASDG about this and Aaron was going to try and provide me a patch so the ScanLab software would either be capable of selecting which port to use (prefered fix) or would at least go to the internal port all the time. Have not heard back from him on this for a few weeks however. At present I have to change the default port when I want to use the JX-100 and switch back when I am done. Kind of a pain but better than plugging cables in and out all the time. If anybody has a patch or fix for this I would be indebted. -- _ /// /_\ Scot L. Harris ...!tarpit!bilver!amigash!scot \XX/ / \ M I G A Orlando, FL (407)273-1759 [Prodigy censor messages? Nah, they wou