Big-O Software

Well I guess I spoke to soon. Now It does the same thing as before.

Did you use the program successfully before the new version?

The Last 2 Versions I have had trouble with.

I mean before 2.2.X...

Also, tell me:

1) Your AIM+ path
2) Your log directory path
3) Do you have deadaim installed also, if so what's its log directory path (whether or not logging is enabled, its log directory path will still be in the registry)
4) The most recent version of my program that hasn't given you trouble
5) Anything else you think might be relevant

Edit: Some more things...

6) Your OS version and service pack # if applicable
7) AIM version

Ok...I'm gonna try this on the laptop running Win98 and follow my own directions. If there's a problem I'll install VB on it and hopefully I'll be able to track it. If not, I'll move on to my Win95 computer downstairs.

Well it seems to be working just fine with this setup:

Windows 98 SE (recent install), AIM 4.8.2790 (the newest release of 4., AIM+ 2.2.1. Pentium 133 MHz, not sure about the RAM. It runs pretty slow, but I tested all the functions and they all work. Everything was newly installed. I pointed the history path to my history shared on another computer. I'm still going to try to reproduce your problem on other computers.

Because of the performance of this program on slow computers I think I'm going to post suggested system requirements for it on its site. The program should operate on any version of windows, with any processor, and sufficient RAM (at least 32 megs).

They All At Least Ran before version 2.2.x.

My AIM+ Path: C:\Program Files
My Log Directory Path: C:\My Documents\AIM Logs
DeadAIM is Installed
It's Log Directory Path is the same as AIM+'s and It Is Logging
The Most Recent Version Ran 1 time fine then I ran it again and it Crashed

Alright. I'm going to install DeadAIM on my test computer and see if that's contributing to the problem.

Progress: It definitely has something to do with DeadAIM! Now I just gotta find out what exactly that is.

I tried running your version 1 just now, and that didn't work after the first time either.

I have AIM 5.1.3036
My AIM+ Path is C:\Program Files\AIM+
My log directory path: C:\Program Files\AIM+\AIM+ History
I used to have DeadAIM, I uninstalled it, but the log path for it is at C:\My Documents\AIM Logs
AIM+ is logging everything fine when I look them up in windows explorer, but not through the history viewer.

So It is DeadAIM! Now you only have to find what in DeadAIM is Causing it?

Ok...this is screwed up...I installed VB on the laptop to debug the problem and it doesnt happen anymore! I can tell you how to fix it temporarily...

Method 1: Uninstall DeadAIM, delete HKEY_CURRENT_USER\Software\JDennis

Method 2: Install VB

Both those seem to resolve the problem. Installing VB must add some critical thing that apparently my prog doesn't need if DeadAIM isn't installed. I think it might be an issue with versions of the required controls. I'll post all the ones I use in multiple zips.

Get this one and the 2 attachments and unzip them all to c:\windows\system32 and replace the files if they are already present.
http://discuss.big-o-software.com/download.php?id=134

Master Jedi wrote:Ok...this is screwed up...I installed VB on the laptop to debug the problem and it doesnt happen anymore! I can tell you how to fix it temporarily...

Method 1: Uninstall DeadAIM, delete HKEY_CURRENT_USER\Software\JDennis

Method 2: Install VB

Both those seem to resolve the problem. Installing VB must add some critical thing that apparently my prog doesn't need if DeadAIM isn't installed.

I just uninstalled DeadAim and deleted that registry key and the history viewer still doesn't work

Try getting all the above attachments extracted into your SYSTEM32 directory. Installing VB seemed to "fix" the problem. The only thing that really changed was the controls.

I got all the controls... would i need to restart my computer?