: >I have a very Strange Problem. It seems as though, when a user shells
: >to dos using the Big Dos version, while locked in a record, that alot of
: >strange things can happen.
: >Upon returning from the dos shell, the novell server still shows the
: >record as locked. Also everyone who is using paradox at the moment will
: >also be locked out of whatever they were doing.
: >I have about 20 stations running a paradox program in a telemarketing
: >environment. One of the tasks they perfrom requires running another
: >program from dos. For the most part it works fine. But every now and then
: >it will lock up everyone who is currently using the program.
: >Help, nobody has been able to figure this one out yet.
: >btw- we are using novell 3.11 and 3.12 servers in a multi server environment
: >with about 10 servers total. All stations running under dos.
: Are you loading any TSR's while shelled out of Paradox. A TSR will load
: into memory where ever it can squeeze in. Paradox parses to memory (when
: shelling) in a specific order. If this order is interrupted, this could
: cause instability. Also, how much base memory is available once Paradox is
: loaded? Are you using the command line parameters -norealheap? This will
: tell Paradox to give back some of the base memory once it is loaded
: (Actually, it re-allocates some base memory for DOS shell functions).
This is absolutely correct. Most people do not realize that the DOS
PRINT command is a TSR! I've solved a network problem once by replacing
the PRINT command with a dummy batch file. Stations are losing
connections occasionally and the substitution works great.
| Pretty good Paradox for Windows Programmer |
| Self-proclaimed Treknologist |
| Editor XCOM: Unofficial Strategy Guide http://userwww.sfsu.edu/~kschang |