You are in a situation of a typical DLL hell. It's too late to repent of you have sinned. The problem is some stupid installer or program that violated the VS C++ runtime DLL distribution policy, such as ovewritten the newer DLLs with its older ones. Now the proper Visual Studio and or Window installer does not know what to do. Usually, you get into such trouble after a few years of month of installing all kinds of software, but it's not good that you have it on a brand new machine. It's a matter of choice of software. On some machines I used to have, I had to reinstall Windows once maybe six month. However, I also have an image of Windows on a hardrive of a machine which is long gone, but it never been reinstalled. Install engineer is the least payed job and if there is no such designated position it is at the bottom of priority list for developers. So people making installers litterally have absolutely no idea what they are doing. Thus, using an installer from an untrusted source is playing Russian roulette. I would recommend identifying this software and never installing it on your physical machine. I keep around a virtual machine for such kind of things, including when you have to encounter dubious web sites, that is with security settings that I don't allow on my physical machine. I also recommend putting Visual Studio 6 there too. It's good to keep your physical machine nice and clean. And J is a clean software.
P.S. If I recall, there are other debuging tools are Server Side Remote Debugging components for the situations when you develop in InterDev and want to debug a web site on a remote machine. That never actually worked for anyone, but caused many people a lot of trouble. So you don't need to bother with them. The debugging tools you describe for C++, I don't recall at all, but they look as most likely candidate for the problem. They might be from an old (pre-service pack) install, thus the newer-older thing. Plus they mess up MFC and possibly C runtime. So I would stay away from them too. Now that they've "crippled" your system, I don't know if you can cleanly get rid of them. There is a possibility this problem in on the knowledge base, if you like to have more fun with this process. ----- Original Message ---- From: Claude Bélanger <[EMAIL PROTECTED]> To: General forum <[email protected]> Sent: Monday, June 19, 2006 7:35:51 PM Subject: Re: [Jgeneral] Crash on % 0 1 2 3 Hi, I installed from Java.com the package J2SE Runtime Environment 5.0 Update 7 and made the link with the method described in «User Manual|Tech Details|Starting Windows Jwdp». Made the tests and all WORK FINE, NO PROBLEM has you have predicted. I also cleaned J from the machine, no remaining directories whatsoever. Made the download and installed with no modifications. Made the test and there it was the USUAL PROBLEM. Here are two things I did not mentioned : 1) Just after I had reinstalled many of the softwares that I use including (VS6) the first time I made the first test it work but as soon as I did a second test it did not work anymore. 2) While reinstalling Visual Studio 6 there was a message about an icon being installed for the purpose of installing some kinds of files to help the C++ debugger in the determination of the source of an error. So after the installation completed, I activated that icon and while it was installing I remember seeing file such as MFC42something being listed (too fast). But for many of the files I said no when it asked to replace newer files with older ones. After it terminated there was a message that some files could be found and could not be installed. It should be possible to reactivate the icon to start the process again saying Yes to the message. Claude Belanger [EMAIL PROTECTED] ----- Original Message ----- From: "Eric Iverson" <[EMAIL PROTECTED]> To: "General forum" <[email protected]> Sent: Monday, June 19, 2006 11:01 AM Subject: Re: [Jgeneral] Crash on % 0 1 2 3 > FE is Front End and in addition to the normal Jwdw (j.exe native windows > front end with GUI support) there is a similar front end written in Java. > Start your normal J and select Help|User Manual|Tech Details|Starting > Windows Jwdp. This explains how to create an icon (red J) that will launch > Jwdp (J wd (GUI) portable (Java) front end). It will be useful to know the > results of your tests there. As jconsole worked, my guess is that Jwdp > will work as well. > > My memory is vague in this area, but I believe there are different ways to > condition exception handling in floating operations and J depends on the > standard way in a clean state. My guess is that something in your > environment changes this state for J and this leads to the unexpected > exception being signalled. The VC++ dev env etc are likely red herrings in > all this. > > I will try to figure out a way for you to reset the J application floating > point state. If you could do this after J was running with the problem and > after the reset the problem went away that would really narrow down the > problem. > > Meanwhile, please run the Jwdp experiment. > > Also, please confirm that the problem happens with an absolutely clean > install of the obeta in a clean directory (delete any old j601 directory > before the install) with no customization or changes. > > ----- Original Message ----- > From: "Claude Bélanger" <[EMAIL PROTECTED]> > To: "General forum" <[email protected]> > Sent: Monday, June 19, 2006 10:34 AM > Subject: Re: [Jgeneral] Crash on % 0 1 2 3 > > >> Bonjour, >> >> I downloaded and installed the latest service packs I could find VS6sp5 >> for Visual Studio >> and VS6sp6 for VB6, VC++ and Vss6.0d. PROBLEM STILL THERE. >> >> In all the tests I made, whenever I checked MDM was not running. >> >> I made a visual check on both machine of MFC42U.DLL and MSVCRT.DLL, >> timestamps and sizes are different on my wife machine and on mine. I >> tried >> to make the switch but I think it did not work. I rename the modules as >> ...OLD.dll and copied over them. In doing that I got the message that I >> was >> trying to copy over existing modules and tried it anyway, but the modules >> had the >> same size and timestamp afterwards. Made a test anyway ... PROBLEM STILL >> THERE. So I copied them in the Jfolder and made a test ...PROBLEM STILL >> THERE. >> >> I do not know what a CONSOLE is but I tried activating Jconsole.exe, >> seems like a DOS INVITE kind of command line. Tried the test and SURPRISE >> NO PROBLEM, works fine with all the tests. The tests I do is «% 0» and «% >> 0 1» both always work, «% 0 1 2» always fails and «% _0» works but «% _0 >> _1» fails. >> >> Explain to me how I can make a test in JAVA FE, I suppose that FE is for >> Family Edition. >> >> Claude Belanger [EMAIL PROTECTED] >> >> >> ----- Original Message ----- >> From: "Oleg Kobchenko" <[EMAIL PROTECTED]> >> To: "General forum" <[email protected]> >> Sent: Sunday, June 18, 2006 6:39 PM >> Subject: Re: [Jgeneral] Crash on % 0 1 2 3 >> >> >>>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
