IWETHEY v. 0.3.0 | TODO
1,095 registered users | 0 active users | 2 LpH | Statistics
Login | Create New User

Welcome to IWETHEY!

New Apparently not.
The biggest issue seems to be when the apps call out to a third-party (irreplaceable) DLL (which supplies an API to their product). I've known this to be the source of much of the conflict--and have been slowly working on working around it. It just got to be too much today. :)

Many fears are born of stupidity and ignorance -
Which you should be feeding with rumour and generalisation.
BOfH, 2002 "Episode" 10
New Ah....
Wrap the DLL with a call with mutexes, maybe... kinda like a synchronized version of an unsynchronized object in Java. :-)

-scott anderson

"Welcome to Rivendell, Mr. Anderson..."
     Ugliest. Hack. Ever. - (tseliot) - (10)
         Shared library collisions? - (admin) - (2)
             Apparently not. - (tseliot) - (1)
                 Ah.... - (admin)
         Are these .EXEs yours as developer, i.e. you have source? - (a6l6e6x) - (1)
             Thanks. My hack gives me time to rewrite from scratch :) -NT - (tseliot)
         Native mode server? - (deSitter) - (4)
             Good idea. -NT - (tseliot)
             Eh? Show your reasoning. -NT - (pwhysall) - (2)
                 AD has claws in the executable -NT - (deSitter) - (1)
                     Evidence, please. - (pwhysall)

Now, with 10% more RAM!
96 ms