Okay, found a neat one...
Don't know if it is a bug, or just something unhandy that can't be avoided.
I have MIME type handling for WAVs and MP3s to save them to WAVS: and MP3S:
Today, I did a /sound some.wav, and found out I had lost the sound, so I
typed !nick some.wav in one of the channel's I hang out in, and the
wav was auto sent to me... DCC receive window opened up, and the file
started coming into WAVS:some.wav.
Then, someone else used !mynick some.wav.
My system of course went to send them WAVS:some.wav.
The DCC from the other person I was getting the wav from was not finished
yet, and the DCC Send window said it was sending the person who
requested the wav from me "WAVS:some.wav and it was 0 bytes long"
Then I get:
�DCC� DCC SEND of file "WAVS:some.wav" to Nick complete, 0 bytes, 0 cps.
And the system promptly locked up.
Feeling daring, I tried it a few more times.
So, I don't know what did it... Either dcc'ing a file that is currently
locked. Or the fact that the reported file size and cps was 0.
Maybe a way around it would be to not attempt to DCC a locked file?
John
DR. John M. Hoyt / AKA Warren Peace - amicon.net SysAdmin
WarNPeace - C-Link! International Coordinator
- ZenMetal/CNet Alpha Team
Find me on irc.reefer.org - ExodusIRC.Net Admin
__________________________________________________________
AmIRC Mailing List - Info & Archive: http://www.vapor.com/
For Listserver Help: <[EMAIL PROTECTED]>, "HELP"
To Unsubscribe: <[EMAIL PROTECTED]>, "UNSUBSCRIBE"
