FWIW I use a low profile 40pin ZIF socket in my M100 (plugged into the 'normal'
socket); not only does it make plugging the cable in and out easier and damage
to the pins less likely, but it also raises the cable a little bit and avoids
that bend you're talking about. They do seem to be a little
Is NEWDOS a ROM we can install on Rex, or is it a COM file?
Tom Wilson
wilso...@gmail.com
(619)940-6311
K6ABZ
On Sat, Mar 28, 2020 at 10:56 PM John R. Hogerhuis wrote:
> I wrote a small program to dial the TCP connection and launch NEWDOS with
> the delay. Seems to work reliably.
>
> 10 OPEN"
I wrote a small program to dial the TCP connection and launch NEWDOS with
the delay. Seems to work reliably.
10 OPEN"COM:98N1E"FOROUTPUTAS1:?#1,"ATDT 192.168.1.85:8085
":CLOSE1:CALL63013,2,2:MENU
SAVE"DIAL
Replace the IP and port with your TCP listener.
-- John.
Don't read too much into the dvi's cpu. Many peripherals like disk drives
and printers have their own cpu exactly the same way.
When you use software with the dvi, it still runs on the m100 using the
m100's cpu and the m100's ram. The dvi is just a peripheral like any other
peripheral, it just com
No plans yet. I suppose I could add it at some point but I need to make sure
all the TPDD stuff is solid. It's looking good so far but lots of testing
needed. The reason for going to Python was two create a version of mComm that
people could tweak to their liking on various platforms. I'm in the
On Sat, Mar 28, 2020 at 6:57 PM Joshua O'Keefe
wrote:
>
> You said you ran into DTR issues, I wonder if the DTR checks can just be
> NOPped out. I guess it's time for me to go learn to read 8085 while I wait
> for my modem to get here.
>
yeah I have a question out to Ken.
If it's DTR/DSR issue
> On Mar 28, 2020, at 6:01 PM, Kurt McCullum wrote:
> Gary Weber (Of Web8201.net fame) had me modify the windows version of mComm
> to work with WiModem232.
Kurt, were you planning to bring the TCP functionality forward into your new
(Python, I think you said?) version of mComm? The potential
Here is my write-up regarding using Wimodem232 + NewDOS + LaddieAlpha
http://bitchin100.com/wiki/index.php?title=Connecting_NEWDOS_to_Wimodem232
-- John.
On Sat, Mar 28, 2020 at 6:01 PM Kurt McCullum wrote:
> Gary Weber (Of Web8201.net fame) had me modify the windows version of
> mComm to work with WiModem232. I don't think I ever released it as an
> install but it does exist. Basically, the WiModem connects on IP port 1983
> (The year the model-t
The email below was the last I heard from Gary about his testing with the
WiModem232. He gives some good instructions on how he made his setup work.
Kurt
- Original message -
From: Gary Weber
To: Kurt McCullum
Subject: Re: Beta 2
Date: Saturday, March 23, 2019 12:44 PM
Hi Kurt,
You r
Gary Weber (Of Web8201.net fame) had me modify the windows version of mComm to
work with WiModem232. I don't think I ever released it as an install but it
does exist. Basically, the WiModem connects on IP port 1983 (The year the
model-t was released) instead of a com port. He had to use the vers
It would be great to get a reference solution that can be shown to work
reliably.
I was never really happy with bluetooth as an intermediate translation
layer to TCP ip.
However I do think with the right attention it should be workable.
Especially If the translation layer knows TPDD speak. Then
On Mar 28, 2020, at 4:40 PM, Stephen Adolph wrote:
>
> Give it a whirl!
Steve, you are doing a terrible job dissuading me from trying to score a
WiModem. Of course, I could also hang it off the back of the Amiga, and I
can't reuse the one on the C64 as it's wired for a Commodore User Port
Give it a whirl!
Iirc, you have to have enough delay to let TCP do its thing.
Also, a complication is when the TPDD packet is split across two or more ip
packets.
On Saturday, March 28, 2020, Joshua O'Keefe
wrote:
> On Mar 28, 2020, at 4:20 PM, Stephen Adolph wrote:
>
>
> Ken made a version
On Mar 28, 2020, at 4:20 PM, Stephen Adolph wrote:
>
> Ken made a version of newdos that had no timeout I believe, and that is what
> used in my experiment.
> Dont know if I could find it again... would have to take a look
How high did you crank the newdos delay value? It looks like it can a
Ken made a version of newdos that had no timeout I believe, and that is
what used in my experiment.
Dont know if I could find it again... would have to take a look.
On Saturday, March 28, 2020, John R. Hogerhuis wrote:
> OK, so... yes I see the same problems with TS-DOS and tcp mode that
> ev
OK, so... yes I see the same problems with TS-DOS and tcp mode that
everyone else does.
I tried TS-DOS and NEWDOS that were loaded into my Rex... no difference.
They hang timing out on the many little directory extension messages.
One thing about the WiModem232 generally, is that you need to be
>See I had no idea the DVI had it's own dedicated CPU, I just assumed the
>M100 was calling all the shots. But I suppose that does make sense,
>after all its not just a disk filing system it's having to handle, but
>video output as well.
This is a pretty easy unit to open up (I didn't say work on
The "delay loops" or timeouts are not part of the tpdd protocol. They're
just a feature of tsdos. Using another Tpdd client, like teeny tells the
tale.
But only if you've also addressed the cable check dtr/DSR issue. I think
this is a setting or jumper on most of these devices to assert DSR. There
>
> Ah - okay cool. Didn't realize that.
>
>
I don¹t think TPDD uses hardware handshaking it relies on delay loops. The
TPDD drive generates DSR to indicate there is something present which is
required by the ROM drivers.
When I tried it via an ESP12 to LaddieAlpha the big issue was the variable
delay even with a modified TPDD I could not g
Tpdd protocol doesn't do any flow control. It's purely request/response.
It does do a cable check dtr/dsr.
TSDOS itself has cable check, and timeout issues in some cases.
I recommend to loop back dtr/DSR if your device cannot assert DSR and use
teeny. It has no timeout issues. Also there are ver
That's what the feature is there for and it worked when I last tested it.
You might want to try with TEENY instead since it has no timeouts like
tsdos does.
Also you might be having cable handshake (dtr/dsr) issues. Model t' require
DSR.
-- John.
I don't think the WiModem does the hardware flow control needed by tpdd
protocol. I might try this with my Rickards modem though.
On Sat, Mar 28, 2020, 2:02 PM Tom Wilson wrote:
> I tried it with a CBMStuff Wimodem 232 talking to LaddieAlpha running in
> TCP mode. No joy.
>
> I didn’t try very h
I tried it with a CBMStuff Wimodem 232 talking to LaddieAlpha running in
TCP mode. No joy.
I didn’t try very hard, so there may be a combination of settings that does
work, but I was never able to get it to work.
On Sat, Mar 28, 2020 at 10:39 AM Gregory McGill
wrote:
> most wimodems are locked
most wimodems are locked to a baud rate and don't support hardware
handshaking.. may make it tough to set up also they only support 8bits no
parity.. with the exception of the gurumodem which does 7 bits and even/odd
parity as well
On Sat, Mar 28, 2020 at 9:38 AM Joshua O'Keefe
wrote:
> Has any
I once was running LaddieAlpha over TCP/IP through my firewall so that I
could access the TPDD while connecting over serial bluetooth to Wifi.
M100 --> bluetooth --> (android phone as a bridge) {cloud} {house}
-- firewall --- server(LaddieAlpha)
was fun to accomplish.
On Sat, Mar 28, 2
Has anyone tried to wire up one of the TPDD emulators with socat or something
to make it network accessible, and then tried reaching it from a WiModem type
device? Having wireless storage seems like it would be a great boon, but most
of the remnants I see in the Club100 library seem to be about
Thanks Stephen!
See I had no idea the DVI had it's own dedicated CPU, I just assumed the
M100 was calling all the shots. But I suppose that does make sense,
after all its not just a disk filing system it's having to handle, but
video output as well.
After I posted my question, I did happen
The DVI plugs into the system bus, and it is quite a bit more involved than
an option ROM. The DVI is really a separate, dedicated computer with a Z80
processor.
The conflict is really just in how some option roms and software (like REX
Manager, Rom2C, PowerDisk others) make use of the model 100
Hey Guys
So last night I spent the evening using my new DVI, courtesy of a 40pin
extension cable people suggested I buy to extend the existing link
cable. I'm pleased to report it all worked out really well, combined
with the new cable from Arcadeshopper, the DVI worked fine. I did have
to
31 matches
Mail list logo
