Hi Roy,

 RJT> I ended up moving a whole mess of the bbs files over there,  and can't 
 RJT> get the share that I stuck in smb.conf to let me hook 
 RJT> into those files from the OS/2 end of things.  The 
 RJT> "sharing and connecting" utility will,  when I tell it 
 RJT> I want to "create a new share",  show me that machine 
 RJT> and the shares that I have defined,  as well as a 
 RJT> bunch of otherwise unused drive letters.  But it 
 RJT> complains when I select the new one and an unused 
 RJT> letter,  complaining that it can't find the resource,  
 RJT> or something to that effect.

From what you have described it sounds like your problems relate almost
totally to permissions on the Linux box. I dont know much about SAMBA but I
would start looking at how SMB Client permissions (OS/2 Peer, W95, etc) are
mapped into the Linux permissions. 

 RJT> Would perhaps manually editing the configs be a way past this?  

As far as OS/2 Peer is concerned, absolutely not! The Files in question allow
you to resolve operational Networking issues that relate to communications
parameters, not User access parameters. All your problems sound almost 100%
like permissions on the Server platform.

I have NEVER needed to manually edit any OS/2 Peer configuration file other
than to configure an OS/2 Client to exist in multiple DOMAINS at the same
time, and thats about the easiest change I can think of. All permission
problems I ran into have been resolved by altering the OS/2 Peer User profile
on the SMB Server that presented the error. With PEER, the SERVER is just
about the only component that determines what resources a Client can access.

If you want to manually edit the MPTS/SMB control files then you FIRST need to 
pick up the EXTENSIVE documentation from an IBM Web site, otherwise you will
never know what each of the bit values does. NONE of this is documented with
OPS/2 Peer, you need access to the developers areas to find out what allthe
values are for.

My advise is DONT play with these, from the sounds of it none of your current
problems will be solved by fiddling in this area. You will end up having to
re-install OS/2 Peer just to get things working again.

Cheers........pk.


--- Maximus/2 3.01