>If anyone has both TP 6.00 and the TP 6.01 maintenance release, I
>would be extremely grateful if I could get a diff file for the command
>line compiler, TPC.EXE. I've got TP 6.00 myself and am in the process
>of expanding the builtin assembler, and would like to add the TP 6.01
>bugfixes at the same time. (NB, I'm looking for something a bit more
>more intelligent than a DOS "FC /B TPC601.EXE TPC600.EXE" generated
>file!)

>>If anyone has both TP 6.00 and the TP 6.01 maintenance release, I
>>would be extremely grateful if I could get a diff file for the command
>>line compiler, TPC.EXE. I've got TP 6.00 myself and am in the process
>>of expanding the builtin assembler, and would like to add the TP 6.01
>>bugfixes at the same time. (NB, I'm looking for something a bit more
>>more intelligent than a DOS "FC /B TPC601.EXE TPC600.EXE" generated
>>file!)

> I only have one version of TP 6; but here's a thought.

> If one were to read TPC - presumably about 70 kB - byte-by-byte, and
> write these as Hex, one per line, is it likely that the output of FC on
> a pair of these files would then be of any use?  Or a Diff could be
> found / written in TP 6?

>>If anyone has both TP 6.00 and the TP 6.01 maintenance release, I
>>would be extremely grateful if I could get a diff file for the command
>>line compiler, TPC.EXE. I've got TP 6.00 myself and am in the process
>>of expanding the builtin assembler, and would like to add the TP 6.01
>>bugfixes at the same time. (NB, I'm looking for something a bit more
>>more intelligent than a DOS "FC /B TPC601.EXE TPC600.EXE" generated
>>file!)

>I only have one version of TP 6; but here's a thought.

>>>If anyone has both TP 6.00 and the TP 6.01 maintenance release, I
>>>would be extremely grateful if I could get a diff file for the command
>>>line compiler, TPC.EXE. I've got TP 6.00 myself and am in the process
>>>of expanding the builtin assembler, and would like to add the TP 6.01
>>>bugfixes at the same time. (NB, I'm looking for something a bit more
>>>more intelligent than a DOS "FC /B TPC601.EXE TPC600.EXE" generated
>>>file!)

>> I only have one version of TP 6; but here's a thought.

>> If one were to read TPC - presumably about 70 kB - byte-by-byte, and
>> write these as Hex, one per line, is it likely that the output of FC on
>> a pair of these files would then be of any use?  Or a Diff could be
>> found / written in TP 6?

>The logical thing would be to try to decompress the binary, and then run it
>through a disassembler and try to compare the results.

>> If one were to read TPC - presumably about 70 kB - byte-by-byte, and
>> write these as Hex, one per line, is it likely that the output of FC on
>> a pair of these files would then be of any use?  Or a Diff could be
>> found / written in TP 6?

>The logical thing would be to try to decompress the binary, and then run it
>through a disassembler and try to compare the results.

>>I only have one version of TP 6; but here's a thought.

>Which one, TP 6.00 (1990-10-23, 69214 bytes) or TP 6.01 (????-??-??, ?????
>bytes)

>I'm sure it could be written in TP, or for that matter about every other
>language, but it's a bit of a waste of time when there are already many of
>these programs around...

> >>I only have one version of TP 6; but here's a thought.

> >Which one, TP 6.00 (1990-10-23, 69214 bytes) or TP 6.01 (????-??-??, ?????
> >bytes)

> Fx: starts old computer, pushes in ancient drive (40MB) - the former, TP
> 6.00.

> >I'm sure it could be written in TP, or for that matter about every other
> >language, but it's a bit of a waste of time when there are already many of
> >these programs around...

> We already know how skilled you are as a programmer; unless you are also
> better than me at searching, rewriting could be quicker ...

>>>I only have one version of TP 6; but here's a thought.

>>Which one, TP 6.00 (1990-10-23, 69214 bytes) or TP 6.01 (????-??-??, ?????
>>bytes)

>Fx: starts old computer, pushes in ancient drive (40MB) - the former, TP
>6.00.

>>> JRS:  In article <ed6d5b69.0107160920.124ad...@posting.google.com>, seen
>>> in news:comp.lang.pascal.borland, Robert AH Prins <pr...@bigfoot.com>
>>> wrote at Mon, 16 Jul 2001 10:20:02 :-

>>>> If anyone has both TP 6.00 and the TP 6.01 maintenance release, I
>>>> would be extremely grateful if I could get a diff file for the command
>>>> line compiler, TPC.EXE. I've got TP 6.00 myself and am in the process
>>>> of expanding the builtin assembler, and would like to add the TP 6.01
>>>> bugfixes at the same time. (NB, I'm looking for something a bit more
>>>> more intelligent than a DOS "FC /B TPC601.EXE TPC600.EXE" generated
>>>> file!)

>>> I only have one version of TP 6; but here's a thought.

>>> If one were to read TPC - presumably about 70 kB - byte-by-byte, and
>>> write these as Hex, one per line, is it likely that the output of FC on
>>> a pair of these files would then be of any use?  Or a Diff could be
>>> found / written in TP 6?

>> The logical thing would be to try to decompress the binary, and then run it
>> through a disassembler and try to compare the results.

> I completely agree. I've aready pushed TP 6.00 through IDA and as the
> changes
> between 6.00 & 6.01 are probably fairly minor, doing the same thing with the
> latter would make such a compare a lot easier to understand, however, I do
> not
> have 6.01 so the only legal way to get what I need is a 60.. vs 6.01
> differences file.

> Robert