Telnet with a Windows 2003 server

[John Esak]

Wow, Bob... Richard Kreiss was the first person to bring this precise
"printer/session-name filePro can't get at it" thing to the FP Room several
months ago, maybe even a year. Every little bit you can do to help solve
this problem will be much appreciated and cause me at least to buy many more
copies of Print Wizard and/or Anzio.

As for brainstrorming it with you... I arrived at just about the same
conclusions you have very quickly with no avenues to pursue. I had even
brought the question up with Ken Brody at the time, and we kind of let it go
as an unsolvable for the moment thing.  I know this message didn't help at
all, but just to let you know, we in the FP Room have been thinking about
this very problem for months now. Tony Ryder bought a copy of Print Wizard
and ran into the exact same issue immediately. He decided to put in a Unix
system partly because of this actual problem... but mostly because of no
easy way to get a good TS non-desktop view into filePro.  He sure loves
Print Wizard though. This is simply the best add-on program that anyone
could buy for filePro. No question.  I have been saying for years that FP
Tech should make a royalty arrangement with you and just include it in its
licensing scheme somehow with every copy. This is one of the really critical
things they need to do in order to stay viable. Ifyou can't print to any
printer, your program is seriously challenged these days. Print Wizard would
remove that issue for them.

John Esak


> -----Original Message-----
> From: filepro-list-bounces+john=valar.com at lists.celestial.com
> [mailto:filepro-list-bounces+john=valar.com at lists.celestial.com] On Behalf
> Of Bob Rasmussen
> Sent: Wednesday, November 28, 2007 4:59 PM
> To: GCC Consulting
> Cc: filepro-list at lists.celestial.com
> Subject: RE: Telnet with a Windows 2003 server
> 
> On Tue, 27 Nov 2007, GCC Consulting wrote:
> 
> > Filepro has a problem with terminal server as one does not know what the
> > terminal server session # is for the printer.  Theresore pfpostprint
> along
> > with printwizard would work by redirecting the print job to the default
> > windows printer for that session.
> 
> Surprisingly, the shell environment you inherit when you connect via
> Terminal Services does not include an environment variable for session-ID,
> although there is one for remote machine (CLIENTNAME) and one for
> SESSIONNAME. However, a program running in a TS environment can find out
> if it is in a TS environment, and what the session ID is. In fact, I have
> just added an ANZ_REMOTE_SESSION internal variable in Anzio 16.0b (now
> available).
> 
> I guess I should put the same capability in Print Wizard. Then, I'll
> provide a way to dereference it in the printer name.
> 
> It would also be possible to write a small program that would output the
> session id, where it could be redirected to a file. Or, what's the best
> way to have an EXE get something into an environment variable, such that
> it will not be lost when the EXE ends? Does Windows have the equivalent of
> "." or reading input from a program, such as
>    set SESSION `someprog.exe'
> ???
> 
> If a variable could be defined, then something called by PFPOSTPRINT could
> dereference that variable, and build an accurate printer name.
> 
> Help me brainstorm here.
> 
> Regards,
> ....Bob Rasmussen,   President,   Rasmussen Software, Inc.
> 
> personal e-mail: ras at anzio.com
>  company e-mail: rsi at anzio.com
>           voice: (US) 503-624-0360 (9:00-6:00 Pacific Time)
>             fax: (US) 503-624-0760
>             web: http://www.anzio.com
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list