From owner-freebsd-emulation@FreeBSD.ORG Sat May 17 19:36:00 2003 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ECC0F37B401 for ; Sat, 17 May 2003 19:36:00 -0700 (PDT) Received: from tank.siteone.net (tank.siteone.net [146.145.78.19]) by mx1.FreeBSD.org (Postfix) with SMTP id 230B443F3F for ; Sat, 17 May 2003 19:36:00 -0700 (PDT) (envelope-from brian@aljex.com) Received: (qmail 38077 invoked by uid 89); 18 May 2003 02:36:00 -0000 Received: from pcp02441074pcs.verona01.nj.comcast.net (HELO aljex.com) (brian@aljex.com@68.36.148.6) by smtp.siteone.net with SMTP; 18 May 2003 02:36:00 -0000 Message-ID: <3EC6F1A0.9040906@aljex.com> Date: Sat, 17 May 2003 22:36:16 -0400 From: "Brian K. White" Organization: Aljex Software User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030512 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-emulation@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Console problem using ibcs2 to run FoxPro for SCO X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 May 2003 02:36:01 -0000 > Here the problem, I'm trying to get Ms FoxPro from SCO > Unix running on FreeBSD. I Have succeeded in getting > corrrect operation on serial terminals, however I need > to get correct operation on the console as well. The > problem on the console seems to be more than an > incompatible terminfo entry. These are the symptoms: > The programs starts up and appears normal, but when I > type in commands, the typing appears in white on > black, not in the normal colour pair, when I press the > [Enter] key the typed command appears on the left of > the screen on the next line down, in the normal colour > pair, and the cursor returns to the command window. No > output from the program appears. FoxPro is still > running however, as pressing [f10] [Enter] drops down > the system menu as normal. This seems like more than a > terminfo entry because there is no program output, > it's as though what I type is not reaching FoxPro, > which is odd considering my comments on the system > menu. > > Do these symptoms ring a bell with anyone. How could I > go about investigating the problem in more detail? > Grateful for any advice or ideas. Thanks. > > Environment = FBSD 4.7, standard kernel, standard PC, > MS FoxPro 2.6 for SCO Unix. > I can't help, but I think I can corroborate and maybe my slightly different symptoms from a different application, and a comment from a head developer of that aplication might mean something to someone else. I use a commercial databse/rad system called filePro (www.fptech.net) on SCO, and they have native SCO and Linux and some other unix versions, but no freebsd. I have gotten the linux version working perfectly under freebsd (4.8-curreent) with termcap tweaks, and commenting out the line in linux_util.c that printf's a console message about a unsupported syscall. I got the SCO binaries to run, but they have terminal problems that are not fixable by termcap/terminfo/stty type things. I've already describe things in detail once on a mailing list for this app, and got a possibly meaningful comment from the guy who can see the source of that app and is a no-foolin developer. So I'll lust paste that here now. In the following, "fp" refers to the application, "filePro". -------- I said ------------ I have gotten linux fp binaries working on my freebsd 4.8-stable So far every thing looks fine except one message that gets sent to the console al lot. May 12 06:01:01 amdemon /kernel: linux: syscall setfsuid16 is obsoleted or not implemented (pid=39008) Do I remember correctly that so far, the best known fix for this is just to locate the string in the kernel source and comment it out? What about sco binaries? I have those almost working. I can run /sbin/sh from a real sco box and can run the fp binaries but not use them. (ex: runmenu will start up, display the screen in proper color and characters, but arrow keys will just cause ^[[A ^[[B to show at the enter selection prompt and the hilite bar does not move. if you blindly enter a good value and hit enter, the correct program will launch but it will have terminal problems too. That's at a console with a good cons25 termcap in place (at least it works fine with the linux bins and works fine with sco bins if use on a sco box and telnetting from the freebsd box, In an xterm it worse, the screen draws only half way and it leaves a few broken ansi codes around. ------------------------------ ----------developer replied-------------- While "blindly entering" a filename, does the highlight move? When at the "enter selection" prompt in *clerk, does pressing "U" take you into update mode immediately, or do you need to press Enter there, as well? If the answers are "it doesn't move" and "you need to press Enter", then the problem is that it is not respecting raw-mode input. ------------------------------------------ what the developer refers to here is several of the binaries that make up the filePro system, have a opening screen where you select a database file or menu or output format etcc to work on. This sscreen has a input field where you can type in a name, and it also has a box displaying all the currently existing names. Normally, you can use arrow keys and a hilight bar will move and you can hit enter to select an existing file visually, but also the input field watches and responds immediately to every keystroke. If you type "j" as the first letter in typing in a name, the highlight bar will jump to the first file that starts with "j" the instant you type the character. (you don't have to press [enter] to "send" the j) the answer to his question is No, the program does not react to keypresses, only registers input after pressing [enter]. --------------I replied------------- interesting... ok, in order to enter a filename I needed to start a program instead of runmenu, but that just uncovered a whole different problem. when I tried rclerk I just got this: ------------------ a filepro error has occurred this version licensed for 5 users on file too many users? [...empty screen...] press h for hard copy or enter to continue ------------------ I pressed "h", and the h appeared in the single highlighted cell that marks the current cursor position. nothing else happened. I pressed enter, and the program exited and I got the hardcopy at the same time. I took long enough switching back from the console to X to write bits in this email that I know it wasn't just a coincidental delay spooling the print job. of course I wasn't really exceeding the license, no other copies of anything fp-ish were running. what should I investigate for this one, shared memory? I tried dclerk and it did the exact same thing. on to try a different program... dscreen draws the file selection screen normally & fully. entering a file name: each character I type appears in the same exact first cell after the name prompt. interesting oddity: I made an error and hit backspace, what showed up in the file name prompt area was "^R" if I "blindly" type in a file name that does exist, and should cause the hilite bar to jump to the middle of the list ("invc" from the demo/tutorial files), the hilite does not move, nor does the cursor, but if I typed it correctly and hit enter, it does recognize it and proceed to ask for which screen to use. I did this a few times and got partly inconsistent results. one time after hitting enter after a file name the screen went black, the last 3/4 of an ansi sequence appeard in the top left corner, and the cursor position had moved (it waas waiting for a screen name at that point. hitting ctrl-c results in "^CBad System Call" appearing in the input prompt area and the program exiting. ( I don't have to hit enter after ctrl-c. If I type in a correct file name, hit enter type in a screen name, hit enter, you might not even notice anything was wrong, the listboxes appear and disappear, and the screen editor screen appears, looks normal, but at the enter selection you must hit enter after anything you want to type. typing "x[enter]" closes the program without fanfare. hitting u-enter does nothing I can see and hitting x-enter after that works. (i didn't have to do anything to get out of update mode, so the u really did nothing) Thanks for giving me something specific to test. I guess this supports your theory, and uncovers another issue besides. Funny thing is... I think it's sco binaries that howie has installed and working on his isp's (freebsd) web server. probably pretty old version of fp though, maybe not even 4.5? don't know the version of freebsd there either. So it may just be a matter of knowing how to properly set up the svr4 emulation, maybe more than just loading the kernel module. ----------------------------------- so... what is "raw-mode input and how do I go about getting ibcs/svr4 emulation to do it ? :) -- Brian K. White -- brian@aljex.com -- http://www.aljex.com/bkw/ +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++. filePro BBx Linux SCO Prosper/FACTS AutoCAD #callahans Satriani