Releasing network print jobs

[yeti]

Hi,

I'm using Foxpro2.6/dos on a Win2000 PC attached to an NT4 server.

I use the SET PRINTER TO \\SERVERNAME\QUEUENAME=LPTn: command to specify which printer queue/port to send my print jobs to. This works fine except that I can't seem to get Foxpro to send a "Flush printer port" type command to release completed print jobs.

Instead I have to wait for the server to timeout (30 seconds etc) before I see anything.

Any ideas?

I heard that using the SET PRINTER TO command twice did the trick - but not for me it seems.

Also, while I'm here - I wholeheartidly recommend a program called "TAME" from

http://www.tamedos.com.

This utility stops DOS programs like FPD from hogging 100% of the processor time under 32-bit o/s like Windows 2000/XP. It's not free, but its cheap and, better still, it works!!!

 

[yeti]

Slight update.

It seems my FPD26 reports are not automatically released by the NT4 spooler for 45-50 seconds. Is there anyway to reduce this? Registry entries on the NT4 server etc???

I've looked elsewhere on this forum but none of the existing suggestions work.

Our old Netware server used to have a timeout as part of the CAPTURE command but the Micosoft NET USE does not appear to have this functionality...

 

[dgrewe]

In the past I used
Set device to print
set printer to ////
.........
set printer to
set printer off
set device to screen
David W. Grewe
Dave@internationalbid.com

 

[FoxEgg]

Dear God,

Let there be a solution to this problem.... 'cos I got exactly the same....

None of the solutions I've tried seem to work ... 45 seconds of delays and when you shut down FPD it prints the report IMMEDIATELY...

Praying for the solution....

John Fox

 

[dgrewe]

John, There is an answer because the last place I work used FPD, Windows 9x on the workstations, and Novell 4 as the network. The problem was solved. It has been a while since I left that company and played with FPD in a Windows enviroment. But if I recall right, it was using 2 set printer to and set printer off calls back to back and/or the print spooling settings on the workstations that fixed the problem.

Have you checked the printer spooling settings. I believe you need to make sure that spooling is off and you print directly to the printer. David W. Grewe
Dave@internationalbid.com

 

[tesar]

Yeti and FoxEgg,
yours MEMLIMIT ?

 

[yeti]

David

The problem has never raised it's head with win95/98 clients - regardless of Server OS (we've used both in the past few years). My problem exists with W2000/XP clients only. Can't comment whether this is the case with Netware at the back end as we have NT4.

There are no timout parameters with the SET command under W2000 so there is no obvious control available.

Since my 1st post though I've found a solution, funninly enough, though the use of the software I was raving at the end of my message: "Tame" from

http://www.tamedos.com

Further configuration of this utility reduced the time delay to zero. For me this is the perfect solution - especially as the tamedos application also reduces the excessive CPU utilization inherent with DOS/FP apps.


Thanks to the group for the input!

 

[yeti]

Tesar,

Just for the record

MEMLIMIT =50,1024,8192