Closed vrs42 closed 2 years ago
Yes, the PIP command concatenates the files. The resulting BASIC.SV should be 73 blocks long IIRC.
The TM.TM is just a 17 block file that serves as a scratch area for OMSI Basic. Any 17 block file would work but it must be 17 blocks long. The editor saves the current program source in that area when you compile or run it, as the compiler and runtime walk over the core copy of it. When execution completes and it returns to the editor, the source is reloaded from there.
COMPIL.SV and RUN.SV are overlays (with a couple of overlays overlaid on them) and the system knows where they are within the BASIC.SV file.
If you build this on your system device, try
. R BASIC
<should print "READY">
10 print "Hello World!" 20 end run
and the result is predictable.
Yes, it can all be lower case as typed above.
What happened when you tried R BASIC? (or RUN if you built it on another disk or tape?). It should type "READY" at you ...
It did type ready, and I can type in the program, but it just crashes when I type "run".
My basic.sv is 79 blocks long, not 73.
I also have an omsi30.sv which is 77 blocks long, which does seem to work.
Vince
omsi30.sv is something entirely different.
What are the lengths of edit.sv, tm.tm, compil.sv, and run.sv on your system?
On Sun, Mar 27, 2022 at 6:46 PM vrs42 @.***> wrote:
It did type ready, and I can type in the program, but it just crashes when I type "run".
My basic.sv is 79 blocks long, not 73.
I also have an omsi30.sv which is 77 blocks long, which does seem to work.
Vince
— Reply to this email directly, view it on GitHub https://github.com/dhogaza/omsi_basic/issues/1#issuecomment-1080095969, or unsubscribe https://github.com/notifications/unsubscribe-auth/APSGK36RNN7TTL22KRXPWWDVCEFPZANCNFSM5RZOTT6A . You are receiving this because you commented.Message ID: @.***>
-- Don Baccus
I can see that my tm.tm has ended up 23 blocks, not 17, so that's probably where the problem is.
Edit.sv is 10 blocks, compil.sv is 17, and run.sv is 24 blocks.
Fixing the length of my tm.tm (I copied compil.sv over it) seems to have fixed the problem.
Thanks!
Vince
Whatever file you need for filler needs to be 17 blocks, as documented. It's dying when trying to compile (before running) your program because it as overlayed the last six blocks of your filler file followed by compil.sv, then transferred control to those blocks of your filler file.
It will work once you get get the right sized filler file.
Did github mess up tm.tm?
On Sun, Mar 27, 2022 at 6:56 PM vrs42 @.***> wrote:
Edit.sv is 10 blocks, compil.sv is 17, and run.sv is 24 blocks.
— Reply to this email directly, view it on GitHub https://github.com/dhogaza/omsi_basic/issues/1#issuecomment-1080099632, or unsubscribe https://github.com/notifications/unsubscribe-auth/APSGK36LE6YHRGLYB2M7QWDVCEGVXANCNFSM5RZOTT6A . You are receiving this because you commented.Message ID: @.***>
-- Don Baccus
Yeah it is a bit sensitive in how it is built. This is PDP-8 software, after all :)
Check out the os8pip program which now works great on OS/X. Should work fine in Linux, too. And since I'm compiling with CLANG and -std=c11 should (crosses fingers) compile with recent MS C compilers, too. I'm only running it on OS/X at the moment, though.
On Sun, Mar 27, 2022 at 7:31 PM Don Baccus @.***> wrote:
Whatever file you need for filler needs to be 17 blocks, as documented. It's dying when trying to compile (before running) your program because it as overlayed the last six blocks of your filler file followed by compil.sv, then transferred control to those blocks of your filler file.
It will work once you get get the right sized filler file.
Did github mess up tm.tm?
On Sun, Mar 27, 2022 at 6:56 PM vrs42 @.***> wrote:
Edit.sv is 10 blocks, compil.sv is 17, and run.sv is 24 blocks.
— Reply to this email directly, view it on GitHub https://github.com/dhogaza/omsi_basic/issues/1#issuecomment-1080099632, or unsubscribe https://github.com/notifications/unsubscribe-auth/APSGK36LE6YHRGLYB2M7QWDVCEGVXANCNFSM5RZOTT6A . You are receiving this because you commented.Message ID: @.***>
-- Don Baccus
-- Don Baccus
Hello!
I realize you aren't finished working on this yet, but I thought I'd try to build it anyway. I ran the commands in "build.bi" and I got an executable, but it doesn't do much.
I'm particularly puzzled by the PIP command: *BASIC.SV_BASEDT.SV,TM.TM,COMPIL.SV,RUN.SV/I which I thought would just concatenate the input files, but seems to have done something else.
Also, what is TM.TM? From the PIP command I thought it would be in .SV format, but it isn't.
Thanks,
Vince