Subj : Re: Exitilus 3.20 To : Diamond Dave From : Tharius Date : Mon Aug 15 2005 02:39 pm "Diamond Dave" wrote in message news:42FC861D.18713.sync@bbs.dmine.net... > Re: Re: Exitilus 3.20 > By: Tharius to Diamond Dave on Fri Aug 12 2005 03:48 am > > > > Co-incidentally now that you have netfoss working, there are several > > othe > > > doors that will automagically be friendlier to your system. > > > > > > Thanks to Mindless Automaton I can tell you Melee works very well. > > I'm > > And unfortunately, the people who wrote the updated Exitilus are long > gone, as > is the original author.... > > Its amazing how much of the old 16-bit stuff still works, but how much of > it > doesn't either (especially if it doesn't support FOSSIL drivers) > > Speaking of NetFoss, I've hears that TW2002 doesn't work with it for some > reason, though it works just fine with the stock Synchronet FOSSIL driver. That's somewhat unusual. I have tracked down a good part of the problem _I_ had with DDPlus. If you can try this with Exitilus it might work. DDPlus has a problem that exhibts itself as a fossil problem. The problem is de-facto DDPlus' WinNT time slicing. These bugs tend to be exceptionally elusive (I spent many months trying to track down bugs all over Melee that turned out to be this above...) as you time slice all over the place. If I force Melee to use Desqview time slicing the problem disappears. How to force it? Well that's going to be difficult if it auto detects but I'm certain a few methods can be invented. At worst, if the door allows a complete disabling of multinode functions then it might not look for a multitasker. Just some ideas, good luck Just an idea that might work. The time slicing code in a lot of these old doors is written at a time when win 95 was very new, desqview was common and NT support was questionable at best. With XP becoming more prevelant, this is now the new "old" problem I think. --- þ Synchronet þ [aceshigh.dyn.dhs.org] - Come fly our friendly skies! .