Slow Printing to Novell Queue via JetDirect

Have recently upgraded a network structure and installed SBS and new Dell PC's running Windows XP SP2.
For logistical reasons have retained Novell 3.12 as manufacturing software runs on this platform, and at this stage cannot be change/upgraded.
When sending a print Oki Microline 5521 via JetDirect print server, it takes 30 seconds for the first page to print. All other pages on same print run follow immediately. Next print sent, also takes 30 seconds for first page to print.
On existing PC running Win 95, same print takes only 5 seconds to print.

Use this capture command to set printers:-
net use lpt1: /delete
net use lpt2: /delete
net use lpt3: /delete
net use lpt1: \\mid_steels\emmag
net use lpt2: \\mid_steels\emmag
net use lpt3: \\mid_steels\emmag
net use /persistent:no

Use this command to start the Novell based app:-
C:\WINDOWS\system32\ /c i:\login\xp_start.bat

XP_Start.bat is as follows


Sysrun0 is as follows:-

Sysmen0 and syscomm are exe files within the Novell app.

Can you help me find a solution to this print problem please?

Who is Participating?
To start, the obligatory "you have NetWare 3.12.  Novell is a company, not an OS."

That said, I suspect that your issue is because you're using WinXP now instead of the more straight-forward Win95 you had been using.

The other part of your problem is you are using Net Use, which means to me you're probably using the crapware(tm) client that comes with Windows.

If you install the Novell Client32 - CUSTOM, not "typical" selecting only IPX, only bindery (not NDS) and no optional functions, your connectivity from Windows to NetWare will work much better.  Then, use the normal NetWare CAPTURE command, rather than NET USE (which is for Windows NetBIOS printing, not for NetWare printing).

Then, in the XP printer object that you must have in order to print from XP, set it to "print directly to printer" instead of using the local spooler at all.  NetWare printing is much more efficient than Windows printing.

Too bad it sounds like you went with Microsoft SBS instead of Novell SBS, but that has little to do with your printing issue.  It's the use of the local Windows spool instead of printing directly to the NetWare queue.
It sounds like an "autoencdap issue" to me, but I don't know how to set it with net use, as I always use Novell's capture.exe. An equivalent of net use would look like:
net use lpt2: \\mid_steels\emmag
capture l=2 q=emmag nt nb nff ti=3

where nt=no tabs, nb=no banner, nff=no form feed and ti=timeout=3 sec. That would "force" NW queue to flush when 3 seconds passed an no further data was received into the queue.

On the flame side, I like NetWare however I don't like Novell's "activity" in the last decade, and probably others neither, so no wonder they look for alternatives. Once, I will write an article on Novell's buying/selling products like Wordperfect, Unix(ware), DRDOS or simply just selling out, like Btrieve (now Pervasive SQL, selling almost same price per user as NW base OS) or NetWare Access Server (sold to Citrix, sinked, look for "Metaframe" or MS Terminal Server) and so on... :-(
Does autoendcap trump the Windows XP spooler "Spool print documents so program fiinishes printing faster" along with "Start printing immediately" (i.e. the default Windows XP printer setup? )

If you do "Print directly to the printer," since the printer is captured to a NetWare queue, then the Windows spooler won't be adding a delay and the program will actually finish printing faster - and you should see the first page faster, too.  

In such case, the autoendcap might make a difference, I suppose, but since all printing in Windows XP - even legacy DOS-based printing - must go through a Windows XP printer object, not taking the effect of local spooling into account is the most likely suspect, IMHO.
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

LJShepherdAuthor Commented:
Many thanks for the replies. I am now in China on business for a week or so, and will not be back at client's office until 25th August, at which time I will put your comments to good use and see what the results are.
LJShepherdAuthor Commented:
Hi Guys,
I have installed a custome version of Novell Client 32 as mentioned by ShineOn, and made all the mods accordingly.
I have also used the Capture command, and tried various configurations of that as  outlined by Maques.
I opend up Pconsole to check what was happening when I sent a print to the queue, and the bottom line is that it still takes anything from 30 - 50 seconds to load the print in the queue. Once it is in the queue and the ready status appears, it leaves the queue immediately and the print appears on the printer.
This leaves me wondering whether it is a general network communication problem between the XP PC, the Small Business Server and Netware.
Any ideas?
Do you have the Windows printer object set to print directly to the printer?
It is still seem to be a workstation/application problem.
Queue flushing/closing is "inititated" by the workstation (printing application/nw client), and as you say, once it is "closed" it gets printed immediately - so it does not seem to be server or printer "based" problem.
Do other applications exhibit this problem (eg. wordpad, etc.) or only your apps?
As I understand this is a DOS application, you should try to specify the "capture .. ti=3" command before it is started and also check if capture was successfully ran [let's say with a "pause" command].
And/or set checkbox for autoendcap and /or specify timeout in the related NWClient property window, I guess its name is "default capture" or something like this.
LJShepherdAuthor Commented:
Hi Guys,
No matter what I try, I just cannot get the prints to speed up. It is still taking 50 seconds or so for the prints to appear.
I have told the client that we may need to look at another solution, and will therefore close the question, and split the points between you.
Many thanks for your efforts.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.