J Windows FE also uses MS VS 6.0. When you install Visual Studio, it may substitute (debug version) DLLs in system32. You may was to make sure that you also install all the latest service packs and patches.
Is mdm.exe running? If yes, kill it and try again. Also it should say what the error is, and in the dialog "Send to Microsoft" there should be detailed information. Reinstalling Visual Studio, it should stop the debugger at a particular place. That info may be helpful. Also does the error appear in Console and Java FE? Windows FE uses MFC42U.DLL and MSVCRT.DLL from system32, so you can copy those from the other machine into J folder and try again. Or compare them with the versions in system32 and possibly try to substitute them there. --- Claude Bélanger <[EMAIL PROTECTED]> wrote: > Hi, here is a followup on the problem : > > 1) I decided to buy a new machine (64 bits CPU) which was planned for > november 2006. > > 2) I installed the machine a couple of weeks ago and made a test of % 0 1 2 > 3 and EVERYTHING WORKED FINE, NO CRASH. > > 3) I continued the instllation of the softwares that I usually use (Office > 2000, VB 6.0, etc) and the cleaning of the old machine which went on the a > home network for my wife. > > 4) Then yesterday, I open J on my new machine and made the test, SURPRISE, > THE PROBLEM IS BACK with the same crashing procedure (C++ Debugger > activated, and the message "J has met with a problem ... Sent this message > to Microsoft"). > > 5) What had changed from the first days of installation : for one thing > Visual Studio 6.0 (Visual Basic, C++) had been installed. I thought that the > interactive debugger for C++ was been activated on the "ftp 0 divide" > condition instead of letting the condition being passed to the J > application. > > 6) So I installed the J601n beta version on my wife newly cleaned machine > and there it was working perfectly, NO PROBLEM WITH % 0 1 2 3. So > floating-point CPU not at fault. > > 7) I tried to disabled the option "Just-in-time debugging" in C++ 6.0 > (Debugger) and in the Visual InterDev (Debugger) with partial success (The > C++ Debugger was not called anymore but the message "J has met with a > problem ... Sent this message to Microsoft" remained. > > 8) I did a complete UNINSTALL of MS Visual studio and made sure that nothing > remain on the machine. SAME PROBLEM as in 7). > > 9) I made an new install of J601n beta in another directory, Same PROBLEM as > in 7). > > 10) I remove J601n from both locations, and I downloaded J601obeta and > installed it and got the SAME PROBLEM as in 7) but it worked fine on my wife > machine. > > 11) What should I try next, any suggestions? > > Claude Belanger, [EMAIL PROTECTED] > > > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
