ok im gonna take a guess and say u have a dll that performs a function on connect, and im going to also take another assumption and say the dll subclasses the mirc to perform certain things, im only guessing this because i too encountered the same problem immediatly after installing VS.net and then found outthat my problem was caused by order of unload on the dlls, remember if a dll subclasses mirc then the next dll u load would be calling functions under that subclassed mirc not the normal mirc. so if u unload dll 1 before dll2 u will get a memory error, something like unable to write to memory block and address 234r123(example not real address block) hopefully this helps alil
