Hey Danny!

Apr 02 12:13 07, Danny Ceppa wrote to Maurice Kinal:

 DC> The problem I'm running into with the linux based ones is that they 
 DC> don't re-create NTFS files well.

Last time I checked (a few years ago) that was only 4.0 and I understand
that 4.5 is current these days.  You're probably right though.  If you pick
a common file system for any shared partitions it won't be an issue. 
However I wouldn't allocate more then 512M for fat16 but that will work for
all.  fat32 shouldn't be an issue and I believe the limit is 36G.  Depends
entirely on what you plan to provide to your network no matter what OS.

 DC> They bring them back as 
 DC> disjointed fragments.  That could be ok with a text file, but it 
 DC> doesn't work for a damn on exe's and jpegs.  

See above.  exe's will never work on a linux system but then again they
never have to.  Right?  As long as they can work on the targetted systems
this should never be an issue.  The only real issue is that the shared
partitions understand and can all read (perhaps some write) to the shared
filesystem.  In your particular case if the linux box is to run (read and
write) the shared filesystem then fat32 partitions would be the way to go. 
Even OS/2 can read and write to those, perhaps even run any exe's there. 
Linux only needs to mount and share them if it is to be used to network
those partitions.

Make sense?  You'll probably need dosfsutils (I think that is what it is
called) to format those partitions from the linux box and either fat16 or
fat32 partitions will work with dosfsutils.  I'll be happy to check for
your particular distribution if you want but I am already sure it is out
there if you are in need.  A quick check of either /sbin (perhaps
/usr/sbin) should tell the tale by looking for an app called 'mkdosfs'.

Life is good,
Maurice

--- Msged/LNX 6.2.0