On Tue, 29 Feb 2000 17:18:31 -0400, L.D. Best wrote:
> It made no sense, and it makes even less sense now.
> I checked everything, including files & buffers. Files were set to 59
> and buffers to 17. But InSight wouldn't work.
> If you were a windoze victim, what I tell you next would probably seem
> sensible. But as a DOS user, you ain't gonna believe this one!
> ---
> Today I solved the problem, and the solution makes even less sense
> than the problem did in the first place. I went back to using the
> called batch file for putting PATH statement in environment ...
> BUT HERE'S THE KICKER: InSight didn't work until I put that call back
> into autoexec at *exactly* the same line where I'd removed it!!!
> ---
> If anyone can figure out WHY this should happen, please let all of us in
> on the secret ... <sigh>
Hi LD;
This isn't the secret but it MAY be part of it.
We have all occasionally had problems with software that SEEMED to be
incompatible with some part of our regular setup.
Like right now this composition window is behaving in a TOTALLY
irrational manner. It wouldn't show the line I had previously typed so
I scrolled up and then the NEXT line disappeared. Right now, the two
sentences previously typed have become vaporware - I can't see anthing
I've typed after the word setup.
Now, it's all back.
See, we get used to working with crap. }-((
That may seem to be a bit of a sidetrack, and it really WASN'T what
I was going to say, but it came along at a perfect time to serve as
an example. <g>
To continue, SHIT ! Now I have 2 cursors !!!
I don't think I can complete this thought with this %$%@X@ composer.
GRRRRRRR! Software sometimes does not work because of a bug only seen
when it tries to execute a particular instruction at a particular point
in memory - like a page boundary, or where a segment wrap might take
place. Maybe, to work right at that point the instruction needs to be
word aligned. The chances of loading the software into a bug activating
position are pretty small - say one chance in 65k if there is only one
bug. N chances if there are N similar bugs.
Hmm. I can read most of that.
I had one case where I couldn't make something run unless I loaded
another copy of command before it, and other cases when loading several
copies would crash it - solely due to the load point - not the amount
of available memory.
I'm talking about commercial software here - not something I wrote.
The likelihood that the particular problem you saw was due to Insight
is very high, but not 100%. The problem could very well be in Qemm !!
Try this. Restore your autoexec to the NON working condition and insert
a COMMAND statement (with environment spec) BEFORE the problem line.
- Clarence Verge
- Using Arachne 1.50b2 for a change.
