I looked at frisbee in a recent Puppy and it uses: -D nl80211,wext
So it would try to connect with the modern protocol first, then fall back to the original. That might explain the time lag.
I looked at frisbee in a recent Puppy and it uses: -D nl80211,wext
So it would try to connect with the modern protocol first, then fall back to the original. That might explain the time lag.
Search through the frisbee code and find the line where wpa_supplicant is called. Add the option "-D wext".
I have just two more words to say about this issue: Maslow's Hammer
@wizard: Here is my gut instinct about this situation. Any file transfer that involves intermediate storage on a USB drive won't be much more efficient than the original procedure, especially with large files.
In the PWF config, can I assume that you are setting INTERFACE=eth1
Try setting DRIVER=wext
Did you reboot after installing the firmware package?
It occurs to me that you could now print anything on a 4x6 thermal label by putting the content in an 800x1200 pixel mono PNG and sending it directly to the printer with CUPS-lpr.
Or you could code the content in ZPL and print it with "-o raw".
Before going any further, I would confirm that these machines can ping each other.
From Machine A, run: ping 192.168.1.4
From Machine B, run: ping 192.168.1.1
Are you making a run back to the shop for more labels, just to be sure that this all works?
You can probably just use: pdftoppm -png xxx.pdf label
That would make the set of PNG files named label-1.png, label-2.png ...
Then print them with: lpr -P LABEL label*.png
Booting from SD cards has always been unreliable.
1. Boot from the Ventoy USB again and check the SD card. Is it detected as a USB or an EMMC device?
2. Can you find the missing menu.lst file on the SD card?