Conference iosg::all-in-1_v30

    Hi,
    
    Put the tables you want to convert in your ALL-IN-1 directory. Then
    convert via PT. This will create a sub-directory called TABLES where
    you can find the converted tables. Then copy them to KOA$PRINT_DIR.
    
    Sjaak.

    Thanks for the reply, Sjaak. But the new tables in [.tables] are empty
    files. I am sorry for these questions as they may be obvious, but I
    don't v3.0 mannual with me.
    
    regards
    Pete

    Hi,
    
    You *HAVE* to put the old X.PRA *AND* X.PRC both in your ALL-IN-1
    directory. Otherwise X.PRC will be empty.
    
    Sjaak.

    I still can't make it work.  I have tried copying the files to every
    direction named and more, and it still creates an empty file.  If
    anybody can get it to work, please let me know!  The files are:
    
    ACES2$:[LANPHEAR]
    
    PORTHP.PRA;1              1  24-JUN-1992 17:34:30.26 
    PORTHP.PRC;1              6  24-JUN-1992 17:36:38.42 
    
    and they work with the old PTU, but not with the COnvert option.
    
      Thanks in advance,				Dan'l

    
    Dan,
    
    Your .PRA misses some header information compared to the ALL-IN-1
    printer tables. I added:
    
    	V003.001 PORTHP
    
    on the first line of PORTHP.PRA and I could convert it to WPS-PLUS V4.*
    format, and edit it furtheron.
    
    I'm not to sure about the PORTHP.PRC yet, as the trick of the header
    didn't work in that case.
        
    	Simon

    PS     I'm not sure if it was the right thing to do, as I cannot test 
           if it really worked (no HP printer here).

    
    Dan,
    
    > and they work with the old PTU
    
    I'm sorry, but I cannot get the PORTHP.PRC to work with the old PTU
    (WPS-PLUS V3.1). The message 'Incompatible set' appears all the time.
    Is V3.1 the version you mentioned?
    
    Ciao,
    
    	Simon

    Simon!  That's the right answer!  Now we have the explanation, and we
    can make their system work the way it used to...
    
    Re: the .PRC, sorry, my fault; I missed the fact it was 6 byte fixed
    records, and I kermited it over like the .PRA (variable).  It's also
    missing the header, so I'll try to figure that out as well.
    
    Also, when I look in KOA$PRINT_DIR, there's "HPLJIII.PRA", but no .PRC
    to go along with it.  Was something left out of the kit, or are the
    PRC's now font specific instead of printer specific?
    
    					Thanks a *lot*, Dan'l

>    Also, when I look in KOA$PRINT_DIR, there's "HPLJIII.PRA", but no .PRC
>    to go along with it.  Was something left out of the kit, or are the
>    PRC's now font specific instead of printer specific?

    Right, the PRC's are font specific, as you can see in the PRA file,
    for each font specified there, there is also a PRC file specified.
    
    Hans

The .PRC files are now font specific.  There is some more information about 
this in the OA$LIB:V4_DEMO.WPL file which should be on your system.

Richard

    Thanks for the quick responses.  I'll check out the v4_demo.
    
    Now that we've converted the .PRA, and we verified that there's nothing
    unusual going on, we're stuck!  Does anybody have a working .PRA file
    for WPS-PLUS V4.0 + for the HP Laserjet II ??  We used the HPLJIII.PRA
    as a basis for the II, but it doesn't work correctly:
    
      For example, if they print a document with a page size of sixty-six, 
    with six line top & bottom margins, it starts printing on the 8th line,
    and then overflows to print an orphan line on the second page!  It then
    repeats this behavior, doubling the size of their printouts!
    
      This probably stems from the fact that the HP's printable area starts
    two lines down from the top (2 + 6 = 8) - it can't print any closer
    than 1/4 inch to any edge of the paper.  The next question, is how did
    this work in previous versions??  The customer can't understand how it
    wont work now, when it worked before the V2.4D upgrade...
    
      The only difference I can see right off is that WPS-PLUS used to use
    half-line spacing in the formatting...
    
      Any ideas?
    
    						Thanks in advance, Dan'l
                                                     

    I think you'd be better off asking in the WPS-PLUS conference:
    
    MAGIC::WPS-PLUS
    
    Hans

There is a supplied WPS-PLUS printer table called LASERJET.PRA for the 
Laserjet II printer.

Richard

    Thank you Richard!  I thought that was another 'old' table from the
    customer (their DIR command doesn't default to /DATE).  Also, I somehow
    expected there to be an HPLJII to go with the III.  Any explanation on
    the naming convention, or is that just the way it happened? :-)
    
    I'll have the customer try it tomorrow, and we'll see what happens.
    
    						Thanks!   Dan'l

I don't know why the WPS-PLUS group chose the names LASERJET and HPLJIII.  
Ask in the WPS-PLUS conference and you may get an explanation.

Richard

    Thanks, Richard.
    
    I've seen .11, I've seen MAGIC::WPS-PLUS, and that's why I'm asking in 
    _this_ conference.  It's us all pulling together to help each other and
    our customers that makes me feel so good.  I'm not trying to flame
    anybody, I'm just trying to find some answers for _our_ customers.
    It's very _easy_ to say that "It's not my fault" - just say it!
    But please, enough of the "see MAGIC::WPS-PLUS".  It's going to wear 
    out your paste buffer.
    
    Oh, just in case anybody doesn't already have MAGIC::WPS-PLUS in their
    notebook, just press keypad-7.
    
    					OA$END_RATHOLE, Dan'l

    The answer for this customer is that the initialization sequence has to
    be:
    	<ESC>E<ESC>&l12D<ESC>&l4E
    
    which resets the printer, sets the line spacing to half lines (12 lpi),
    and then sets a top margin of 4 (half) lines.  Note that 6 lpi and a
    top margin of two lines (the default) starts a full line further down
    the page.  A top margin of one line isn't right, either...  Must be
    an HP 'feature'.  Also, if you take out the vertical positioning
    capabilities, you may need to set the spacing back to 6 lpi (I didn't
    test it).
    
    					Cheers, Dan'l