I haven't tried the "standalone" job method, but at least under INETD, you
need to use the HFS name in lieu of the MPE name to get it to work
(ie. use /SYS/SAMBA/SMBD instead of SMBD.SAMBA.SYS).

A couple other quick things I've noticed (I'm trying to get a better
list of "oddities" together):
1.  SMBSTATUS also need PM capability
2.  There's a "magic" filesize around 30K where copying files in
either direction breaks down.  Over this amount you get disconnects
or outright failures.  I'm still trying to get all of the permutations of
this one figured out.
3.  Copying MPE files with record sizes of 1-3 bytes (regardless of the
number of records) causes errors.

I've been using Windows NT 4.0 sp2 for these tests.  I haven't verified
what protocol I connected to the samba daemon with either.  I have noticed
that Windows 95 acts quite differently in prior testing so who knows....  When
I get a better list together, I'll post some results.

Regards,
Michael L Gueterman
Easy Does It Technologies
email: [log in to unmask]
http://www.editcorp.com
voice: (509) 943-5108
fax:   (509) 946-1170
--


----------
From:  [log in to unmask][SMTP:[log in to unmask]]
Sent:  Thursday, January 16, 1997 10:54 AM
To:  [log in to unmask]
Subject:  Re: [HP3000-L] Testing SAMBA - Problems

Hi Mark,

are there any clues in the /usr/local/samba/var/log.smb logfile?

Lars...