From: Brian or Doug To: ml@qoole.com Reply-To: ml@qoole.com Date: Mon, 23 Feb 1998 16:28:11 -0500 Subject: Re: Like it or lump it! [QOOLE] I agree, who cares about a little SIGSEV they don't hurt your level, Qoole backs your map up whne it happens *thank god* it's not that bad so just put up with it untill Matt and Paul fix this problem. Kenancy Valenwell wrote: > You know what? The more I read about everybodies SIGSEVs, the more I go > "What the #$%^*(!@#? I'll just accept it, and hopefully it will go away one > day for all of us, because unless we are willing to code QOOLE ourselves, we > will just have to give Matt and Paul the time they need to make QOOLE even > better. We all have SIGSEVs, but I still love QOOLE the mostest. Thanks > Matt! Thanks Paul! For QOOLE, just keep the improvements coming and keep up > the good work, cuz I'm behind ya all the way! > Ken B. > kbagwell@slip.net > > -----Original Message----- > From: Charles R. Holy > To: ml@qoole.com > Date: Sunday, February 22, 1998 8:41 PM > Subject: Re: SIG... > > >I can't really comment on the SIGSEV errors as that was not the problem > >I encountered using 2.31 with .MAP files. When I tried running a .MAP > >file from another editor in Qoole I received a "Couldn't Spawn Server" > >error when I compiled the level. The same file ran fine from the other > >editor and also from Qoole v2.00, which leads me to think it was more > >likely a software than a hardware problem (My current hardware setup is > >roughly equivalent to yours). > > > >Of course, my difficulties might just have been a problem resulting from > >an error on my system installing 2.31 or something similar. I'm > >planning on trying 2.31 again when I get a new system (in 2-3 weeks I > >hope) and I'll see how it works then. > > > >Thanks for the input. > > > >Kenancy Valenwell wrote: > >> > >> I must agree. People's experience with SIGSEV's varies, even with the > same > >> version. Most of us are using 2.31, and I've had almost no SIGSEVs > >> (Homemade Pent 133, 1.3gb hard drive with 200 megs left, 32mb of RAM, > 2megs > >> video. and SIS chipset motherboard). So, if it is hardware related, it's > >> hard to track down what the rquirements are to prevent this from > happening. > >> And I also agree that it seemed to happen to me only when a window was > going > >> to pop up. > >> Ken B. > >> kbagwell@slip.net > >> > > > >-- > >Charles R. Holy > >Design Works > >holy@mwt.net > >