First of all, here is a copy of the UCCOM3 notes file, for developers (notes.bas in the zip file)

[code:1:b12abba516]
'''''''''''''''''''''''''''''''''''''''''''''''
'||| UCCOM Notes File
'||| By Unfair
'|||
'||| I am releasing this source code because
'||| I am done with this project - it has
'||| accomplished what I wanted, and I don't
'||| have time to add all the features people
'||| want included.
'|||
'||| If you modify it I have only one request
'||| please leave the credits the same and just
'||| add your name to them, rather than taking
'||| full credit for this, as a lot of other
'||| people, including myself, have put time,
'||| thought, or effort into this.
'|||
'||| -------------------------------------------
'|||
'||| Here's an outline of everything I think
'||| developers using this code should know.
'|||
'||| Important features that have not been
'||| implemented but should be:
'|||
'||| 1. User permissions for ban/unban, etc.
'||| 2. Allow a customizable user default
'||| permission level.
'||| 3. Need a readme/tutorial to explain it
'||| (If you make a good one and email
'||| it to me at imunfair@yahoo.com I
'||| may post it on my site with UCCOM3
'||| - you get all the credit for the
'||| tutorial of course).
'||| 4. Implement a redirection of IMs. (since
'||| they come in a different connection)
'||| Details on how to do this are given
'||| further on.
'||| 5. Code the 5A protocol (sometimes used by
'||| AOL 8) - or code a 2A login to AOL
'||| so that the 5A protocol is never used.
'|||
'|||
'||| -------------------------------------------
'|||
'||| Ok, here's a quick runthrough on how IMs work.
'||| In AOL 9 the IMs come through a seperate connection.
'||| (sorry I don't remember if they do on AOL 8 or not)
'||| Basically you have to use the same proxy concept.
'|||
'||| The server that AOL connects to for IMs is assigned by
'||| IP in one of the packets during logon. What you need to
'||| do is replace that Server:Port with the LocalIP:LocalPort
'||| where LocalPort is the port you're listening on, and
'||| LocalIP is the IP of the computer uccom is running on.
'|||
'||| Once you have replaced those and passed the info on to AOL
'||| you will need to listen for a new connection and pass that
'||| on to AOL as I have with the main connection - filtering
'||| and renumbering packets as needed.
'|||
'||| Oh and one last thing, when you modify that IP you will have
'||| to change the packet length, if you have changed the length of
'||| the IP it is sending (otherwise AOL will signoff because of the
'||| error)... look at my chatsend functions if you need to see how
'||| to determine the length of the packet.
'|||
'||| Format: 2A02 D1F6 0036 etc...
'||| (Proto type - 2 bytes)(Packet counter - 2 bytes)(Packet length - 2 bytes)(etc....
'|||
'||| The length is not the length of the total packet, only the length
'||| of the bytes beginning after the two length ones.
'|||
'||| Happy coding!
'|||
'||| -Unfair
'|||
'||| -------------------------------------------
'||| Original source and program may be obtained
'||| at http:\\www.tsourceweb.com
'|||
'||| Email - Unfair@tsourceweb.com
'|||
[/code:1:b12abba516]

The UCCOM3 source code may be downloaded from:
[url]http://www.tsourceweb.com/files/uccom_3_src.zip[/url]

A compiled version along with the winsock ocx may be obtained here:
[url]http://www.tsourceweb.com/files/uccom_3.zip[/url]


If you take the source and modify it, please leave the credits the same, or include the credits in your program as all those people put at least a little thought or effort into helping, and I know it took me many hours to figure out the AOL protocol and code it correctly.

Enjoy.

-Unfair
 

 
Here are instructions on how to set it up (not step by step, but should be enough to allow you to do it correctly if you do each step)

1. Open AOL

2. Go to 'sign on options' and create a new connection (should be either a broadband or lan connection) - if you use AOL as your ISP I don't think this version of UCCOM will work for you.

3. Once you have finished creating your new connection, go back into 'sign on options' and click on 'expert setup' in the top right corner.

4. Click through the expert setup settings until you get to a screen which asks if you would like to configure proxy settings manually or automatically.

5. Click manual.

6. Change the Host from "Americaonline.aol.com" to "localhost", leave the port the same, DO NOT enable the proxy.

7. Click ok, etc etc till you get back to the signin screen, and make sure you have the connection you created in this tutorial selected (otherwise UCCOM will NOT work)

8. Sign on



If you ever need to sign on without UCCOM then just switch back to your old connection name on the signin screen.

You HAVE to start UCCOM BEFORE you try to sign in using the connection you just created, otherwise AOL will not sign in.

The welcome window probably will not open (I disabled it), and while UCCOM is running chats will not open in AOL, even though you joined them to prevent AOL from being lagged by people scrolling, etc.

Have fun.

-Unfair
 

 
[quote:5bac619677="Maxamize"]nicely said Tony, - maybe some of us will get a kick out of the source.

Thanks 8)[/quote:5bac619677]

[quote:5bac619677="HipHop101"]I'm still having a lil trouble connecting to aol. I'm using aol9.0 and I changed everything to localhost same port, but when I try connecting to aol it stops on step 2. Then it jus shows "[localhost]" in the connection log. Any help would be greatly appreciated. You can also aim me on "sincereLshere" thx.[/quote:5bac619677]
 

 
Right click on the tray icon (down by your clock) and go to "show aolproxy" - make sure it's set to "americaonline.aol.com" for the server, and 5190 for the port.

(AOL should be set to connect to localhost on port 5190 ... DO NOT check "use proxy" in the AOL settings - "localhost" should be in the server box itself.)

It sounds to me like AOL is connecting to UCCOM, but UCCOM isn't connecting to the aol server, so it times out...

The only other option I can think of is if you already have something using port 5190, so aolproxy isnt able to start listening on that port...

I'm sure you knew this, but you have to start up UCCOM BEFORE you try to log in with AOL.


Those are the only things I can think of at the moment, if one of them works, or if you solve the problem on your own, please post - even if it was a stupid problem - it may help someone else in the future :)


NOTE: troubleshooting tip: right click on the tray icon and open aolproxy before trying to connect with AOL - if AOL is connecting to UCCOM then the status will change from "listening" to "connected", otherwise you know it's a problem with the way you have AOL setup.
 

 
I'm AbLE To Log in througH localhost with uccom on but i can't fiGure out how to USe it i am newb with aim hacks but so many annoying people aND bots iN chat rooms. So caN someone help figure Out how to use it?????
 

 
is there a tutorial sum where that teaches you how to use uccom or can sum1 please help me out...my aim screen name is brightskindyme..im in dying need to learn how to use this...I have a sidekick and i want 2 start my own chat but ppl are always taking over chats...and I know ppl that ban from sidekick but sum1 has set them as a op...I download the program fine i just dont know how to use it and i didnt see a place to go 4 help

---

Post last edited by 'mskeys' at 06 May 2005 05:44 pm
 

 
You have to run it from a regular computer that has AOL, then just op yourself and you can type the commands from a sidekick
 

 
I believe you need to be on a LAN too, because it never worked for me on 56K.
 

 
Nope. Long as you dont use AOL as your dialup isp itll work..im using it right now and im on netzero
 

 
then that seems to be my problem ;p
 

 
If you want to figure out how to get AOL to use a proxy even if it's your ISP, be my guest. If you can figure that out then you can get UCCOM3 even with AOL as your ISP
 

 
Another note about UCCOM3 - Some people have been complaining that it sends invites to "Unfair is back", heres why it does that:

I was lazy when I coded it, it needed a screenname to invite so your name would enter the chat - the UCCOM code blocks the failed invites normally. If you're paranoid that it's reporting anything here's how you can change it to your own screenname:

1. use the search function in VB and find the string 556E66616972206973206261636B in the source code. It's in hexidecimal format, and stands for "Unfair is back".

2. Convert your own screenname to hexidecimal format, the same length as the one shown above (28 characters in hex, 14 normal characters)... if your screenname is too short, stick some spaces in the middle to make it longer... if it's too long then I guess you're out of luck.

An example replacement would be "my screenname" which is 6D79202073637265656E6E616D65 in hex. Note that it has two spaces between "my" and "screenname to make it the 14 characters long.

3. Replace 556E66616972206973206261636B with whatever your hexidecimal string of the same length is - DO NOT replace anything else - if you don't replace it with the same length hexidecimal string AOL will disconnect you every time you attempt to join a chat.

4. Recompile the program and you're done.
 

 
I dunno if this is a funny question, but can you get around paying for AOL?
 

 
Go here:

http://free.aol.com/tryaolfree/index3.adp?promo=715368&service=aol

sign up and get 3 months free. When it's nearly the end of those 3 months, call them up and say you want to cancel. If they actually are going to cancel it you can either let them, or hang up and call back to talk to another rep. But, if they start talking to you, asking about interests and stuff.. tell them a little about yourself (they're trying to find a keyword you haven't seen). As long as they can find some reason to give you extra time they'll usually give you an extra month or two to "look" at those keywords.

I had AOL for 12 months, and they always kept extending it. I just got rid of it at the end because I was afraid I'd forget to extend it and didn't really use it at that point anyway. (but I had to FORCE them to take me off, they offered me another 3 months free if I would stay, lol..)


Oh one other tip - do the surveys if you can.. I forget the keyword, it's [something]place ... but basically they give you money to do surveys, supposedly offsetting the cost of your AOL ... but if you're on the free plan they actually CREDIT it to your credit card... so you get free AOL, PLUS they pay you. :P
 

 
UCCOM patch based on some packets given to me the other day (it appears as if AOL sent an invalid packet?) Anyway, this should fix it:

Go to the ctlAOLproxy control code.
Find:

If ServerRemainder = "" Then
	PacketLength = Hex2LngVar(Mid(Data, 9, 4), 4) + 6
Else
	Data = ServerRemainder & Data
	ServerRemainder = ""
	PacketLength = Hex2LngVar(Mid(Data, 9, 4), 4) + 6
End If

Add after:

If Len(Data) >= 4 And LCase(Mid(Data, 1, 4)) <> "2a01" And LCase(Mid(Data, 1, 4)) <> "2a02" And LCase(Mid(Data, 1, 4)) <> "2a04" Then
	ServerRemainder = ""
	Exit Sub
End If

It will slow down processing slightly, but not noticably unless you're on a slow computer.
 

 
And thats supposed to do what
 

 
Makes sure that the packet begins with the correct characters - what was happening before was apparently a partial packet was being sent. (the end part of a packet)

If that runs into a partial end part of a packet it will drop it, and everything after it until it gets to a real packet beginning - safer than trying to mid the packet and possibly getting a 2a02 that is data in the packet.

---

Post last edited by 'unfair' at 28 Jun 2005 05:33 pm
 

 
lol i used uccom with dial up before ;x well lets say it was 2 dial ups ;x
 

 
Hello bump!

Considering how they said thats almost the only way to get uccom(or any aolproxy) working with a dial up connection, your post is irrelavant.
 

 
I'm still having a little trouble connecting to AOL. I'm using AOL 9.0 and I set up the connection with localhost, the same port, etc. but when I try connecting to AOL it stops on Step 3, and then sends me back to the log-in screen. I watched the AOLproxy and it changes from "Listening" to "Connected" for a few seconds while it's stopped on Step 3, but changes back to "Listening" once I'm sent back to the log-in screen. Any help on this would be greatly appreciated.

--Neon
 

 
Well, connected merely means that the AOL client is actually connecting to AOLProxy. Make sure that localhost is actually set as the server - not as a proxy. Beyond that I can't help you much because I don't have AOL anymore, so I am unable to test it and make sure it still works for me. You could try asking cerjam, or one of the other people who run UCCOM3 mods to test the original and see if it still works for them.
 

 
I have localhost set as the server, so I guess I'll ask around. Thanks anyway.

--Neon
 

 
used to happen to me, cancel the connection at step 3 and reconnect. works for me dunno why
 

 
Well, if it was using the 5a protocol, that would explain it. UCCOM was only coded to use 2a, but sometimes AOL will try to connect with the other version for some mysterious reason. If that's the case you just have to try again and hope it goes with 2a the next time.
 

 
No you don't, Theres a way to reset it to 2A, log on with uccom, close it, and hope AOL errors and crashes, when it crashes for some reason it resets to 2A
 

 
Well, if it was using the 5a protocol, that would explain it. UCCOM was only coded to use 2a, but sometimes AOL will try to connect with the other version for some mysterious reason. If that's the case you just have to try again and hope it goes with 2a the next time.

-

it wasn't 5a, I used aol9 and it happened every time.
 

 
Odd, because when I still had AOL, I used it with AOL8 somewhat, but mostly AOL9.