Re: wolf 3d-- bug? -- the culprit?

[nathan@visi.com (Nathan Mates)]

In article <34EBE93E.8C9FBF35@swbell.net>,
Rubywand  <rubywand@swbell.net> wrote:
>     Evidently, when Hierarchic is present in SYSTEM/System.Setup/ and
>loaded-in during system startup, Wolf-3D bombs about 50% of the time
>upon exit.

   Given that I found crash-causing code in the ROM code of my ROM 3
box, I *highly* doubt it's Hierarchic. I have a fix on my ROM 01
system (similar code is in RAM and easier to patch). And, I do have
the Hierarchic init v1.6.1 on my ROM 01 system. Wolfy works great with
Hierarchic and my patch.

   The problem is due to an OS bug (which can be worked around at the
app level), in which critical tools can be incompletely dumped from
RAM under the wrong circumstances. The only reason why it has probably
remained undetected so far is that the conditions to set it off are
quite rare-- an app which has called _SetTSPtr to manually patch out
a toolset.

   Adding or removing inits can mask or expose memory trashing
bugs. You may shift things around to a configuration where critical
sections of ram get zapped, or relatively unused parts are trashed. I
can say definitively that crashes on my system were caused by an OS
bug, not any init, not any addon. And that's proof by code, not proof
by absence of crashes.

Nathan Mates
--
<*> Nathan Mates http://www.visi.com/~nathan/      <*>
# What are the facts? Again and again and again-- what are the _facts_?
# Shun wishful thinking, avoid opinion, care not what the neighbors
# think-- what are the facts, and to how many decimal places? -R.A. Heinlein