characters sent to printer during bootup

HP laser jet4L printer receives characters when computer is booted up and must be cleared with the reset button.  Occurs approximately 75% of the time.  Wasting paper and toner.  lpt.vxd dated 5/1/97 loaded but no help.
dcurrensAsked:
Who is Participating?
 
thoffmanConnect With a Mentor Commented:
I had seen a similar problem at my work.  MS Knowledge Base article Q157145 (http://support.microsoft.com/support/kb/articles/q157/1/45.asp) explains this problem.  According to that article, "This behavior occurs when the Drvwppqt.vxd virtual device driver is loaded or if you are not using an IEEE 1284 printer cable."

The Drvwppqt.vxd driver is used by MS Backup (or Seagate BackupExec) to check your parallel port for tape backup devices.  I have found that renaming all instances of this driver to Drvwppqt.old fixes the problem.  Note, though, that if you are actually using a parallel tape backup device with MS Backup, you cannot do this, since Windows won't be able to detect it anymore.  Considering that most tape backup drives these days are either IDE or SCSI, this shouldn't be a problem.
0
 
vikiingCommented:
Just only as a try, ¿what happens if you unplug the printer's power cord at start up, and reconnect it once Win is alive?

¿Do you know exactly what those characters are?; perhaps it can give you an idea about it's origin...
0
 
Asta CuCommented:
Have you checked your printer documentation to make sure the printer isn't in some type of off-line test mode?  That, or driver problems can cause these crazy characters to print at boot.  I assume you've checked that there aren't any problems in device manager surrounding the printer and/or lpt port assignment.
0
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
Asta CuCommented:
Please post which operating system you're using, it helps to get you more concise answers/possibilities.
0
 
thoffmanCommented:
It's most likely your parallel port settings.  Try going into your BIOS and switching the type of port to EPP, ECP, Standard, or Bi-directional.  If the port is on a card, check the card's documentation for information on how to switch the port type.

If this doesn't work, let me know what type of computer you have (processor, speed, RAM, etc).
0
 
thoffmanCommented:
To help answer this question, we need more info.

1)  What kind of computer do you have, 486/Pentium Classic, PII, AMD K6-2, etc?  How fast?
2)  Is it name brand?  If so, which brand?
3)  How is the parallel port set?  ECP, EPP, etc.
4)  How much RAM do you have?
5)  Is your cable IEEE-1284 compliant (Bi-di)?
6)  Have you tried another cable?
7)  Does the printer seem to be receiving data when you first turn the printer on, or some time during the Windows startup?  If it's during the startup, can you tell when (if you do a step-by-step, does it happen after a certain step)?
0
 
dcurrensAuthor Commented:
Generic PII, 266MHz, 64MB RAM, bidirectional cable.  Only tried this cable.  The printer has no on/off switch, always in a standby mode.  THIS IS AN INTERMITTENT PROBLEM.  OCCURS APPROX. 75% OF THE TIME.  I looked in my BIOS setup and could not find parallel port setup(ECP,EPP).  Never had this problem with win3.1.  A local newspaper columinist,who specializes in computer problems answered my question with "this is a known problem" and "try a more recent version of LPT.VXD"; which I did and still did not fix the problem.  Problem occurs when turning on computer and windows is loading.  Have no tried a boot up in a step by step mode.
0
 
Asta CuCommented:
It would help to know your current Windows version, motherboard and bios as well.

Are there any errors in Device Manager?
Could the printer by in some type of test mode?

I agree with Thoffman, access via SAFE MODE, look for any errors and/or duplicates -- deleting all occurrences of duplicates that are in error, rebooting.

The Windows95 troubleshooter may also prove helpful.

Can you find a bootlog.txt file on your computer, to see what failed to load?  This is created automatically if there are start-up problems, or if/when you request it by the SAFE PROMPT routine.  Since the problem is intermittent, and the printer appears to be getting signals and functioning as expected part of the time, leads me to believe the driver and/or setup is the problem.

A little more info from you about your environment would help.
0
 
Asta CuCommented:
This is the HP Link for your printer, which includes the most recent driver, troubleshooting info and a wealth of resources that may also prove helpful for you.

http://www.hp.com/cposupport/prodhome/lj4si.html
0
 
thoffmanCommented:
Does it happen only on boot, or does it also happen when sending a print job?  It could be a bad printer cable.  If you know somebody else with a computer and printer, see if you could borrow their cable.  If it fixes the problem, buy a new cable.  Your cable could have a break in the insulation, and, during boot or heavy hard drive activity, you're picking up some RF interference from your computer that is causing garbage.

As for the BIOS settings, what brand of BIOS do you have?  What date is it?  I work at a company that has several different computers with different BIOS's, so I could find one with the same BIOS and figure out where the port settings are.  Some implementations of the ECP protocol were buggy (both on motherboards and printers), and many motherboards default to ECP.  This problem you are describing is one of the symptoms of an incompatible ECP port.

We have a couple of 4L's over here that haven't had any problems.  I could try hooking one up to a machine similar to yours to see if I can reproduce the problem.
0
 
dcurrensAuthor Commented:
Sorry I haven't answered sooner, but have been very busy.  I have fixed the problem by putting a data switch inline with the printer. The switch is in the off position when i boot-up.  Thanks for your help.  
0
 
jrhelgesonCommented:
This question has been dormant since 2-7-1999, Are you still interested in this issue or should this question be archived?
0
 
thoffmanCommented:
Actually, I think I might know the answer, if anybody is interested.  I had forgotten about this question until jrhelgeson asked if it should be closed, but stumbled across, and solved, a similar problem at my work.

MS Knowledge Base article Q157145 (http://support.microsoft.com/support/kb/articles/q157/1/45.asp) explains this problem.  According to that article, "This behavior occurs when the Drvwppqt.vxd virtual device driver is loaded or if you are not using an IEEE 1284 printer cable."

The Drvwppqt.vxd driver is used by MS Backup (or Seagate BackupExec) to check your parallel port for tape backup devices.  I have found that renaming all instances of this driver to Drvwppqt.old fixes the problem.  Note, though, that if you are actually using a parallel tape backup device with MS Backup, you cannot do this, since Windows won't be able to detect it anymore.  Considering that most tape backup drives these days are either IDE or SCSI, this shouldn't be a problem.



0
 
dcurrensAuthor Commented:
thoffman had the correct answer.
0
 
dcurrensAuthor Commented:
thoffman had the right answer.
0
 
jrhelgesonCommented:
Reject current "answer" and let thoffman take the credit (and the points).

JRHelgeson
0
 
Asta CuCommented:
Congratulations!
0
 
dcurrensAuthor Commented:
DO NOT REOPEN Question.  Hoffman had the best answer.
0
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.