Unbelievable, I installed Strawberry Perl on Windows and then I saw the debugger trick!
That teaches me a lesson. Anyway, for future search-engine visitors, here is what I successfully did:
Opened the debugger and wrote this:
file r 2000 C:\Users\home\Desktop\myfile.txt
(it doesn't work with quotes around the file path, which is interesting -- but I didn't have time to check vulnerabilities)
And then verified with this (and thanked God I didn't have to write PEEK):
1 FOR N=&2000 TO &4000: PRINT CHR$(?N);: NEXT
In addition: I have created a "feature request" issue on the BeebEm GitHub project, because I believe it would be useful to allow byte import from the GUI (without using debugger) -- not a huge deal, but a nice idea:
https://github.com/stardot/beebem-windows/issues/141
The real problem in the end was deciding which address I could load my file to. On the Speccy (I know you are sick of hearing about the Spectrum) the memory map is usually ROM + screen display + BASIC system variables + whatever you want. Anywhere above screen memory (23296) you may stomp your muddy wellingtons, although it might trash the BASIC editor or make your printer upset.
The Beeb was the Plug'n'Play of the 80s. I saw in the manual they said (something like) "never write directly to the screen area, always use the OS--OSWRCH,OS--something". I'm drunk. But they were TEN YEARS ahead of their time. It was a great machine.
Whenever I look at the Beeb maps I'm just like "oh my god this is a huge confusing list of Tube and DFS and -- where can I actually put anything". That's because I'm stupid.
Best wishes. I'll come back when I finish that Droom port. (and you will be right in saying "OMG it's a Huffman-compressed bitmap, instead of the beautiful vector draw we had in BBC BASIC." Shut yer mouth, it had to be done, I didn't grow up with a polygon you could fill.)
That teaches me a lesson. Anyway, for future search-engine visitors, here is what I successfully did:
Opened the debugger and wrote this:
file r 2000 C:\Users\home\Desktop\myfile.txt
(it doesn't work with quotes around the file path, which is interesting -- but I didn't have time to check vulnerabilities)
And then verified with this (and thanked God I didn't have to write PEEK):
1 FOR N=&2000 TO &4000: PRINT CHR$(?N);: NEXT
In addition: I have created a "feature request" issue on the BeebEm GitHub project, because I believe it would be useful to allow byte import from the GUI (without using debugger) -- not a huge deal, but a nice idea:
https://github.com/stardot/beebem-windows/issues/141
The real problem in the end was deciding which address I could load my file to. On the Speccy (I know you are sick of hearing about the Spectrum) the memory map is usually ROM + screen display + BASIC system variables + whatever you want. Anywhere above screen memory (23296) you may stomp your muddy wellingtons, although it might trash the BASIC editor or make your printer upset.
The Beeb was the Plug'n'Play of the 80s. I saw in the manual they said (something like) "never write directly to the screen area, always use the OS--OSWRCH,OS--something". I'm drunk. But they were TEN YEARS ahead of their time. It was a great machine.
Whenever I look at the Beeb maps I'm just like "oh my god this is a huge confusing list of Tube and DFS and -- where can I actually put anything". That's because I'm stupid.
Best wishes. I'll come back when I finish that Droom port. (and you will be right in saying "OMG it's a Huffman-compressed bitmap, instead of the beautiful vector draw we had in BBC BASIC." Shut yer mouth, it had to be done, I didn't grow up with a polygon you could fill.)
Statistics: Posted by equinox — Tue Nov 12, 2024 1:48 am