printing from Win95

Andrew Tridgell tridge at
Wed Sep 23 02:50:22 GMT 1998

> Something similar to this has been posted to the samba group a few
> times, but I didn't see any replys.  Anyway - the last few revisions of
> the code that I've checked out (including one from 12:11pm Sept 23 EST)
> have broken printing from Win95 machines.

It's not as simple as that. Printing works fine from Win95 for me (my
wife uses it all the time).

> There was an error writing to \\village\laser for printer (HP LaserJet
> 4M Plus):
> There was a problem printing to the printer due to an unknown system
> error.
> Restart Windows, and the try printer again.

you may have to do a comparitive sniff to work out what's
wrong. Download a earlier version (one that works) then get a sniff or
log of that printing. Then use the current version and get another
log. Then look at them to find the first point at which they diverge.
Then stare at the surrounding packets till you find what the
difference is in how Samba reponded.

Alternatively (if you don't like staring at sniffs) use the -D option
to CVS to pull out different versions till you find the exact code
change that caused the problem. For example:

cvs -d :pserver:cvs at co -D "9/1/98" samba/source
... compile and test in samba/source ... note result ...
rm -rf samba/source
cvs -d :pserver:cvs at co -D "9/20/98" samba/source
... compile and test in samba/source ... note result ...

then use a bisection search on the date to find the day (and even
hour/minute) that the code was broken. You'll probably find it in a
few tests. Then use diff to see exactly what bit of code caused the

The advantage of this method is that it is almost completely
automated. You don't need to know anything about how the code works to
find the bug!

More information about the samba-technical mailing list