========================================================================= Date: Thu, 27 Aug 1992 22:06:29 CDT Reply-To: The TUG DVI driver standards discussion list Sender: The TUG DVI driver standards discussion list From: Mike Castle Subject: unix dvi to vm/cms dvi I'm not sure if this is the forum to ask such a question, but in my review of the past year or so's discussions, this looks like a knowledgable group. I have a dvi file created on a unix system that I want to print out on our IBM mainframe running vm/cms. Our unix is ascii based, and the IBM is ebcdic based. When ever I try to prepare the dvi for printing on our 3820 printer, the program cannon recognize the dvi file. I transfer it using ftp, trying ascii, binary, and binary with a specified fixed record length. Nothing seems to work. Has anyone had this problem, and developed a solution for it?? I'm pretty much at a loss. Any help is appreciated. Mike Castle Mike Castle Life is like a clock: You can work constantly Nexus and be right all the time, or not work at all S087891@UMRVMA.UMR.EDU and be right at least twice a day. -- mrc We are all of us living in the shadow of Manhattan. -- Watchmen ========================================================================= Date: Thu, 27 Aug 1992 23:21:50 -0700 Reply-To: The TUG DVI driver standards discussion list Sender: The TUG DVI driver standards discussion list From: Don Hosek Subject: Re: unix dvi to vm/cms dvi The file should be transferred binary with fixed length records (F1024 I believe should be the standard). Then check the last record using Xedit in hex mode. There will likely be padding of x00's. Those need to be changed to xDF's. After this change, the file should process fine. -dh