yes, TS-DOS is in the same default place, same block #

On Sun, Apr 5, 2020 at 2:49 PM Ken Pettit <[email protected]> wrote:

> Hey Steve,
>
> I downloaded it from the Wiki, but I have a question.  Is the starting
> directory image the same as 4.8, or has that changed also?  VirutalT writes
> both the REX software as well as the starting directory image.
>
> Ken
>
> On 4/5/20 10:51 AM, Stephen Adolph wrote:
>
> sure that would be great.
> Do you need an image?  or did you grab it from the wiki?  use the "full"
> image 32k that includes directories.
> thx
> Steve
>
>
> On Sun, Apr 5, 2020 at 1:23 PM Ken Pettit <[email protected]> wrote:
>
>> Steve,
>>
>> Since I am workingon a VirtualT 1.8 release, should I pull in REX release
>> 258 as the FW loaded for "Create Default Flash" button when choosing REX
>> memory emulation?
>>
>> Ken
>>
>> On 4/4/20 12:14 PM, Stephen Adolph wrote:
>>
>> Yes.  That's what is available now.
>> I can post an upgrade version later so long as you are on 254 now.
>>
>> A lot of people have  not upgraded to rhe new directory format hence I
>> force it with a wipe.
>>
>> On Saturday, April 4, 2020, Josh Malone <[email protected]> wrote:
>>
>>> So, this is also a "wipe and re-load completely" upgrade? Is that
>>> necessary? Seems like the bug is only in REXMGR which is just block 0,
>>> right? Or are the stored RAM images also corrupt and not usable on 258?
>>>
>>> -Josh
>>>
>>> On Sat, Apr 4, 2020 at 8:20 AM Stephen Adolph <[email protected]>
>>> wrote:
>>>
>>>> Peter, thanks for finding this bug. It's been in the code for a long
>>>> time!
>>>> Found the issue.  Injection point for a new .DO file was off by 1 byte.
>>>> Release 258 should fix this.
>>>>
>>>> It is posted at the REX wiki.
>>>>
>>>> Would appreciate people to go and give 258 a try.  It should be the
>>>> same as 254, which was the prior posted release, with this bug fix added.
>>>>
>>>> I will say that I have not tested every model with every possible
>>>> configuration.  So any bug reports would be useful.
>>>>
>>>> thanks
>>>> Steve
>>>>
>>>>>
>>
>

Reply via email to