• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 686
  • Last Modified:

Epic to PDF Trouble

Hello
We are tring to make a PDF from a Epic 5.1, the file we need PDF'ed is just over a meg, so it's not big, and It gives me the following error.
 Error: ioerror; OffendingCommand: show
that shows up on the txt file that appears after it fails to make the pdf. I tried different combinations and most worked.
PDFing a file under a meg in Epic works
PDFing a word file over(way over) a meg works
PDFing the same file from the same computer under a different account works
PDFing anoter file over a meg did NOT work
I tried deleting and reinstalling Epic and it still didn't work
I tried deleting and reinstalling Adobe(just for kicks) and that didn't change anything

Does any of this make sense to anyone out there please help.
o and we are running xp pro if that helps anyone
0
samme
Asked:
samme
  • 3
  • 2
1 Solution
 
GlennHarrisCommented:
Sounds like a disk error; Suggestion: Print the epic doc to a postscript file (a printer that handles postscript, but 'on file', not a port) then use acrobat distiller to pdf it, this method never fails.
0
 
sammeAuthor Commented:
Thanks but I'm not the one who is making the conversions and the person who is, wants it as simple as possible, convincing him to make two conversions instead of one would be impossible he would consider it a waste of time. anyway I need to get it back like it was working before. is there any reason having to little space on the hardrive would affect this, I know virtual memory could but he has 1.24 gig of ram and a file thats 220 meg, big I know but I was able to pdf a 230 meg word doc. please help if you can.
(sorry I took so long getting back Isubmitted the question right before I got off on Friday and it wouldn't have did any good to check it over the weekend)
0
 
sammeAuthor Commented:
I just realized I'm sending mixed signals I said that the file was just over a meg in my question but I didn't realize that this size is not includeing pictures
0
 
GlennHarrisCommented:
Sorry to hear about the stubborn user; FWIW, Microsoft recommends that a Word doc should not exceed 32mb; While you might reach 60mb you create system instability. You should be using the Word Outline feature to create sub-documents. It likely won't print correctly due to the file size. Also, be aware that sub-docs are also 'unstable' and tend to become easily corrupted. The print to PS then distill is your only option.
0
 
sammeAuthor Commented:
Yes it's the file size, I didn't have enough hard disk space to use the allocated Virtual Memory, I made a few system changes and everything worked again. thanks for the help and the info about the file size.
0

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now