[Date Prev][Date Next]
[Thread Prev][Thread Next]
[Date Index]
[Thread Index]
[New search]
To: "Deborah Snavely" <dsnavely@xxxxxxxxxxx>, <framers@xxxxxxxxx>
Subject: RE: Where to send repeatable fatal Frame 6 error logs?
From: "Deborah Snavely" <dsnavely@xxxxxxxxxxx>
Date: Tue, 17 Jul 2001 12:40:12 -0700
Sender: owner-framers@xxxxxxxxx
Thread-Index: AcEO3X9u4HU4yMvuS0WbKbm1vMbI1QAAgCAgAAYSbfA=
Thread-Topic: Where to send repeatable fatal Frame 6 error logs?
Got it, thanks to you all. The address is "fmerror@adobe.com" and only applies for where to send those crash logs. My next-to-last crash managed to fail without even generating the dialog box, which was when I sent out the message. Then I tried one of the suggestions that resulted and got a "normal" crash. To those who responded with suggestions, thank you for ideas. None panned out but it's easy to overlook the obvious at this stage, so I thank you! Deborah Snavely Document Architect QA & Documentation Aurigin Systems, Inc. home office: 541-688-8690 voicemail only: 408-517-7414 > -----Original Message----- > From: Deborah Snavely > Sent: Tuesday, July 17, 2001 9:43 AM > To: 'framers@omsys.com' > Subject: P.S. Where to send repeatable fatal Frame 6 error logs? > > P.s. Please send by direct email; I get the digest. > > -----Original Message----- > From: Deborah Snavely > Sent: Tuesday, July 17, 2001 9:28 AM > To: 'framers@omsys.com' > Subject: Where to send repeatable fatal Frame 6 error logs? > > I have a lovely repeatable crash on printing to PS file using > Distiller driver, that's blocking me from delivering PDFs for a > release, and I'd adore to send my collection of fatal error logs to > Adobe if I can find where to send them. (Frame has now quit giving me > the "serious error and must quit" message when I run the same process > again; it just dies.) > > I was working through this book and its files a few months ago, > resolving iteratively and painfully issues that seemed to derive from > someone else accidentally importing plain ASCII text into the files as > JIF (because that's what Frame 6/Win was defaulting to and the other > party didn't know any better). And now I've come back to try and > finish the process only to discover that the files are once again > breaking at the same place they did originally. The usual tricks (save > to MIF and back, and examining the fatal page in MIF code) aren't > getting me anywhere now. > > Thanks in advance. > > Deborah Snavely > Document Architect > QA & Documentation > Aurigin Systems, Inc. > home office: 541-688-8690 > voicemail only: 408-517-7414 > ** To unsubscribe, send a message to majordomo@omsys.com ** ** with "unsubscribe framers" (no quotes) in the body. **