cs450125@pc.usl.edu (Sahoo Anirvudha) (03/07/90)
I have recently purchased Ultrascript PC plus. The program, at least the
version that I have, has no trouble running on a 640k machine. I recently
downloaded the program still.ps from the adobe file server, but for some reason
I can not get Ultrascript to work with it. The program (still.ps) writes the
optimized output directly to my screen and not to the printer. The interpreter
in Ultrascript tells me that it cannot directly access files, so that option
is out. And Ultrascript seems to write directly to the screen, so screen
capture programs will not work. If anyone out there can think of a solution
for this problem, it would be greatly appreciated. Still.ps seems to work,
but I am not about to copy the code from the screen and retype it in by hand.
Thanks,
cs450125@pc.usl.edu
130.70.40.3geof@aurora.com (Geoffrey H. Cooper) (03/13/90)
In article <4896@rouge.usl.edu> cs450125@pc.usl.edu (Sahoo Anirvudha) writes: >I can not get Ultrascript to work with it. The program (still.ps) writes the >optimized output directly to my screen and not to the printer. The interpreter >in Ultrascript tells me that it cannot directly access files, so that option USPC should be able to read or write files directly. If you type: (foo.ps)(w) file this should open "foo.ps" for write, trashing anything that was in there previously (be careful how you use this, folks). The current directory should default to the current directory when you started the PS job (from USPRINT or USPC or whatever). Some pitfalls in this: - Filenames follow MS-DOS syntax, hence some file names can't be used (e.g., extensions with >3 characters, more than two "."s and so on). - Directories can be specified using either slash / or backslash \, as in any MS-DOS system call. Note that you must double the backslash to put it into a PostScript string (hint: use slash): (c:\\mydir\\foo.ps)(r)file - To conditionally open a file, using "stopped" to catch the error from the "file" operator. - There is a very severe limit on the number of files that can be opened at a time. Typically, this is enough to say "(foo)run" from executive, but not to have the file "foo" contain another file open. Hint: the executive itself uses at least one extra file descriptor, so try running the file in question directly using "print" instead of executive. - Files are always opened in binary mode. You may see a trailing "^Z" when reading it. - As with any MS-DOS program, disk corruption results when the same file is opened twice simultaneously for reading and writing. - Don't forget to close the file or you may get nothing. -- geof@aurora.com / aurora!geof@decwrl.dec.com / geof%aurora.com@decwrl.dec.com