Re: [M100] Some M100 SIG files
looking at the files, .DES is a description file, flat ascii, and .pw1 is basic in asciiwillardSent from my Galaxy Tab® A null
Re: [M100] New user (Hello!). Programming Tandy 102 without Basic?
In article , DJCC wrote: Sorry about the late response.. > Hi there! > Searching the archives, I've found http://www.sdc.org/~goosey/ > <http://www.sdc.org/~goosey/> with dev resources. Are there others that > might be interesting? Besides what I have listed? Humm. There are a couple of other (ancient) 8080 assemblers around. And I know of 2 efforts at NEW x80 toolchains being worked on, but afaik they're not ready for release yet. :-) You can check out the SDCC project, they were working on an 8080/8085 dev system to go with their z80 stuff but I think someone here recently checked and it still doesn't work for 8085. And as Ken mentioned Virtual T has its own assembler system that sounds pretty nice. Willard > Thanks! > djcc -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. --Robert E. Howard
Re: [M100] Unknown DIN plug
thats exactly what that is!Sent from my Galaxy Tab® A Original message From: Ronald Hudson Date: 11/24/22 8:06 AM (GMT-07:00) To: m...@bitchin100.com, m100@lists.bitchin100.com Subject: Re: [M100] Unknown DIN plug If that looks like the same Phone connection that is on the back of theM100,ThenThis was to plug into the cable when you took the M100 away. The Phoneline passed thru the M100 on its way to the phone itself. When you tookthe M100 away (Serious Couch computing?) the phone would bedisconnected. This gadget re-connects the phone in the absence of theM100On Wed, 2022-11-23 at 12:31 -0600, Wayne Lorentz wrote:> I've been dragging this plug around with me in my Model 100 bag for> years and years and years, but I've never known what it's for.> > Today I tried to look it up in old Radio Shack catalogs, but found> nothing.> > I'm sure someone on this list must know what it is for: > preview.jpega> JPEG Image · 152 KB> > >
Re: [M100] BCR woes
yes the light is very dim.did you get the docs? i had to practice a lot with the known good samples in the docs before i got any good with it.the 2 keys to success seem to be angle and speed. you have to be surprisingly fast with the wand to get good scans. Sent from my Galaxy Tab® A null
[M100] Tandy 600 update 2
The disk drive works!!! I was able to read the original disk, copy the formatter into ramdisk, format a new disk, and write my data files to it! Also used mtools to copy the utility disk files to my new disk, and those read fine! (caveat, this disk was previously formatted 720K Mac so there was no chance of linux finding valid sectors on side 1 and getting confused) I swear this thing was literally used once in 1985 and then stored away. And yes, WORD.!30 appears to simply be a copy of ROM WORD. I was hoping for something new. Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. -- R.E. Howard
Re: [M100] Tandy 600!!!
On Thu, 15 Sep 2022 21:34:55 -0700 Gregory McGill wrote: > I'm in on building some I need one or two > also I need software point me the way I can't build my own but I can pay. > > Greg > Willard
Re: [M100] Tandy 600 updates
Woot! I left the T600 unplugged last night and this morning my data files were still intact That's a good sign. On Fri, 16 Sep 2022 09:51:18 -0400 "Brian K. White" wrote: > I have an original 600 util disk and those are the files from it, > also they match what the manual says. I'm just trying to make sure mtools made good copies. At this point I believe they did! Next step will be to make sure the T600 can still read disks, then maybe even write one! (but not my master Utilities Disk!) > I'll take another look at the printer.dvr file and see if I somehow > made a bad copy. You're right that the the specific nature of the > discrepancy looks suspicious. Yeah xmodem always does full blocks, legacy of it's CP/M origin. > > That Word fileis probably just a copy of the same program from the > main rom. The way files work is weird. You can copy programs from > either the main rom or an option rom to ram or to disk, and from disk > to ram. I don't fully understand how executables work, but it seems > like they have a filename and a unique numbered extension even when > they are part of a rom. Yeah, I figured word.!30 would just be ROM copied to disk but I'll investigate further. It would be cool to have something unique to upload and preserve! :-) Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. -- R.E. Howard
[M100] Tandy 600 updates
So I let the 600 charge a good 6 or 7 hours. Took it into the kitchen, which is my best-lit room, and could actually see the screen. Typed some text into Word for over a half-hour before the low-power light came on. So the big battery isn't completely dead but is feeling its age for sure! Haven't tried to read the disk yet, on the 600. So, the disk. I downloaded the utilities disk files from tandy.wiki, and only one was different from the copies linux mtools made. What is the proper size for PRINTER.DVR my copy is 61 bytes. The copy on tandy.wiki is 128 bytes. Since 128 bytes is 1 xmodem block, I'm suspicious. Especially since bytes from 0x3C on are all 0x20 the first 61 bytes are identical. Also my disk has an a additional file, Word.!30 that is 13600 bytes long. ROM "file" dump or something interesting? Anyway, I believe that mtools can correctly read Tandy 600 disks, at least as long as the kernel can be convinced that the disk really is single sided. A disk that had been previously formatted dsdd may be more trouble. I will test that when I can. Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. -- R.E. Howard
[M100] Tandy 600!!!
I bought a Tandy 600! And it seems to be working! It's a very clean, new-looking box. Used once, declared useless, and stored away, I'm sure. 32k, multiplan. tandy.wiki has almost all the docs. mtools under linux seems to work fine for reading the 360k 1sdd 3.5" disk. I believe those files are on the Net, so I'm going to grab them and do comparisons before declaring victory there. I seem to remember somebody here still sells the 96K RAM modules? I've got the BASIC.!55 file but can't do anything with it until RAM upgrade. Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. -- R.E. Howard
[M100] New version of m100.def and friends
After way too long, I am releasing the new version of m100.def and related files. The big new star is t200.def which supports the Tandy 200! http://www.sdc.org/~goosey/m100/m100def-2022-04-11.zip for UNIX ASM80 and ZMAC http://www.sdc.org/~goosey/m100/asx-m100-2022-04-11.zip for AS http://www.sdc.org/~goosey/m100/dosm100-2022-04-11.zip for DOS/windows Telemark TASM Also these are available through Club 100's personal libraries under Willard Goosey I don't have addresses for quite all the labels under T200 but most of them are there. So, I still don't have a t200 myself so the t200 stuff is all untested. Please let me know about any bugs, even though I can't promise a FAST response... Willard (I tried sending this on 4/12 and it apparently never made it?) -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. -- R.E. Howard
[M100] New Version of m100.def and friends
After way too long, I am releasing the new version of m100.def and related files. The big new star is t200.def which supports the Tandy 200! http://www.sdc.org/~goosey/m100/m100def-2022-04-11.zip for UNIX ASM80 and ZMAC http://www.sdc.org/~goosey/m100/asx-m100-2022-04-11.zip for AS http://www.sdc.org/~goosey/m100/dosm100-2022-04-11.zip for DOS/windows Telemark TASM Also these are available through Club 100's personal libraries under Willard Goosey I don't have addresses for quite all the labels under T200 but most of them are there. So, I still don't have a t200 myself so the t200 stuff is all untested. Please let me know about any bugs, even though I can't promise a FAST response... Willard
Re: [M100] MAZE029 - An 8080 Assembly Language Maze Game with a 3D perspective
There's the mailing list archive, but no wiki, alas. And I played around with gnusim8085 a little, it would use the asm/asm80/zmac headers (classic ASM.COM syntax)... but the version I have doesn't know about include files on its own (but then niether does asm80) and more annoyingly didn't seem to have any way to save binaries? Willard
Re: [M100] MAZE029 - An 8080 Assembly Language Maze Game with a 3D perspective
Sorry for the delay in response. Work + medical issues here... I'm not really clear on what you're looking for. If you want on-machine assembers the best is in the ROM II expansion ROM. It's available as an image and works with REX. Other than that there are a couple of assembers written in BASIC but I haven't tried them and YMMV. For cross assemblers, what's the host OS? Anyway, a brief glance at your code looks like you're targetting CP/M's ASM.COM so (afaik) the most compatible UNIX cross assembler is ASM80 which you can get from my web page, http://www.sdc.org/~goosey/unix/asm80-2020-10-06.tar.gz There is also ZMAC which I don't have a handy url for sorry. z80 but it has a handy flag to show z80-only opcodes as errors for 8080 use! Also AS includes 8080. This is a big one, has crosss assemblers for like almost all the 8-bit CPUs... http://shop-pdp.net/ The old standard dos/windows assember is TASM (telemark asm aka table asm) sorry I don't have a url for that one. the Virtual T emulator INCLUDES an assember but I don't know anything about it. (if you're using RISC OS there's zmac (again no url) and my asm80 at ...riscos/asm80... ) if you're going to use asm80/zmac/asx/tasm may I suggest my header files that document a lot of the ROM API for you? http://www.sdc.org/~goosey/m100/m100def-2020-05-09.zip (new version with Tandy 200 support RSN (i promise! :)) Even CP/M's ASM.COM would work fine. All of these (except virtualT i'm sure) generate bog standard intel HEX files, and there are BASIC and BASIC/assem loaders to create a .CO from the hex files. GNU objcopy also works. Somebody had a neat python script to turn HEX into a BASIC program that does its own loading but I lost track of that one. :-(
Re: [M100] t200 addresses? from hterm.git
hi ben!on the model T's rst7 uses the following byte as a parameter but yes
otherwise. 503c is the published entry point for LCD and 1604 is POPALL which
pops all the regs off the stack and returns.so this conflict is resolved
anyway.yay progress!willardSent from my Galaxy Tab® A
Original message From: Ben Wiley Sittler
Date: 2/12/22 4:05 PM (GMT-07:00) To: m...@bitchin100.com Subject: Re: [M100]
t200 addresses? from hterm.git I believe that in hex that sequence looks likee5
d5 c5 f5 ff 08 cd 3c 50 c3 04 16In machine code it might bePUSH HPUSH DPUSH
BPUSH PSWRST 7SUB HL-BC (undocumented!)CALL Sat, Feb 12,
2022, 11:26 Willard Goosey wrote:sorry its been a rough week
will look at this tomorrow...thank you for thiswillardSent from my Galaxy Tab®
A Original message From: B 9 Date: 2/8/22
4:31 PM (GMT-07:00) To: m...@bitchin100.com Subject: Re: [M100] t200
addresses? from hterm.git On Sun, Jan 23, 2022 at 4:47 PM Stephen Adolph
wrote: Also, sometimes both entries can be valid.
Depends on the use case.That may be right. Both call 20540, asc("@") and 20528
print "@" to the screen, so I could see the reasoning for calling both 503CH
and 5030H as LCDPUT. However, the techref only lists 503CH and there's the
question of what do those extra 12 bytes of instructions do? I PEEKed and
they're not NOPs. So, what is the use case for calling 5030H instead?—b9P.S.
For anyone who can understand 8085 machine code, the extra bytes are: 229, 213,
197, 245, 255, 8, 205, 60, 80, 195, 4, 22.
Re: [M100] t200 addresses? from hterm.git
sorry its been a rough week will look at this tomorrow...thank you for
thiswillardSent from my Galaxy Tab® A
Original message From: B 9 Date: 2/8/22
4:31 PM (GMT-07:00) To: m...@bitchin100.com Subject: Re: [M100] t200
addresses? from hterm.git On Sun, Jan 23, 2022 at 4:47 PM Stephen Adolph
wrote: Also, sometimes both entries can be valid.
Depends on the use case.That may be right. Both call 20540, asc("@") and 20528
print "@" to the screen, so I could see the reasoning for calling both 503CH
and 5030H as LCDPUT. However, the techref only lists 503CH and there's the
question of what do those extra 12 bytes of instructions do? I PEEKed and
they're not NOPs. So, what is the use case for calling 5030H instead?—b9P.S.
For anyone who can understand 8085 machine code, the extra bytes are: 229, 213,
197, 245, 255, 8, 205, 60, 80, 195, 4, 22.
Re: [M100] t200 addresses? from hterm.git
I was looking at that today...I can't even get the dependencies of the dependencies for raspian jesse.Im afraid my linux boxen are almost as outdated as my model 100!WillardSent from my Galaxy Tab® A null
Re: [M100] t200 addresses? from hterm.git
So, which addresses for the named routines actually work?I'm especially nervous about the off-by-one differences...I still don't have a T200 so I can't test this myself... :-(WillardSent from my Galaxy Tab® A null
[M100] t200 addresses? from hterm.git
I'm seeing different addresses in hterm.git/lib/T200rom*.asmcan a t200 dev confirm these?LCD 503CH (everywhere else)LCD 5030H (T200rom_published_lib.asm)KYREAD 0C00HKYREAD 8B03HCHSNS 1404HCHSNS 1422HSENDCS 6E1EHSENDCS 8617HCLSCOM 87B6HCLSCOM 87B5HGETTOP 6E8CHGETTOP 6E8DHKILASC 2AB5HKILASC 2AB4HwillardSent from my Galaxy Tab® A
[M100] dev system filenames
Should it be m200.def or t200.def?(yes im still alive)(yes i think this is actually happening soon)WillardSent from my Galaxy Tab® A
Re: [M100] m200.def --- eventually m200smallclib hopefully
Alright! I figured most of this stuff would already be done, just scattered all over the place. (I don't know if I'll have anything ready to release tomorrow, if not it'll be next thur. before I have any time off...) Willard
Re: [M100] m200.def --- eventually m200smallclib hopefully
>Hi: I've got an M200 -- actually I may have more than one. What state of >goodness is required? >Ben > Working is all I need. I wouldn't care if it was a beater. Willard
Re: [M100] m200.def --- eventually m200smallclib hopefully
>There's always Virtual T! Actually very well suited to test suites. > I'm just not into emulators. They're just not my thing for some reason. :-) Willard
[M100] m200.def --- eventually m200smallclib hopefully
So, due to popular demand (one d00d asked) I've started putting together a m200.def to match m100.def. This will hopefully lead to an equally (in)capable m200smallclib, but first things first!!! This is complicated by the fact that I don't have a m200... This is pre-alpha completely untested stuff! So, starting from the club100 scan of the m200 techref, there are some addresses I just can't read. They are: CHPLPT SNDCOM(*) INZCOM (*)also need to know if SNDCOM is the same evil hack of "jump into the middle of sd232 (which preserves BC) so we need a dummy value on the stack" as the m100 call. Also, to get smallclib's cstart.a85 fully working I need the m200 versions of these: RSTDOG (1bb1h on m100) POWERFLAG (0f932h on m100) Last week was hell at work so I haven't had a chance to do any other research. URLs to other m200 assembly docs welcome! Lastly, anybody have a m200 for sale? :-) Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. -- R.E. Howard
Re: [M100] "Card File" for M100 via REX?
You're welcome! What little I messed with it, I liked crdfil. Willard
Re: [M100] "Card File" for M100 via REX?
I've played with crdfil.rom a little with my m100+REX, it seemed to work fine. I really liked it, just didn't have much need. You need a regular Intel HEX file to binary converter... That would depend on what OS you use... Or you can grab it at http://www.sdc.org/~goosey/m100/crdfil.100.rom.zip that is just a plain zipped .bx file. Willard
Re: [M100] Cassette file transfer question
Yep that's it. I didn't remember that it's supposedly read/write. that's good. Never tried it, my trsdos box is a 4P... which has no cassette port! :-/ Willard
Re: [M100] Cassette file transfer question
IIRC TRSDOS 6 (and maybe earlier versions -- sorry I'm not a trsdos guy) includes a special command to read m100 tape data files. but I do not believe they are directly compatible. Willard
Re: [M100] asm80 updated (Startingn to be OT though(
On October 18, 2020 6:44:51 PM MDT, Ken Pettit wrote: >On 10/18/20 5:20 PM, Willard Goosey wrote: >> My specialty is making software nobody else uses. ;-) Willard > >Yeah, I have my fair share of that type of code also! :) Like my >23,000 line program to convert ASCII drawings into .svg or .png with >full color. For instance: That's pretty neat! But yes, model 100... i got nothing... Willard
Re: [M100] asm80 updated
On October 18, 2020 9:18:42 PM MDT, Daryl Tester wrote: >RISC OS - that takes me back ... > It's pretty nice on a Raspberry Pi... >Nice work! Thanks! Willard
Re: [M100] asm80 updated
On October 18, 2020 12:05:10 PM MDT, Ken Pettit wrote: >Hey Willard, > >RISC OS? Wow, didn't even know such a thing existed. :) > Well, RISC OS people know about the z88 rather than the model 100, but who knows I might not be the only person who runs RISC OS and might want to cross assemble some 8080 code. I probably am though. My specialty is making software nobody else uses. ;-) Willard
Re: [M100] asm80 updated
On October 18, 2020 11:15:56 AM MDT, Kurt McCullum wrote: >Thanks for putting this together Willard! > It's still my main assembler for m100 stuff. :-) I think the overtime well I've been trapped in the last couple of years has dried up, so if there's any issues with asm80 let me know, I might be able to respond in a reasonable time frame now. :-) Willard
[M100] asm80 updated
I'm still here! Updated asm80, a ASM.COM style 8080 and 8085 cross assembler for linux and (now! RISC OS) asm80 is now a vanilla 8080 assmembler (RIM and SIM supported) asm85 is the same assembler but supports the "undocumented" opcodes using the Tundra names. http://www.sdc.org/~goosey/unix/asm80-2020-10-06.tar.gz http://www.sdc.org/~goosey/riscos/asm80-20201006.zip Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. --Robert E. Howard
[M100] unix cross development updates!
My Model 100 is still down :-( but here are some updates for m100 cross development! http://www.sdc.org/~goosey/unix/asm80-2020-05-08.tar.gz Important new update for asm80!!! Older versions don't handle DB instructions of the form "DB 'X' + 80h" correctly, either erroring out or worse, failing silently! (also http://www.sdc.org/~goosey/riscos/asm80-20200508.zip for RISC OS 5 but I haven't tested the rest of my xdev tools under RISC OS yet) http://www.sdc.org/~goosey/m100/m100def-2020-05-09.zip (also .tar.gz) update for my asm80/zmac definitions files. 8085undoc.def and .zm gave the RIM instruction the wrong opcode. In the asm80 defs file that's just a comment but it was an active bug in the ZMAC macros. (tasm & asx don't use that macro file, they already know full 8085.) These are also all available in the Club 100 Personal Librarys "Willard Goosey" / linux cross development The Tandy Warlock hits! Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. --Robert E. Howard
Re: [M100] M100 escape sequences.
On Sun, 12 Apr 2020 21:07:48 -0700 Ken Pettit wrote: > Hey Steve, > > If you look at the VirtualT source code for tdockvid.cpp, you will > see a case statement on line 676 which processes ESC codes from the > DVI code. Though it looks like from my code, I didn't figure out what > ESC-X does either: >> > > > ESC-Q (cursor off) > > ESC-X (?) > > 1(the desired character) > > ESC-P (cursor on) > > ESC-X (?) M100 is mostly a VT52? I found a reference: https://github.com/microsoft/terminal/blob/master/doc/specs/%23976%20-%20VT52%20escape%20sequences.md that indicates on VT52, ESC X is "turn printer off" which would match ESC W "turn printer on". Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. -- R.E. Howard
Re: [M100] Option Rom File Formats
yes .hex is the wrong format. you have to turn them back into raw binaries with a hex2bin. also http://bitchin100.com/wiki/images/6/63/M100_OPTION_ROMS.zip has most of the roms all ready to for REX. (about the only useful rom not there is crdfil.rom) hoot, guardian etch, and logit are weird, undocumented, require special equipment, or some combination...WillardSent from my Galaxy Tab® A null
Re: [M100] memory corruption on power cycle?
> Have you tried running a RAM tester? There are a few in the archive: > http://www.club100.org/library/libutl.html It was passing those tests right after the new battery was installed, but that's a good idea, I should re-run those! Good suggestion, thanks! Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. --Robert E. Howard
Re: [M100] memory corruption on power cycle?
In article , Stephen Adolph wrote: > Willard, I assume this all happens only when REX is installed? Huh, no! With or without REX. I'm suspecting a bad RAM or power supply issues. Neither amuse me. :-( > Assuming that there is no defect with REX, then * what release of > firmware is running? IE the REXMGR software load version. There is no > way to know directly but you can report the Checksum value and that > should correlate. it says : Software 4.0 cs=6e83 model: rex firmware: 6(1) > * is your socket healthy? are the pins making good > contact? Seems to be. REX works fine! -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. --Robert E. Howard
[M100] memory corruption on power cycle?
New nicad, new REX (from arcadeshopper (thanks!!!) with 4.9). M100 still scrambles the RAM directory on power cycle. (fairly consistantly. File directory entries are 2 bytes too low after a power cycle!) help? Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. --Robert E. Howard
[M100] continued m100 woes
My m100 got a new nicad but its still not happy.i did a lot of testing.it all comes down to my REX saving/loading bad ram images.Reinstalled 4.9 twice...then i was sick all week so i haven't touched it since.my 2 days off are already gone, time for another 40+hour weekmaybe i can work on it more next weeksorry about the delaysWillardSent from my Galaxy Tab® A
Re: [M100] mcomm android support?
In article , Peter Noeth wrote: > I would be interested in what you would use an M100 for on a trip, as > opposed to a standard laptop or tablet. Are you a news reporter? No I'm not a reporter. :-) My laptops all died a few years ago. One crashed its hdd, the other, well, I kinda fried the cpu playing too much DOOM. :-( The Model 100 lives on! A tablet is fine for consuming Internet but doing anything creative on one is slow and painful. I run out of patience with on-screen keyboards real quick! I could lug around my bluetooth keyboard, sure, but the M100 isn't really much larger... So why take a M100 on a trip? Hmm... 1) ELEVEN.BA 'nuff said. :-) 2) playing other games. TREK.BA is actually a pretty good version. With a REX, I have 4 memory banks full of games (not counting ROG). 3) *writing* other games! ROG is pretty complete. What's my next project? 4) diary-keeping. I really allow too much of my life to go by without record or inspection. 5) misc. note keeping. There are people who wouldn't believe it possible but my hand writing is getting even worse 6) expense tracking. Sure I keep recipts but a backup copy is always good. 7) Who knows what else? I've got a text editor, text formatters (ultimate rom, super rom), spreadsheets (lucid, multiplan), databases (lucid, crdfil, shedul/addrs), outliners (thought), FORTH (mforth), a powerful and complicated assembler/debugger combo (rom2). It can even read bar codes! :-) And, having an excuse to bring the tablet along means I also have a way to display the pdf docs for the ROMS! :-) Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. --Robert E. Howard
Re: [M100] mcomm android support?
In article <0bf7f816-5622-48c4-b1d2-375e66a5f...@www.fastmail.com>, Kurt McCullum wrote: > Willard > I just checked the mComm Android code. Unfortunately, it does not modify > the existing files to check for proper EOL and EOF characters. It gives > you a byte for byte representation of the file. I may have some time of > Christmas to add that in for you. I'll keep you posted. ...if you want to, I wasn't making a feature request or a bug report. Certainly, don't waste Christmas on it! I'm totally Ok with dealing with such issues outside of mcomm. > The current version is 1.9 and if you want I can email that directly to > you since the members file area is down. That however I would appreciate! :-) Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. --Robert E. Howard
Re: [M100] mcomm android support?
In article <3d9d68de-1198-44da-bfa1-b9e15da6b...@www.fastmail.com>, Kurt McCullum wrote: > Are you using the latest version of mComm for Android, or an early one? An early one. 1.41 IIRC. Works fine for me! It just happens to be the version I had saved locally. No particular other reason, except that club100 member files are still down. Debugging php is probably bad for you, Ken may have to wait for his doctor to clear him for such pain. ;-) Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. --Robert E. Howard
Re: [M100] mcomm android support?
Jim Anderson wrote: > I've seen CR-only EOL markers in two other places - the original MacOS > (pre-OSX) and on the Tandy WP-2. But my Mac was never a pdd server either(*). I probably got it in my head that m100 used bare cr's and converted them. Booze may have been involved. > jim (*)my Mac could be a pdd client, but that software's not happy in 32-bit mode and anyway wha? Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. --Robert E. Howard
Re: [M100] mcomm android support?
In article <44f24f91-fcb9-4830-af26-5f6718fe3...@www.fastmail.com>, Kurt McCullum wrote: > Willard, > EOF is a control Z (Character 26) at the end of the file. That one I am > familiar with. Yes, and it's migrated into a frightful number of my .DO files... I think Procomm may have either saved them or added them during ASCII downloads. (This tells you something about how old these files are, because I started using desklink+teeny back in the early 2000's sometime!)(*) I know why so many files have raw linefeeds for eol, they were downloaded onto a linux machine. More confusing are the files with cr only eols. I can only assume I got confused at some point, because my CoCo has never been a m100 file server... And I don't even know what happened to the 2013 programming contest files, they were totally screwed... Anyway, I found a text editor (quickedit) that claims it can save files with crlf eols and it's not afraid of .DO filenames. So far, so good! > Kurt (*)I've seen things, man. BASIC code written by a CS guy who'd had enough of the prof's #%@$ and ghods I guess I *am* that much of an idiot there's the proof right there... Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. --Robert E. Howard
[M100] mcomm android support?
So I'm giving android mcomm (an ancient version) a serious test. I figure, why anst over rather to take my m100 *or* my tablet on trips, when I can take both and have the tablet be my m100's disk drive? :-) However I've had some issues, not with mcomm itself, but around it... 1) I've been sloppy about EOL/EOF stuff and mcomm doesn't filter... Are there android apps that can test/repair EOL issues with files? 2)How to teach an android editor/viewer that .DO files are flat text and it's OK to display them? I swear android is worse than classic MacOS about file types... Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. -- R.E. Howard
[M100] z88dk!?!?!
So it looks like z88dk is adding 8080 (8085) support and model 100 stuff! anybody who's doing less than 8 hours of overtime every week (ie not me) want to check this out? https://github.com/z88dk Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. --Robert E. Howard
Re: [M100] Model 100 software archive
In article , Ben Wallace wrote: > programs? I was hoping to find a copy of Scripsit for the Model 100 > since I have the guidebooks but not the actual tape. check http://www.classiccmp.org/cini/systems.htm Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. --Robert E. Howard
[M100] m100 repairs
My m100 is over at my ISP, getting a new NiCad installed. So no model-100-ness until I get it back. :-( Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. --Robert E. Howard
Re: [M100] breaking the silence
In article , Josh Malone wrote: > I'm assuming this NiCad has already been replaced in the recent past? If > it's original, definitely get it out of there. Well, it just went a good 12 hours without corrupting its RAM... I'm going to try to use my m100 this week, and we'll see if it has any more problem. Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. --Robert E. Howard
[M100] breaking the silence
I haven't been doing much M100 stuff, too busy at work! Also my M100 started having memory corruption issues, so I decided that it needed a new NiCad. Yesterday I finally opened it up, and the NiCad looks fine, and measures 3.9V. The caps all look good also, no swelling or leaking. The AA's on the other hand, were kind of nasty. So I cleaned up the AA holder with vinegar and then a careful water rinse and let it dry overnight, and this afternoon put in fresh AAs. So far it hasn't lost any files, so I'm hoping my problems are over. I've been baddly missing my M100! -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. --Robert E. Howard
Re: [M100] system boot disk for DVI
In article , Chris Oliver wrote: > But physically creating the floppy from the .dat file is above my pay > grade - esp. given that I only have a Tandy Coco to work with (and I'm > guessing the disk format is different between the Model 100 and the > Coco). *Just* enough that they can't read each other's disks without programming. :-( They're both Microsoft FAT-8. I had the CoCo reading DVI disks with pure Disk BASIC (well, the first 35 tracks anyway...:) But I don't have a DVI so I stopped there. (last time I looked at DVI stuff there were only the Teledisk images available! the raw sector dump images are new to me!) Actually (I haven't tried this) but if you've got OS9 running on at least double-sided floppies or a hard drive and you can download dvi.dat to it, you can probably use dskwrite to write a physical disk (just change the sector count to 40*18= 720 sectors... umm, I may have lost you there? Did I loose you? > Many thanks in advance, > Chris Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. --Robert E. Howard
[M100] Nc100 was Re: Mcomm
Sounds like the nc100 may be closer to a z88 than m100?Interested in z88 but i don't know much about it...WillardSent from my T-Mobile 4G LTE Device
Re: [M100] status of the m100
On Mon, 26 Aug 2019 19:44:21 -0700 "Kurt McCullum" wrote: > An android phone (or TV Box) can be setup with the mComm app to > emulate a TPDD emulator. But no known solutions for iPhone. > I need to see if my current tablet supports OTG. If it does it might become the portable PDD drive. :-) Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. -- R.E. Howard
Re: [M100] status of the m100
On Mon, 26 Aug 2019 22:51:26 +0300 Serhiy Sosonniy wrote: > Hi, Willard > If I understand correctly, you digitized all your tapes? Opposite direction actually, I was playing .wavs from: http://www.classiccmp.org/cini/systems.htm into my m100 to get the actual files because I am teh 3vi1 P1r@t3 d00d IIRC I got calc and starblaze from somewhere else, but they are on the Net if you look a little (translation: I don't remember where I got them :) 16 bits and a dead man's disk, yo ho ho and a bottle of jolt! Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. -- R.E. Howard
Re: [M100] status of the m100
On Mon, 26 Aug 2019 06:27:27 -0400 Stephen Adolph wrote: > Hi Wllard, > If you know can you tell me > 1. What the firmware installed in rex was before the failure. 4.8 from bitchin100 > 2. What firmware are you using now. r49_m100t102_254_rebuild > > Thx Steve > Not that I'm blaming REX... I think my m100 may be in need of a new NiCAD, and had RAM corruption that hosed the RAM images. :-( -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. -- R.E. Howard
[M100] status of the m100
Haven't said much here lately... Let me see, what m100 stuff have I been doing?... My pocketchip, which was my main pdd server, died. fortunately the day after I backed up all the m100 stuff... :-) My REX corrupted itself and I upgraded to 4.9 when I rebuilt it, files were lost :-( Messed around with the m100 as a terminal. Installed m100 terminfo files. Lynx wants 4 lines of text for its ui? Pathetic!!! ;-) Played a bunch of .wav files at my m100. I do believe I now have almost all the old Tandy tape software. CALC.BA is probably the most useful of the bunch, followed by Starblaze and maybe Personal Finance (I haven't really tried out Specaculator, but if it's as weak as the CoCo version it'll be pretty sad). ;-) I'd read horror stories about trying to load m100 data files from tape, but these worked fine. I guess they weren't large enough to trigger the bugs? Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. -- R.E. Howard
[M100] new files uploaded
m100def-2019-07-22.zip dosm100-2019-07-22.zip asx-m100-2019-07-22.zip uploaded to my website at http://www.sdc.org/~goosey/ (files themselves in ~goosey/m100/) and to my "Willard Goosey" personal library at club100.org m100.def and wp2.def updated with typo fixes and more system variables. ASX code and miniHOWTO updated for ASX 5.2x and newer cross assemblers. Sorry this took so long guys, I've had some serious burnout issues. :-( I'm feeling much better now! Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. --Robert E. Howard
Re: [M100] club100 member uploads?
In article , Kurt McCullum wrote: > The members file area is still working as far as I am aware. I last > uploaded at the end of April. Excellent! New stuff Real Soon Now... :-) Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. --Robert E. Howard
[M100] club100 member uploads?
Last I remember, the member uploads on Club100 was broken. Did that get fixed yet? I have some updates to upload! Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. -- R.E. Howard
[M100] smallc-85 updated
OTOH smallC-85 updated back in January and I missed that... Oops. building now... Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. -- R.E. Howard
[M100] ASX updated
Back in March the ASX assembler suite updated to version 5 patch 31. (I'm gettting better at this, that wasn't an entire year ago! :) Working on updating source and my mini-HOWTO to reflect the new version, but it seems that smallc-85 is still happy with it. Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. --Robert E. Howard
Re: [M100] In the hospital
In article <5d31dc4b.2050...@gmail.com>, Ken Pettit wrote: > Hey Gang, > I had to come to the hospital again on Wednesday because of cardio > issues. After the angiogram yesterday, the Dr. told me I need bypass > surgery, which they will schedule for sometime early next week. I'm > still hanging out here while waiting, which is kinda why I have time to > send emails on the list :) Good luck! Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. --Robert E. Howard
Re: [M100] Posits versus floating point
In article , John R. Hogerhuis wrote: > I noticed Woz's 6502 code is well commented and on the web. It looks like > it uses a binary mantissa. If you're looking for an 8080 fp lib, the one extracted from Lawrence Livermore Labs BASIC (LLLBASIC) has a pretty good rep. The one inside Processor Technology FOCAL, OTOH, is notoriously inaccurate. :(Yes this is the one I keep threatening to port to m100/wp2 ): I don't really know how "good" the fp libs in C/80 and BDS C are... > I guess the value of (packed) BCD is multiply / divide by 10 is a bit > shift operation. And base 10 rounding operations are straightforward. BCD is somewhat wasteful of RAM, (1 bit per digit usually unused) but yes, it makes decimal math much more predictable. Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. --Robert E. Howard
Re: [M100] Posits versus floating point
In article , John R. Hogerhuis wrote: > Actually thinking some more about it, why would BCD floating point code > be more compact even in ROM? I haven't really looked, but the 8085 might be at nearly as efficient at BCD as pure binary. Also, the M100 was the "Micro Executive WorkStation", and as a "business machine" it was marketed at people more interested in having money values add up properly (which BCD is good at) than having small/fast ROM. And those posits sounded like they'd be complicated to implement. I'm sure not going to do a posit lib for 8080. -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. --Robert E. Howard
Re: [M100] Posits versus floating point
In article <5d2f2bc9.4010...@gmail.com>, Ken Pettit wrote: > Hey John, > I was reading the posts about posits ... pretty interesting. > But the Model T ROM doesn't actually use IEEE floating point format ... > It uses a format where the first byte contains the sign bit and 7-bit > exponent, followed by 3 or 7 bytes of BCD encoded data. For the > exponent, 40h represents "zero". In single precision, pi would be (all > hex): I was thinking that, but I wasn't sure and didn't want to be Wrong On The Internet again this week. :-) My friend Lex is involved in HPC research. I pointed this out to him and his response was "meh". Personally, I'm very much not in love with IEEE floats. Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. --Robert E. Howard
Re: [M100] teeny-linux
In article , John R. Hogerhuis wrote: > On Wed, May 22, 2019, 7:54 AM Ron Klein wrote: > > Hi John, > > > > Thank you for the info! > > > > I'm not opposed to mono at all -- I'm trying to use this on a Raspberry Pi > > and didn't want the overhead of a mono environment. Perhaps that's not > > even an issue for the Pi. > > It really isn't. The runtime isn't really that huge a download. LaddieAlpha runs fine on the Pi. Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. --Robert E. Howard
Re: [M100] copying dvi system disks
An annoying, if understandable, quirk!willardSent from my Galaxy Tab® A Original message From: Brian White Date: 5/14/19 11:42 PM (GMT-07:00) To: Model 100 Discussion Subject: Re: [M100] copying dvi system disks Just to clarify, when you copy the 100/200 disk with a 200, the resulting copy works on both 100 and 200, just like the original.If you have a DVI, and the 100/200 version of the system disk, try use only a 200 to make copies of that disk. If you only have a 100 or 102, and you obviously need to make copies for your own use since you want to minimize wear on the original, at least make sure they are labeled as no good for use with 200, even though the original is, and even though there are files for 200 on it, and it looks just like the original in all ways.-- bkw
Re: [M100] test
Admittedly I was starting to wonder, myself...still pulling overtime, no time/energy for m100 :-(willardSent from my Galaxy Tab® A Original message From: Kurt McCullum Date: 5/14/19 9:33 PM (GMT-07:00) To: m100@lists.bitchin100.com Subject: Re: [M100] test Yes the list is active. Often VERY active. It's been quiet for a couple days but it's definitely still alive and well.KurtOn Tue, May 14, 2019, at 6:24 PM, Ed Graffius wrote:IS this still active? I am looking for any type of forum where I can ask a few M100 questions...
Re: [M100] Tandy WP-2
In article , Anthony Coghlan wrote: > does odd things, such as jumping to another nearby part of the text. I haven't had that happen. Weird. > work well. I share Willard's concern that it may be a challenge to do > much more from a programming perspective on the WP-2, though. It has a fairly decent ROM interface... But it has no tolerance for bugs in its .CO files at all! Any mistake, and it's a visit to Cold Start City. :-( It really seems like it has some rules about binary files that were never explained... Sometimes a binary will run directly from the RAM disk, and other times it will only run from main memory... Binaries tend to change size as they get copied between PDD/RAMdisk/memory. It's very frustrating. Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. --Robert E. Howard
Re: [M100] Tandy WP-2
In article , Abraham Moller wrote: > Hi all, > I had a few questions about the Tandy WP-2. How many here have used the > machine? It seems like a nice upgrade from the Model 100, although the > lack of BASIC is a disappointment. The 80x8 display, XMODEM capability, > and 128K drop-in RAM upgrade seem like the main advantages. It also > looks like Forth and an Infocom interpreter have been ported to the > machine. As a computer, the WP-2 isn't that great... The 80x8 screen is very slow, and XMODEM only works at 1200 bps. the 128K RAM can only be used as a RAM disk, not regular z80 memory. > Has anyone here used or upgraded WP-2 CamelForth (besides John Hogerhuis, > of course)? It looks promising, and disk I/O plus inline assembler would > make it really strong. I've never been a forth guy, I'm afraid. :-( My WP-2 is an early one with the scroll bug described in the CamelForth docs. I got that far in CamelForth and that was about it. > Also, does anyone on the list have the source for > the WP-2 zxzvm Infocom interpreter (Christopher from randomvariations.com > ported it, but I can't find his email address anywhere)? AFAIK no one does. :-( > Is the WP-2 worth it for tinkering? Has anyone developed other apps for > the WP-2? There are a few utilities in the M100 CIS archive (via club 100). I haven't gotten any further than "Hello World" for it myself. An assembly .def file for ASM80/ZMAC, TASM, and AS cross assemblers for WP-2 is part of my m100defs.zip archive. wp2.def has everything I know from the Tech Manual and the CIS archive in it. It's an OK word processor, assuming you either have a live parallel-port printer or a filter to go from wp2 .DO to (WP2 documents are not plain ASCII -- the wiki has the best description). > A Z80 laptop running Forth and zcode interpreter would be > really nice and a great addition to my planned portable computing > exhibit at VCF SE 9.0. If you want a computer to do computery things, it's probably a skip. It's good for taking notes in class, or things of that nature. Good for keeping a journal (main thing mine gets used for), or for doing nanowritemo. Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. --Robert E. Howard
Re: [M100] question regarding floppy disks.
In article , Stephen Adolph wrote: > I'll start by saying this isn't an M100 or TPDD discussion, but just > looking to understand something. > I have a Tandy Coco3 with a 3.5 inch floppy drive. The drive is a > standard PC drive and it is working well. > Does anyone know what's going on? The media itself in a 1.44M disk is different, "denser" in some way. It needs a stronger magnetic field for it to be written reliably. Even with a 1.44M drive, writing at Double Density rather than High Density just isn't going to be reliable. It can be done, yes, tape over the HD hole, but the lifetime of the write will be from hours to weeks. And yes, I found this out the hard way... :-( > thx > Steve -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. --Robert E. Howard
Re: [M100] 100/102 to USB?
In article , > Well we either need more buffer on the Model T side or > (counterintuitively) less buffering on the PC side. Heh, a varient of this got hashed out in, what, the 200x's or the 201x's, with IP flow control. > For FTDI devices on Windows you can set the buffers to trigger > data-ready events on 1 byte. I don't want to, but I guess I should get my hands on a semi-current windows machine. :-( > -- John. -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. --Robert E. Howard
Re: [M100] 100/102 to USB?
In article , John R. Hogerhuis wrote: > My experience is the same. I've found it to be Linux specific. That's why > hardware flow control, or inserting some delays is the only way to avoid > overrun. I wouldn't be surprised if modern MacOS has the same issues. Why not throw a couple Kbytes at the serial driver for buffer? RAM is cheap! > -- John. Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. --Robert E. Howard
Re: [M100] 100/102 to USB?
In article , > I thought this too, but I couldn't get sustainable transfer using > anything above 58e1e (I also tried without the parity check but it > didn't work better). > It seems the serial buffer of the M100 is too small for reliably use > xon-xoff. It's basically bufferbloat on the other side. The PC/Mac/whatev recieves an XOFF and sticks it in a large recieve buffer and goes on with blasting bytes at the M100. By the time it gets around to actually *processing* the XOFF it's already overrun the M100's buffer. :-( Faster serial transfers work best with things like old DOS term programs that don't know about 16650 FIFOs. ;-) I never had any trouble with Procomm under msdos on a 386. Minicom under Linux is nothing but trouble! Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. --Robert E. Howard
Re: [M100] testing new email client
On 14 Feb, goo...@sdc.org wrote: > testing > testing > obm100: I am reminded anew just how fragile the RAM filesystem is. > Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. --Robert E. Howard
Re: [M100] WP-2 screen issue
On Sat, 2 Feb 2019 19:43:32 -0500 Anthony Coghlan wrote: > Not sure what type > of memory cards were used - looks too small to be PCMCIA. Some proprietary old card standard that never caught on. They do apparently show up occasionally on eBay but they're way over-priced because "rare". :-( Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. -- R.E. Howard
Re: [M100] fig-FORTH
On Sat, 2 Feb 2019 11:39:23 -0500 Stephen Pereira wrote: > Subject: [M100] fig-FORTH If you're not intent on starting this from scratch, the old CIS m100 archive (on club100 -- huge 23meg download but worth it!) has a fig-FORTH with various support files in lib-08. There's also a version in the Club 100 UPS archive (old member uploads) (club100.org/library/libups.html -- in comet's section) but it requires the chipmunk floppy drive :-( I'm not a FORTH guy myself, sorry. I can do 1 1 + . but I can't ever seem to get further than that. :-( I don't know offhand of any HEX loaders that load from the serial port but that just means I haven't needed one. ;-) Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. -- R.E. Howard
Re: [M100] Brand new member
On Sun, 27 Jan 2019 15:51:07 -0500 Stephen Pereira wrote: > Hi Willard, and thanks a million for letting me know this! > No problem. > I’ve been pulling my hair out, trying to figure out what I was > missing. Why in the world did it end up this way? Why would folks > make an XMODEM program and advertise it as a way to handle .CO files, I always assumed that the xmodem authors simply didn't have the documentation about writing .CO files available. It turns out that writing .CO files from a .CO is complicated and fragile. (See this list archive over the last (gaaa!) 2 years, where I had MANY questions about making that work...) > but then they don’t? Too weird for me! I am so glad to know that I > am not totally incompetent! > To be fair, it is in the docs for xmodem.ba and xmdpw.ba that they only support transferring ASCII files.. ;-) Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. -- R.E. Howard
Re: [M100] File Buffer Size
On Tue, 27 Nov 2018 07:45:15 -0800 Kurt McCullum wrote: > Thanks Willard, > > I'll take a look at that when I get home. I was testing last night > and I think this may be a TS-DOS issue as well. Humm... I don't believe I have anything on TS-DOS's internals. I'd suggest starting with the bitchin100 wiki. Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. -- R.E. Howard
Re: [M100] File Buffer Size
On Mon, 26 Nov 2018 14:44:44 -0800 Kurt McCullum wrote: > When opening a file in BASIC, a file buffer gets created. Does anyone > happen to know the size of each file buffer? I can't seem to find that > in any of the manuals. > Kurt I believe you mean this... /* from covington map... * - File Descriptor Block (Address Given by VARPTR(#file)) Format - * *Byte: * 0 - File status (0-not open, 1-open for input, 2 open for * output or append) * 2 & 3 - Address of file directory entry * 4 - File device (248-RAM, 249-MoDeM, 250-LinePrinTer, * 251-WAND, 252-COM, 253-CASsette, 254-CRT, 255-LCD) * 6 - Offset from buffer start (see bytes 9) for start of next record * 7 & 8 - Relative position of next 256 byte block from beginning of file * 9 - Start of 256 byte buffer for data transfer */ Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. -- R.E. Howard
Re: [M100] E-mail duplications
On Tue, 13 Nov 2018 09:05:27 -0800 Daryl Tester wrote: > Just the one. Change anything? Excellent. Yeah, when claws-mail puts up the the message edit window the trick is to remove anything from the To: or CC: entry slots. The actual address isn't shown, but it's there. because it's *friendly*. Pfhfhft! > Cheers, >--dt > Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. -- R.E. Howard
Re: [M100] E-mail duplications
On Tue, 13 Nov 2018 07:56:28 +1030 Daryl Tester wrote: > Of your smallC-100 update? Only saw one copy, but I think > it's usually when you're replying to someone else's email > that it happens (having said that, I didn't see two replies > to Ken's email). > So how about dis one? Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. -- R.E. Howard
[M100] ASX also updated!
The ASX assembler suite also updated to version 5.20. It looks like the main thing fixed that is of interest to M100 people is that the linker now has an option to generate type 1 (8-bit data/16bit address) Intel HEX files with a type 1 (16-bit) execution address. (*) I'm going to thrash on this some to make sure it's happy, then I'll have to update my makefiles for the new linker option. (*)I don't know why anyone would do it any other way, but whatever. Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. -- R.E. Howard
Re: [M100] smallC-85 updated
On Sat, 10 Nov 2018 18:45:33 -0800 Ken Pettit wrote: > Man, I wish I had time to think! :) One of these days. > > Ken > :-( I hope work slows down for you soon! Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. -- R.E. Howard
Re: [M100] E-mail duplications
On Sun, 16 Sep 2018 22:35:58 -0600 Willard Goosey wrote: > On Thu, 13 Sep 2018 16:46:45 +0930 > Daryl Tester wrote: Once again hoping for 1 copy of this to go out? -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. -- R.E. Howard
Re: [M100] smallC-85 updated
On Sat, 10 Nov 2018 17:01:51 -0500 Stephen Adolph wrote: > Great stuff! Gotta download and play around with this. > I wish I'd noticed this back in July but even if I had, I wouldn't have had time to mess with it. Work is finally slowing down and I actually have a little time to think now! Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. -- R.E. Howard
Re: [M100] smallC-85 updated
On Thu, 8 Nov 2018 20:38:17 -0700 Willard Goosey wrote: > As of July 19 2018 SmallC-85 has an update! > https://github.com/ncb85/SmallC-85 > > sizeof() works better now... properly reporting the size of pointers > and unsigned types. > Nevermind about sizeof() they fixed all the struct bugs! (I think... testing...) All the stupid stuff that had me stalled now works: 1) Functions can have struct pointers for parameters. 2) Globally declared structs with pointers or arrays inside are allocated correctly. 3) Globally defined structs that aren't declared no longer confuse the compiler. 4) Can now take the address of a struct. So now I'm busy updating documentation and code for m100smallclib. The 8080 still makes me drink Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. -- R.E. Howard
[M100] smallC-85 updated
As of July 19 2018 SmallC-85 has an update! https://github.com/ncb85/SmallC-85 sizeof() works better now... properly reporting the size of pointers and unsigned types. This is the compiler that my m100smallclib project uses. And m100smallclib is not dead, I recently found a quick way to remove another Defect Attractor -- all the ROM calls that had no proper wrapper functions (because they took no arguements and either returned nothing, or returned a value in HL) now have lowercase function names. Therefore you don't need to shout to say things like crlf() :-) I'm still heading for a beta release! Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. -- R.E. Howard
Re: [M100] coco drive thingie was wav format...
Sent from my Galaxy Tab® A Original message From: Jesus R Date: 10/3/18 5:03 PM (GMT-07:00) To: m100@lists.bitchin100.com Subject: [M100] coco drive thingie was wav format... The coco drive is not compatible with the TRS 80 Model 100 per the seller. He also said he has not interest in developing it for the RS T80 Model 100 at this time. Jesus R the coco's serial port is a little quirky. Also if he did write the coco side software he's probably not very excited by the idea of rewriting it in 8085 assembly. Willard
[M100] coco drive thingie was wav format...
Sent from my Galaxy Tab® A Original message From: "John R. Hogerhuis" Date: 10/3/18 1:16 PM (GMT-07:00) To: m...@bitchin100.com Subject: Re: [M100] program library in WAV format " So it's like a PDD server but running its own protocol, not PDD or Drivewire. " He loves standards so much he invented his own ;-) -- John. I kinda fell out of the coco list a couple of years ago, so i don't know this guy or where he got his software, so im gonna say nothing. It is interesting that his(?) software isn't even trying to be Disk BASIC compatible... Willard
Re: [M100] program library in WAV format
The guy has another one for sale, so there's more info... It actually hooks up with the coco serial port and has a driver for BASIC to talk to it. So it's like a PDD server but running its own protocol, not PDD or Drivewire. Willard Sent from my Galaxy Tab® A Original message From: Greg Swallow Date: 10/3/18 7:26 AM (GMT-07:00) To: m...@bitchin100.com Subject: Re: [M100] program library in WAV format Has anyone tried, or looked into, something like this device for the CoCo? https://www.ebay.com/itm/TRS80-CoCo-Hard-Drive-Emulation-128MB-20x-faster-than-tape/332796444857?hash=item4d7c36c0b9:g:yMEAAOSwrCZbKozt:sc:USPSPriority!85120!US!-1 I just don't have $100 to spare just now. God Bless,
Re: [M100] E-mail duplications
On Thu, 13 Sep 2018 16:46:45 +0930 Daryl Tester wrote: > Willard's reply is a classic example - two copies go out, because testing testing 0 1 2 3 Ani Kin had Padme Hummin 256 to the power of testing! so claws mail had the list address listed twice as the list address? Hopefully there will be one and exactly one copy of this posted. Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. -- R.E. Howard
Re: [M100] E-mail duplications
On Wed, 12 Sep 2018 22:56:36 -0700 "John R. Hogerhuis" wrote: > Hello Peter, > > I've never heard of that problem. I guess it's unique to the digest > thingy, which most of us do not use. > No I see it too. Actually I've been getting a little cranky about it! :-( What was happening with me is that, when I reply to the list, instead of being presented with a "To:" address of m...@bitchin100.com it comes up as "CC:". Hence, if I don't manually change it to "To:" I send the list 2 copies of my response. So I have to be careful and manually set the header to "To:". (This is in Claws Mail under Raspian). I imagine other pretty pretty GUI apps are doing the same thing. I think it's trying to send the response to the originator (m100 list) and also to everybody else (m100 list...) So yeah, it would be appreciated if posters would take the time to make sure the post is To: m100... and not CC: m100 Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. -- R.E. Howard
Re: [M100] m100smallclib : Defect Attractor! prsnam()
On Sat, 2 Jun 2018 09:25:32 -0700 "John R. Hogerhuis" wrote: > 2nd rule of optimization is also don’t. > > 3rd rule of optimization: Not yet! 4th rule: Look at the actual costs first. The changes would save 2 entire t-states (1 whole clock tick). Not worth it. ;-) Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. -- R.E. Howard
Re: [M100] compact embedded ML coding
On Fri, 1 Jun 2018 07:36:32 -0500 John Gardner wrote: > ...pop B... 6809? > > Hi Willard - > > 70C20, actually. I'm not smart enough for 808X."8) Assembly in 808x isn't about smart, it's about having the patience to look up every other instruction in a book. ;-) The classic example: mvi b,0 ; move the 8bit value 0 into b lxi b,0 ; move the 16bit value 0 into bc Assembly programming. Because some people enjoy pain. :-) Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. -- R.E. Howard
Re: [M100] compact embedded ML coding
On Fri, 1 Jun 2018 07:20:52 -0400 Stephen Adolph wrote: > Sure no problem. Let me know what you need > Whatever program you use to convert the hex file into the data statements. hex2co is all well and good but without a pdd client CO files are definitely harder to move to M100... Thanks! Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. -- R.E. Howard
Re: [M100] m100smallclib : Defect Attractor! prsnam()
On Fri, 1 Jun 2018 06:10:07 -0400 Josh Malone wrote: > Sounds quite reasonable to this novice c coder :) > Done, then! (Except for the Obvious Optimization that I just noticed... But then I'd have to recompile and run all the test programs that call prsnam() again. Not tonight!) First rule of Optimization: Don't. Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. -- R.E. Howard
[M100] m100smallclib : Defect Attractor! prsnam()
OK, though I've been pretty distracted I'm still moving towards a beta release for the SmallC lib. I want to be able to freeze the interface so that there will be backwards compatibility from any further versions. ESR recently made a blog post about "Defect Attractors" -- design features that are easily misused or otherwise sort-of encourage bugs. As you can imagine, shims from one language to another (say, an assembly ROM API to a C lib...:) are big offenders here, if only because the mindset of the "hidden" language still tends to be visible in the interface and that's jarring. I've been thinking about this, and one function in particular keeps jumping to my mind. prsnam(). The current prototype is prsnam(char *s, int i) parses a file.do filename into the FILNAM system variable as FILE DO s=filename i=length of filename. And I see a Defect Attractor here! If a proper C function wants to know the length of a string it calls freaking strlen() on it. It does not expect the caller to do its job for it. So I propose to replace it with prsnam(char *s) that will call strlen() itself, making the interface a little simpler and removing a Defect Attractor. Any thoughts? Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. -- R.E. Howard
Re: [M100] compact embedded ML coding
On Thu, 31 May 2018 12:22:43 -0700 "John R. Hogerhuis" wrote: > Here is the classic 8085 relative jump for those interested. > > It requires some code at a fixed location :-) Classic cleverness! Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. -- R.E. Howard
Re: [M100] compact embedded ML coding
On Thu, 31 May 2018 14:15:19 -0500 John Gardner wrote: > Your code can figure out it's execution address with something like: > > call @Boo > Boo pop B > pop A > > Boo's address is now in register pair A,B... > Umm, on a point of order... I see what you're saying there, and neat trick! But... pop B pulls a 16bit value off the stack into BC pop A is (probably) going to be a syntax error. It would be "pop psw" in Intel or "pop AF" in Z80 and anyway not what you want. This isn't a 6809, you can't pop into (A,B). :-( So what you want to say is... [boring 8080 code] call boo boo pop b ; BC = address of boo [more code] Code in Assembly, and grow strong Willard -- Willard Goosey goo...@sdc.org Socorro, New Mexico, USA I search my heart and find Cimmeria, land of Darkness and the Night. -- R.E. Howard
