I periodically, but rarely, see a "WriteFile" error=38 show up in my log file. It occurred most recently while a user was playing a DOS door (Operation Overkill). Unfortunately it crashed the game in progress.
Any way to know what's causing this?
More details of the error could be helpful (e.g. check the message in your data/error.log and report back?).
Error=38 is ENAMETOOLONG, so that seems unlikely to be the actual error code. WinError value would be more helpful in this case.
Re: !VDD WriteFile failure (Error=38)
By: Digital Man to Codefenix on Mon Aug 24 2020 03:31 pm
More details of the error could be helpful (e.g. check the message in your data/error.log and report back?).
Error=38 is ENAMETOOLONG, so that seems unlikely to be the actual error code. WinError value would be more helpful in this case.
Checked data/error.log. Indeed shows Error=38. Hopefully the extra detail is enough.
Sun Aug 23 21:56:09 2020 conchaos.synchro.net
term Node 1 <*user*> !VDD WriteFile(0x3a08, 2) FAILURE (Error=38)
edit the file exec/sbbsecho.ini and set the single line
"Debug=true". Then run a Windows debug viewer (like https://docs.microsoft.com/en-us/sysinternals/downloads/debugview)
Re: !VDD WriteFile failure (Error=38)
By: Digital Man to Codefenix on Tue Aug 25 2020 01:40 pm
edit the file exec/sbbsecho.ini and set the single line
"Debug=true". Then run a Windows debug viewer (like https://docs.microsoft.com/en-us/sysinternals/downloads/debugview)
I assume you meant exec/sbbsexec.ini, so that's the file I modified :)
Debugger is running. Hopefully I capture something interesting the next time a crash happens.
Sysop: | Rempala |
---|---|
Location: | Richlands, NC |
Users: | 113 |
Nodes: | 10 (0 / 10) |
Uptime: | 127:32:10 |
Calls: | 374 |
Files: | 6 |
Messages: | 111,243 |