> On Feb 24, 2023, at 7:55 AM, Brian K. White wrote:
> dl2 makes the most sense if I didn't care about the "dl" part. It says what
> it is and what to expect correctly and succinctly.
You are not obligated to take end user expectation into the equation here,
however the end user is mostly just
Thank you Josh,
WooHoo! First had to move my ol’ LapLink cable from the HP to the MBP as my
other 9-to-9 pin cable I was using was not, after all, null-modem; even with
all my adapters attaching it to the M100 and USB-to-RS232. Restarted TS-DOS on
the M100 and checked FILES. Had created a file
Thanks indeed.
On Fri, Oct 16, 2020, 1:30 PM Joshua O'Keefe
wrote:
> On Oct 16, 2020, at 9:57 AM, Kurt McCullum wrote:
> > Feel free to re-package it.
>
> Thanks, Kurt! I have posted the repackaged version with a simple install
> script (and a minor path edit to the launcher script) to
>
On Oct 16, 2020, at 9:57 AM, Kurt McCullum wrote:
> Feel free to re-package it.
Thanks, Kurt! I have posted the repackaged version with a simple install
script (and a minor path edit to the launcher script) to
http://public.nachomountain.com/files/m100/
Hi Josh,
For heaven’s sakes! Yes, had the folder open to see, but expected something as
would be a folder by the name of the .deb. I did a least know it was Debian.
Yes, there are three files actually. “debian-binary" as well.
Rest it is. Too tired to remember even AT SVR32.
Thanks again,
Josh,
Feel free to re-package it. My only warning is that the supporting CO files
(DOS100/DOS200/DOSNEC/SAR100/SAR200) and the dictionary (mcomm.dic) need to be
in the same directory as the python code. This allows UR-II and SARDINE to load
those files regardless of what directory you are
On Oct 16, 2020, at 9:41 AM, Greg Swallow wrote:
> "ar x mComm_1.2_all,deb" ends up at another command prompt. From what I can
> tell does not “open” the .deb file
Hi Greg,
A .deb file is an archive (similar in concept to a ZIP file) that contains a
couple of tar files. Running the "ar"
> Hey Josh,
Trying out the instructions you posted, but unable to get past the ar command
line.
"ar x mComm_1.2_all,deb" ends up at another command prompt. From what I can
tell does not “open” the .deb file. Tried ar -x with the same results. Wondered
if all was a11, but saw that it is indeed
Thank you all for the your wisdom and information.
I am finding the Mid-2012 MBP is indeed a great buy. I did upgrade it when
received it with 16gb of RAM and a 1TB SSD. Not difficult at all. Catalina was
already installed on the HDD so I had cloned the HDD to the SSD as an external
first. Was
On Oct 14, 2020, at 5:13 PM, Joshua O'Keefe wrote:
> I'll try mComm after dinner. I unpacked the .deb back when it was released
> and have it lying around somewhere.
Apologies for replying to myself, but I have successfully run Python mComm on
macOS Catalina 10.15. It took a bit of doing:
I just built dlplus from bkw's master branch and while it did emit some
compiler warnings, it built and runs out of the box perfectly on macOS Catalina
10.15.
I'll try mComm after dinner. I unpacked the .deb back when it was released and
have it lying around somewhere.
All 3 of LaddieAlpha, the python version of mComm, and dlplus probably work.
I have used Laddie and dlplus on macos myself, so those 2 I can say for
sure.
I built dlplus on macos a year or two ago and it worked normally. I use
macports for the gcc/gnu environment. I don't like brew but it
LaddieAlpha and DLPlus are the options.
I've never found installing Mono on OSX to be a big deal but I haven't done
it for a while.
The advantage of LaddieAlpha is it's already built and you don't need to
set up a compiler.
Guess I should try compiling and running it on .net core. That's cross
Greg,
There is no native version of mComm for macOS. There is a Python version that
works under Linux but I have no idea if that would actually work under maxOS.
I think LaddieAlpha is your best bet.
Kurt
On Wed, Oct 14, 2020, at 8:27 AM, Greg Swallow wrote:
> All,
>
> Most of my old,
On Oct 14, 2020, at 8:27 AM, Greg Swallow wrote:
> .Was able to pickup aMid-2012 MacBook Pro i7 for a song and am wondering if
> anyone has had luck with DLPlus or mComm on macOS?
Greg,
The mid-2012s are great machines -- my daily driver is the 12" of that vintage
with memory and disk
All,
Most of my old, Core2Quad and earlier, computers are starting to have issues
with the latest openSuse and I am looking to going all macOS. Or, close to all.
My brother-in-law handed his old MacBook Pro CoreDuo done to me and I have
found use for it as it runs software I have for my
Good to know... yeah, if I knew that, I'd forgotten about it.
In LaddieAlpha I do a bunch of transformations on the filenames to make
them TS-DOS / Model T friendly and not cause crashes. I build fixes for
problems like this into the code (then promptly forget about them).
I'll check and see if
I finally have dplus working on Linux Mint to my M100, and I thought I
should let everyone know how I did it. I finally figured out that if
the file was in lowercase on the "drive" (PC) then it would not
transfer properly. This was hard to catch because in TS-DOS it showed
up in all caps like
The same reason almost all code in linux or the entire open source world
says that or something like it somewhere.
It just means no one is making any promises that you can sue over. Every
single line of free volunteer code always comes under a warranty that reads
"This will definitely kill your
0403 is an Ftdi vid.
So whatever problem is occurring is likely to be hardware / cabling issues
no linux driver.
— John.
0403 and 6001 are the vid and pid, respectively, according to my very
old friend lsusb.
On 23 December 2017 at 00:26, John R. Hogerhuis wrote:
> Well that confirms that ftdi_sio, the normal Linux driver is being used for
> usbserial.
>
> lsusb would given some details about
Well that confirms that ftdi_sio, the normal Linux driver is being used for
usbserial.
lsusb would given some details about vid and pid and manufacturer.
-- John.
FYI, you need a space after grep.
I just ran that ok, here:
(standard input):usblp 22891 0
(standard input):usb_storage62209 0
(standard input):btusb 32412 0
(standard input):bluetooth 395423 23 bnep,ath3k,btusb,rfcomm
(standard
On Fri, Dec 22, 2017 at 11:26 PM Peter Vollan wrote:
> Then why does dmesg say that the driver is only for testing and one
> off purposes?
>
Would you run
lsmod | grep-iH usb
And
lsusb
— John.
Then why does dmesg say that the driver is only for testing and one
off purposes?
On 22 December 2017 at 16:17, Brian White wrote:
> These drivers are decades old and standard heavily used and tested and
> common to all distributions. If a /dev/ttyUSB* exists at all, then
These drivers are decades old and standard heavily used and tested and
common to all distributions. If a /dev/ttyUSB* exists at all, then udev did
everything and you're done thinking about drivers.
If you have more than one usb adapter from different manufacturers, and
they're both unreliable,
On Fri, Dec 22, 2017 at 10:44 AM Peter Vollan wrote:
> So far, "dmesg" has always said that I am using the generic driver,
> "only for testing and one off purposes". And I have already gone into
> Synaptic and downloaded everything that looked promising.
>
Kernel drivers
So far, "dmesg" has always said that I am using the generic driver,
"only for testing and one off purposes". And I have already gone into
Synaptic and downloaded everything that looked promising.
On 21 December 2017 at 13:07, John R. Hogerhuis wrote:
>
>
> On Thu, Dec 21,
On Thu, Dec 21, 2017 at 1:00 PM, Peter Vollan wrote:
> TS-DOS. I have a REXX installed.
> Now I am just getting "drive not ready", I have tried LaddieAlpha as well
> as dl.
> When I declared victory, I had just sent a small text file from the
> m100 to the linux laptop. So
TS-DOS. I have a REXX installed.
Now I am just getting "drive not ready", I have tried LaddieAlpha as well as dl.
When I declared victory, I had just sent a small text file from the
m100 to the linux laptop. So it did work, briefly.
On 21 December 2017 at 12:53, John R. Hogerhuis
On Thu, Dec 21, 2017 at 12:42 PM, Peter Vollan wrote:
> This last cable that I bought from Amazon, I went through the Tandy
> wiki page first. I just decided to get the one will the null modem
> built in.
Can you list a series of steps that reliably demonstrate a problem?
Brian White
> [bw.al...@gmail.com]
> Skickat: den 21 december 2017 12:05
> Till: m...@bitchin100.com
> Ämne: Re: [M100] dlplus on linux mint
>
> That's reasonable. I only say those are known vs unknown. I ohmed them all
> out and mapped the actual connections by hand, not mer
-pin to 9-pin serial instead of USB?
>>
>> Joan in Reno
>>
>>
>> From: Peter Vollan <dprogra...@gmail.com>
>> To: m...@bitchin100.com
>> Sent: Wednesday, December 20, 2017 7:52 PM
>> Subject: [M100] dlplus on linux mint
>>
>> On
.@sbcglobal.net> wrote:
> Just curious, but why not use 25-pin to 9-pin serial instead of USB?
>
> Joan in Reno
>
>
> From: Peter Vollan <dprogra...@gmail.com>
> To: m...@bitchin100.com
> Sent: Wednesday, December 20, 2017 7:52 PM
> S
> From: Peter Vollan <dprogra...@gmail.com>
> To: m...@bitchin100.com
> Sent: Wednesday, December 20, 2017 7:52 PM
> Subject: [M100] dlplus on linux mint
>
> On a positive note, thank you to everyone whose advice helped me to
> finally get Virtual T working on my Linux Min
Brian White
[bw.al...@gmail.com]
Skickat: den 21 december 2017 12:05
Till: m...@bitchin100.com
Ämne: Re: [M100] dlplus on linux mint
That's reasonable. I only say those are known vs unknown. I ohmed them all out
and mapped the actual connections by hand, not merely used them.
For various reasons
Just curious, but why not use 25-pin to 9-pin serial instead of USB?
Joan in Reno
From: Peter Vollan <dprogra...@gmail.com>
To: m...@bitchin100.com
Sent: Wednesday, December 20, 2017 7:52 PM
Subject: [M100] dlplus on linux mint
On a positive note, thank you to everyone whose
That's reasonable. I only say those are known vs unknown. I ohmed them all
out and mapped the actual connections by hand, not merely used them.
For various reasons in each case, I don't think you have to worry about
your usb-serial adapter, OS, or the dlplus software.
That leaves the hardware of
The problem is, I do not know why my three other cables did not work,
so I am skeptical of just spending money for another one.
On 20 December 2017 at 21:49, Brian White wrote:
> Get one of these cables (one of the 3 "ideal" ones, ie, get the cables2go
> one. You almost
Get one of these cables (one of the 3 "ideal" ones, ie, get the cables2go
one. You almost certainly do not need any different usb-serial adapter, but
if you want then get the ftdi one linked there too.
I actually use an old and underpowered atom cpu netbook, so, speed/power of
the linux host is
What’s going wrong?
On a positive note, thank you to everyone whose advice helped me to
finally get Virtual T working on my Linux Mint laptop.
I think I may have said that I had Desklink working, and was
communicating with my Model 100. Well, I spoke too soon. The best way
I can explain it is that it seemed to be
...@mykopat.slu.se
Från: M100 [m100-boun...@lists.bitchin100.com] för John R. Hogerhuis
[jho...@pobox.com]
Skickat: den 29 november 2017 06:39
Till: m...@bitchin100.com
Ämne: Re: [M100] dlplus on linux mint
On Tue, Nov 28, 2017 at 9:34 PM Peter Vollan
<dprogra...@gmail.
Well, the "generic, experimental" driver just did not work. The other
serial to usb driver did.
On 28 November 2017 at 21:39, John R. Hogerhuis wrote:
>
> On Tue, Nov 28, 2017 at 9:34 PM Peter Vollan wrote:
>>
>> Success at last!!!
>>
>> You guys were
On Tue, Nov 28, 2017 at 9:34 PM Peter Vollan wrote:
> Success at last!!!
>
> You guys were right about the permssions issue. Not only that... I
> change permissions on /dev/ttyUSB0 and it changes back for some
> reason? Well anyway "sudo" avoids that problem.
>
Usb devices
Success at last!!!
You guys were right about the permssions issue. Not only that... I
change permissions on /dev/ttyUSB0 and it changes back for some
reason? Well anyway "sudo" avoids that problem.
I am afraid that, on top of that, the Radio Shack serial to USB cable
did not work. I suspected as
sudo cp ./dl /usr/local/bin
sudo chmod 755 /usr/local/bin/dl
bkw@miata:~$ ls /dev/ttyUSB*
/dev/ttyUSB0
bkw@miata:~$ cd ~/Documents/TRS-80/Model_200/files
bkw@miata:~/Documents/TRS-80/Model_200/files$ ls
DCPREP.DO RUN-CO.DO SERIAL.DO START.DO
bkw@miata:~/Documents/TRS-80/Model_200/files$
1
On 27 November 2017 at 19:57, Daryl Tester
wrote:
> On Mon, 27 Nov 2017 19:53:47 -0800, Peter Vollan wrote:
>
>> ./dl /dev/ttyUSB0 puts me right back at the command prompt. And I can
>> see ttyUSB0 in the /dev directory. Did I miscompile desklink?
>
>
>
Maybe try it with sudo to see if it’s a permissions problem.
Also type dmesg to see if there are any kernel errors after it exits.
Another possibility would be compile for debug and run it under gdb to see
if it hits an exception. Or step through to see where it fails.
— John.
On Mon, Nov 27,
On Mon, 27 Nov 2017 19:53:47 -0800, Peter Vollan wrote:
./dl /dev/ttyUSB0 puts me right back at the command prompt. And I can
see ttyUSB0 in the /dev directory. Did I miscompile desklink?
What does running "echo $?" immediately after the command return?
--
Regards,
Daryl Tester
./dl /dev/ttyUSB0 puts me right back at the command prompt. And I can
see ttyUSB0 in the /dev directory. Did I miscompile desklink?
On 27 November 2017 at 15:37, John R. Hogerhuis wrote:
> When you plug in your usb serial device you can type
>
> dmesg
>
> And it will print out
When you plug in your usb serial device you can type
dmesg
And it will print out recent kernel messages. You can usually tell what
/dev/ttyUSBx device just got added from the scrawl.
— John.
On Mon, Nov 27, 2017 at 3:34 PM Peter Vollan wrote:
> I am not certain which
I am not certain which USB port I am on. But on the other hand,
desklink gives the say result whatever port I enter, or if I enter
none at all.
On 27 November 2017 at 15:17, John R. Hogerhuis wrote:
> Shouldn’t do that. It should run and stay running unless you hit ctrl-c
>
>
Shouldn’t do that. It should run and stay running unless you hit ctrl-c
Guessing there’s a hardware problem with the port, or a software /
permissions issue.
You could also try LaddieAlpha.
— John.
On Mon, Nov 27, 2017 at 3:14 PM Peter Vollan wrote:
> When I run "./dl"
When I run "./dl" followed by the usb port of my usb adaptor, I just
get the command line again. Shouldn't dlplus do something else, like
it does in DOS? Dlplus seemed to compile fine in the first place.
I realise that another possible wrinkle is that my cable(s) is not
working. I am using a
55 matches
Mail list logo