Quick correction, if you don't have a Z80 rst 7 is gonna end poorly - try rst 6 instead. Only see these things AFTER hitting send..
Start DDT A100 # Start assembly at location $100 mvi c,2 # Put 2 in the C-register for Console Out mv e,48 # $48 is ASCII H call 5 # entry point for all system calls (BDOS) mvi c,2 # Put 2 in C-register for Console Out mvi e,49 #$49 ASCII I call 5 # BDOS call again rst 6 # return to DDT g100 to execute, should print something like "HI" with memory location after. Still tons of fun! On Sat, Mar 16, 2024 at 4:03 PM Brian Brindle <bbrin...@gmail.com> wrote: > Simple DDT "HI" program - can be expanded to "hello world" if ambitious > enough. > > Start DDT > A100 # Start assembly at location $100 > > mvi c,2 # Put 2 in the C-register for Console Out > mv e,48 # $48 is ASCII H > call 5 # entry point for all system calls (BDOS) > mvi c,2 # Put 2 in C-register for Console Out > mvi e,49 #$49 ASCII I > call 5 # BDOS call again > rst 7 # return to DDT > > g100 to execute, should print something like "HI" with memory location > after. > > Tons of fun! > > Brian > > > > On Sat, Mar 16, 2024 at 3:12 PM Will Senn <will.s...@gmail.com> wrote: > >> Brian, >> >> Definitely. DDT is great. I'll be working through that next. I finally >> got a program working and assembled - from the 2.2 manual - read chars >> until *. Now, I just gotta get hello, world working.... I was sure, it >> would work... oh, wait, when it says to CALL CPM, I bet it's not talking >> about where CP/M is DE1EH... I bet it's that 0005H entry point... off to >> explore. >> >> Will >> >> On 3/16/24 1:08 PM, Brian Brindle wrote: >> >> If you just want to play, don't discount ddt in CP/M. Cheap and dirty way >> to play with everything. >> >> On Sat, Mar 16, 2024, 1:48 PM Stephen Adolph <twospru...@gmail.com> >> wrote: >> >>> regarding file transfer, use >>> IMPORT >>> or >>> EXPORT >>> in CP/M. Included in package. >>> These programs access a "TPDD". Filenames are 8.3 format, >>> >>> cheers >>> Steve >>> >>> On Sat, Mar 16, 2024 at 1:36 PM Will Senn <will.s...@gmail.com> wrote: >>> >>>> I broke down and started reading the manuals (REXCPM, CP/M 2.2, etc). >>>> It's starting to come together (again?)... I've inlined the answers I >>>> figured out for posterity or the next clueless newb who comes along. >>>> >>>> On 3/16/24 11:00 AM, Will Senn wrote: >>>> >>>> 2. CP/M works from RexCPM, which is great, cuz CP/M recognizes more >>>> memory: >>>> >>>> 64K CP/M 2.2 M100 CP/M + REXCPM 2MB 1.0 >>>> >>>> Yes, it does recognize more memory and it serves up an A: drive that's >>>> a big chunk of that 2MBs. Solid. Talked about here: >>>> http://bitchin100.com/wiki/index.php?title=M100_CP/M >>>> >>>> My questions are as follows: >>>> >>>> 4. In CP/M, how do I get back to MENU? >>>> >>>> Duh, F8 :). >>>> >>>> 5. When I start CP/M, is it just running CP/M against the M100's memory >>>> or am I in some special whizbang virtual environment where I have >>>> additional disks available somehow? >>>> >>>> It's a whizbang environment for sure - 64K ram and a nearly 2MB A: >>>> drive. >>>> >>>> As for my broken ASM, another duh, thanks John for the tip - I need to >>>> write a CP/M friendly program that call it's routines and not the ROM >>>> calls. >>>> >>>> CP/M seems the way to go, though. It kinda reminds me of RT11, but with >>>> ASM instead of MACRO11. ed... well, after you figure out that you need to >>>> retrieve the file contents into the buffer, it kinda makes sense - nice >>>> video - I love ED: >>>> https://www.youtube.com/watch?v=7pqaj050X7g >>>> >>>> Still need to figure out how to get files into and out of cp/m though... >>>> >>>> Off to read some more. >>>> >>>> -will >>>> >>> >>
