Michael B. Brutman wrote:
I don't think you have a networking problem; I think it is a
hardware problem, or very bad device driver settings.
Could you give any hints on the device driver settings part?
General failure reading drive C is a bad sign. I would make a
new backup of that server
Hi Marcos ,
So where exactly is the file server that's storing the data
file(s) in this scenario? Is it on the doctor's PC, assistant's
PC, or some other location?
In another location.
could you be more specific about
1) where is the database located (not geografically, but what machine)
I remember databases benefitting from a high amount of file handles,
not 'benefit'. for some problems, many handles are needed, otherwise
the database will not work at all.
there is NEVER spurious problems caused by too many handles.
but likely that's already being taken care of by caching
Hi,
On Sat, Jun 16, 2012 at 10:07 AM, Bernd Blaauw bbla...@home.nl wrote:
Op 16-6-2012 15:25, Marcos Favero Florence de Barros schreef:
I downloaded SHARE from Japheth's site, and it turned out to be
the same file I had. Where could I find other versions? I Couldn't
find it by searching the
I'm running FreeDOS, but yes, Linux is a possibility. This
database project started modestly in 2006, but now the Health
Center is relying more and more on it, so I want it to be very
safe.
in that case don't gamble with untested share.exe
Still I would definitely prefer to stay with FreeDOS
Hi,
On Sat, Jun 16, 2012 at 10:55 AM, Tom Ehlert t...@drivesnapshot.de wrote:
Japheth's SHARE is probably the one and only SHARE for FreeDOS. no use
to search the internet
If I remember correctly (but haven't tested), Japheth made some minor
adjustments for FreeDOS (only) to SHARE to work
Tom Ehlert:
could you be more specific about
1) where is the database located (not geografically, but what machine)
2) what's the 'servers' operating system ?
The database is in a Pentium machine running FreeDOS and
MS-Client with a Realtek RTL8139 network adapter card. I'm at
home now, so I
but likely that's already being taken care of by caching
software.
???
UIDE and LBACACHE will only work with INT 13h (local) drives, not network
drives. Caching shouldn't be an issue, at least for the clients -- could be a
problem on the server, though.
According to RBIL, DR/Novell/Caldera
if the answer to 2) is 'FreeDOS' then either SHARE.EXE is not running
or SHARE.EXE is buggy. the latter is quite likely as it was never
really tested against network access.
I think SHARE.COM must be running because the two-computer test
network works perfectly -- as long as the two users
Hi Tom,
This might be irrelevant to the case at hand.
if the answer to 2) is 'FreeDOS' then either SHARE.EXE is not running
or SHARE.EXE is buggy. the latter is quite likely as it was never
really tested against network access.
If you know; does FreeDOS's file locking (ie SHARE) propagate
Bernd Blaauw bbla...@home.nl wrote:
[..] test your setup against an MS-DOS environment instead of
FreeDOS? That could determine (or rule out) some issues.
Tom Ehlert t...@drivesnapshot.de wrote:
try using MSDOS or linux (or even Windows) for the
'server' machine, and see if the problema go
Am 15.06.2012 um 23:26 schrieb Marcos Favero Florence de Barros:
It did work, but it turned out to be very fragile.
As soon as the two people use the database more intensively, the
system crashes -- in most cases, both server and client. If on
the other hand they do things slowly, it works
Pardon the intrusion from my unexperienced self, just a few questions
On Sat, Jun 16, 2012 at 8:59 PM, Ulrich Hansen uhan...@mainz-online.de wrote:
I have read that MS Client with MS DOS works OK for you. But if you want to
stick with Free Software, why not use a real Samba server
13 matches
Mail list logo