| |
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....
|
| |
chatGPZ
Registered: Dec 2001
Posts: 11386 |
yay, missed this. thx :) |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
Quote: simple crossdev packer? cld by tlr
cbmtools 0.6
I'll assume you're talking about pucrunch.
Personally I've found that simply injecting a 202 blocks file into VICE (or a d64 image) is a lot quicker than whatever crucher/decruncher solution. Even RLE doesn't beat loading the full data while skipping TDE. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11386 |
as long as 202 blocks works, sure - however in demo you often want to use d000-ffff too, and then the problem starts :) |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
Well, I'll handle that when I need to. Already have something planned that's going to need the full 64K stuffed with data, so it might be sooner rather than later.
In the old days I would simply code in the ML monitor of my cartridge when I needed all the memory, which is something I'm going to avoid at all cost ;) |
| |
Krill
Registered: Apr 2002
Posts: 2980 |
Quoting CompyxThat, I understand, fastloaders need a different sector interleave and such. I guess I was a bit surprised by the code itself, such as calling strlen() in a loop and an uncomfortable mix of C and C++.
I'm pedantic, I know ;) Granted, it's not pretty. Just a tool quickly hacked together to do its job. And at some point it will read and write that 50x fastload format i have yet to actually turn into working code. :)
But back on topic: Wouldn't it be possible to pipe commands and files into a running VICE instance, such as a reset-load-run combination? For me, VICE startup times themselves feel pretty long already, no matter if auto-running a program or not. |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
I think the remote monitor feature of VICE could be useful, I haven't looked into that yet. If I could inject the new code and data into a running VICE instance from VIM (:make x64) that would seriously cut down on start-up time.
The assembler I use is very fast (64tass), c1541 is also pretty quick, starting VICE is the biggest bottleneck.
Guess I'll have to grep my way through the gazillion command line options x64 has ;) |
| |
iAN CooG
Registered: May 2002
Posts: 3194 |
long time on startup is mostly taken by the ram test at $fd50. use a cart like TFR or patch your kernal rom like this (fc /b output)
00001D60: 3C 00
00001D69: 03 9F |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
Quote: long time on startup is mostly taken by the ram test at $fd50. use a cart like TFR or patch your kernal rom like this (fc /b output)
00001D60: 3C 00
00001D69: 03 9F
Please forgive my ignorance, but what is TFR, my guess would be something like 'the final replay'? |
| |
iAN CooG
Registered: May 2002
Posts: 3194 |
exactly that |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
Yup, a google search had already answered my own question ;)
I will check it out after I come back from work.
I also managed to get the remote monitor working, with telnet I can inject data into memory, attach disk images, and much more.
Some serious hacking for a simple graphics editor :) |
| Previous - 1 | 2 | 3 | 4 | 5 | 6 | 7 - Next |
