| |
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....
|
| |
Krill
Registered: Apr 2002
Posts: 2969 |
Quoting algorithmthere should be a loadersymbols.inc file generated which will give you the offset jump table The jump table (consecutive jmp instructions jumping to the public routines, located at the beginning of loader.prg and install.prg) is only needed if you don't use loadersymbols.inc for whatever reason, otherwise it's just a waste of space and time. |
| |
Krill
Registered: Apr 2002
Posts: 2969 |
Quote: yeah dont init loader when your part (music irq, whatever) is running. that gave me exactly the same errors =D
Can you elaborate? Normally, the init procedure should not be disturbed by whatever your IRQ handlers do, but KERNAL must be enabled, sprites are forbidden, and $dd00 must only be written to with proper masking (as opposed to $dd00 access after install). |
| |
chatGPZ
Registered: Dec 2001
Posts: 11352 |
i was probably doing one of the things you shouldnt do, likely sprites :) |
| |
Cruzer
Registered: Dec 2001
Posts: 1048 |
Just downloaded and recompiled it, without chmod'ing. This time no problems, so if zip file hasn't been altered, please disregard my previous statement about write protected files being the problem. I was pretty sure it was the chmod that solved it, but apparently I must have done something else too. Sorry for the false alarm! But hey, I'm a n00b, what can you expect? :) |
| |
Krill
Registered: Apr 2002
Posts: 2969 |
There is a regression bug with the dependencies of the binary target, which i fixed today, snuck in when i added the +4 target. This effectively required a make clean before each make prg. (Cruzer: Doing the chmod probably touched all files so make would rebuild everything.)
Will fix the file permissions (must have changed due to various copying across media and OSes) and also a few other minor things (like the Java dependency), then upload a new version.
Sorry for the inconvenience. |
| |
TheRyk
Registered: Mar 2009
Posts: 2218 |
Only because there was a lot of blabla about Krill Loader after BCC#10 (see CRX Race) and I had admitted having had trouble with Krill-Loader-using releases (which I've never contributed carelessly to the loader without decently checking out other reasons, however), I feel obliged to make crystal clear, that all my problems turned out to be a slightly broken power suppy providing about 11.7 V on the 12 V on-load(!).
About 0.3 to 0.5 V difference seems(!) neglectable, but was DEFINETELY the reason, as 2 drives (with perfectly clean reading-head) failed with the power supply in question (tested with BCC#10 trackmos, CRX Race and David Bowie Collection) but worked fine with 2 other power supplies producing 12 V or slightly more.
Bottom Line: I recommend everyone, especially DATA-Land, to measure power supply _on-load_ (i.e. while-loading) if you face crashes with releases using Krill loader. |
| |
Thunder.Bird
Registered: Nov 2003
Posts: 109 |
Didn't you pay your electricity bills? *heheheh* :D
At X2016 mayby somebody helps you out with a PSU.
"Remember to spread the love" ;) |
| |
chatGPZ
Registered: Dec 2001
Posts: 11352 |
i feel like pointing to post #3 :) |
| |
Ninja
Registered: Jan 2002
Posts: 411 |
Well, your conclusion is true if most other loaders fail, too. If it is only Krill's loader which fails, then another conclusion might be that it is too far on some edge and he has now a starting point to find out which.
Have you tried the loaders of lft and Bitbreaker? |
| |
Bitbreaker
Registered: Oct 2002
Posts: 504 |
It is not even clear what kind of problems occur, nor is there a testcase to track down the quality of the problem. There's so many points where loading can fail, be it the stepping, the spinning speed, transfer. Then also, how are errors covered? Does the respective release make use of error codes or hang? One could also just ask an oracle about a solution. One slight hint the low 12 line gives might be spinning speed at least, but it is only a hint. Also, it is often easy to blame the loader when things break, but never it was the fault of irqs fucking registers or wild and arbitrary poking on $dd00 :-D
As for further evaluation i can hand out a bitfire .d64 for testing, but also doing some measures on spinning speed would be worth a try. Such cases need collection of data and further information. |
| Previous - 1 | 2 | 3 | 4 | 5 | 6 - Next |
