Re: [M100] REX second source

Hi Steve, I agree that transferring would be work. I feel that separating the hardware and software may be the path forward, especially if the hardware design is proven. My clocks use a 240mm square PCB that I source from Pcbcart. Experience has shown that they are cheaper than OSH part for

Re: [M100] REX second source

"Is arcanities a word?" ...how about "arcana" ;) -- bkw

Re: [M100] REX second source

I think you are worrying about things you don't have to worry about at all. None of that is actually a problem. Those requirements just means my mom can't do it. My mom can't compile a c program either. So what? It's a non-issue. That still leaves a lot of people in the world who can do all of

Re: [M100] REX second source

Doug, thanks for your note - read on...let's discuss. I'd be happy to put the board files on Oshpark, and place the software, firmware, test applications in a git, but that isn't enough. One needs to install the firmware and test the hardware afterwards.. and that assumes you can assemble a REX

Re: [M100] REX second source

You can absolutely put everything up in a git repo. Sourcing components and assembling units is an entirely separate issue from simply documenting the design. The cad files, schematics, code, and general documentation and parts lists are all things that can be placed in git repos. People do it

Re: [M100] THAT didn't work... ;-)

Without having to extend (hack, violate, corrupt, make incompatible, "embrace and extend") the tpdd protocol, you could probably use inotify to make a static file whose size reamains constant, exists before, during and after the tpdd server (any tpdd server not just laddie) tries to access it, yet

Re: [M100] REX second source

This may be obvious to he point of insulting, but in case it's not, I definitely recommend just put the stuff up in github. Several things happen: * Incremental improvements that ratchet up and accumulate over time. Someone like me who is NOT up for taking over any big project and couldn't have

Re: [M100] THAT didn't work... ;-)

Huh? No the behavior of the pipe itself is perfect! Date blocked on the pipe *before getting the time* so it could sit there for days and still report current time when the pipe is finally read.  It's just that something on the mono/laddiealpha/tsdos train doesn't like the file it's reading

Re: [M100] THAT didn't work... ;-)

On Mon, Jan 9, 2017 at 1:04 PM, Willard Goosey wrote: > So I tried a clever trick and it didn't work. > > (This is NOT a bug report about any of the named programs, as it's a > weird edge case.) > > So UNIX (and therefore Linux) has these things called "named > pipes". They're

Re: [M100] THAT didn't work... ;-)

if you want to be able to write to a named pipe before your reader is created you have to open the named pipe as read/write using an extra step e.g. |--- pi@glooston:~/GnuCOBOL/open-cobol-code/branches/gnu-cobol-2.0 $ mkfifo foo pi@glooston:~/GnuCOBOL/open-cobol-code/branches/gnu-cobol-2.0 $

Re: [M100] REX second source

Hi I've been very quiet on this list for a very long time. While I do have a M100, M200 and an Olivetti and have engaged a little in discussion sometimes, I am not an active user. My focus is the archival restoration of machines from that era, up to about 1982. I'm responding as my small

Re: [M100] T600 basic rom

Correction, those links are not all in one email, but in the last few emails. -- bkw On Jan 9, 2017 3:15 PM, "Brian White" wrote: > That's a long story I answered already a couple posts back. > > I found 2 different versions on M100SIG, one is missing files compared to >

Re: [M100] T600 basic rom

That's a long story I answered already a couple posts back. I found 2 different versions on M100SIG, one is missing files compared to the other. I also found essentially a file listing of the top level dir of the Merch archive, from an early time when it was hosted via http instead of ftp. While

Re: [M100] T600 basic rom

Merch probably refers to Roger Merchberger. GAFiated. I don't know his current email but you could message him on Facebook. Do you have the M100SIG zip file? -- John.

[M100] REX second source

Anyone on the list interested in ramping up on * design of REX * manufacturing of REX * ongoing development / bugfix for the REX software stream? It would take some doing but maybe now is the right time to look for someone with the interest, energy and hardware/software skills to take over the

Re: [M100] T600 basic rom

Archive.org has at least an index of that lost "Merch" archive. Looks like a lot of overlap with the Tandy 600 dir in th M100SIG archive, but not identical. Sadly I can't get into the directories. The "hhos" dir might be the system roms, since the system rom was called HHOS, hand held os.

Re: [M100] T600 basic rom

I'll have to read more to find out what a !55 file is. And I won't be able to try loading from a disk until I have a working disk drive. That's going to be a project. My internal drive doesn't work. I have an external 3.5" 720k drive that was originally for tandy 1000-something. If I can make my

Re: [M100] T600 basic rom

In the past I have used some PC utilities to make t600 readable discs. FDformat I believe. Do you have your disc drive working and do you have a way to transfer from PC to T600? ..steve On Mon, Jan 9, 2017 at 7:06 AM, Stephen Adolph wrote: > this might be a loadable basic