Gordon Woolf's Blog

PageMaker 7 goes better with Windows 8

Three years ago I wrote an entry here about successfully installing PageMaker 7 desktop publishing software in Windows 7. Well, now I am happy to report just a few, mostly expected problems in getting that software to work with the 64-bit version of Windows 8.
There are a couple of gotchas, but they were easily overcome.

GOTCHA 1:  Do not to try installing an Adobe postscript print driver in 64-bit.

However I did install Distiller 5.0 which then told me I needed a postscript print driver. I then saw that one of the options for a manual install of a printer to print to file was the MS Publisher Imagesetter so I selected that to print to file and PageMaker 7.0 created a PDF via Distiller with none of the problems I saw with Win7. The MS Publisher driver presumably came as part of the Office pack I have but I'd guess than anything which installs an imagesetter driver would work with PM. Other people's experiences welcome. 

GOTCHA 2: You cannot run scripts in PageMaker on the 64-bit version of Windows.

I suspect that PMscript.exe is a 16-bit program so if you need to run scripts, then 32-bit installation is the best you can aim for - probably via a program such as VirtualBox. However most of the Utilities in PM7 do continue to work.

GOTCHA 3: Do NOT install Adobe Type Manager. It isn't needed.

Win8 is happy with postscript fonts. The fonts you need for templates are in a folder on the installation DVD named Fonts > Template Fonts. To install them in 64-bit Windows 8, just select the .PFM files of those you want, right click and select "Install". There are many other fonts in the Fonts > Extra Fonts folder.

PageMaker remains essential to me for opening old files, especially books created before the advent of InDesign. However it can also be tempting to use PageMaker for a simple DTP job that does not need the power of InDesign. I'm pleased therefore that it can remain in mu arsenal. Despite it now being relatively ancient in computing terms it is still on sale on the Adobe website for $499, about half the price of InDesign CS6. 

 

Windows 7: should it be Windows Silver?

November 1985 saw Windows first shipped in the USA and not long afterwards in Australia. So I wonder why Windows 7 wasn't called Windows Silver?

I can still see quite vividly that MSDOS screen in front of me at the newspaper in the small High Country town of Myrtleford that required me to click on a file entry to start the runtime version of Windows which then started the desktop publishing program PageMaker.

I'd already used the same program with Apple Macintosh in Western Australia but a PC was half the cost. And had used Xerox Ventura on a PC with the GEM "graphic environment management" system on top of DR (Digital Research) DOS, but Windows was still a massive advance.

Businesses weren't buying Windows because they wanted to but because it enabled the program they needed to run. Even the most hard hearted accountant could see that new equipment was worth buying when it would pay its full capital and running costs in less than six months compared to how the job had been done before.

The hardest job, a year or two later, was persuading newspapers in the bush that they really needed a network to transfer files, and that "sneaker net" with a shoebox of 5.25" disks had had its day.

Adobe v Apple: It's happened before

On the AppleInsider blog, Daniel Eran Dilger gives the background to the current Flash war with the comment "This all happened before".

His story and timeline of PostScript, the Laserwriter, TrueType, Aldus PageMaker, Macromedia's Freehand is almost all as I recall it and heard at the time from mainly Adobe insiders. The only statement I see which is a bit questionable is his assertion that Adobe did not realise when buying Aldus that the rights to Freehand did not come with the sale since they still belonged to the originators. Not until they bought Macromedia 10 years later did Freehand enter Adobe's fold.

However, if you think that lack of foresight (or what is now called "due dilligence" is impossible I can quote a tale from Australian media history. Our main TV weekly program guide which once sold a million copies a week was part of a publishing company sold off by News Ltd (which many years previously had been in the free-to-air TV business here) and ultimately sold to one of our major TV channels. After the final sale, the other leading TV company "revealed" that they owned 50% of the title. Within a week the magazine was being published by that company's publishing arm, from another city, with an entirely new staff.

Quite a blow for the other TV channel -- but I worked for that magazine several years earlier and as a fairly junior player I knew that the magazine was only half owned by the company publishing it. So I question how the money/management people did not know that essential fact when talking of multi-million deals. Could Adobe have not known about Freehand in 1994? Maybe.

It does not seem long ago that there were continuing email list discussions on the relative merits of true PostScript and the clones built in to printers. It dawned on most of us very slowly that the future lay in postscript interpreters resident on the computer, so slowly for me that the PostScript 2 laser printer I paid $5000 for (and $500 for each cartridge) we were unable to give away. It recently ended at the tip despite still being in working order.

The column is at:
http://www.appleinsider.com/articles/10/05/14/adobe_apple_war_on_flash_reminiscent_of_postscript_struggle.html&page=1

Software that refuses to die

How many software programs from 1994 are you still using?

When I upgraded to Windows 7 and chose the 64-bit version, I expected to say goodbye to some of the pieces of software that I've used for many years.

But my barcode creation software, UPCTools, bought in 1994, refuses to die...it just keeps on working, now with its fifth operating system since it first ran in Windows 95 (or was it Windows 3.1?).

Admittedly it now runs in XP Mode, but I can select it from the Start menu of Windows 7, and then just use the UPC Tools menu item "copy" to copy the result in to InDesign (which was no more than a twinkle in the eye of some of the software people at Aldus when this software was written by Jerry Whiting at Azalea Software). The barcode fonts, which were in Type 1 Postscript format, installed in the Windows 7 font folder by just dragging them in en masse. When viewed now within InDesign those fonts show up as just one font with eight styles (to suit three inkspread requirements plus half height versions. 

Yes that is Windows 7 and the software running does say Copyright 1994. Some software was written with the future in mind!

Incidentally, to get software that runs in the XP virtual environment to show up in the Start menu of Windows 7 you have to put a shortcut in the "All Users" subfolder of the Start menu in XP and then reboot your PC. It took me a while to work that one out.

Of course I'm not suggesting you should buy the 1994 version of UPCTools but if you are looking for barcode software that will work in to the next decade, You'll find lots of info about barcodes in general at http://www.azalea.com/FAQ/

Overall, I'm happy with the decision to upgrade and the computer with its extra memory is performing well -- not a BSOD since the upgrade, though I was previously thinking it had to be replaced.

Give your Printing Problems the Binary Chop!

The Binary Chop isn't a new form of karate. It reverses the power of the computer by calculating using two digits, the equivalent of on and off, just as the computer does.

There are many problems with printing — in fact as a consultant, I have more calls about printing problems than any other aspect of desktop publishing — but the most common problem can easily be solved using the Binary Chop.

This problem is that a file just refuses to print.

Firstly, check that a known good file will still print. If it does, then it is almost certain that the problem is with the non-printing file, and not with your printer or network. You could also try creating a PDF of the file. And, if that works, try printing from the PDF.

Here are a series of other steps to take:

1. Make a copy of the file under a new name and check whether this prints (sometimes the process of re-ordering and compression in file size which occurs from a Save as… command will solve the problem).
2. If you are on a network, try printing the file from the computer to which the printer is attached (which may also enable you to check whether the printer begins to accept information and whether this continues for some time before the printer returns to Idle mode. You can also check this on networks by following the progress of the job from your computer using the network software).
3. Using the copy of the file, try printing without graphics by using the Omit graphics selection under print Options if this exists. If the file prints then selectively delete and restore graphics files until you isolate the one causing the problem.
4. If the file has multiple pages, send half the pages, then the other half. This is the first application of the Binary Chop; by halving the non-printing pages each time, until you can isolate, hopefully, a single non-printing page. If you have more than one non-printing page, look for typefaces or graphics which they have in common.
5. Take one non printing page and cut and paste half the objects to a new file. Try both halves. If one half prints, you know your problem is almost certainly in the other half. Either way, continue halving the number of objects until you isolate a single object which will not print. See below for a solution if both halves print but not the whole.
6. If everything else prints, go back to the original page, make another copy, delete just the offending item, and, hopefully, your page will print.
7. Replace the offending object, which may be a graphic or a piece of type.

PageMaker works in Windows 7

There is now an update to this post, on using PM7 with Windows 8

It just needed the courage to do it: I've installed PageMaker 7 into Windows 7 and it is working with none of the problems which made me abandon a straight installation of PageMaker in XP and go for installing it within Virtual PC using Win98.

The only "problem" is the aparent slowness of loading multiple fonts in Windows 7 though I've just been told that you can just put all the .pfm and .pfb files into a new folder and drag the pfm files into the Windows font folder or go for the slow way with the additional possibility of selecting a well hidden option to keep the new fonts where they are.

But, contrary to some comments I found on the Internet, postscript fonts work fine with Windows 7. Also, when opening some files within PageMaker and getting the expected missing font dialog, I was able to select equivalent OpenType fonts and they seem to have worked -- i.e. Garamond Pro OTF for Garamond postscript font. I'd guess that some extended characters will give problems but I have not yet tested that.

Yes, I do most page layout work now with InDesign but I still like PageMaker. It is simple, ultra quick in Win7, and while I still often have to think how to do things with InDesign, it is second nature in PageMaker. And there are few things in basic page layouts which PageMaker cannot do.

UPDATE: See my own added comment following my move from 32-bit to 64-bit Windows 7 (But I'm still able to use PageMaker - in XP mode)