| |
Compyx
Registered: Jan 2005
Posts: 631 |
VICE: attach disk image and run .prg file from OS filesystem
With VICE (2.4.27 on Linux), I'm trying to figure out how to attach a D64 image to drive 8 (with TDE) while running a .prg file from my OS file system.
I've tried a wide variety of command line options, but I either get a message about extra arguments on the command line, or VICE tries to load the .prg file from the attached disk image, which obviously fails as well.
Does anyone know how to do this? I'm trying to keep my assemble-run-debug cycle as fast as possible.
/Compyx |
|
... 56 posts hidden. Click here to view all posts....
|
| |
Compyx
Registered: Jan 2005
Posts: 631 |
After playing around with the remote monitor some more, I noticed that by ignoring the BASIC interpreter, any code I run that doesn't set up IRQ's results in the code executing with a nice blinking cursor on screen (the BASIC interpreter's IRQ is still in edit mode).
This of course has to do with skipping the interpreter, so I now inject a BASIC program with the remote monitor and set the proper pointers in $2b/$2c (can probably be omitted) and $2d/$2e. I can now LIST the program and RUN it in VICE. But I don't seem to be able to find the correct location in BASIC/KERNAL to execute a proper RUN from the monitor.
So my question is, how do I properly hook into the BASIC interpreter so I can RUN a program as if I typed 'RUN' and, after executing my program, get the interpreter back in edit mode? |
| |
Burglar
Registered: Dec 2004
Posts: 1101 |
jsr $a659
jmp $a7ae |
| |
Frantic
Registered: Mar 2003
Posts: 1648 |
Compyx: Yes, please write something about it for Codebase! Should go into the cross development part of the wiki I suppose:
https://codebase64.org/doku.php?id=base:crossdev |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
Nope, I get a nice READY prompt, but my program isn't executed, nor is it there any more when I do a LIST.
You might be onto something though, I don't get stuff like ?undef when I tried jumping straight into the handlers for GOTO, GOSUB and RUN. Probably need to set a few more pointers. |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
Quote: Compyx: Yes, please write something about it for Codebase! Should go into the cross development part of the wiki I suppose:
https://codebase64.org/doku.php?id=base:crossdev
I will, already working on it mentally ;) |
| |
Burglar
Registered: Dec 2004
Posts: 1101 |
well I dunno mate, I was just guessing ;)
but why all the basic-fuckage? |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
I enjoy it :)
Well, not really. Basically (pun intended) I need VICE to act as if it was doing an auto-start, without actually doing an auto-start since I use a running VICE session, if that makes any sense.
My VICE session works fine with 'demo' code: code that sets up IRQ's and never returns. The problem is code that returns to the interpreter and doesn't alter IRQ's. Since I inject code into VICE and use a 'g $xxxx', BASIC has no idea I just executed a program and remains in interactive mode. With a bloody blinking cursor as result, even for 'jmp *'. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11386 |
if you want to behave it like autostart, then you HAVE to issue a reset, and then load/run the program (eg by putting the respective commands into the keyboard buffer). anything else will behave subtle different (unless you put massive effort into putting the machine into the same state). |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
Using the keyboard buffer might just work! Last time I did that was in Fisher-Price OS, and since BASIC V2 is also made by that same company, who knows? ;) |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
Amazingly, filling the keyboard buffer with 'RUN\r' and setting its length to $04 works.
My little BASIC program executes and returns properly.
Thanks Groepaz! |
| Previous - 1 | 2 | 3 | 4 | 5 | 6 | 7 - Next |
