I'm using the latest version of SMBFS and I do increase the stack as mentioned in another thread.

I'm copying files from the peg2 to a unix based NAS (QNAP 119).

When it tries to copy a files greater in size than a few megs or so a 'object in use' error is given.

Any ideas?

Matt

Have you tried the older smbf instead (1.63 vs 1.71) ?
I had similar and other troubles with the newer version
(here at least, with MOS 1.4.5 and MosNet communicating
with a WinXP Pro PC) so I'm stuck with 1.63 now...

Thanks Elena,

Now where might I find 1.63??

Matt

> 1.71

Latest version is v1.73.

http://sourceforge.net/project/showfiles.php?group_id=139532&package_id=153070

I don't remember where I got 1.63, maybe on Aminet.

Now I don't know if your problems may be related to the ones
I have, I can just tell that starting with some version
(1.7x ?) I get ridicolous upload speeds (about 20 kbps)
and sometimes strange errors.

PS tried 1.73 too: same troubles.

smbfs-1.73 /MorphOS-2.2 /Peg2-G4 /Win2k-PC

Its crashes here only a few kilo /meg with more than one smbfs devices at same time.

If only one smbfs device mounted at same time, then its work here fine with big files up to 4GB. (>4GB delivered false sizes.)
Download speed (with morphos 2.2 default netstack) its here around 4,5MByte/s and Upload Speed around 700kByte/s.

I voted for each device a separate logon script, which was previously registered device closes.

Hints for Scripts:
- have Name of mounted device
- have Icons
- have default stack 4096
- have Programm "MOSSYS:c/IconX"
- have Tooltypes:
STARTPRI=-127
DONOTWAIT
WINDOW=CON:0/200/600/150/SMBFS_Start/AUTO/NOTOOLBAR/MAXREVIEW512
- one default smbfs Device Script is copied to WBstartup
- Modify all <...> to required entry


One Script:

; Wait for TCP/IP stack to show up
IF NOT EXISTS MOSSYS:s/network-startup
WaitForPort MIAMI.1 LOOP 10
ELSE
WaitForPort NETSTACK LOOP 10
ENDIF
; First start needs some delay.
IF NOT EXISTS T:SMBFS.log
ECHO "smbfs for '<user>' " >>T:SMBFS.log
WAIT 3
ENDIF
Date LFORMAT "(re)started at %Y-%m-%d %T" >>T:SMBFS.log

; modify Break (Process) number for old smbfs-mount
;Break 3 >>T:SMBFS.log
Break 4 >>T:SMBFS.log
;Break 5 >>T:SMBFS.log
Wait 1

; <device-name:>
Run <>NIL: SMBFS DOMAIN=<netgroup> USER=<user> PASSWORD=<password> DEVICE=<device-name:> VOLUME=<name for mos:> CACHE=10000 SERVICE=//<pc-name>/<device-name> >>T:SMBFS.log
Wait 1

Status
Status >>T:SMBFS.log
Wait 10
EndCLI



[ Edited by mk on 2009/6/28 10:44 ]

Thanks MK for the great script.

I was only using 1 smbfs device.

All versions of SMBFS failed.

I'm afraid the a poster on the mosgroup, may know the issue.

He stated that my NAS uses a new samba security standard and that no smbfs will work with these new standards.

He recommended that I use SMB Client, because that will still work.

Does anyone have SMB Client working on MOS?

Thanks for all the help!

Matt

I was able to play with 1.73 and get it more capable, but alas 2 main issues came into play.

Here are 2 issues that I have encountered:
1. Larger files great than 30 megs or so give an 'object in use' error.
2. Smaller files copy over and some are corrupted.

Here is the command I'm using

SMBFS workstation=nas server=192.168.10.12 cache=10000 volume=nas119st service=//qnap119/public

I have tried various SMBFS commands with the same issues.

I emailed the author of SMBFS with the hopes of a resolution, I would guess code modification of SMBFS is the issue now...

I have problems mounting my LanDisk with smbfs... with smbclient it is accessible though. smbfs has always worked fine on MorphOS when mounting Windows shares, but maybe NAS devices don't have that good implementations of samba on them? Google told that my LanDisk has also problems when trying mount it from Vista or Linux too. You get what you pay for in this case I guess...

For smbclient I just tested some really old version from my A1200's backup on my MorphOS :) Seemed to work...