"Wolfgang Ehrhardt"
wrote in message news:42d7f03e.683835@news.individual.net...
> On Fri, 15 Jul 2005 09:10:54 -0400, "Dave R." dot com> wrote:
>
>>I've become the maintainer for a large BP7 code base where I work.
>>The
>>compiler has been patched for the RT 200 bug, but I don't know what
>>method was used and I can't find anyone still with the company that
>>knows. I'd like to know since I see that there were several methods,
>>but not all of them are immune to the problem, they only delay the
>>problem to a faster processor speed. Is there any (reasonably) easy
>>way
>>to determine?
>
> The compiler needs no patch for RT200 (as far as I know). I guess you
> talk about the CRT unit and the *.tpl. If you are using BP7 you should
> have the (patched) source code.
>
> So what exactly is your problem?
>
> Do you have lost the patched source of crt.asm?
>
> Or do you have a question about the patch in the source? If yes, post
> the relevant code snippet for getting help.
Sorry I wasn't clear - I was lumping the run-time library and compiler
together but of course it is the CRT unit that was patched to resolve
the RT200 issue. I don't have a patched crt.asm (or any crt.asm for that
matter). The previous developer said words to the effect of "Install
these (BP7) disks, then copy these files into your BIN directory to fix
some problems we've had."
So I guess my problem is two part:
1. I'm concerned after reading some of the articles and posts about the
RT200 bug that once processors get fast enough we will run into it (or
similar) again if we didn't apply the right patch, and I want to be able
to determine what patch was applied.
2. I don't have the patched source.
Any help would be appreciated.
Regards,
Dave
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
