Subject: | Re: not exact read write error
| Date: | Wed, 23 Aug 2023 13:45:29 -0400
| From: | Steve Green <steve@oasistradingpost.com>
| Newsgroups: | pnews.paradox-development
|
On 08/23/2023 10:48 AM, Mark Bannister wrote:
> On 8/23/2023 9:27 AM, Steve Green wrote:
>> haven't deleted the net file, I can try that on Sunday morning when I
>> have a clean system
>>
>> I've seen the error before, and it leans towards "hardware issue", but
>> the current scenario has the same thing running all day on the same
>> hardware and same OS.. we even replaced the drive
>>
>
> If hardware related maybe some jobs running at night stressing hardware?
same jobs, no matter where they run, and they run way faster on this
particular dial-in
my question, is the read-write error on the lock file itself getting
written to, or is the lock file telling us the problem is locking or
copying one of the files? can't manually reproduce this anywhere outside
of those two places in the code.. but those two places in the code get
hit on all day long, in a variety of contexts, including the exact same
proc calling the exact same files, in other processes
it's why they call this thing "paradox" :-)
--
Steven Green
Myrtle Beach, South Carolina USA
http://www.OasisTradingPost.com
Collectibles and Memorabilia
Vintage Lego Sets and Parts
- and Paradox support, too
|