I don't know why that would be. It must have something to do with how Windows queues its print jobs. There must be a difference between setting up a "network" printer versus a "local port" printer.A print job was sent while the computer was not ready. Usually, these get stuck on the computer that sent the job. Today, the job was printed as soon as Puppy booted up.
You don't need a separate script. You already have an auto-start script for Samba - just add the code there. But mount sdb1 before you start the Samba server.I added a start up script to auto log on sdb1