5 Replies Latest reply on Dec 5, 2014 4:35 AM by BigJohnD

    My PM 7.0 began crashing about a year ago on my Win 7 machine.

    TheGarpster01

      There seemed to be no definable reason, and it was only occasionally, so I wasn't too bothered. But now I can't work for more than 15-20 minutes before it will either freeze, or crash the program completely.

       

      Even after I've just cleaned the Registry, a RegClean report run immediately afterwards showed 42 errors, with the first 2 being:

      Invalid File or Folder  #####  HKEY_LOCAL_MACHINE\Software\Classes\.p65\ShellNew\Filename  #####  C:\Windows\ShellNew\PageMaker.p65

      Invalid File or Folder  #####  HKEY_LOCAL_MACHINE\Software\Classes\.pm6\ShellNew\Filename  #####  C:\Windows\ShellNew\PageMaker.pm6

       

      Why it references PageMaker.6 & 6.5 I've no idea. Is that a clue? Most of the other errors reported relate to "Speech\Engines\SR\en-US" for some unknown reason.

       

      I have spent many hours running it in all the provided compatibility modes, all to no avail. I have even tried running it on my Win XP Pro machine but it crashed there too.


      So I'm wondering if there's an error in the pub itself. It will often balk at some point when converting (currently a 36pp pub) to PDF. I remember seeing a PM menu command to "check publication for layout errors" or some-such, when PM would beep if an error was found. Can't find it now, though.

       

      I see there are many of you in this forum having problems running PM 7 in Win 7 and beyond, so did anyone ever discover a fix?

        • 1. Re: My PM 7.0 began crashing about a year ago on my Win 7 machine.
          Jay Chevako Level 3

          While some people claim to have gotten Pagemaker to work on Win 7, I have never heard anyone getting it to reliably create pdfs.  Stick to your windows XP machine, pagemaker was unstable enough on a platform it was rated to use. windows 7 and Pagemaker don't mix, look to the dozens of threads on the subject.

           

          Document corruption sounds likely.


          Diagnostic recompose ( from PageMaker for Desktop Publishers)

          Hold down the Shift and Alt/Option keys while choosing "Hyphenation" from the Type menu. Do this with the pointer tool clicked and no objects selected. The result will be one or more beeps:

          • One beep means PageMaker didn't find a problem. This does not necessarily mean there is nothing wrong, just that nothing was found.
          • Two beeps means PageMaker found and fixed a problem.
          • Three beeps means PageMaker found a problem it could not repair.

          Most problems are with fonts, or graphics. Disable the fonts that you use in the publication and try to create a pdf, if it works enable each font one at a time and create a pdf, repeat until you can isolate the problem font.
          If the pdf will not work with all of the fonts disabled look to the graphics. Create a pdf of each individual page until you find the page with the problem and then look to the graphics on that page. Graphics should be placed, not pasted into pagemaker, tiff and eps are the most reliable formats. I always resized my graphics to fit at 100% so as to avoid large preview images, which helps avoid corruption.
          Jay

          • 2. Re: My PM 7.0 began crashing about a year ago on my Win 7 machine.
            BigJohnD Level 3

            The long term solution is to use PM7 on a contemporary version of Windows, like Win2K.  Jay's answer is otherwise the best you're going to get.

            • 3. Re: My PM 7.0 began crashing about a year ago on my Win 7 machine.
              Test Screen Name Most Valuable Participant

              Those are normal entries, because PageMaker 7 is still able to open PM 6 and PM 6.5 entries. Or it was, once, before you let a registry cleaner loose. Those things are POISON!

               

              I concur with the advice. Run it on Windows XP. Old computers very cheap.

              • 4. Re: My PM 7.0 began crashing about a year ago on my Win 7 machine.
                KyriRo

                So I'm here on behalf of a customer. They are running Windows 7 Home edition. They have been using this program on this computer since they bought it in 2012. This was prompted by them being unable to use PM6.5 any longer so when they bought the new computer, they contacted Adobe support and through a series of misinforming emails the customer was able to buy PM7 and then an installation disc was sent to them. From then until this morning they were able to use PM7 without any issue. Yesterday a tech had gone out to clean up her computer because it was so infested the customer could no longer do anything without the computer locking up or flooding itself with ads.

                 

                Scouring these forums I've seen, more times than I care to count or recollect, people saying that they've gotten it to work on WIn7 and that it was never built to play Win7 in the first place. That's fine and dandy, but no one is saying how they got it to work. I'd love to know this as the customer seems unwilling to change to InDesgin. While I haven't had the "its a real possibility you will have to change" conversation with them, part of the misinforming email mentioned above was Adobe trying to force her into InDesign and she caught it before payment and switched it to PM7.

                 

                I've run this program in every able compatibility version both as user and admin. I've uninstalled and reinstalled the software running the install as user and admin multiple times. After the first installation it installed PMv7.0.2, which is the most recent version I believe. Installing the associated software, adobe distiller, doesn't help either. During the installation I get 2 errors: one telling me the unInstaller didn't install so I may not be able to unInstall this product, and another telling me that there was an error creating the registry set. The installer then continues its process to finish and I'm still unable to open it.

                 

                I'm toying with the idea of setting up a virtual XP machine holding only this program so the customer can use it whenever she needs to, but if I can get this running another way I'd love to do so.

                • 5. Re: My PM 7.0 began crashing about a year ago on my Win 7 machine.
                  BobLevine MVP & Adobe Community Professional

                  I can do nothing but offer you my best wishes for good luck…you’re going

                  to need it.

                   

                  If they don’t want to move to Indesign (which I understand) you can point

                  them to either Serif Page Plus (about $90) or the free, open source

                  scribus. Either application is lightyears ahead of Pagemaker which was

                  pretty much archaic more than 15 years ago. Today? It’s just ancient, at

                  best with no support and no updates.

                  • 6. Re: My PM 7.0 began crashing about a year ago on my Win 7 machine.
                    BigJohnD Level 3

                    KyriRo wrote:

                     

                    I'm toying with the idea of setting up a virtual XP machine holding only this program so the customer can use it whenever she needs to, but if I can get this running another way I'd love to do so.

                    I believe there has been success with PM7 operating within virtual WinXP. A forum search might find some thing of relevance.

                     

                    My view is that this is only a temporary workaround and that it won't be long before a longer term solution is needed when it is realised that PM is archaic and obsolete.