Return to BSD News archive
Xref: sserve comp.os.386bsd.apps:824 comp.windows.x.i386unix:6291 Newsgroups: comp.os.386bsd.apps,comp.windows.x.i386unix Path: sserve!cserve.cs.adfa.oz.au!wkt From: wkt@cserve.cs.adfa.oz.au (Warren Toomey) Subject: Re: Problems with xv-3.00a and a question. Message-ID: <1994Jan7.022121.29531@sserve.cc.adfa.oz.au> Sender: news@sserve.cc.adfa.oz.au Organization: Australian Defence Force Academy References: <CJ3M5r.Cvp@news.direct.net> <s902150.757870494@numbat> Date: Fri, 7 Jan 1994 02:21:21 GMT In article <s902150.757870494@numbat>, s902150@numbat.cs.rmit.OZ.AU (Brian Havard) writes: | |> I've also come across this problem but I found that if you leave it |> going for long enough (a couple of minutes usually) it _does_ come up. |> I'm using a 386-40 8 megs. Top shows it using all free CPU time the |> whole time. Once it does come up, however, I found it failed to set the |> palette correctly and was exruciatingly (spel?) slow to do anything. I've had the same problem. Earlier versions of xv were fast to start and fast to use. I've even compiled xv without TIFF support to minimise memory usage, and I have a 386DX40 with 16Megs, so no real memory deficiency. Can anybody with a coprocessor (387, 486DX) comment on speed, just to exclude this from suspicion. Perhaps the only solution is to gprof it. Thanks, Warren -- `` ... nor do I regularly post multi-kilobyte screeds about driver software I can't release because aliens haven't used the radio receivers in my head to give me permission yet.'' -- John F. Woods