[Heff]

Originally Posted by Bawt

It's missing some .ocx file.

No it's not

[Bawt]

Originally Posted by Heff

No it's not

Then why does it says that when I run the .exe? Hmm?

[Heff]

Originally Posted by Bawt

Then why does it says that when I run the .exe? Hmm?

Well maybe it is, but not for me. There's a separete error.

[Heff]

Originally Posted by microsoft

If you call the SendData method in the WinSock control before the socket has been connected, you will receive the Microsoft Visual Basic Error:
Run-time error: 40006

"Wrong protocol or connection state for the requested transaction or request."

the error 40006 is generated due to socket is not connected yet so check for connection status before using senddata method

It's using winsock so Bawt probably doesn't have that ocx. Also they fucked up the winsock. It could be a pw stealer. Except a non-working one at that.

[Bawt]

Originally Posted by Heff

the error 40006 is generated due to socket is not connected yet so check for connection status before using senddata method

Does not compute.

[p1nba11]

he said that that program is crap and wait for final release. I thought it was good, worked once for me but ill keep ya posted, for final release

[Heff]

Originally Posted by p1nba11

he said that that program is crap and wait for final release. I thought it was good, worked once for me but ill keep ya posted, for final release

Yeah bullshit

[CokedandReady]

yea it keeps erroring