Thanks for the suggestion, Philip.  But still the same error.
        Bob

-----Original Message-----
From: M100 <[email protected]> On Behalf Of Philip Avery
Sent: Tuesday, November 17, 2020 3:59 PM
To: [email protected]
Subject: Re: [M100] STRUGGLING to get REXCPM loaded

Bob, I believe you need to rename your TSD101 file to be TSD101.BX

Philip

On 18/11/2020 9:25 am, Bert Put wrote:
> Bob, I definitely second Steve's NADSBox suggestion, that worked very 
> well for me.
>
> Cheers,    Bert
>
>
> On 11/17/20 1:29 PM, Stephen Adolph wrote:
>> Bob, I recommend you use, if you can, laddiealpha on your working 
>> windows box?
>> Nadsbox should work, works for me.
>> You do need to be sure that the visible directory has the correct 
>> file name visible.
>>
>> TSD100.BX is the correct image file name for TS-DOS.
>>
>> Steve
>>
>>
>> On Tue, Nov 17, 2020 at 1:48 PM <[email protected] 
>> <mailto:[email protected]>> wrote:
>>
>>      Steve et al,____
>>
>>      __ __
>>
>>      I was successful in getting RXCINI.DO into my M100 using mComm on a
>>      Win XP laptop with a real serial port.____
>>
>>      Ran RXCINI just fine and got RXCMGR installed.  The problem all
>>      along was the Dell “legacy port replicator”.  Clearly the Dell
>>      implementation of a serial port emulation was flawed.____
>>
>>      __ __
>>
>>      Now using RXCMGR, I am trying to load OptROM images (*.BR) from the
>>      root directory of my NADSBox.  For example, I chose F2 to LOAD an
>>      OptROM image, type in the filename (ex: TSD100) and NADSBox is
>>      connected, but I always get the same error “File name error”.  I
>>      know the .BR files for various OptROMs are there on the NADSBox SD
>>      card, so I appear to be stumped again.____
>>
>>      __ __
>>
>>      Are there differently named OptROM images intended for use with
>>      RXCMGR?____
>>
>>      __ __
>>
>>      __ __
>>
>>      *From:* M100 <[email protected]
>>      <mailto:[email protected]>> *On Behalf Of
>>      *[email protected] <mailto:[email protected]>
>>      *Sent:* Saturday, November 14, 2020 8:27 PM
>>      *To:* [email protected] <mailto:[email protected]>
>>      *Subject:* Re: [M100] STRUGGLING to get REXCPM loaded____
>>
>>      __ __
>>
>>      Steve,____
>>
>>      I’ve had enough for today.  I’ll go at it again in a day or two.  No
>>      need to fret over this.  I am sure I will get it one of these 
>> days.____
>>
>>                      Cheers,____
>>
>>                      Bob____
>>
>>      __ __
>>
>>      *From:* M100 <[email protected]
>>      <mailto:[email protected]>> *On Behalf Of *Stephen
>>      Adolph
>>      *Sent:* Saturday, November 14, 2020 7:37 PM
>>      *To:* [email protected] <mailto:[email protected]>
>>      *Subject:* Re: [M100] STRUGGLING to get REXCPM loaded____
>>
>>      __ __
>>
>>      If you continue to struggle, try this:____
>>
>>      __ __
>>
>>      
>> http://bitchin100.com/wiki/index.php?title=REXCPM#Test_your_REXCPM_In
>> stallation____
>>
>>      __ __
>>
>>      On Sat, Nov 14, 2020 at 7:35 PM Stephen Adolph <[email protected]
>>      <mailto:[email protected]>> wrote:____
>>
>>          Hi Bob,____
>>
>>          my guess is that there are one of 2 things wrong.____
>>
>>          1) the socket has some loose connections or____
>>
>>          2) the 8 bit transfer didn't go as planned and there is
>>          something amiss with RXCINI.DO____
>>
>>          __ __
>>
>>          I must say, I need to make my utilities more bulletproof.  I
>>          think I will adopt the Ron Weisen encoding...7 bit.____
>>
>>          __ __
>>
>>          Steve____
>>
>>          __ __
>>
>>          On Sat, Nov 14, 2020 at 4:06 PM <[email protected]
>>          <mailto:[email protected]>> wrote:____
>>
>>              Hello all!____
>>
>>               ____
>>
>>              Today I finally tried to install REXCPM in my M100.  I have
>>              not yet succeeded.  Any suggestions would sure be
>>              appreciated.  Here is the scenario:____
>>
>>               ____
>>
>>              Using a Null Modem cable, I transferred the RXCINI.DO file
>>              carefully to the M100.  I used 1200baud with TeraTerm on my
>>              Dell Win10 laptop, 8 bits, etc.  My Dell Win10 machine came
>>              with a Dell external device that provides supports legacy
>>              ports via USB cable to an external box with physical serial,
>>              parallel, Ethernet, and USB connections.  ____
>>
>>               ____
>>
>>              The transfer was successful and I looked at the lines of
>>              code in the  .DO file and compared to a screen listing of
>>              RXCINI (used Notepad).  All good.____
>>
>>               ____
>>
>>              I connect my NADSbox with RXC_11.BR <http://RXC_11.BR> AND
>>              RXCINI.DO In the root directory and using the cable that I
>>              have always used with my NADSbox.  Then I start through the
>>              steps found onthe Bitchin100 page:____
>>
>>              http://bitchin100.com/wiki/index.php?title=REXCPM____
>>
>>               ____
>>
>>              I at step 4, I select Yes to both options, and Y to 
>> proceed.____
>>
>>              I see a line on my screen that shows dots appearing:____
>>
>>                 Loading at: 62000 <…………………….____
>>
>>                 ..____
>>
>>              Note that I see only two dots on the last line then the
>>              screen goes off with the M100 powered off.  When I turn it
>>              back on, it is apparent that a cold start has 
>> occurred.____
>>
>>               ____
>>
>>              I have repeated all the steps carefully at least 4 times
>>              (Cold started M100, transfer RXCINI.DO, RUN”RXCINI”.  I
>>              never get to step 6.  The result is always the same.____
>>
>>               ____
>>
>>              I am pretty sure that my transfer of RXCINI.DO is not
>>              corrupted.____
>>
>>               ____
>>
>>              Any suggestions?____
>>
>>               ____
>>
>>                          Thanks in advance,____
>>
>>                          Bob____
>>

Reply via email to