Path: utzoo!attcan!uunet!decwrl!mips!swrinde!cs.utexas.edu!sun-barr!rutgers!maverick.ksu.ksu.edu!kxb
From: kxb@math.ksu.edu (Karl Buck)
Newsgroups: comp.windows.ms
Subject: Re: Windows 3.0 and PC-NFS 3.0.1
Message-ID: <1990Sep25.125527.22372@maverick.ksu.ksu.edu>
Date: 25 Sep 90 12:55:27 GMT
References: <9487@uhccux.uhcc.Hawaii.Edu> <1060@travis.csd.harris.com>
Sender: news@maverick.ksu.ksu.edu (The News Guru)
Organization: Kansas State University
Lines: 23

leoh@hardy.hdw.csd.harris.com (Leo Hinds) writes:

>In article <9487@uhccux.uhcc.Hawaii.Edu> pilger@uhunix1.uhcc.Hawaii.Edu (Eric Pilger) writes:
>By the way, once the redirected printing (via lptx.os2) is "complete" (as 
>far as the application is concerned), which method do people here use to 
>get pc-nfs to spool the actual output? ...

Yes, too bad the hot key method does not work. It is the most conveinient.
I followed the advice of a friend and looked for something in the 
system.ini that might define key strokes that are to be ignored by
windows and passed to Dos but to no avail.  

>The (default) hot-key is a problem ... so the only alternative besides 
>quitting Win3 appears to do a PM(File)(Run)"Net print * lptx" ... but 
>unfortunately that usually ends up with a hung system ... any thoughts?

I've just been using the PRT -T60 in my config.sys just before NFSRUN. 
Almost all my jobs get passed in 60 sec or less (configure yours how you
want) and I've had no barfing by windows or the application yet.

If it matters I'm connecting to a 386sx to a sparc 1 via a Western 
Digital EtherCard+. Also, I'm using Command Post instead of the regular
file manager (works fine).