Closed Bug 91307 Opened 23 years ago Closed 23 years ago

Can't Print on Win98(isolated incident)

Categories

(Core :: Printing: Output, defect)

x86
Windows NT
defect
Not set
major

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: sol, Assigned: dcone)

Details

I can't print anything on Windows 98 using a recent commercial branch build.

I am able to print the same content from Netscape Communicator 4.7 on the same
machine.

Using 2001-07-17-05 commercial branch on Win98.

Steps to reproduce:

1. Launch the browser.

2. After the page finishes loading (mine is home.netscape.com), press the
"Print" button on the main toolbar.

3. When Print dialog appears, press "OK".

Expected result: Page spools to printer, and is then printed. (Print progress is
noted in the sys tray.)

Actual result: Nothing - it appears that the print job has not been sent to the
printer.

Note: I cannot print from Mail either. I select a message, press "Print" from
the main Mail toolbar, say "OK" in the print dialog, and ... nothing.
I tried using 2001-07-18-05 commercial branch (I uninstalled the 07-17, and did
a custom install of 07-18).

I still experience the same problem.
worksforme on yesterday's 7/17 branch and today's 7/18 branch on win98.
I also tried new profile and old profile.

Let me try on someone else's box.


Todd Pringle was *not* able to reproduce running 07-17 on Win98.
Using 7/18 branch on win98, I tried to print to a bogus printer (the "Rendering
Subsystem" from some fax software.)  I didn't expect it to do anything useful,
but it actually crashed in gkgfxwin.  Talkback ID = TB33049872W.
I have confirmed on another machine upstairs on Mail QA team.

Fenella has Windows with yesterday's branch build.
printing works on her system.
Sol, can you try another URL?
I tried printing to another printer - that did not help. I tried printing a
different URL - that did not help.
Sol, how about clean re-install?
In recent builds (since ~ 7/15/2001) I have been having printing problems too on
Win98.

My system prints directly to the printer spooler (rather than to the local Win98
spooler).  Until recent builds this has worked just fine for me.

Now when I try to print, the 1st page appears, followed by a page generated by
the printer telling me that the job was too large for the printer's memory.

Note that I have been able to print emails, but not web pages longer than 1
page.
I tried a clean install - it did not help. (I uninstalled 07-17 commercial
branch, and installed 07-18 commercial branch. I used the "Custom" path and left
everything checked.)

I also created a new profile - that did not help. I tried printing both
home.netscape.com and www.yahoo.com.
I just tried another QA machine(Paul W.) with yesterday's branch on windows..
printing works on that machine
Sol, Don suggested wiping out your registry also...
The not printing could be a thousand reasons.. and if it can not be reproduced 
on other machines.. or a regression time can not be found.. then I would say its 
a local problem and the software needs to have a fresh re-install.  I can 
not think of anything that changed printing.. I have been printing all week.. 
not a problem on all platforms and OS's with the lastest trunk and branch.  I 
might be worried if there were some work going on there.. but.. there really has 
not.. that I know of.  When was the last time you printed.. with what build.. 
can you install that and print.  It sounds like Mozilla can not get the Device 
to print to..and silently fails.  How much memory do you have on your computer.. 
also.. can you print a really simple URL.. local with like two lines of text?

Do the pages have lots of images.. imagelib has some memory issues..but thats 
been around for a few months..
I just crashed trying to print an email.

I printed the email but nothing happened.  I then noticed a little Netscape
window hidden in the lower right corner of my screen.  I closed that by choosing
the Close option in the window frame.  I then tried to print the same email
again, and the crash occurred immediately.  A talkback report was submitted.
my 2 cents: my winNT 0718 branch from today prints web pages 
(google..netscape) fine.
We should check the printer driver version you are using, Sol.  
Don - I am unable to print a very simple text file.

The text file contains "asdfasdfasdf". Strangely - I was able to print this text
file from Netscape one time, and I have failed every time after that.

I am using a new machine (got it on Friday), so I have never been able to print
from the client. As I said above, however, I am able to print from Communicator.

Lisa - I installed the printer drivers this morning from the network.
I can print if I initiate request w/ ctrl p, but not with print icon (in both
navigator and messenger)

Win98
Build ID: 2001071803
Severity: normal → major
Brent was using trunk build...I also downloaded trunk bits
and tried printing from both icon and Ctrl-P..

worksforme on trunk also. 2001071803
Hmmm, WFM win98, commercial 20010718, will check on w2k now
wfm - win NT - 20010717 branch
PDT+ in hopes of a fix...
Whiteboard: PDT+
Can't repro.. so I doubt there is a fix.
Reproduces for me with the Windows branch build (2001071805) at the following url:

www.macsurfer.com

1) Got to url
2) Print page
3) Crash occurs: GKLAYOUT.DLL

This doesn't occur on Mac branch build (2001071803)
Tested under Windows ME
Never mind my last comments... The crash is mentioned is a different issue.
We think we've dodged this one :-)  Removing the PDT+.
Whiteboard: PDT+
updating summary.
Summary: Can't Print on Win98 → Can't Print on Win98(isolated incident)
Sol's problem has been solved.  Esther and I went to his system and we installed
a n HP LaserJet 5Si printer driver.  This worked.  Then, we went back to the HP
LaserJet 5Si PostScript printer driver Sol used and we updated it the driver
again.  The Adobe PS driver is v4.00 and this works.   So, Sol is now able to print.

Pls track the crashes found in separate bugs.
Thanks
Don, I think we can mark this WFM now...
Yes.. this works for me
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
verified on 7/19 branch build.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.