Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
First release of Li3IRC! (A QB IRC Client)
#1
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
COUNT HACKED BY RAZVEEE

RAZVEE IS A SCRIPT KIDDIE- hacker9
Reply
#2
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
ammit potato!
Reply
#3
I'm trying to fix it now.
COUNT HACKED BY RAZVEEE

RAZVEE IS A SCRIPT KIDDIE- hacker9
Reply
#4
Nice!!!
y smiley is 24 bit.
[Image: anya2.jpg]

Genso's Junkyard:
http://rel.betterwebber.com/
Reply
#5
works for me, major props for doing it in QB!!!
This is the end of everything, you are the end of everything." -Slipknot - Everything Ends

"GOD HATES US ALL!!" -Slayer - God Hates Us All
Reply
#6
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
COUNT HACKED BY RAZVEEE

RAZVEE IS A SCRIPT KIDDIE- hacker9
Reply
#7
I was on it but nobody else was Sad
earn.
Reply
#8
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.
Reply
#9
Don't recent headers need recent libs? Just a thought...
am an asshole. Get used to it.
Reply
#10
winsock2.h is for the winsock 2 API, wsock2.h is for using wsock2.vxd directly, it's what the API uses...
COUNT HACKED BY RAZVEEE

RAZVEE IS A SCRIPT KIDDIE- hacker9
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)