| |
mankeli
Registered: Oct 2010
Posts: 146 |
Spindle and Sparkle demos not launching
Can someone explain why demos using Sparkle or Spindle loaders can't be run from 1541U by selecting the launch file and using "mount & run"?
You got to use "Run Disk" for the whole image. 99.9999% of the C64 demos can be launched with mount & run, and somehow this only seems affect those aforementioned loaders. |
|
... 60 posts hidden. Click here to view all posts....
|
| |
tlr
Registered: Sep 2003
Posts: 1790 |
Quote: It's because of the disk ID bytes at drive memory $12/$13. A shortcut is given to execute an FDC read job, which at some point compares on-disk ID to what is expected, but what is expected hasn't been set and is just $00, so error 29 Disk ID Mismatch occurs.
Interesting! So how does this work on regular load? It still uses FDC read jobs so who sets up $12/$13?
There is the BAM flag at $1c which indicates we are not initialized so I guess that is involved somehow? |
| |
tlr
Registered: Sep 2003
Posts: 1790 |
Quote: Interesting! So how does this work on regular load? It still uses FDC read jobs so who sets up $12/$13?
There is the BAM flag at $1c which indicates we are not initialized so I guess that is involved somehow?
To answer my own question: The id always gets set up when doing a SEEK ($b0).
A regular load seems to always do initialize in the beginning of the directory search, but for loaders that do not use this a SEEK is sufficient.
That job code handling is done by the $45 check at $f3ec. |
| |
Krill
Registered: Apr 2002
Posts: 2981 |
Quoting Martin PiperI remember now, it was the transwarp example that issues a M-E with the partial just loaded file in the read buffer: Transwarp V0.84 Yes, that's part of the 2-blocks bootstrap fastload strapped in front to speed up booting the actual loader.
Was 1-block in early dev versions, but that turned out to be too slow for my purposes. =)
(You can always fall back to loading Transwarp itself via ,8+RUN not ,8,1 when autorun won't work for some reason.)
As for the problems described here, i like the concept of a multi-loader coming in a self-contained package in C-64 memory, that would function just fine when run immediately after drive reset, new disk etc. :)
Then again, no particular love for non-stock aftermarket hardware. |
| |
Burglar
Registered: Dec 2004
Posts: 1105 |
Quoting mankeliThis happens on U64 too. (Ultimate 64 Elite V1.43 - 3.11) Aerial Core for example doesn't work with mount & run, it needs run disk.
Areal Core has its own issues, it does not load on a stock c64+1541 without cartridge due to the dirart and not having the boot prg as first file.
trying to load the prg will give file not found, unless you modify the filename with ? and * |
| |
Krill
Registered: Apr 2002
Posts: 2981 |
Quoting Burglarit does not load on a stock c64+1541 without cartridge due to the dirart and not having the boot prg as first file.
trying to load the prg will give file not found, unless you modify the filename with ? and * Time to add that "disk image linting" to cc1541 we talked about recently. =) |
| |
tlr
Registered: Sep 2003
Posts: 1790 |
Quote: Quoting Burglarit does not load on a stock c64+1541 without cartridge due to the dirart and not having the boot prg as first file.
trying to load the prg will give file not found, unless you modify the filename with ? and * Time to add that "disk image linting" to cc1541 we talked about recently. =)
Great idea! |
| |
Martin Piper
Registered: Nov 2007
Posts: 726 |
Quote: Quoting Martin PiperI remember now, it was the transwarp example that issues a M-E with the partial just loaded file in the read buffer: Transwarp V0.84 Yes, that's part of the 2-blocks bootstrap fastload strapped in front to speed up booting the actual loader.
Was 1-block in early dev versions, but that turned out to be too slow for my purposes. =)
(You can always fall back to loading Transwarp itself via ,8+RUN not ,8,1 when autorun won't work for some reason.)
As for the problems described here, i like the concept of a multi-loader coming in a self-contained package in C-64 memory, that would function just fine when run immediately after drive reset, new disk etc. :)
Then again, no particular love for non-stock aftermarket hardware.
I really liked the way that bootstrap code started executing on the C64 then switched over to the fastload. |
| |
mankeli
Registered: Oct 2010
Posts: 146 |
Quote: Quoting mankeliThis happens on U64 too. (Ultimate 64 Elite V1.43 - 3.11) Aerial Core for example doesn't work with mount & run, it needs run disk.
Areal Core has its own issues, it does not load on a stock c64+1541 without cartridge due to the dirart and not having the boot prg as first file.
trying to load the prg will give file not found, unless you modify the filename with ? and *
Oh, thanks for reporting!
Getting the dirart to even work was a huge pain ^^
But yeah atleast the problem got narrowed down to Basic LOAD leaving some state to 1541 which Spindle then depends on. As an another example Skybox doesn't work with mount and run either, and it probably has dirart as DEL Files. |
| |
tlr
Registered: Sep 2003
Posts: 1790 |
Quoting mankeliBut yeah atleast the problem got narrowed down to Basic LOAD leaving some state to 1541 which Spindle then depends on.
As LordCrass identified, it's only the disk ID that is not set up. This could be fixed in the M-E bootstrap code such that a seek is done before the reads. I think that could fit.
For an inject run strategy to work with the current code, the 1541 needs to be configured with this disk ID as a minimum. |
| |
WVL
Registered: Mar 2002
Posts: 903 |
Wouldn't it be the job of 1541u/u64 to set up the drive correctly with the right ID set? This sounds fixable to me.
Then again, I know nothing about drive code and don't understand why the disk ID would matter anyway? And what is linting (is that the disk structure with one t/s pointing to the next t/s?).
The last time I did anything with that is when I made cd1541 to make the d64 for pearls for Pigs (because cc1541 didn't support 40 tracks back then). Or.. actually I think jackasser added 40 track just in time in cc1541 and I still made my own tool which I can't seem to compile anymore...
So what I wanted to say : if I can make my own d64 creation tool knowing almost nothing about d64 and drives, then others will have done so too. The result: d64's with lots of small problems. A tool to check a d64 would be helpful. |
| Previous - 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 - Next |
