report printing (AREV64)
At 04 FEB 2024 04:11:16PM Barry Stevens wrote:
oi10.2.1
1.
run a report to printer . Selected from printer select popup
blank page printed
2.
run again and select printer that I have a OIPI (Classic) and
Report is displayed as expected.
BUT, click on 'Print' button and nothing happens.
Click export , select PDF , delay then the following message .
Report is only 1/4 page
At 04 FEB 2024 04:27PM Barry Stevens wrote:
oi10.2.1
1.
run a report to printer . Selected from printer select popup
blank page printed
2.
run again and select printer that I have a OIPI (Classic) and
Report is displayed as expected.
BUT, click on 'Print' button and nothing happens.
Click export , select PDF , delay then the following message .
Report is only 1/4 page
maybe a clue!
if I do a LISTBASIC …. (P
a blank page is printed.
At 04 FEB 2024 08:29PM Donald Bakke wrote:
Do you have the VSPDF8.ocx registered?
Also, if you intended to make your screenshots embedded in your message, use the Picture tool (Ctrl+P) rather than the Link tool.
At 04 FEB 2024 08:37PM Barry Stevens wrote:
Do you have the VSPDF8.ocx registered?
Also, if you intended to make your screenshots embedded in your message, use the Picture tool (Ctrl+P) rather than the Link tool.
How do I tell if it got registered or not. Do I assume clientsetup registers it?
It is in the oiclient10 folder.
oops, more haste less speed. (plus brain fart)
At 04 FEB 2024 11:30PM Barry Stevens wrote:
Do you have the VSPDF8.ocx registered?
Also, if you intended to make your screenshots embedded in your message, use the Picture tool (Ctrl+P) rather than the Link tool.
How do I tell if it got registered or not. Do I assume clientsetup registers it?
It is in the oiclient10 folder.
oops, more haste less speed. (plus brain fart)
registered - still no good
At 05 FEB 2024 01:27AM Barry Stevens wrote:
Do you have the VSPDF8.ocx registered?
Also, if you intended to make your screenshots embedded in your message, use the Picture tool (Ctrl+P) rather than the Link tool.
How do I tell if it got registered or not. Do I assume clientsetup registers it?
It is in the oiclient10 folder.
oops, more haste less speed. (plus brain fart)
registered - still no good
Re-Installing 'Microsoft XPS Document Writer' has got it all working now
At 05 FEB 2024 02:16AM Barry Stevens wrote:
Do you have the VSPDF8.ocx registered?
Also, if you intended to make your screenshots embedded in your message, use the Picture tool (Ctrl+P) rather than the Link tool.
How do I tell if it got registered or not. Do I assume clientsetup registers it?
It is in the oiclient10 folder.
oops, more haste less speed. (plus brain fart)
registered - still no good
Re-Installing 'Microsoft XPS Document Writer' has got it all working now
Correction:
The OIPI Print button is now working but not this one:
1.
run a report to printer . Selected from printer select popup
report does setprinter 2 ; printer on ;print print…;printer off
blank page printed
At 05 FEB 2024 07:30AM bshumsky wrote:
Hi, Barry. Sorry, it's gotten a bit confusing in this thread, and so let me ask some questions…
- What version of Windows are you running this on?
- Does OIPI work from OI itself (not AREV64)?
- After you installed the XPS Document Writer, did you reboot your PC ("just in case")?
- What is your default printer in Windows?
- What printer are you selecting in AREV64?
- After you installed the XPS Document Writer, is your PDISK behaving any better (from the other thread)?
Thanks,
- Bryan Shumsky
At 05 FEB 2024 03:02PM Barry Stevens wrote:
Hi, Barry. Sorry, it's gotten a bit confusing in this thread, and so let me ask some questions…
- What version of Windows are you running this on?
- Does OIPI work from OI itself (not AREV64)?
- After you installed the XPS Document Writer, did you reboot your PC ("just in case")?
- What is your default printer in Windows?
- What printer are you selecting in AREV64?
- After you installed the XPS Document Writer, is your PDISK behaving any better (from the other thread)?
Thanks,
- Bryan Shumsky
- What version of Windows are you running this on?
Windows 10
- Does OIPI work from OI itself (not AREV64)?
OIPI is working from AREV64 now after the XPS Document Writer install
- After you installed the XPS Document Writer, did you reboot your PC ("just in case")?
Yes
- What is your default printer in Windows?
A Brother hl-2305 -
- What printer are you selecting in AREV64?
Brother hl-2305
- After you installed the XPS Document Writer, is your PDISK behaving any better (from the other thread)?
NO
At 05 FEB 2024 03:07PM bshumsky wrote:
Thanks for the answers. And just to clarify, when you say it's working in AREV64, do you mean that your program which does a printer on, print, print, printer off works now too? Or only things like LIST VOC (P work still?
Thanks,
- Bryan Shumsky
At 05 FEB 2024 04:13PM Barry Stevens wrote:
Thanks for the answers. And just to clarify, when you say it's working in AREV64, do you mean that your program which does a printer on, print, print, printer off works now too? Or only things like LIST VOC (P work still?
Thanks,
- Bryan Shumsky
Sorry, getting confused myself now.
Ok, state of the nation:
run report to OIPI - displays report in the oipi form - select printer - prints report. ALL GOOD
run report to the Brother HL-2305 printer (Evironment printer type is HP-LASERJET) - blank page printed - 1 page report - but sometimes 3 blank pages. - ALL BAD
PDISK C:\temp\test.txt - get the redirection msg (no file is created at this point - in AREV it does)
run PDISK again and dont get an exists-overwrite message.
run report - no file created - ALL BAD
At 05 FEB 2024 07:14PM Barry Stevens wrote:
Thanks for the answers. And just to clarify, when you say it's working in AREV64, do you mean that your program which does a printer on, print, print, printer off works now too? Or only things like LIST VOC (P work still?
Thanks,
- Bryan Shumsky
Sorry, getting confused myself now.
Ok, state of the nation:
run report to OIPI - displays report in the oipi form - select printer - prints report. ALL GOOD
run report to the Brother HL-2305 printer (Evironment printer type is HP-LASERJET) - blank page printed - 1 page report - but sometimes 3 blank pages. - ALL BAD
PDISK C:\temp\test.txt - get the redirection msg (no file is created at this point - in AREV it does)
run PDISK again and dont get an exists-overwrite message.
run report - no file created - ALL BAD
further test:
PDISK C:\temp\test.txt
list voc ( P
pdisk prn
C:\temp\test.txt has the list
At 05 FEB 2024 09:41PM bshumsky wrote:
Hi, Barry. OK, I've just tried a simple test here, and I'm happy to say it worked, so let's see how it differs from what you've been trying.
I started up AREV64 in SYSPROG, hit F5 and at TCL entered:
EDIT SYSPROCS BARRY_TESTING
I created a new program with the following lines:
PRINTER ON
PRINT "HELLO WORLD"
PRINT "THIS IS A TEST"
PRINTER OFF
PRINTER CLOSE
I pressed shift+F9 to compile, and then ESC to exit (it told me there was an active select list, but I said to exit anyway). Back at TCL, I typed:
PDISK D:\TEMP\BARRYTEST.TXT
and got the redirect message.
I then typed:
RUN SYSPROCS BARRY_TESTING
and when it (silently) completed, I typed
PDISK PRN
And got the "Your open print files have been closed" message. I then looked in the D:\TEMP folder, and found the BARRYTEST.TXT file with the two lines of output.
If you do the EXACT SAME THING, do you have the same results?
Thanks,
- Bryan Shumsky
At 05 FEB 2024 09:47PM bshumsky wrote:
There are also a few additional environmental settings we can try. There is now a CFG_DIRECTPRINT which controls some behaviors of the DIRECTPRINT processor (which is used internally for some AREV64 printing). On my system, the CFG_DIRECTPRINT record contains the following:
<1> 0
<2> OIPI_PDF Printer
<3> Text
If the BARRY_TESTING program (in the other post) still doesn't work, try changing (or creating) the CFG_DIRECTPRINT record so that it looks like the above, exit and re-enter OI, and see if that makes any difference?
- Bryan Shumsky
At 05 FEB 2024 10:47PM Barry Stevens wrote:
There are also a few additional environmental settings we can try. There is now a CFG_DIRECTPRINT which controls some behaviors of the DIRECTPRINT processor (which is used internally for some AREV64 printing). On my system, the CFG_DIRECTPRINT record contains the following:
<1> 0
<2> OIPI_PDF Printer
<3> Text
If the BARRY_TESTING program (in the other post) still doesn't work, try changing (or creating) the CFG_DIRECTPRINT record so that it looks like the above, exit and re-enter OI, and see if that makes any difference?
- Bryan Shumsky
changed the CFG_DIRECTPRINT as above
I did the "BARRY_TESTING" routine from the previous post in both SYSPROG and MYAPP(BSBS)
results below same in both:
pdisk works
no pdisk - output to oipi (which has not been a problem (printer 1) )
TCL → SETPRINTER 2 (the brother)
ran and no printing happened.
btw: I see you have PRINTER CLOSE - I have never seen tis before and my progs dont have it. Is that something I need to add to all my print routines.
What I really need to get working is printer output - pdisk is not required in live, was just an elimination issue test.
At 06 FEB 2024 12:20AM Barry Stevens wrote:
There are also a few additional environmental settings we can try. There is now a CFG_DIRECTPRINT which controls some behaviors of the DIRECTPRINT processor (which is used internally for some AREV64 printing). On my system, the CFG_DIRECTPRINT record contains the following:
<1> 0
<2> OIPI_PDF Printer
<3> Text
If the BARRY_TESTING program (in the other post) still doesn't work, try changing (or creating) the CFG_DIRECTPRINT record so that it looks like the above, exit and re-enter OI, and see if that makes any difference?
- Bryan Shumsky
changed the CFG_DIRECTPRINT as above
I did the "BARRY_TESTING" routine from the previous post in both SYSPROG and MYAPP(BSBS)
results below same in both:
pdisk works
no pdisk - output to oipi (which has not been a problem (printer 1) )
TCL → SETPRINTER 2 (the brother)
ran and no printing happened.
btw: I see you have PRINTER CLOSE - I have never seen tis before and my progs dont have it. Is that something I need to add to all my print routines.
What I really need to get working is printer output - pdisk is not required in live, was just an elimination issue test.
ran and no printing happened.I actually do see the spooler receiving data and the printer showing 'receiving data' but nothing printed.
Now my printing prog.
ran to OIPI and all works.
ran to printer (2) , blank page printed
pdisk c:\temp\test.txt
ran myprog
pdisk prn
as soon as I did the pdisk prn, 3 blank pages printed on the printer.
had changed the printing prog to - not ask for printer - added PRINTER CLOSE
setprinter 2
run myprog
printer shows receiving data - no printing
remove the printer close
run myprog
blank page is printed
remove the printer close from barry_testing
printer shows receiving data - no printing
This is totally weird!!
At 06 FEB 2024 01:45PM bshumsky wrote:
Hi, Barry.
I believe this may all be related to that change in DirectPrint mentioned earlier (which as discussed was actually needed to make AREV64 printing work under 64-bit Windows 10 and Windows 11). There is some additional configuration that _might_ need to be done, and I'm guessing that's what we need in your case.
I have a document discussing this change ready for "pre-release" - it discusses the configuration you need to change. Please take a look at it here:
Following those directions, please select your desired printer, and select the type of "data output" it should use. You may try any of the 3 provided options to see which one (if any) works…
Let us know how it goes?
- Bryan Shumsky
At 06 FEB 2024 02:55PM Barry Stevens wrote:
Hi, Barry.
I believe this may all be related to that change in DirectPrint mentioned earlier (which as discussed was actually needed to make AREV64 printing work under 64-bit Windows 10 and Windows 11). There is some additional configuration that _might_ need to be done, and I'm guessing that's what we need in your case.
I have a document discussing this change ready for "pre-release" - it discusses the configuration you need to change. Please take a look at it here:
Following those directions, please select your desired printer, and select the type of "data output" it should use. You may try any of the 3 provided options to see which one (if any) works…
Let us know how it goes?
- Bryan Shumsky
I had tried that. But I will see if I missed anything and follow your doc…and make sure I had restarted OI as well.
Thanks.
At 06 FEB 2024 03:12PM Barry Stevens wrote:
Hi, Barry.
I believe this may all be related to that change in DirectPrint mentioned earlier (which as discussed was actually needed to make AREV64 printing work under 64-bit Windows 10 and Windows 11). There is some additional configuration that _might_ need to be done, and I'm guessing that's what we need in your case.
I have a document discussing this change ready for "pre-release" - it discusses the configuration you need to change. Please take a look at it here:
Following those directions, please select your desired printer, and select the type of "data output" it should use. You may try any of the 3 provided options to see which one (if any) works…
Let us know how it goes?
- Bryan Shumsky
Just while I think of it. (While I am still in your timezone)
In the live site situation (single PC), the actual printer is a receipt printer on a parallel printer port.
Would I just enter LPT1 (Allowed?) in the printer name. I would be sending epson esc codes.
At 06 FEB 2024 03:23PM bshumsky wrote:
Does Windows recognize the receipt printer by name? If so, you should still be able to address it by name as well.
At 06 FEB 2024 04:13PM Barry Stevens wrote:
Hi, Barry.
I believe this may all be related to that change in DirectPrint mentioned earlier (which as discussed was actually needed to make AREV64 printing work under 64-bit Windows 10 and Windows 11). There is some additional configuration that _might_ need to be done, and I'm guessing that's what we need in your case.
I have a document discussing this change ready for "pre-release" - it discusses the configuration you need to change. Please take a look at it here:
Following those directions, please select your desired printer, and select the type of "data output" it should use. You may try any of the 3 provided options to see which one (if any) works…
Let us know how it goes?
- Bryan Shumsky
I had tried that. But I will see if I missed anything and follow your doc…and make sure I had restarted OI as well.
Thanks.
Using TEXT worked!!
which I had done before, BUT, I dont think I exited OI. Maybe add that to your documentation!!
Now I can sleep at night. :smile:
Thanks for ALL your help, as usual.