I would be interested in four pairs if this ever gets rolling.
Best,
CAM
--
C.A. Magaret
Sent from my newfangled mobile technogizmo. Please forgive any typos,
inelegant brevity, or nonsensical auto-corrections.
> On Jul 7, 2021, at 14:39, Jamie Nichol wrote:
>
> Peter,
>
> Looks like a
bkw
On Mon, Jul 12, 2021, 9:48 PM Brian Brindle wrote:
>
>
> On Mon, Jul 12, 2021 at 5:34 PM Brian K. White
> wrote:
>
>>
>>
>> master actually? or latest default branch which is not master but 0.4.1?
>> I didn't have master marked as default currently because I thought I had
>> made it worse,
On Mon, Jul 12, 2021 at 5:34 PM Brian K. White wrote:
>
>
> master actually? or latest default branch which is not master but 0.4.1?
> I didn't have master marked as default currently because I thought I had
> made it worse, you know like the partly-broken point mid-way in a
> refactor, so I made
On 7/12/2021 4:34 PM, Brian K. White wrote:
On 7/12/21 7:23 AM, Brian Brindle wrote:
I agree on the risk with the USB ports, you wouldn't typically design
something like this. But I appreciate the out of the box thinking
that got me past that. The current limiting etc can easily be done in
the
On 7/11/21 8:13 AM, Brian Brindle wrote:
Then you go and pop a USB jack on the BC port
I missed my que, what I meant to say was "THERE ARE NO RULES.
ELECTRONICS IS THE PURGE."
--
bkw
On 7/12/21 7:23 AM, Brian Brindle wrote:
I agree on the risk with the USB ports, you wouldn't typically design
something like this. But I appreciate the out of the box thinking that
got me past that. The current limiting etc can easily be done in the end
device, and that's what I choose to do.
I've disassembled and taken a quick look. it is quite different than "MO"
would have done, but the trampoline is clear.
(using DASMX140, which seems to be a really good disassembler!)
On Mon, Jul 12, 2021 at 1:30 PM John R. Hogerhuis wrote:
> I think it very doable. It comes down to the comp
On Mon, Jul 12, 2021 at 11:02 AM Brian K. White
wrote:
> On 7/12/21 1:30 PM, John R. Hogerhuis wrote:
>
> > Definitely worth it given SuperROM being the best ROM :-)
> >
> > -- John.
>
>
> I wish you wouldn't be so coy and cryptic about your stance on what the
> best option rom ever released was.
On 7/12/21 1:30 PM, John R. Hogerhuis wrote:
I think it very doable. It comes down to the completeness and quality of
the disassembly and identifying all jumps into the BASIC ROM including
indirect or computed jumps and mapping them from M100 to NEC.
The option ROM skeleton and trampoline stuf
I think it very doable. It comes down to the completeness and quality of
the disassembly and identifying all jumps into the BASIC ROM including
indirect or computed jumps and mapping them from M100 to NEC.
The option ROM skeleton and trampoline stuff is probably the best
understood and easiest par
I can only say that if you think you can do it, then I think you can do it.
It certainly would be cool.
--
bkw
On 7/12/21 8:30 AM, Stephen Adolph wrote:
Noting that SuperROM has never been found (or never released?) for
NEC, it seems to me given what I know about making applications run on
bot
Brian your response was much appreciated. I am still having a problem with
my Pi. I got it working at home but then I took it to the office and
plugged it in but I thought I would be able to change the wifi from the
terminal connection. No joy. I guess I need to change the wpa supplicant
file at
Hi Bill,
I totally missed that you actually had your console working, sorry the
systemd changes make me blind with rage.
If you are primarily using BBSes X-modem works pretty well, if you have an
X-Modem capable term on your M100. You can also send files to/from the M100
via the Linux command lin
Interesting! Was discussing the availability of a SuperRom image for NEC
just this past weekend on Discord with @Fezzler and I was wondering how
difficult it would be to convert.
Your description of the process is somewhat 'greek' to me so I'm guessing
that I'd need to level up a bit to be able to
Noting that SuperROM has never been found (or never released?) for NEC, it
seems to me given what I know about making applications run on both
platforms, that it should be very straightforward to translate the M100
SuperROM into an NEC variant. After all, the NEC and M100 are so similar.
Does any
Thank you so much! Embarrassingly I discovered my problem was that that I had
to go into raspi-config and designate my country so the WiFi would work. The
packages I was trying to install on my raspberry pi weren’t installing because
no internet. Once I got that sorted and made a couple change
I agree on the risk with the USB ports, you wouldn't typically design
something like this. But I appreciate the out of the box thinking that got
me past that. The current limiting etc can easily be done in the end
device, and that's what I choose to do. In reality, only one person is
likely ever go
HI Bill,
The divergence from systemd is frustrating but at last current versions of
Raspian still have ifconfig...
I'm using Raspian 10 here are my quick and dirty hints:
Get your termcap sorted:
https://zork.net/~octal/mod100.xhtml
You will note that termcap doesn't exist like it should though
“That IS a bit risky. Ideally there should be some sort of current limit to
avoid drawing more than 50 or 60 ma. But I don't know how to do that in a small
practical way.”
Wouldn’t a 82 (or 100 for 50ma) ohm resistor in series do the trick?
Scott M.
From: Brian White
Sent: Sunday, July 11, 202
19 matches
Mail list logo