Glad to help out. On Fri, 6 Jan 2023 at 15:44, Stephen Adolph <[email protected]> wrote:
> I did, thanks for pointing out it needed more info and to change 258 to > 260. > > On Fri, Jan 6, 2023 at 6:24 PM Peter Vollan <[email protected]> wrote: > >> You just changed the wiki, didn't you? Well I don't get that checksum so >> I should do the upgrade. >> >> >> On Fri, 6 Jan 2023 at 15:21, Stephen Adolph <[email protected]> wrote: >> >>> revision is the same as build number. basically, as I fix bugs, >>> revision moves forward. >>> I don't recall if, in the old software for REX Classic, which I no >>> longer provide any updates for, if revision is something you can find out >>> directly. >>> >>> You would want to look at the checksum. >>> >>> 1) check information on REX by pressing I - should give you checksum on >>> the top 16k of the REX firmware >>> >>> 2) Compare with these values. if different, upgrade. >>> M100 = DF79 >>> T200 = 18BA >>> NEC = 3B3E >>> >>> On Fri, Jan 6, 2023 at 5:46 PM Peter Vollan <[email protected]> >>> wrote: >>> >>>> What is this about revision 258 or 260? Is there a way to find out what >>>> revision I am on or if I need this upgrade? >>>> >>>> >>>> On Fri, 6 Jan 2023 at 13:18, Stephen Adolph <[email protected]> >>>> wrote: >>>> >>>>> the last load I made for REX classic is here: >>>>> https://bitchin100.com/wiki/index.php?title=REX_Release_4.9 >>>>> >>>>> It isn't perfect but it is the least buggy version of REX classic >>>>> firmware. >>>>> 4.8 is certainly not a great load to be using. I suggest a complete >>>>> rebuild. >>>>> >>>>> Steve >>>>> >>>>> On Fri, Jan 6, 2023 at 4:15 PM Stephen Adolph <[email protected]> >>>>> wrote: >>>>> >>>>>> REXCPM has no firmware per se. The CPLD is programmed but rexcpm is >>>>>>> based on RAM so you have to load the REX software to initialize it. >>>>>> >>>>>> >>>>>>> Details are at the REX wiki. >>>>>> >>>>>> >>>>>> >>>>>>> https://bitchin100.com/wiki/index.php?title=REXCPM >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>> >>>>>>> On Friday, January 6, 2023, Hiraghm <[email protected]> wrote: >>>>>> >>>>>> So I have 2 model 100s, one I got as a backup that has a small >>>>>>> scratch on the screen. >>>>>> >>>>>> >>>>>>> The backup I tried recapping last weekend... and thought I'd killed >>>>>>> it. >>>>>> >>>>>> >>>>>>> I just got it working again (pulled the mb and scrubbed the back >>>>>>> with isopropyl alcohol using a toothbrush). >>>>>> >>>>>> >>>>>>> So I had had a classic REX in my main M100, and I pulled it to >>>>>>> install in my backup. >>>>>> >>>>>> >>>>>>> iirc, I had v 4.8 (.48?) , and I believe 4.9 is the latest. Can >>>>>>> anyone share how to flash the new version to the rom? >>>>>> >>>>>> >>>>>>> >>>>>>> If I successfully recap the main M100, I intend installing the >>>>>>> REXCP/M in it. Would I flash the lastest firmware the same way? If now, >>>>>>> how >>>>>>> should I go about doing that? >>>>>> >>>>>> >>>>>>> >>>>>>> Also, is it possible to replace the main rom with a rom image on the >>>>>>> REX, fixing the Y2K? I'd like to have Ultimate ROM 2, and someday I'd >>>>>>> like >>>>>>> to create a custom ROM to replace the BASIC interpreter with Small-C or >>>>>>> maybe a primitive Python-alike; or maybe just an assembler, if nothing >>>>>>> else. That way I could write compilable (or assemble-able) programs for >>>>>>> it, >>>>>>> on it. >>>>>> >>>>>> >>>>>>> >>>>>>> Also also, what's the other rom socket for? I've forgotten :( >>>>>> >>>>>> >>>>>>> (I've been fafiated from playing with my Model 100s for awhile now; >>>>>>> hope to start using them as terminals and for writing, soon) >>>>>> >>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>>
