CompuServe Thread

Forum unknown · Programming

#_CXD22

5 messages in this thread
#19375From: Fred KohlerMay 19, 1986 10:28 PM
Scott, my problem was that I forgot to link the render.c file to the C runtime library. As far as VMI is concerned, I'm not sure what that refers to but I think it has to do with vertical line spacing. You should only have to change the values in printertag.asm and case 0 and case 4 of render.c when writing your printer driver (providing, of course, that it is an 8-pin B&W printer). -Fred-
#19385From: scott drysdaleMay 19, 1986 10:46 PM
hmm. but is the VMI thing a "dots per linefeed" or "dots per inch" or what? as to the nature of the printhead, it's a 7 wire printhead – actually, it has eight, but their protocal only lets you use 7. it compensates during the linefeed in graphics mode. typical radio shack product. but it DOES work, and it IS cheap, and it's almost reasonably fast in draft mode (80 cps). enough for us weekend warriors. –Scotty
#19385From: scott drysdaleMay 19, 1986 10:46 PM
hmm. but is the VMI thing a "dots per linefeed" or "dots per inch" or what? as to the nature of the printhead, it's a 7 wire printhead – actually, it has eight, but their protocal only lets you use 7. it compensates during the linefeed in graphics mode. typical radio shack product. but it DOES work, and it IS cheap, and it's almost reasonably fast in draft mode (80 cps). enough for us weekend warriors. –Scotty
#19420From: Larry Phillips/ICUGMay 20, 1986 1:31 AM
Fred, be sure to read the ERRATA.ARC file available in the DLs here. It is apparently critical to LINK the files in the proper order when compiling a printer driver.
#19420From: Larry Phillips/ICUGMay 20, 1986 1:31 AM
Fred, be sure to read the ERRATA.ARC file available in the DLs here. It is apparently critical to LINK the files in the proper order when compiling a printer driver.