| |
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....
|
| |
algorithm
Registered: May 2002
Posts: 705 |
Sorry, should be something like exomizer mem -f test.raw -ocomp.01 |
| |
Bitbreaker
Registered: Oct 2002
Posts: 508 |
The drive reset only happens if you keep the watchdog option enabled. It has been discussed many times :-) Also. in general, no problem with starting a SFX, but one needs to take care that if things get depacked under IO, that the IRQ is safe with $01 being #$34, also usually the SFX extractors lock the IRQ, one needs to remove the SEI to keep the irq running. Better choice is to do levepacked files, means files without an own decompression code per file. Many packers support that and many packers also include a decompression code for standalone use, in case of loadcompd (load and depacking on the fly) the decompressors are even integrated into Krill's loader for a bunch of packers. There's all the comfort one can think of. Btw.: Placing the loader at $c000 is even more of a hindrance, the mem above is not bad or smelly, it's there and usable. |
| |
Chesoner
Registered: Apr 2013
Posts: 29 |
After a lot of testing it looks like kickassembler/krill with winvice is not a great combination. if I attach the drive and set true drive emulation on in winvice and start code with kickassembler it is kind of random if it will load and decrunch a file from the attached drive correct. If i put all the files on a d64 en start the coding from the d64 file it will load/decrunch good.
I can't see why this is but at least it is working. |
| |
Count Zero
Registered: Jan 2003
Posts: 1940 |
Did you make sure that virtual device traps in vice are disabled and no 2nd drive is enabled? |
| |
chatGPZ
Registered: Dec 2001
Posts: 11391 |
Quote:and start code with kickassembler
???? |
| |
Chesoner
Registered: Apr 2013
Posts: 29 |
Quote: Quote:and start code with kickassembler
????
I use sublime for coding and kickassembler to compile and start the code in winvice. |
| |
Bitbreaker
Registered: Oct 2002
Posts: 508 |
And you are sure that you don't have clashes regarding the used zeropage-addresses and you only write sane values to $dd00? I did whole demos with that loader and things always worked out of the box. There's some common pitfalls however regarding the use of irq loaders in general. |
| |
Oswald
Registered: Apr 2002
Posts: 5095 |
" if I attach the drive and set true drive emulation on in winvice and start code with kickassembler it is kind of random if it will load and decrunch a file from the attached drive correct. If i put all the files on a d64 en start the coding from the d64 file it will load/decrunch good."
its hard to understand whats the difference between the 2 scenarios, altho that is the key to your problem.
a) start up winvice, attach _DRIVE_ (?) manually in WinVice, THEN start the program with kickass ???!? (files are not in d64 now??)
b) put everything on a d64 then start coding from d64 ?!?!?! |
| |
doynax
Account closed
Registered: Oct 2004
Posts: 212 |
I forget the details, and never completely tracked down the cause in the first place but IIRC the "Handle TDE for autostart" option triggered similar issues in older VICE versions. Something about the stepper motor phase getting into an illegal state and seemingly not being possible to realign. As I recall attaching the image late aggravated the problem.
This may have been G64-specific though. |
| |
Bitbreaker
Registered: Oct 2002
Posts: 508 |
Doynax: i happend to have that kind of autorun problems on 1541u version 1 with my loader :-)
What vice version is used? |
| Previous - 1 | 2 | 3 | 4 | 5 | 6 | 7 - Next |
