This app was originally written by kirk for Fatdog64 but works just as well in Slacko and Precise. It is a simple rox app where you just click it and it scans for shares, then it makes a drive icon for each share which you simply click and it shows the network share. If a password is needed a box pops up requiring the username and password.

The reason for this app is that Pnethood, while it has served us well for many years is often failing to discover network shares in the latest Puppies even though the shares exist. This is because it's major dependency nbtscan is getting old and largely unmaintained.

This is designed for home use. For a more heavy-duty solution use YASSM by rcrsn51. The next Slacko will be shipping with both in place of Pnethood.

This is tested working with XP, Windows 7, Mac and Puppy-samba shares. It is tested with the latest Slacko-beta, Precise Puppy and latest Wary/Racy Beta.

Once you install the pet there is a directory made in /root/network with the Network icon inside. Navigate to that and just click the Network icon to begin. There is no menu entry.

If you forget to unmount shares at shutdown then there is a service script to take care of that.

Warning: No warranty. There is the possibility that if you do something silly like deleting a mounted share then there will be data loss on the share. If you have problems just reboot.

Dependencies:

rox-filer
mpscan (should be already there in most pups)
mount.cifs (should be already there in most pups)
smbclient (should be already there in most pups)
base64 (only in latest pups - includes slacko-533, wary/racy-5.3,precise-5.4)

This will likely fail in Lupu, just test if base64 is there with

Code:

which base64

EDIT:
update to 0.8 fixed issues with nounix and sec=ntlm thanks to shinobar and gcmartin

In any case, The scan only needs to be done when you need to find new shares, the existing shares need not be updated.

kirk actually hacked mpscan in fatdog to time out quicker. I have that source and will compile soon. I just checked, and mpscan is a part of kirk's File-Sharing rox app present in all puppies. I compiled mpscan on the raspberry-pi so I can test how fast it is in SAP6 (provided I have smbclient, can't remember). I know the FIle-Sharing works fine in SAP6.

peebee, do you ever use that File-Sharing app? I'd be interested to know how fast/slow that is for you._________________Woof Mailing List | keep the faith |

peebee, do you ever use that File-Sharing app? I'd be interested to know how fast/slow that is for you.

No other devices - just the desktop and laptop....I'm a simple soul lol

No - haven't used the file-sharing app - not even sure I knew it existed - is it in the menu?? Where would I find it?

When I went back to 5.3.6.5 the direct command found the server. Then when I did rcrsn51's test command it also found the server but took a long time to finish with the Timeout output.

Actually pnethood sometimes doesn't find the server and a couple of presses of the rescan are needed - its almost like the server goes to sleep and has to be kicked back into action._________________ LxPup = Puppy + LXDE

If you want to recompile just run ./configure && make and strip the bin in the src dir with strip --strip-unneeded mpscan

Back up the old /usr/sbin/mpscan and replace with the new binary.

I can't see any difference.

-

BTW, it works (sort of) on the raspberry pi, but network_roxapp doesn't produce the win7 mounts. even though I get the prompt for a user and password. It's some weird error, probably to do with the fact that I had to install nearly all of debian samba, which links to kerberos and all the security stuff. The mac and my puppy share worked fine. I'll save that for another day.
NOTE: raspi users, please don't use on SAP6 because there is a potential data loss bug specific to the SAP6 OS and the network_roxapp.

Network scan found my share in an acceptable time - c. 10 secs
~
Seems to have fixed it for me.

Ok, good news . Even though I had no issues and and couldn't really tell the difference in speed, kirk must have seen something and made the appropriate adjustments. I haven't done a diff so as of now I don't know. Maybe I don't need to know .

Some note: some windows servers only listen on ports 445 instead of 139.

Yeah.. do you reckon it's worth running a second loop on failure ? Or maybe a 'help' file or README ? It's nice and simple how it is, more complication breeds complications .. . There is the config file, a readme file could point that out I guess._________________Woof Mailing List | keep the faith |