Greetings all -

We are having problems printing consistently in Arev 3.03 via Citrix Metaframe. Arev programs that work fine on an NT client, at times will lock the entire Citrix server, when run thru the Citrix client.

Arev is running on a NetWare 4.11 server, using the NLM's. It seems to hang after a print job is completed, and a PCPERFORM invokes a

"net use lpt1 /delete". We're using a NetWare 3.x CAPTURE.EXE to initially capture the job to the Novell queue.

As always, any ideas, things to check, workarounds, etc., would be appreciated … !

Why not try an endcap to end the capture?

The Sprezzatura Group

[/i]World leaders in all things RevSoft[/i]

We previously used ENDCAP, before we started using NT clients - but from NT, the ENDCAP wouldn't push the job out of the Novell print queue.

However, it may be worth a try on Citrix … ?

What are the timeouts set to? ti=?? you may want to shorten the time.

Dale Walker

Dale_walker@integrityonline.com

We've been setting CAPTURE with ti=0, as follows:

CAPTURE q= nb nt ti=0 c=

We have found that in a mixed NT W/Stn and W95 client scenario

that the NT Stations have to run printer connections differently

from the W95 stations.

It may be that you have to change the method in your case.

At the operating system level we have setup batch files to run

net use LPTx /delete but we call those batch files thus:-

SUSPEND EXIT PRT1 where PRT1 is the name of the batch file.

In this manner we have achieved 100% success rates when re-directing

between multiple networked printers from NT W/stns across NT Network.

This particular issue is peculiar to NT W/Stn clients.

For W95 clients we run full scripting as VOC entries thus:-

SUSPEND EXIT NET USE LPT1 \\servername\sharename /YES

SETPRINTER x

In this manner again we have 100% success in re-direction.

Notice that with the W95 stations we do not run the /DELETE line

as this seems to cause lockups under this scenario.

Hope this helps

Kind Regards,

Kevin Gray

Graycorp

(email - kevin@graycorp.com.au)

Interesting -

I will try your NT scenario - we've been using:

PCPERFORM "BATCHFILE"

where BATCHFILE is a DOS batch file containing:

net use lpt1 /delete

Thanks !!!

Kevin,

The reason we use SUSPEND in lieu of PCPERFORM has to do with

the memory issues. Seem to remember a note about that on the

knowledgebase some years ago.

Regards,

Kevin Gray

Suggest setting ti=10. Setting ti=0 causes a bit of grief. When set at 0 it wont print until you exit the application. If you are running graphics in other applications, set ti=25.

Dale

Dale_Walker@IntegrityOnline3.com

OK, I'm going to try ti=10. Then I shouldn't need an endcap, like I've been doing:

EXECUTE "SUSPEND EXIT ENDCAP.BAT"

(endcap.bat does a net use lpt1 /delete). Sometimes it works, sometimes it hangs the entire Citrix server …

View this thread on the forum...