Possible User (Self) Corruption of XP Pro

Calling this a Win XP problem may be a stretch, but I think I have caused one & would like to hear a plan for attacking it.

I have used Value Line Mutual Fund Survey successfully for a number of years on my computers, and initially on my current laptop using Win XP Pro, but for the past nine months every time I call up a graph I get a dialog labeled bc453rtl.dll, saying, "Floating point: divide by zero." When I hit OK or the red X, the whole program exits. I have talked & written to the Value Line Tech reps, but they are unable to help. The program works fine on a different machine running Win XP Home. I have tried copying both the working folder on the Home machine to the Pro machine (same result), and copying bc453rtl.dll from the Home machine to the Pro machine into C:\Windows\System, the only place I found it (still no change). The earliest Restore Point I have on the Pro machine follows the period of failures, so I can't just recover a working Restore Point. When the Survey program, which was first written for Win 95, installs it alters Win.ini and System.ini, but looking at those files fails to show any reference to the problem dll file. I have tried changing compatibiliy modes, too. The fact that the program works fine on the Home machine makes me think I have caused this problem and it is in Win XP Pro operating system. My hard drive is 2/3 empty, and the chip is pentium 4. I have 384 MB of RAM. Does any of this suggest a solution?

 

unfortunatly, it would be difficult for us to help you on this.

The program is dividing a number by zero. This is bad data. In order to help, we would need to know the programs internals to understand where the bad data came from, and what dependancies that program has that could cause it to generate the bad data.

Your best bet is to be insistant with the phone techs and ask for escalation or a supervisior until they get you someone with the expertise to answer your questions. Be polite but firm and you will get the guy you need on the horn.

 

Have you tried completely uninstalling the program from Pro and reinstalling from the source disk or download?

Johanna

 

Some troublesome legacy programs can be made to work by not only running them in a compatibility mode but actually installing them using the proper compatibility mode. You do this by creating a shortcut to the install or setup executable file for the program. Then edit that shortcut(pif) to select the desired mode that you would like to emulate for the installation. That can make enough difference in some cases that it will install so that you may then run it either normally or in a selected compatibility mode.

Good luck.

 

Actions Taken

For all who posted advice, many thanks. Results and thoughts follow:

JoeHobart recommended escalating the appeal to the app service rep's supervisor. The rep told me the app had a fairly small customer base and they didn't upgrade the basic product much, just the data part of it. I have written to the company president, but my letter was not acknowledged. I will make another phone effort, as you advise.

Johanna suggests fully uninstalling. I have done this numerous times, but since the app is not certificated (?), MS's Install/Remove Programs doesn't recognize it. Uninstalltion consist only of deleting the folder at C:\ that seems to contain all of the app. The customer service tech has had me do this too. The app comes each month, in its entirety, on a CD, so reinstalling it is routine.

Surferdude2 advises to set up a shortcut that is Win95 compatible. I copied the setup/data program from the CD to my desktop and made it Win95 compatible, then I created a S/C to that setup and made IT Win95 compatible too.

None of the above actions have made a difference.

Because the CD will setup correctly on my other computer, I am convinced the fault does not lie in the app/data, but in something I have done to Win XP Pro. I have just downloaded Rose Softwares Registry First Aid and will delete the Value Line app, clean the registry and reinstall. If that doesn't work I'm stuck at square one.

 

Result of Registry Cleanup

We,\l did as I said I woul, but the app continues to malfunction as before.

 

that stinks. sounds like this company didnt actually write the engine, but bought/licensed it and filled it with data