Subject: | Re: not exact read write error
| Date: | Thu, 24 Aug 2023 08:01:13 +0200
| From: | =?UTF-8?Q?G=c3=bcnter?= <info@NoSpam-mk-news.com>
| Newsgroups: | pnews.paradox-development
|
sometimes the LCK's remain, more often in WIN11 with actual Updates,
most if another Instance of P9 Runtime is open, so we start Runtime ever
with batch to delete LCK's in :PRIV:.
Am 23.08.23 um 22:09 schrieb Steve Green:
> On 08/23/2023 02:11 PM, Kevin Zawicki wrote:
>> It seems like it might be hardware issue, cables, drive, net card, etc.
>> But I think you would see it more and more frequently.
>>
>> Corrupt table? Maybe even the that that repair OK.
>> Can you manually replace the table from scratch?
>
> I'm thinking maybe a bad shared memory spot
>
> all the shared files work fine everywhere else, including that lock
> file.. even on the problem machine, the lock file comes and goes cleanly
>
> the only thing not shared is the priv, and I've moved that, deliberately
> deleted and copied files, etc
>
> it's been doing this for over a week.. I have a work-around, but it's
> not a smart work-around
>
> it's a mystery..
>
>
|