CompuServe Messages

Problems with CMD

    07-Jun-90 09:16:48
Sb: #107273-Problems with CMD
Fm: Christopher R. Hertel 76424,213
To: Thomas Holaday 70407,534
Ok, everyone… Here's the scoop. I used CMD to capture the HP PCL output from ProDraw, then copied CMD_file to a PC via Zmodem. I then copied that file to a floppy disk and moved to another PC that had an HP printer attached. Finally, I copied the file to LPT1:–which didn't work–'till I tried the MS-DOS /b option: bingo! So, I determined that the CMD program was working, and that my problem must be either in the transfer of the file from PC to VAX, or in the VAX queue (as many of you suggested). Well, it turns out to be a number of small things… First, the VMS file structures are a bit goofy (from a micro point of view). If I used my PC network to put the PC file into a shared area, and then asked the VAX to print it, the file, from the VAX side just isn't correct. I have to do a special copy (NFT> copy /image/noconvert/variable CMD_FILE. DUA2:[CHRIS.TMP]CMD_FILE.LIS) to get the VAX to handle the file correctly. I also have to make sure that I use the proper FORM when printing the file on the VAX queue. Apparently, WordPerfect assumes *nothing* about the state of the printer when it creates a file, so it has no problem printing its files. The ProDraw output, however, doesn't seem to do well if the printer was set to landscape prior to receiving the file. Anyway, I have it working now, though I am still confused as to why WordPerfect can produce an HP file that prints normally and the CMD-generated files need so much assistance. I'll continue this saga whenever I get more information… Chris -)—–