* Original message posted in: OS2LAN.
* Crossposted in: UNIX.
Hello All!
For those who have been generously participating in the ongoing discussion 
with me about the inability of OS/2 to reliably write to an SCO VisionFS 
share, I have some additional information that I'm amazed I didn't notice in 
the first place.
All I can say is I must have been so shocked that it -didn't- work, that I 
failed to note the unique circumstances under which it did not work.
Preliminary note: I was able to replicate this error on three different OS/2 
workstations all talking to the same SCO VisionFS system, but using different 
shares on different accounts. It's also worth noting that I've not tried 
these tests on a -different- SCO server, but will have the opportunity to try 
it one last time at work tomorrow using a different OS/2 -and- SCO system.
Anyway... Quite simply: OS/2 cannot write a file of < 4096 bytes to the SCO 
VisionFS share. All files > 4096 bytes write perfectly well -- well not quite 
perfectly well.
With significantly less frequency, but always the same files, some files 
written are 2k-4k smaller than the original. I've not yet been able to 
determine if this is the same 2k-4k every time, as I've not dug that deep, 
but once a file 'fails', it fails every time the file is 'written' to the SCO 
server.
However, I'm fairly confident that this 2k-4k loss issue is directly related 
to the inability to write -any- file < 4k.
So.... Anybody have any ideas? thoughts? (Other than the aforementioned 
NFS/SMB solutions? -- after all, I'm trying to fix -THIS- configuration -- 
not build a new one. )
Can anybody point me in the direction of an Administrator's Troubleshooting 
Guide to NetBIOS implementations? Perhaps something that thoroughly documents 
the IBMLAN.INI files and/or whatever equivalent configurations might exist on 
the Unix side.
Also note (for reinforcement) that I -cannot- duplicate this problem from a 
Windows95 client to the same SCO server, therefore I am fairly confident that 
the problem is an -OS/2 Client- problem and not an SCO VisionFS problem.
Anyways... here I sit.. awaiting some new ideas. :)
--- 
---------------