Network printer page on boot recurrence 2

[KimberTech]

Two 98se systems on peer to peer. Lex' printer using HP4 driver...long story. Unit prints one page without user interaction with 3 hearts on the top left, only happens on boot. Then its fine...works great any other time.
Nothing else odd.

In the process of removing modemshare ...and have removed lantastic 7.0...have just upgraded from 95B to 98SE.

I am hoping I do NOT have to remove and reinstall printers to correct this. It will take me ages to reconfigure the software apps, as they are mapped internally to the printer as it sits and will lose the settings if I delete them.

HELP?


OK...pulling my hair out.
Problem has reoccured on one of the printers.
The page prints immediately after boot, before login to the network even occurs.
I have looked in MSCONFIG but I am not finding any answers.
Back to searching the Lex documentation and crossing my fingers that someone out there has run into this before.
Thanks ahead for any insight.

Kimber



Kimber

The more I learn,I realize how much more there is to know!

 

[apex1x]

Did this "printing ghost" start just recently?
Check your MBR and system for a virus.
Find anything suspicious in the MSCONFIG?
Make sure those programs you removed are removed from the registry... try running a regclean type program.
Thats all I can think of for now.
Let us know how it goes. ~Apex1x
Miller's Law:
You can't tell how deep a puddle is until you step into it.

 

[KimberTech]

systems started doing this after a Lexmark tech "fixed" network printer problems on windows 95.
After the upgrade to 98 it started happening more often.

msconfig nothing unusual.
regclean was run and then I manually edited everything else out of it to make sure it was clean.
Antivirus is up to date.

Thanks for your reply....I am completely at a loss on this one. Kimber

The more I learn,I realize how much more there is to know!

 

[mudskipper]

I appologize, but I cannot find the document that solved this issue for me. I believe that we found the information on Lexmark's website.

There is a file that is unneeded (I believe in the Windows directory). After deleting it, this issue went away. I will see if I can locate the doc for you and post back. I'm hoping that this is enough info to get you searching on the right track in case I am unable to find it!

Mudskipper
___________________________________________________________________________________

Groucho said it best- "A four year-old child could understand this! Quick! Run out and find me a four year-old child: I can't make heads nor tails out of this!"

 

[mudskipper]

Ah. Found a similar Doc at

http://support.microsoft.com/default.aspx?scid=KB;en-us;q157145

Possibly try renaming Drvwppqt.vxd ....that might have been it....

Mudskipper
___________________________________________________________________________________

Groucho said it best- "A four year-old child could understand this! Quick! Run out and find me a four year-old child: I can't make heads nor tails out of this!"

 

[mudskipper]

I just like to hear myself talk LOL

Yup, just found my printout. We renamed that file DRVWPPQT.VXD. Enjoy

Mudskipper
___________________________________________________________________________________

Groucho said it best- "A four year-old child could understand this! Quick! Run out and find me a four year-old child: I can't make heads nor tails out of this!"

 

[KimberTech]

I will give this a try the next time I go in...
If this works....I am going to jump up and down...it has been driving me up a wall for weeks.

I will post as soon as I know.....THANKS! Kimber

The more I learn,I realize how much more there is to know!

 

[KimberTech]

OK...I tried renaming the file, and that just changed the garbage that was printed.
Next I tried the cable, and it was not compliant as the article states.
Thanks to YOU MUDSKIPPER I have solved a VERY OLD problem for the client, and I look like a hero.

Thanks millions!

Kimber Kimber

The more I learn,I realize how much more there is to know!

 

[ImaKatLover2]

My thanks too to Mudslinger. I just 'discovered' this website today and also had this problem for years! In our instance, renaming the file worked. Hurray!