Another small clarification... I do NOT have special code here to 
analyse LCK-files. I found some code to analyse PDOXUSRS.TRA files 
(users starting/ending/etc), and to match up the session starts/ends, 
etc. Different animal!

   - Mike


On 27/05/2017 13:43, Steven Green wrote:
> yeah, it's actually pdoxwin running, but that shouldn't matter.. I 
> figured that changing the file with notepad would break it.. the 
> "dirlock" result was a surprise.. it's definitely not a dirlock :-)
> 
> this stupid old laptop, which is about to be replaced, thinks there's an 
> SD card in F:, and I can't delete, uninstall, etc.. that's why I tried 
> changing it.. I'll send a copy of the files to your email.. if you can 
> change F to C, or run them as F on your machine, that would be great
> 
> -- 
> 
> Steven Green
> Myrtle Beach, South Carolina, USA
> 
> http://www.OasisTradingPost.com
> 
> Collectibles and Memorabilia
> Vintage Lego Sets and Parts
> - and Paradox support, too
> 
> "Michael Kennedy"  wrote in message 
> news:5928b07b$1@pnews.thedbcommunity.com...
> 
> Steve,
> 
> It might take me a few shots to recall some useful details...
> 
> Probably irrelevant, but are you using PDoxDOS or some version of
> PDoxWin? Or both  ;-)
> 
> On 26/05/2017 21:01, Steven Green wrote:
>> client has a growing lock file, on an on-going basis.. the reasons are 
>> understandable and for the moment, unavoidable.. when everyone gets 
>> out of paradox, it goes away, so it's not damaged
> 
> This was a very major issue, some decades ago. And now I don't recall
> the causes/solutions. Perhaps Locks are being placed, but not released.
> 
>> all the machines are 64-bit, so lockdump and netdump will NOT run on 
>> their machines (16 bit)
>>
>> copied both to my system.. they seem to be making a good net file, I 
>> can always read it with netdump just fine, it's always 13030 bytes, 
>> the data matches what the app says, etc
> 
> Sounds perfect.
> 
>> here's the issue, Mike :-)  long story, but I can't use the same drive 
>> letter on my machine.. at the command prompt, lockdump throws an 
>> Abort/Retry/Fail cuz it can't find the net file on the correct drive.. 
>> so I edit the lock file, substitute a different drive letter, and save 
>> the file.. then lockdump says "This is a Directory Lock"
> 
> Maybe try SUBST to assign the required letter - if that letter is free.
> 
> When you change the Drive-letter, make sure you use a "hex" editor - a
> standard editor would likely mess up a hex-editing session. Also, the
> drive-letter might be held in multiple places inside a hex file, perhaps
> as a letter a-z, A-Z, and/or as a number (0=A, or 1=A, or 0=C, or 1=C, 
> etc).
> 
> When investigating this issue way-back-when, I wrote some code to
> analyse the lock-files. The only detail I recall now is that the code
> searched for pairs (Lock and Unlock) within the file, and then
> highlighted the unmatched/unreleased locks/entries. I'm sure I have that
> code somewhere, if it might help (I might even have previously sent it
> to you/others!).
> 
> Or, if you want, send me the Lockfile, and I'll check if I can access it
> here.
> 
> The Directory-Lock message seems wrong - that was/is an option to place
> a lock on a Directory, and thereby avoid having to place/release all the
> individual record/block locks thereafter.
> 
>    - Mike
> 
> ---
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus
>