Re: Strange file (2)

On Feb 23, 1:01*am, drop dead google <foodman...@gmail.com> wrote:
> I tried changing the record size to 256 as you suggested and get
> exactly
> the same thing as before.
>
> The maximum length of data strung into SPULE-PA is 59 characters.
>
> The program, including all copies, SP2 stuff, etc., is 7,628 lines so
> I don't see any point in posting the whole thing. Furthermore, since
> I am probably the only person still using the 16-bit compiler and

Then the compiler is _MicroSoft_ Version 5, which is a completely
different compiler than what you previously said which was "Micro-
Focus version 5".

MicroSoft 5 is equivalent to Microfocus 3.1 or so and is 16bit.

> an ancient version of SP2, it would not be possible to duplicate
> my environment.

> Satements referencing SPULE and its record are presumably the
> the only ones which can have some affect on the file. That
> is why I posted only the relevant lines. I had not posted the
> code in the original post since I saw no point because of its
> utter simplicity. The data for the posted code is:
>
> *BB * * *02/11/12 * 11:39 * 11:56 * * :17 * *5.00 **1.42
>
> You mis-quoted me when you said "It wasn't about how or whether _you_
> could
> diagnose the problem, you had already told us that you could not."

I didn't quote you at all. It wasn't a quote, that would have been set
in quotation marks, it was a summary of your messages.

> I did not say that I "could not" solve the problem in my original post
> nor would I have said that. *I said "Any ideas anyone?"

Whether you said that you could not is irrelevant, you could not and
have not.

But the comment was not about you not diagnosing, it was expecting us
to diagnose based on a lack of adequate data, and even incorrect
information.


> Obviously there is something wrong. It may even be a compiler or
> linker
> bug which only arises in a specific set of circumstances.
>
> I wrote a tiny program containing the posted code and it works fine.

> There is must be something else being executed which is causing the
> problem.
> I can remove chunks of code in an attempt to narrow the problem down.

It is possible that it is the SP2. Check that the generated code
included is a correct match for the panel file being used. Also check
that the panel file is not larger than 1 megabyte. In fact rebuild the
panel file to compact it, if it gets too large then strange things
happen.

Turn on bounds checking to see if it is a corruption from an invalid
index value.