Qbasicnews.com

Full Version: First release of Li3IRC! (A QB IRC Client)
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2
http://lithium.zext.net/n/f/Li3IRC.zip

read the readme please.. then try to logon to irc.esper.net, and /join #qbrpg

if you have trouble logging on, try changing the port number to 6667 or 6666

if it crashes with a QB error, email me with the error code, and attach log.txt

my email is http://mailto:lithium@zext.net

have fun Big Grin

(oh yeah.. feedback? sujestions?)

P.S. When connecting, don't just wait for "Connection established." to type in /join (whatever), that only means that the client and server have connect, not that you have logged on
wait untill a whole bunch of text scrolls by the screen. then do the /join thing
Holy crap, and I was just looking for a new client! You rock!

edit:
the program really bogs down my system, then crashes me =o=
it usually freezes up after i get connected
i can't type anything at the prompt
I'm trying to fix it now.
Nice!!!
works for me, major props for doing it in QB!!!
Apparently there are problems with Win9x/ME configuration of DSock, that cause memory corruption.. so unless someone can find a copy of wsock2.h (the header for wsock2.vxd), or documentation on the subject.. there's no way that v1ctor can fix this, and no way that Li3IRC will work properly on Win9X/ME machines...

yeah it sucks, i know Sad
I was on it but nobody else was Sad
Quote:Apparently there are problems with Win9x/ME configuration of DSock, that cause memory corruption.. so unless someone can find a copy of wsock2.h (the header for wsock2.vxd), or documentation on the subject.. there's no way that v1ctor can fix this, and no way that Li3IRC will work properly on Win9X/ME machines...

yeah it sucks, i know Sad

Hehe... uploaded WinSock2.h http://www.freewebs.com/iamdrv/WinSock2.h.txt - renamed with .txt on the end because freewebs is brain-dead - which is from MS visual studio 7 (.NET) so it should be pretty recent... hope this helps.
Don't recent headers need recent libs? Just a thought...
winsock2.h is for the winsock 2 API, wsock2.h is for using wsock2.vxd directly, it's what the API uses...
Pages: 1 2