I only wish Kurt had told me he had implemented that feature sooner. Could have saved me months of bother with my com ports ;-) On 28 May 2015 5:47 pm, "Mike Stein" <[email protected]> wrote:
> Definitely a useful tool; simple to implement and in practice most > people are probably just transferring text files anyway. > > And apparently it also has a bonus function that can repair Windows com > port problems... ;-) > > m > > ----- Original Message ----- > > *From:* Kurt McCullum <[email protected]> > *To:* Model 100 Discussion <[email protected]> > *Sent:* Thursday, May 28, 2015 12:02 PM > *Subject:* Re: [M100] Update on my M100 and REX > > Mike, > > Yes, using the TELCOM mode is limited to .DO files or untokenized .BA > files (which will tokenize while loading in Basic). The latest version is > also a TPDD server and a Sardine dictionary disk server. > > Kurt > > > > On Thursday, May 28, 2015 8:50 AM, Mike Stein <[email protected]> > wrote: > > > Excellent! > > I understood that Mcomm can only transfer .DO files; can it also transfer > .BA and .CO files? > > m > > ----- Original Message ----- > *From:* James Zeun <[email protected]> > *To:* Model 100 Discussion <[email protected]> > *Sent:* Thursday, May 28, 2015 8:10 AM > *Subject:* Re: [M100] Update on my M100 and REX > > Well I have some good news! What James with some M100 related good > news?! Say it aint so!! ha > > My hat has to go off to Kurt and MCOMM, I was able to set it up an hour > ago with the minimal amount of fuss and all is working. I've downloaded > software and also loaded software through BASIC using the "COM:98N1E" > command. AND....AND!! All through my machines onboard serial port! The > machine has about 4 com ports, two of which are actually on the back of the > machine. So I disabled all the others, including the printer port and > result!! Back working in Windows! > > I've spoken to Stephen and it looks like I'm sending the REX back to him > for study. If it turns out that it's not faulty, then the problem has to be > with my odd M100. Either it's faulty or due to being dramatically different > to other M100's. It is somehow incompatible with the REX module. I would > like to send Stephen my M100, but Canada is a long way and I just dont > trust the post man not to bang it. It's a pity, because I'm sure if i sent > it him, he could give it some scrutiny and figure out how my model differs > to US machines. Should be worth a paragraph on the M100 wiki at the very > least :P > > BTW guys, i was given a floppy drive a while back. I've bought a cable for > it off Ken, but I'm guessing I need software to access the drive? If so, > could anyone point me in the right direction. I've no way of knowing if > this drive works, I'm aware the belts do perish. > > > On 28 May 2015 at 07:25, Mike Stein <[email protected]> wrote: > > Not worth the trouble IMO; you'll want a null modem cable anyway for > transferring files down the road, so why not just use TEENY etc. or Mcomm > to begin with. > > m > > ----- Original Message ----- > *From:* James Zeun <[email protected]> > *To:* Model 100 Discussion <[email protected]> > *Sent:* Thursday, May 28, 2015 2:08 AM > *Subject:* Re: [M100] Update on my M100 and REX > > Sadly I don't, are they way to get hold of? > On 28 May 2015 6:04 am, "John R. Hogerhuis" <[email protected]> wrote: > > Also assumes he has a cassette cable. > > But I do have an audio file of it somewhere if it's needed. > > -- John. > > > > > -- > My retro tech blog and general ramblings > http://bytemyvdu.wordpress.com/ > > > >
