| |
Krill
Registered: Apr 2002
Posts: 2969 |
Release id #118713 : Krill's Loader, repository version 146
Please post feature requests, bug reports, questions etc. here.
Highest priority on my to-do list are speed enhancements, anything else you'd like for your next stunning demo? |
|
... 50 posts hidden. Click here to view all posts....
|
| |
algorithm
Registered: May 2002
Posts: 705 |
Cruzer, I would call the jsr initialise loader routine first line in the code before any SEI, setting interrupts etc. (I assume you are doing this?) |
| |
chatGPZ
Registered: Dec 2001
Posts: 11352 |
yeah dont init loader when your part (music irq, whatever) is running. that gave me exactly the same errors =D |
| |
Cruzer
Registered: Dec 2001
Posts: 1048 |
Already tried sei, cli, turning off all interrupts before calling install, not turning them off, etc., with the same result. So I figured something had to be wrong with install-c64.prg. While browsing around in the source files I noticed some of them were write protected, so I did a recursive chmod 777, and after compiling again, I was able to jsr install without errors. Woo-yay! :D |
| |
Radiant
Registered: Sep 2004
Posts: 639 |
Yeah, lots of write protected files in the latest version. Makes it semi-broken I'd say. |
| |
Cruzer
Registered: Dec 2001
Posts: 1048 |
And I got it to load a file with an interrupt running \o/
Sure hope I have grown from this experience. :)
Guess I still have a lot to learn though, e.g. how to load a file without the drive having to access the dir each time, and how to integrate it with packers. |
| |
algorithm
Registered: May 2002
Posts: 705 |
I think krills loader caches the data on the drive and by default it points to the next file on the disk for preperation.
Once the decompressor option is enabled in the config.inc file and the loader is compiled, there should be a loadersymbols.inc file generated which will give you the offset jump table for use in loading compressed files.
Using exomizer for example, you can pack a datafile using something like exomizer mem -f testdata.prg -ocompdata |
| |
Oswald
Registered: Apr 2002
Posts: 5086 |
"I think krills loader caches the data on the drive and by default it points to the next file on the disk for preperation."
yeah, thats how it worked last time I've used it. the loader positions the head on the next file in the directory structure after finished with the previous, so place files in loading order in the disk. |
| |
Luca
Registered: Apr 2002
Posts: 178 |
Thank you Krill for your help, compiling it has been actually easier than I imagined :) |
| |
Krill
Registered: Apr 2002
Posts: 2969 |
Quote: "I think krills loader caches the data on the drive and by default it points to the next file on the disk for preperation."
yeah, thats how it worked last time I've used it. the loader positions the head on the next file in the directory structure after finished with the previous, so place files in loading order in the disk.
There is a drive-side cache for the files' starting track/sector. This is a sliding window on the directory, holding about 30 file entries on 1541, with 4 bytes per entry (2 bytes track/sector, 2 bytes filename hash).
Normally the directory should only be accessed once, unless you have more files than can be held in the cache.
If the directory is larger than what the cache can hold, and a file cannot be found in the cache, the directory track will be read again, trying to find that file. This will likely leave another chunk of the directory in the cache.
Now, if you have more files than the cache can hold, and you jump wildly about the directory, the loader will be forced to revisit the directory track here and there.
If it jumps back to the directory track despite all files fitting into the cache, it's a bug on my side.
Does the problem still exist? |
| |
Krill
Registered: Apr 2002
Posts: 2969 |
Quoting CruzerWhile browsing around in the source files I noticed some of them were write protected, so I did a recursive chmod 777, and after compiling again, I was able to jsr install without errors. Woo-yay! :D Quoting CruzerYeah, lots of write protected files in the latest version. Makes it semi-broken I'd say. Okay, this is interesting. Of course i checked if the zip i uploaded builds fine after download, but i didn't check the prg target, nor did i suspect, or ever hear, that read-only source files would silently produce broken binaries.
Will investigate, but can anybody tell me more about this? |
| Previous - 1 | 2 | 3 | 4 | 5 | 6 - Next |
