[Date Prev][Date Next]
[Thread Prev][Thread Next]
[Date Index] [Thread Index] [New search]
To: "'Dina Davidson'" <DinaD@xxxxxxxxxxx>, "Schwedland, Steve" <Schwedsl@xxxxxxxxxxxxxx>, "'Derooy, Diane'" <diane.derooy@xxxxxxxxx>, framers@xxxxxxxxx, "'manderson@xxxxxxxxxx'" <manderson@xxxxxxxxxx>
Subject: RE: FM5.5.3 crashing on print?
From: "Schwedland, Steve" <Schwedsl@xxxxxxxxxxxxxx>
Date: Wed, 27 Jan 1999 12:07:39 -0500
Dina, Quite right for non-postscript printers you definitely do not want to use the Adobe postscript driver. However if you are using a postscript printer then the original install disks may have antiquated postscript drivers on them. Remember that the printer installation consists of the postscript driver file (pscript.drv) and the postscript printer description file (PPD). This problem is caused by the antiquated pscript.drv file interacting incorrectly with FrameMaker, therefore she must be using a postscript printer. Re-installing the printer using the latest postscript driver file and the correct PPD file will certainly solve this problem. ______________________________________ Steve Schwedland Digital Publishing Facilitator SYKES Enterprises, Incorporated Worldwide Product Information Development 5757 Central Avenue, Suite G Boulder, CO 80301 Telephone: (303) 440-0909; ext. 133 Fax: (303) 440-6369 firstname.lastname@example.org > -----Original Message----- > From: Dina Davidson [SMTP:DinaD@Xantrex.com] > Sent: Wednesday, January 27, 1999 9:58 AM > To: 'Schwedland, Steve'; 'Derooy, Diane'; email@example.com; > 'firstname.lastname@example.org' > Subject: RE: FM5.5.3 crashing on print? > > Yikes! This advice scares me. You should mostly likely use the drivers > that > came provided with your local printer unless you have a good reason not > to. > If the printer in your office is not a PS printer, DO NOT use the Adobe > driver. You will get pages of PS code and a big headache! I agree that > the > Windows drivers are next to useless, but the solution is not that simple. > > Dina Davidson > Technical Publications Coordinator/Technical Communicator > Xantrex Technology Inc. > mailto:email@example.com > > > > -----Original Message----- > > From: Schwedland, Steve [mailto:Schwedsl@corp.sykes.com] > > Sent: Wednesday, January 27, 1999 8:49 AM > > To: 'Derooy, Diane'; firstname.lastname@example.org; 'email@example.com' > > Subject: RE: FM5.5.3 crashing on print? > > > > > > Diane, > > I've seen more of this problem than I want to think about. > > In my office we > > have several people who think they know all about just about > > everything and > > I have been butting heads with some of them about this issue. > > Sometimes it > > will appear to work just fine and then a new application will > > be installed > > and the problem will come back. This leads people down the > > wrong path for > > solutions. The problem is in fact the out dated printer > > driver that Windows > > installs (version 4.00.xx). > > > > The solution is to go to the Adobe site and download the > > latest printer > > driver installer, I use 4.2.1. Use this to re-install all of > > your printers > > (or at least you default printer). That should clear up the > > problem. In > > fact I have found that re-installing the printers will often > > fix many of the > > Weird errors that crop up from time to time. > > > > ______________________________________ > > Steve Schwedland > > Digital Publishing Facilitator > > SYKES Enterprises, Incorporated > > Worldwide Product Information Development > > 5757 Central Avenue, Suite G > > Boulder, CO 80301 > > Telephone: (303) 440-0909; ext. 133 > > Fax: (303) 440-6369 > > firstname.lastname@example.org > > > > > > > -----Original Message----- > > > From: Derooy, Diane [SMTP:email@example.com] > > > Sent: Friday, January 22, 1999 10:38 AM > > > To: firstname.lastname@example.org; 'email@example.com' > > > Subject: RE: FM5.5.3 crashing on print? > > > > > > Martin, I have a problem printing from Frame 5.5.3, also. > > > > > > What happens to me is that whether I'm printing from a book > > or a file > > > (happens more often with generated text like TOCs), that > > old familiar > > > white > > > box comes up with the message, "An error occurred... etc." > > and then gives > > > me > > > the option of closing the file or choosing "Ignore." > > > > > > At first I let it crash, but one day I just clicked "Ignore" and it > > > continued sending the text to the printer. Every couple of > > seconds, the > > > box > > > would come back up, and I'd click Ignore again. The command > > seemed to > > > require that I click Ignore in increments of two times with > > each episode: > > > two times, four times, six times, eight times. And then it > > would resume. I > > > never know how many times I'll have to click the box, but > > in a 75-page > > > file, > > > I click the Ignore button a minimum of 150 times, with an > > average of 400 > > > times per file being about typical. > > > > > > Adobe's explanation had to do with shifting the blame to > > > Windows--something > > > to do with antiquated printer drivers. I went to > > Microsoft's site and > > > downloaded a file that was supposed to fix this and had the > > network guy > > > install it, since that's our policy here. It didn't cure > > the problem, > > > although I crash less often, for some inexplicable reason. > > So I have no > > > idea > > > what to pursue next. > > > > > > In our shop we use Visio and Word97, two file formats not > > recognized by FM > > > 5.5.3, so we have to do a lot of adapting for the privilege of using > > > Frame. > > > I have a love/hate relationship with Frame, and a tolerate/hate > > > relationship > > > with Adobe. ;^} > > > > > > Adobe's answer, as always: Buy FM 5.5.6. Not much > > possibility of talking > > > my > > > manager into that, considering what he's witnessed here (it > > crashes on > > > him, > > > too, and then of course, there's that PDF conversion thing...) > > > > > > Please let me know if you manage to get your problem fixed. > > Maybe there's > > > an > > > answer for me there, too. > > > > > > Diane De Rooy > > > > > > ** To unsubscribe, send a message to firstname.lastname@example.org ** > > > ** with "unsubscribe framers" (no quotes) in the body. ** > > > > ** To unsubscribe, send a message to email@example.com ** > > ** with "unsubscribe framers" (no quotes) in the body. ** > > ** To unsubscribe, send a message to firstname.lastname@example.org ** ** with "unsubscribe framers" (no quotes) in the body. **