Hello all!

We have a HP Laserjet 9000 that supports duplex printing, and I can do so from AREV by sending the correct control codes to the printer. When I try to set the printer to duplex using

STAT=SET_PRINTER("DUPLEX",2)

it returns a -4, which is "Invalid MSG parameter passed to the Set_Printer function.".

Does anyone have any ideas as to why I'm getting a -4 instead of -16 or maybe even a 1. Are there any workarounds? (i've tried all the advice on sending control codes through windows without any luck)

Thanks in advance!

Carl

Carl,

We haven't tried duplex printing with the OIPI (yet) but have you tried the Get_Printer("DUPLEX") function to see if you get a valid return first?

dbakke@srpcs.com

SRP Computer Solutions, Inc.

I can duplicate the -4 for "DUPLEX".

I have tested this on two printer: 1) HP LaserJet 4050n with duplexer and 2) Xerox Phaser 860DP. Both printer are network printers and we are printing from a Windows 2000 PC.

In both cases when I Set_Printer("DUPLEX",2), a -4 is returned. The printed output is printed on one-side only.

FWIW,

Ray Chan

Hi Carl, Ray, and Don,

The Set_Printer function is returning a -4, because this command was removed for some reason a while ago (and the help file was not updated). The Get_Printer DUPLEX will work. I am working with Revelation to re-introduce this feature if possible. I think the 16-bit version of the OIPI had problems with this command, but the 32-bit version should work fine.

Tony

Tony,

Thanks. Hopefully, it won't be too much problem and you can put the Set_Printer DUPLEX option back in.

It would be neato.

Ray

Folks:

We've fixed this and have a new oipi32.exe to send to anyone who is a current Works member.

Please contact Info@revelation.com with your request, please supply your works number and Expiration date.

Thanks-

Mike Ruane

Thanks for the quick and rapid response .

Ray

We aim to please!

Okay, the new OIPI32.exe works. That is, when I Set_Printer to Duplex/2 and then do a Get_Printer Duplex I see a "2". No more negative numbers

However, I'm probably missing something. In testing Duplexing, I see that it's printing on one-side on the first page, but duplex on page 2 and 3 for example. The general structure of my code is as follows:

Set_Printer("INIT"……)

Set_Printer("DUPLEX",2)

* to illustrate the point try this

For i=1 to 200

…build my data using

…Set_Printer("TEXT",I)

Next i

* close job

Set_Printer('TERM',0)

Is this a switch?

Thanks,

Ray

Hi Ray,

You are using the DUPLEX message correctly in your code.

I think there may be a timing dependency with the underlying printer control, which is causing this behavior. I have sent a few ideas off to Revelation, and they may need to change the interface to make this feature work perfectly. I was not able to test this feature, because my printer does not support duplex printing.

Tony

Tony,

You are using the DUPLEX message correctly in your code.

Well it's about time that I'm doing something right .

Thanks for the response and looking forward to changes for the Duplex feature.

Ray

Wow, thanks to all for the quick fix!!

View this thread on the forum...