Re: samba

In message <djgr7j$35f$1@xxxxxxxxxxxxxxxxxxx>
"Saxon Seed" <saxon@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

> My SA RISCPC 4.02 was connecting to the network using both Samba and
> Omniclient. Omniclient still works but Samba only runs for 10 seconds before
> the error message - Internal error, trap while in trap handler. Internal
> error. Abort on data transfer at &03813574, pc=A19FF400: registers at
> 0012A254.
> What does all this mean? But more importantly, how can I get Samba working
> again? Advice needed, preferably simple.
>
> Saxon Seed
>
>

I assume here you are talking about the Samba Server called smbserve -
because I don't know of a client called Samba. (Clients are Lanman98 and
LanmanFS). If I'm wrong, ignore what follows.

When I first tried smbserve I got that sort of instability. A while later I
tried fiddling with it, and got it fairly stable. I think the setting that
made the difference was either related to protocol or nameserver. My stable
setup has password level 0, debug level 1, socket TX and RX buf size 16384,
all 4 options buttons ticked, protocol Lanman2.

When I used it to copy my 30GB disc to a backup I did hit a number of problems:

If a directory had more than about 195 objects in it, the server froze up.

If a directory had files whose names were the same with different
extensions, and had the same RISC OS type, duplicate file names would be
created. For example:
jpeg image called image/jpg
jpeg image called image
In each case smbserve strips off the extension, and adds an extension based
on the filetype, thus producing two image.jpg files.

It seems to have a 10 character filename limit, truncating the name at that
point.

I'm trying to remember which copying method it was that failed with files
over 250MBytes. ShareFS does work with these, and I think LanMan98 does.
That suggests another limit in smbserve, but it could be something else.

--
Alan Adams
alan.adams@xxxxxxxxxxxxxxxxxxxxxxxxxxx
http://www.nckc.org.uk/
.

Quantcast