Greg,

I just finished writing this up, there are likely typos but I wanted to get
it to you before I get sidetracked again.  Things are very busy around
here. E-mail me if you have any questions. I will try and improve them this
week.

Linux instructions (rough draft)
-----------------------------------------
Minicom is the "standard" in Linux terminal programs. You need a program
that will alllow for the binary transfer of data without a transfer
protocol.  Minicom can be configured for thie.  To configure Minicom,
 install it with apt get minicom and you will also need PV, so install it
also. TO actually configure Minicom for binary transfers you need to create
a small script sendbin.sh:

-------------------------------------------------
#!/bin/sh
INFILE=/dev/null
OUTFILE=/dev/null

while [ $# -gt 0 ]; do
 case "$1" in
 -i)
 shift
 INFILE="$1"
 ;;
 -o)
 shift
 OUTFILE="$1"
 ;;
 -h|--help)
 echo "$0 -i infile -o outfile"
 ;;
 *)
 INFILE="$1"
 esac
 shift
done
cat << EOF
binary-xfer utility for minicom
Sending file ${INFILE} to ${OUTFILE}
EOF

/usr/bin/pv --force -i 0.25 -B 128  ${INFILE}  2>&1 > ${OUTFILE}
# Use the line below if you don't have pv!

# /bin/cat ${INFILE} > ${OUTFILE}
cat << EOF

File transfer complete
EOF
sleep 10
-------------------------------------------------

Open Minicon and user <CTRL>-A, O to open the options menu.  From there
select "File Transfer Protcols", we are going to all a new selection.
Slots A through I are used so select J and enter the following values

bin        /home/kimberley/scripts/sendbin.sh -o %l  Y    U    Y       N
    N

This will create a new protocol for transferring data directly, while
passing binary values without change.

Use this new option to send your file.  Connect using Telecom and press F2
for Download, enter the filename "rxcini.do" and press <CTRL>-A, S to send
a file in Minicom.  Select the protocol, the new one, "bin", that was just
added. User the left/right arrow keys and "Enter" to select "Goto" in
Minicom and enter the directory to which you unzipped "rxcini.DO" to.  Used
the same keys to select "show" to filter the files, enter "rxcini.DO" Use
the up/down arrow to move the pointer to the file and then the left/right
arrows to select "tag" to actually select the file to send. Finally, press
"enter" to actually send the file.  When the transfer is complete, press
"F2" on the M100/T102 again to stop the transfer.

RXCINI.DO loads a file from the TPDD or emulator.  Under Linux the best
option is Laddie Alpha under Mono.  You need to install Mono and download
Laddie Alphe. Laddie Alpha can be downloaded from the Bitchin100 site at
http://bitchin100.com/wiki/index.php?title=LaddieCon#LaddieAlpha . Now you
need to install Mono, Debian based systems run "sudo apt install
mono-complete". You also need the file RXC_11.zip.  Make a directory and
unzip RXC_11.zip into the directory.  Change directories to the new
directory and run "mono LaddieAlpha.exe /dev/ttyUSB0", replacing ttyUSB0
with the device you are using.  Now follow the instructions to running
RXCINI.DO in the official documentation.

Classic REX functionality should now be working.

You can put Option ROM images into the same directory and use Laddie Alpha
to load these onto the REX also.

Grab the CP/M initialization files and the image for your sized REXCPM and
place these in the same directory.

Install the TS-DOS option ROM to copy the CPM.CO and CPMUPD.CO files to the
M100/T102 from Laddie Alpha.  These are the files to install the CP/M
functionality.  Leave the *.BK file in the directory, CPMUPD.CO will
transfer this to the REX.

Follow the instructions for CP/M on the M100/T102 found here:
http://bitchin100.com/wiki/index.php?title=M100_CP/M

-------------------------------------

--Jim


On Thu, Jul 23, 2020 at 10:54 PM Greg Swallow <[email protected]> wrote:

> Jim,
>
> I could use your Linux help/step-by/information. Just converted my last
> Windows PC to elementaryOS. Am also running openSuse Tumbleweed, but am
> consolidating to one/two system(s).
>
> Dropped an PCI 2-port RS232 in and am working on getting it working for
> the M100.
>
> Thanks,
>
> GregS <><
>
> Jul 23, 2020 7:32:22 PM Jim Hart <[email protected]>:
>
> > I received mine yesterday, and after some trouble getting it initialized
> (all on the Linux host), it is working great.  If anyone is having trouble
> with installing the software from Linux, let me know and I can offer my
> solutions.
> >
> > I have the basic REX functionality and the CPM both working in the
> REXCPM.
> >
> > Thanks again Stephen for a great device.
> >
> > --Jim
> >
> > On Thu, Jul 23, 2020 at 8:30 PM Kevin Slater <[email protected]>
> wrote:
> >
> >> I also want to let you know I received my as well. I was on vacation so
> didn't get held mail until Wednesday. Looks great, haven't installed it yet
> but will get to it soon as I'm looking forward to it!
> >>
> >> Kevin
> >>
> >>> On 07/22/2020 8:51 PM Stephen Adolph <[email protected]> wrote:
> >>>
> >>> Great stuff Brian.  Glad it arrived and is working for you.  REXCPM
> benefitted from a lot of good ideas from others.  The cable harness and
> Molex carrier add to the quality significantly.
> >>>
> >>> On Wednesday, July 22, 2020, Brian Brindle < [email protected]>
> wrote:
> >>>> Just checked the mail ten minutes ago and found mine in the box! Have
> to say, very impressed with the quality of everything. Even enjoyed the
> extra effort and details in the initialization software. Fantastic work!
> >>>>
> >>>> Thanks for everything Steve!
> >>>>
> >>>> Brian
> >>>>
> >>>> On Thu, Jul 16, 2020, 2:17 PM John R. Hogerhuis < [email protected]>
> wrote:
> >>>>
> >>>>> On Thu, Jul 16, 2020 at 7:36 AM Stephen Adolph <
> [email protected]> wrote:
> >>>>>
> >>>>>> John, what flavor?  T102 or M100?cheers
> >>>>>>
> >>>>>>> M100 please
> >>>>>
> >>>>> -- John.
> >>>>>
> > --
> > --Jim [email protected]
> >
>


-- 
--Jim Hart
[email protected]

Reply via email to