On 6/11/2011 2:18 AM, Doug Bissett wrote:
eCS's Samba server package installed fairly easily as the page claimed
(
http://svn.netlabs.org/samba). After slightly further editing of
config.sys (to put in two LIBPATH spots where the Samba packge is
installed) and rebooting I got connection!
This is confirmed for all three Windows computers: XP SP3, Vista laptop
and the new 64 bit Windows 7 I'm working up to replace the XP.
Connecting to the OS/2 disks/volumes is 100%. I test copied a folder
with over 2000 files occupying about 25 MB and it came across in a jiff.
A big accolade from me to those who put that all together, in WPI form
as well, which made installation indeed as simple as in Windows or the
Mac. A WPS configuration folder is created and one can complete the
installation and make further adjustments with GUI "widgets". The
installation gives one the option of creating a new Samba configuration
from scratch or porting over one's IBM LAN Manager settings. I chose
the latter.
I'll be thinking and suggesting how the above page may be improved
although in my case I fell over badly due to rushing and being mentally
scattered: trying to do multiple things, not computer related where the
computer system can't be off-line for long...
There is one problem to be solved: I can't print to the printers which
are Samba shared. When I do a test print you can see a brief Samba
message popup saying various things are happening but no job appears in
the OS/2 printer window; the printer light blinks hopefully but nothing
prints.
Because of thi I might still have to go back to the IBM LAN manager for
a while longer. That's not hard to do - just copy the IBM LAN version
of config.sys to be the active one and the same with IBMCOM\protocol.ini
and reboot.