| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | message area woes |
Whilst masticating on , Mike Tripp (1:382/61) wrote to Robert Wolfe: AH>>> extension .~~~ and thus can't be read by my reader, by AH>>> Bluewave, or online. What could be causing the problem, and how AH>>> can it be fixed? Using latest OS/2 versions of Max and Squish AH>>> since they came out, and haven't changed anything. RW>> I am assuming that this means that the files were left open by RW>> some process that died unexpectedly. MT> I'll second that motion. I have caught glimpses of them from MT> another node on the LAN during toss sessions, but Squish works so MT> fast that they're gone again before you can DIR again. If MT> they're being stranded, it would indicate to me also that the MT> Squish EXE is terminating abnormally (process manually killed or MT> issue with a hardware resource - disk/memory error). MT> Logs should contain a clue...either real errors logged MT> (doubtful), or "Begin," statements without matching "End." MT> statements (my bet). I'll check the logs again next time it happens. *adh* --- Msged/2 6.0.1* Origin: tncbbs.no-ip.com - Try the CROSSFIRE echo - all welcome (1:261/1000) SEEN-BY: 3/0 633/267 640/954 712/0 313 550 620 848 @PATH: 261/1000 10/3 140/1 138/146 392 123/500 261/38 712/848 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.