2 Replies Latest reply on Mar 5, 2012 12:49 PM by planserendipity

    XP runtime crash

    planserendipity

      Hello

       

      I've created a single user runtime for Windows using FM Pro Adv 10 v3.

      The runtime was created on Windows XP SP3 and contains no plugins.

      The runtime has been distributed to about 20 beta testers for evaluation.

      The runtime works fine for 19 of the users, however one user is experiencing repeated crashes when he performs actions that include a COMMIT command. Not every COMMIT causes a crash but eventually one does.

      I have recompiled the runtime several times and the user has downloaded and run each but to no avail. The runtime is installed using the Innostep installer software and is about 30Mb in size. It is not a graphics intensive app.

      He has Windows XP SP3.

      I'm running out if ideas of what to suggest to resolve this problem.

      Here's what I am about to suggest he check next. Can you think of any others?

       

      1. Run software update;

      2. Check how much free hard drive space is remaining;

      3. How much RAM;

      4. What graphics card;

      5. Antivirus software?

       

      What do you think is the most likely cause of these crashes?

      Is anyone aware of any software conflicts between a FM runtime and Windows software?

      Would it be useful for him to create a new Windows account on his PC and install/run the runtime from there?

       

      Any thoughts would be much appreciated.

       

      Cheers,

       

      PS

        • 1. Re: XP runtime crash
          Stephen Huston

          I encountered this with some old XP systems several version of FM Runtime back. In my case, it turned out that the computers which failed were all Dell-built and had a registration system which included a driver which conflicted with that version of FM runtime engines.

           

          If you have only 1 out of 20, collect info on the hardware, including source/manufacturer, and see if it is the only one of its kind.

           

          If so, look into what the machine may have pre-installed that is non-standard.

           

          If it si not unique (or if nothing surfaces based on it being unique), look ofr other stuff only it has. Sometimes it's drivers from old game installations, registration modules, and who knows.

           

          And, of course, one hopes someone else reading your post may have run into something specific which is easier to track down than by process of elimination.

          • 2. Re: XP runtime crash
            planserendipity

            Thanks Stephen,

            This gives me a few new leads to follow

            Cheers,

             

            PS