Hi Todd,

running SMBD under INETD or the SMB Monitor job is now
pretty much the same from the user's perspective. The very
first versions did not need PM capability under the INETD
because INETD handled the BSD socket bind() to port 139.

The more recent versions need PM also for validating user
ID and password (the setuid() stuff was not available in
the early versions) so PM is also needed under INETD now.

Regarding the PFE or DOS EDIT problems I cannot provide a
quick answer without more details but usually increasing
the debug level on smb.conf gives helpful messages in the
log.smb file.

With Windows Write for example I found a problem related
to temporary file names that have illegal characters for
the HFS on MPE (example ~WRIxxxx.TMP which has a ~).

I still have not found the time to add some filename mapping
to overcome this, but it is on my TODO list (just need time).

Cheers, Lars.