| |
Chesoner
Registered: Apr 2013
Posts: 29 |
Krill loader not working
Hi There,
We are still strungling with the Krill loader, I have to say that we have progressed a lot but we get the following problem :
If we use the following command :
Make prg INSTALL=4000 RESIDENT=9000 zp=10
The install is working good at 4000 but the loader is still located at 0400. if we forced it to load at 9000 it ain't working.
Are we doing something wrong here ? |
|
... 55 posts hidden. Click here to view all posts....
|
| |
Pantaloon
Registered: Aug 2003
Posts: 124 |
I've used Krills loader alot and never really had problems that wasn't caused by bad code from my own side. If you post your code here (your interrupts etc and how you setup the loader) we would probably spot the error directly. |
| |
Axis/Oxyron
Account closed
Registered: Apr 2007
Posts: 91 |
Most important is to track down, where the problem occurs (loading, decrunching or something else). So my first test whould be to stop the cpu with an endless loop after loading. And compare the loaded memory with the original file. If this looks ok, do the same with the memory after decrunch. And so on... |
| |
Count Zero
Registered: Jan 2003
Posts: 1932 |
Axis: you are obviously too simple minded then! Abstract description of obscure problem without telling which parameters got used (remember - my notice on true drive and device traps passed uncommented) are definately enough to yell for help and moan whenever no suitable solutions surfaces within the minute ...
cough - not that it turns off anyone from further following the thread ... |
| |
Chesoner
Registered: Apr 2013
Posts: 29 |
@count zero: your true drive and device trap weren't unnoticed, it's better to not comment on the rest of the post.
I found after a lot of testing what the problem was, now we have to find a fix for the problem but at least we addressed the issue.
Thanks everyone for the advice !! |
| |
chatGPZ
Registered: Dec 2001
Posts: 11386 |
so what was the problem? |
| |
Chesoner
Registered: Apr 2013
Posts: 29 |
Quote: so what was the problem?
I used an existing d64 file and when I put the files on the d64 disk it was kind of random if it loaded correctly.
Now I have automated this process so a new d64 file is created and the files are on a fresh new d64 disk and everything runs fine.
It seems that the used .d64 file is not valid (anymore) for some reason. The first part always runned fine on the disk but loaded random the next part correct. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11386 |
what did you use to copy the file to the old d64? |
| |
Chesoner
Registered: Apr 2013
Posts: 29 |
Quote: what did you use to copy the file to the old d64?
I used DirMaster v2.2.009 for transfering files |
| |
chatGPZ
Registered: Dec 2001
Posts: 11386 |
there is your problem =P |
| |
Chesoner
Registered: Apr 2013
Posts: 29 |
hehe, it would be a logic conclusion |
| Previous - 1 | 2 | 3 | 4 | 5 | 6 | 7 - Next |
