[THIN] Re: Winframe Printing
- From: "Glenn Stokes" <ezra77@xxxxxxxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Fri, 15 Aug 2003 15:42:41 -0400
It is a local printer attached to LPT1. It is set to "spool print jobs so that
printing finishes faster." Then the box below that is checked for printing
immediately. The print processor is set to winprint. and the data type is RAW.
I tried it with printing directly to the printer and that does not work. Like I
mentioned earlier no other windows 2000 driver will get the printer to do a
test page other then other 700 series drivers. I would think that has alot to
do with it since the job on winframe thinks its printing to a hp 500. When I
install a hp 500 in w2k that looks like it will print, but nothing comes out. I
wish HP made a driver for the 712 in w2k
----- Original Message -----
From: Ron Oglesby
To: thin@xxxxxxxxxxxxx
Sent: Friday, August 15, 2003 2:00 PM
Subject: [THIN] Re: Winframe Printing
No I mean look at the client and tell me the settings. Default does me no
good. I have no idea about your build, wether it is a completely local printer
or hanging off something else,. What are the spooler settings (print directly
to the printer or spool etc.)
Print format raw or emf, etc
Look if the job gets from the client to the Citrix server IT IS A CLIENT
CONFIG PROBLEM. You may change something on the server (like a print type or
driver mapping) butit is gernally because the client config cant be changed by
a stubborn user.
Ron Oglesby
Senior Technical Architect
RapidApp
Office 312.372.7188
Mobile 815.325.7618
email roglesby@xxxxxxxxxxxx
-----Original Message-----
From: Glenn Stokes [mailto:ezra77@xxxxxxxxxxxxxxxx]
Sent: Friday, August 15, 2003 12:10 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Winframe Printing
Default settings. Nothing different.
----- Original Message -----
From: Ron Oglesby
To: thin@xxxxxxxxxxxxx
Sent: Friday, August 15, 2003 12:31 PM
Subject: [THIN] Re: Winframe Printing
Ok so the print job gets created and it gets to the client. How are the
client printer/spooling settings configured?
Winframe was crappy and if you think 1.7 is bad you should have been around
for 1.5. I had to do phone support for that product!!! WOW what a way to learn.
Ron Oglesby
Senior Technical Architect
RapidApp
Office 312.372.7188
Mobile 815.325.7618
email roglesby@xxxxxxxxxxxx
-----Original Message-----
From: Glenn Stokes [mailto:ezra77@xxxxxxxxxxxxxxxx]
Sent: Friday, August 15, 2003 10:48 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Winframe Printing
It will not autocreate the printer since Winframe does not have a driver
for the 712c. I discovered that only the 700 series driver in w2k will actually
get the printer to work at all. In the past we have created a printer in
winframe and used the 500 series driver to drive the hp712 on the 95/98
workstations. It worked perfectly. But now with 2000 as the client it will not
work. Remember the winframe is running 1.7 on nt 3.51.
Thanks
----- Original Message -----
From: Ron Oglesby
To: thin@xxxxxxxxxxxxx
Sent: Friday, August 15, 2003 11:21 AM
Subject: [THIN] Re: Winframe Printing
I love these...
"We are in the process of changing our computers to w2k workstations, and
now cannot get any printing to happen."
Ok. I get that no print jobs come out, but WHERE are they failing? Does
the auto-creation process not work? Were you auto-creating before or did you
just setup static printers that were there every time the client logged in
(common with winframe since autocreation was really bad)? Are there any
errors? Do you even see the printers or print jobs on the servers? Etc. (don't
be a user right. need some more info)
I it sounds to me like a simple driver name problem if you are using auto
creation but who knows without more info.
Ron Oglesby
Senior Technical Architect
RapidApp
Office 312.372.7188
Mobile 815.325.7618
email roglesby@xxxxxxxxxxxx
-----Original Message-----
From: Glenn Stokes [mailto:ezra77@xxxxxxxxxxxxxxxx]
Sent: Friday, August 15, 2003 9:54 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Winframe Printing
We have a citrix winframe system where I work and everything was fine
with remote printing using win95\98 and a HP deskjet 712c. We are in the
process of changing our computers to w2k workstations, and now cannot get any
printing to happen. These are all dialin machines using the ICA client. Any
suggestions (I know, I know, get rid of the winframe, and go with metaframe).
Glenn
MIS Tech
The Training School at Vineland
Other related posts:
