[Virtualacorn-list] Printing from VA via an Access shared printer

[Jeremy Nicoll - virtualacorn]

Chris Shepheard <chris.shepheard at chrispics.co.uk> wrote:

> In message <gemini.k80cdc006luvw00xs at wingsandbeaks.org.uk.invalid>
>           Jeremy Nicoll - virtualacorn 
> <jn.ml.vac.83 at wingsandbeaks.org.uk> wrote:

> > Is the margin info that you think has gone missing defined in the
> > application that is generating the print-out (eg in OvnPro), or by the
> > printer definition in !printers?
> 
> They are defined in !Printers' paper sizes.

On both the real RPC and VRPC ?

Are both using the same version of !printers?

I presume the way the failing-print works is that !printers on the VRPC
builds the data that needs to be sent to the printer, then sends that across
the (wireless) network to the real RPC. I'd expect the data being sent to be
identical to what would (by experiment) end up inside a PrintOut file. 
[That's because it's always been possible if one wanted several copies of
something printed to create it once into a PrintOut file, then drag that n
times to the !printers iconbar icon, or indeed just *copy it directly to the
printer device.]

I don't know if at that end the data is received by the real RPC's !printers
application or just by some part of RO itself.  I'd kind of expect the real
RPC's !printers to be receiving the data, then driving the parallel port.
But that's just a guess.



I don't know if margin info is actually in the PrintOut file.  After all,
the 'same' printed results could be achieved on different sizes of paper
just by prefacing the page image data with setup info, if the printer is
intelligent enough to work that way.  Maybe each machine's !printers uses
its own page-size info to send data to the printer regardless of where the
PrintOut file is coming from. 

Someone like Ian Hamilton (if that's the right name; the guy who wrote a
print spooler) would know.

-- 
Jeremy C B Nicoll - my opinions are my own.