Return to BSD News archive
Xref: sserve comp.os.386bsd.apps:994 comp.os.386bsd.questions:9177 Newsgroups: comp.os.386bsd.apps,comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!comp.vuw.ac.nz!actrix!optimation.co.nz!audi!nickg From: nickg@audi.optimation.co.nz (Nick Gridley) Subject: Re: Xfractint/curses problems. Message-ID: <NICKG.94Mar10134515@audi.optimation.co.nz> Sender: nickg@optimation.co.nz (Nick Gridley) Organization: Optimation Consulting References: <199402260411.XAA19363@freenet.buffalo.edu> <SWILDNER.94Mar3003212@channelz.GUN.de> Date: Thu, 10 Mar 1994 00:45:14 GMT Lines: 35 In article <SWILDNER.94Mar3003212@channelz.GUN.de> swildner@channelz.GUN.de (Sascha Wildner) writes: > In article <199402260411.XAA19363@freenet.buffalo.edu> ae516@freenet.buffalo.edu (Christopher L. Mikkelson) writes: > > Has anyone gotten xfractint compiled and working on FreeBSD? I have > successfully compiled it, but the text mode operations don't work. > I think it *might* be a problem with FreeBSD curses (and also 386bsd > 0.1 curses, because I had the same symptoms there). Also, other > curses apps (e.g. pcomm) seem to not work too well. Rogue, Nethack, > Hack, and the other games work fine, though :-). Has anyone else > noticed such symptoms? any fixes? > > I've noticed the same with xfractint. Often (when choosing a fractal > type, for example) the display is not updated correctly or the cursor > is at the wrong position. > > Sorry, no fixes. Otherwise, xfractint runs fine. Hmmm. I noticed this a while ago. I thought I knew how curses worked and so I build a debug version (of curses) and proceeded to debug. After some investigation, it seemed that the information was getting sent from curses (via write) to the kernel, it was just not popping up on screen. (from a user point of view, not a kernel) I also tried sending it to a serial terminal - same prob. However, all the debug output made things run slow but correctly. At this point I got rather confused. It looked like a kernel problem which made it doubly weird. So, because, as you say xfractint runs fine, I gave up on the problem. Nick Gridley.