| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | SOM.IR corruption |
Will ..
WH> WTF! Just looked at config.sys and what a mess on the set somir= line
WH> - how the heck is this thing running, anyway? Anyway, reset it and
WH> I'll see what happens - maybe that where some of the funnies are coming
WH> from lately.
Oh, if what I've found is correct, it gets REAL worse!
Check your Email. I've copied off another of my tons of log lines time
trace analysis deals which show what I think is very suspicious evidence
that the SOM.IR files are getting corrupted in a very different way than we
thought.
Again, what I'm finding is that Z! ain't responsible at all for the
lockups. In fact the file and disk corruption is taking place, per my log
showings, even HOURS before the final lock up hits. After the WPS crashes
and the system clock freezes on the WPS, the box is actually running in the
background for a long time yet mashing even more damage here and there. Z!
and a constant bashing of TCP/IP data simply exacerbates the final product
of the brewer's art!
I'd like for you to think about what I posted as well as the other parties
involved before we go ranting and raving here. I could be very wrong.
Thanks.
--> Sleep well; OS/2's still awake! ;)
Mike {at} 1:117/3001
--- Maximus/2 3.01
* Origin: Ziplog Public Port (1:117/3001)SEEN-BY: 633/267 270 @PATH: 117/3001 100 106/1 379/1 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™.