Bonsoir!
I submit here a problem i encount to proper run Paradox Dos 4.5 on Lan Server 
with workstations under OS/2. After hours at phone with IBM support ("Paradox 
is really an obligation for you ?") and Borland France ("???"), i do a try 
here. I'm sorry if it's a little long but after weeks of test i've 
experimented a little :-))
Pdox is installed on a LS 3.00.1 server under OS/2 GA 2.11, HPFS-386 on SCSI 
drives. Server is a Dell PowerEdge DX4.  My topogy is EtherNet 10Bt with 100% 
SMC products. Stations are DX33 or DX2/66 with 8 or more memory all running 
OS/2 2.11 GA.
For a short description : Pdox hang or exit with a unexpected condition when 
I work on a table (Edit,Coedit,Query,Restructure, etc ) and decide to add 
another to the workplace. The hang behavior is Pdox send data trought the 
network (i can see the leds on the hubs) and seem to be chashed, but the 
mouse is allready moving, and sometime exit with an unexpected condition : 
lock read error (I've adminitrator right, and HD are as perfects).
It's really strange because only one user (me) access the paradox object on a 
shared ressource on the net (O:\Pdox45 and O:\PDOXDATA). The Pdoxuser.net is 
located in the root of the O:\ drive. 
As the doc say i've indicated 'Other' (8) in the Network type field into 
Nupdate.
After each crash test :-) i manually destoy all .lck and pdoxusers.net before 
continuing.
Sometime Pdox let me play as i like with all the tables from a primary 
station, but when from a second station a try to view a table, a similar hang 
behavior appear, the action on the first station can be completed like end a 
edit session, the Pdox on the first station hang only when i try to quit 
Pdox..
In rare occasions this dangerous game with locks an others stuffs with 
Paradox litteraly trash my Lanserver computer !!!???!! strange for the most 
robust NOS!
I've tried the following tips without any success : 
   Split the differents dirs used by paradox into separate logicals units.
   Change the location of PDOXUSER.NET.
   Change DPMI MEM and DPMI Network buff size into session information.
   Play with the dirty parameters into IBMLAN.INI..server and work stations
   Add the Virtual API Networks supplied with LS 3.0..
   Install PDOX on another server in the domain.
As long i know Pdox4.5 run perfectly from DOS-Lan Requester logged on a Lan 
Server 3.0 server.. But but, i can't try it on my Dos stations with to few 
memory (1Mb :-(), and dont expect to reformat and reinstall OS/2 Workstations 
to DOS! Or only when i would be too tired..
 
I suppose the problem come from the lock sheme done by Lan server with a 
Workstation under OS/2, i've moved some dirty parameters related to some 
obsfucated locking settings into IBMLAN.INI, with same finals hangs..
To have a more pure diagnostic of this problem, and eliminate some part of 
complexity build into Paradox, i've tried the DataPerfect Database (WPC), it 
is reputed to do really soft locking via  Share calls, and don't have any 
settings nor install prog just copy (copy *.*) and run. On a local disk two 
sessions run smothly with nice data refresh and records lock, shared on a 
server disk and runned from two OS/2 WS the data become totally altered when 
one of the users do the a little modification into the Database, and form 2 
or more DOS-Lan Requester all is perfect.
NB : I perfectly handle the manners to run Pdox Dos locally (without Net 
connections) under Os/2, and have already successfully run two sessions on 
the same computer with the '-share' parameter.. so i've skipped all the 
memory settings pb, encountered by all Paradox users under OS/2. I work all 
the days with Paradox in local mode under OS/2.
you can help me if : 
    -run Pdox in a similar configuration, with success 
    -run any DOS based database with Lan Server and OS/2 WS.
    -explain-me brievly how Pdox handle the lock, and how the network type is 
     important to setup into Nupdate.
    -have a little utils capable of doing some simple locks test.
Thanks!
Ciao',
Mathieu 
--- GEcho 1.10+
---------------