Date: Mon, 21 May 2001 23:58:40 -0700 From: "Ted Mittelstaedt" <tedm@toybox.placo.com> To: "David Banning" <david@banning.com> Cc: <questions@FreeBSD.ORG> Subject: RE: digiboard serial port behaviour problem Message-ID: <003e01c0e28c$a1e349a0$1401a8c0@tedm.placo.com> In-Reply-To: <20010522021147.A4215@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Well, to kind of start over, You said that normal FreeBSD programs work fine on the system. But, this database program hangs when it comes time for the opening screen. My guess is that the database program is doing something during the opening screen that has nothing whatsoever to do with the terminal session, but is making the process crash. Since this is an SCO program that is most likely a function call into the SCO libraries, and thence to the ibcs2 emulator. SO, next question - where did you get the SCO libraries your using under your FreeBSD version from? Did they come from the old version of SCO that you had which did successfully run the database program, or did they come from a different version of SCO? Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com >-----Original Message----- >From: David Banning [mailto:sky_tracker@yahoo.com] >Sent: Monday, May 21, 2001 7:12 PM >To: Ted Mittelstaedt >Cc: David Banning; questions@FreeBSD.ORG >Subject: Re: digiboard serial port behaviour problem > > >> >I am converting an old SCO system to FreeBSD and the database they >> >are running is an old SCO 3.2 binary. >> > >> >The digiboard PC/xe board seems to work with vi and mutt fine but >> >when there t comes time for the opening screen on this database program >> > (I guess there is a burst of a lot of characters at one time) >> >the terminal hangs. >> > >> >> Are you ABSOLUTELY sure that the TERMINAL hangs and not the session? > >After some testing, it appears to be the session that is hanging. >Turning the wyse50 terminal off and on again does not produce >a working line again. >I even try to kill it with a "kill -9" and it takes quite a while >to die. > >> This would seem to be a session thing, not a terminal problem. But, >> if it really is a terminal problem, then you might be able to >> specify padding in the termcap entry for the terminal that would >> fix the problem. Padding was often used for older 3-wire >installations that >> used xon/xoff and the older terminals that >> only supported xon/xoff. > >Well I wonder about this now. I have tried a test that man >termcap suggests (in vi delete 16 lines, then hit u several times quickly) >and it appears to work just fine. >It also appears that I have eliminated the digiboard as the culprit. >I attached a dumb terminal to /dev/cuaa0 and I get the same problem. >I also tried connecting a dumb terminal directly to a full (7 wire?) >serial line, and I have the problem there too. > >So now I am stumped even as to where to look for the problem. >I did a "stty -f /dev/cuaD00" on one of the ports and got; > >speed 38400 baud; >lflags: -icanon -isig -iexten -echo >iflags: -icrnl -ixon -ixany -imaxbel -brkint >oflags: -opost onocr onlret >cflags: cs8 -parenb > >Any ideas where to go from here? > >_________________________________________________________ >Do You Yahoo!? >Get your free @yahoo.com address at http://mail.yahoo.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?003e01c0e28c$a1e349a0$1401a8c0>