mario72
Content Type
Profiles
Forums
Events
Posts posted by mario72
-
-
If you guys still want to use AIM, AIM phoenix was created, you dont need special software for it, its just clients 5.x and higher will run, long live aim haha
0 -
On 5/1/2017 at 1:45 PM, sdfox7 said:
I could appreciate your desire for the vintage "real thing".
In my experience, it's been nice using the virtual machines. Being able to install and run Windows 95/98 and NT4.0/2000/XP/7 all on the same machine is very convenient. The performance is also very good, as my system has an SSD.
On 5/1/2017 at 1:45 PM, sdfox7 said:I could appreciate your desire for the vintage "real thing".
In my experience, it's been nice using the virtual machines. Being able to install and run Windows 95/98 and NT4.0/2000/XP/7 all on the same machine is very convenient. The performance is also very good, as my system has an SSD.
Well, regardless of client version your using AIM is going down as it is
0 -
see virtual machines dont cut it.. at least for me..
I just wish there was a port/server to get into AIM with at least the 32 bit versions of AIM
1 -
1 hour ago, Yushatak said:
I've never been a big AIM user, so I'm not particularly motivated to do this myself, but someone else could..
You could solve this problem by reverse engineering the protocol of the version of AIM you want to use and the most recent one, and creating a server program (which could run locally or on another machine) to accept the older protocol from clients which could could point to it instead of AOL itself since it supports changing the server (if it didn't you could use the hosts file to redirect). When it connects to that server program, the server would then spit out a modern protocol request and send that to the actual AOL server. Upon receiving data, it would then relay it back to the client.
It's less lightweight than just running AIM by itself, but since you could put the server on another computer someone could potentially do this on a public server someplace (privacy concerns of course, for those who care about that) it could be done remotely or on another local machine to offset the resource usage.
Depending on how different the protocols really are, you could potentially patch the software, but that'd be much more of a headache to do and may not necessarily be possible.
x64 doesn't support 16-bit applications at all - the NTVDM is the component that lets them run, and they made the decision to never port that to x64. Before anybody says that it wasn't possible, there was NTVDM on NT4 for DEC ALPHA, so they already had code for an emulating NTVDM. They just consciously chose not to support it (which pisses me off to this day)..
Someone could potentially create a build of DOSBOX with a custom Win3x video and mouse driver that would "export" the windows to the host system for display outside of the Win3x system, much like VM solutions do these days. That's what I'd really like to see happen, but I'm not the sort of coder who knows how to make Win3x drivers enough to hack that up. I made NTVDM64, which takes over as the EXE handler for Windows and reroutes 16-bit EXEs into DOSBOX, but that's an incomplete solution and for some reason breaks some normal 32/64-bit EXEs (rare occurrence, never figured out the cause). I wrote that in Python, though, so perhaps I should take a crack at it in C# now that that's my predominant coding language.
Anyway I'm getting somewhat off topic, so I'll stop there.
Well for the time being i am running Trillian so i dont know what worth is there in trying to do what you recommended, one thing i tried was messing with the ocm files and maybe tricking the server that the client that is connecting is an older version but that didnt work either. Thanks for the information though
0 -
2 hours ago, Gabby said:
Just wanted to update those who are still holding out for AIM 5.9
Today I tried AIM 5.9.6089 in a virtual machine for Windows 98 and still doesn't connect. No cigar. It's proving to be a modification we'd need to make in the way AIM connects to but I'd have no idea where to finish with that.
In your case since your running a x86 architecture you can run aim 1 through 1.7 without any issues..
5.9 wont work, if you wanna run AIM on win 98 you can run any version between 1 and 2 will work..Me personally if theres a way to get the 16 bit installer to work on a win 7 x64 architecture that would be perfect (ive tried extracting from the new executable installer no luck).. my guess is AOL configured all the other oscar servers to kick you out if your using a newer client (greater than version 2)
Any other updates anyone?
0 -
from reading this thread and doing some research
version 1.0 to version 1.7 will work with any 32 bit system (from 98 to 7)
for 64 bit versions, i've tried changing server and port numbers and ive searched for aim servers (login.icq.com works, you need an icq screename and password),
changing the configuration of the program to trick the server into believing its an older version would work to (i dont know how to do that).. i also tried packaging the 16 bit installer but it still wont
fly on the 64 bit version.. any others have any updates?
0
AOL Instant Messenger 4.8 no longer connects
in Windows 9x/ME
Posted
yep, sorry for the misclarification.