On Wed, 25 Dec 2013 23:49:25 UTC, Marcel M�ller
Post by Marcel MüllerPost by Doug BissettThe latest SAMBA seems to have fixed most of the problems that older
versions had, although I think that EAs are restricted to 32K, while
OS/2 wil use 64K EAs. The only place where EAs are essential is for
the desktop, I have always found that the rest of them will be
recreated, if the program thinks they are needed.
REXX crashes on large scripts when EAs are restricted to less than 64k.
Without any EAs REXX is only a bit slower because it cannot store the
results from the compiler. But without EAs the desktop cannot store
folder settings and it does not remember file types (.TYPE EA).
Furthermore thumbnails of images are recreated all the time, incredibly
slow over the network. So one usually don't want to use an OS/2 client
without EAs.
(Using OS/2 as server for other OS the story is different.)
Are you actually using a remote computer to store the OS/2 desktop? I
would think that would be a bit risky. I never considered using REXX
over the network either. I do use pictures and movies over the
network, with no trouble. The icons don't show the picture, but
performance is not an issue. I do have a 1 Gbs network. I haven't
tried that using a virtual machine, but it should not be any
different, as long as the network runs at 1 Gbs, and the machine is
capable of doing the necessary processing.
Post by Marcel MüllerPost by Doug BissettThe client needs either netdrive, or EVFS (look for EVFS.IFS), which
is part of eCS (perhaps not the ancient version that you have, I don't
remember).
No EVFS here. Never heard of that before.
I don't remember which version of eCS first had that.
Post by Marcel MüllerPost by Doug BissettThe client is also completely separate from the SAMBA
server, and it can be used at the same time as the old NETBIOS over
TCP/IP.
The /client/ can safely run in parallel to IBM Peer. But the server
cannot run this way, because only one process can listen on the SMB ports.
Post by Doug BissettYou can also run SAMBA server, along side of PEER, as long as you use
NETBIOS, and not NETBIOS over TCP/IP.
NETBIOS is dead. Almost no one can connect to a NETBIOS server anymore.
No Linux, no recent Win.
Post by Doug BissettPost by Marcel MüllerSo even if the server most likely does not share this problems I need to
disable IBM Peer to get the samba server up. So I need the client too to
use the server.
There is a way to use PEER with a SAMBA server (not on the same
machine), but I don't recommend it.
What do you mean with 'there is a way'? I am running IBM Peer against
Samba 3.6.6 (Debian) all the time. It works just fine. Only Thunderbird
seems to dislike this combination since version 3.something. If the
profile directory is on a Samba share TB is incredibly slow due to heavy
network traffic.
Post by Doug BissettPost by Marcel MüllerPost by Doug BissettYou may need other prereqs, if your system is not up to date.
Well, I should have mentioned that is is eCS 1.05 - not that up to date.
But beyond that recent libraries like libc065 should be in place.
That is the update that I mean. You also need the freely available
stuff that is listed near the top of the SAMBA SVN page.
I think this should be no serious problem. Netdrive is the weak link and
EVFS seem not to be an option for me. I guess it requires an eCS 2 license.
Post by Doug BissettI never got Win7 Home to log onto the old PEER network, even after
doing a LOT of messing around. I think I got Win 7 PRO to do it, at
I have only the pro version.
Post by Doug Bissettone point, but that didn't solve the problem with Win 7 Home, or
transfering files larger than 2 GB. SAMBA is the easy way to do it.
The 2GB limit is final to IBM Peer. But this is no big deal. What should
eCS do with larger files. The only thing I can think of is to play a
large video. But all of my eCS machines are VMs on a headless server.
And playing large videos in a VM over RDP is an amazingly bad idea.
Recently, I have been using ZIP/UNZIP for my backups. I use the
versions that do support files larger than 2 GB. I actually use RSync
to transfer those files to other machines, but I can also do it with
SAMBA, and Peter Moylan's FTP program. Even with a 1Gbs network, it
takes a while to transfer those large files.
Post by Marcel MüllerPost by Doug BissettThere is also the old NETBEUI support for windows. I have heard that
it can be installed on Win 7, but I never tried it.
In our company they failed to reliably connect from a W2k3 Server to an
old DOS check-out over NETBIOS with this old driver. They ended up by
running an NT4 VM as bridge on the server because the POS software
needed too much DOS memory to run in parallel with an IP stack. I would
wonder if W2k8 aka Win7 is reliable with this driver.
Post by Doug BissettI am pretty sure that it is still there. Of course, you would need to
install NETBIOS on your OS/2 machines for that to work (you can have
both NETBIOS, and NETBIOS over TCP/IP), and you may have problems with
other devices (routers, or wireless) not passing netbios packets.
I won't experiment with NETBIOS anymore. I disabled it more than 10
years ago for several good reasons.
Marcel
Maybe somebody else can suggest something. My only suggestion is to
get a later version of eCS, with support for the SAMBA client, or get
netdrive so you can use the client that way. Win7, and 8, are not user
friendly when it comes to communicating with other operating systems
(they even cause troubles for older versions of windows). The old OS/2
networking is obsolete, and the best that we have now is SAMBA. If
that fails to do the job, you are left high and dry, mostly thanks to
Microsoft, but partly because OS/2 uses EAs that are not entirely
compatible with other operating systems, so they are not fully
supported by the tools (SAMBA) that are ported from them.
--
From the eComStation of Doug Bissett
dougb007 at telus dot net
(Please make the obvious changes, to e-mail me)