| |
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 |
its not an undocumented feature at all (try "help" in the monitor, for example :=))
Quote:Build by copying then modifying a known working base snapshot image, and you should be fine. Works well for me, at least.
the problem is that snapshot loading alters the entire machine state - and how it does that exactly. the only way to have a defined proper machine state after it is resetting the machine.
i went through a couple iterations of different ways of starting my binaries in emu - and now i am back to plain old autostart, and that with enabled "copy file to d64" - because everything else gave me unexpected results at least once. |
| |
Perplex
Registered: Feb 2009
Posts: 255 |
It very seldom leads to unexpected results that are not obviously wrong, though. In which case a simple rebuild will solve it. It works close to 100% of the time, and lets me see the results about .1 seconds after I start building. If it fails a rebuild helps in most cases, and if not I can always quit the emulator and start normally. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11386 |
Quote:It very seldom leads to unexpected results that are not obviously wrong, though.
really depends on what you are doing. and it may not be so obviously wrong afterall - and thats when the trouble starts. i gladly trade a second wait time for that uncertainty :=) |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
I'll stick to injecting my program into a disk image with other test files and then running VICE. I need a 'clean' machine state to properly test my code. My code does a lot of IRQ setup/teardown and $01 manipulation (it's a custom graphics editor)
I'll check out the remote monitor feature, might be interesting if I can get it to work from within VIM. |
| |
Burglar
Registered: Dec 2004
Posts: 1101 |
Check this article I wrote a while ago, should be useful in your case, it's got d64 creation in the full example.
http://codebase64.org/doku.php?id=base:cross_development_using_.. |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
I already read that article a while ago ;)
My makefile looks similar to the one in the article, including image creation with c1541. I'm skipping the exomizer bit for now, both crunching and decrunching take way too long for a fast assemble-run-debug cycle. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11386 |
thats why i use pucrunch while deving :) |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
Didn't try that one. I'm going to assume it's faster than exomizer. Exomizer is as fast as shit going through a coffee filter (Dutch figure of speech). |
| |
chatGPZ
Registered: Dec 2001
Posts: 11386 |
yes, it packs a LOT faster (instant on my box) and depacking is also a bit quicker.
that said, i wonder why noone made a simplier (crossdev)packer that is optimized for speed only (and the only purpose would be being able to make RUNable programs from stuff that loads outside 0801-cfff). something to put on the never ending TODO list, i guess =) |
| |
iAN CooG
Registered: May 2002
Posts: 3193 |
simple crossdev packer? cld by tlr
cbmtools 0.6 |
| Previous - 1 | 2 | 3 | 4 | 5 | 6 | 7 - Next |
