Log inRegister an accountBrowse CSDbHelp & documentationFacts & StatisticsThe forumsAvailable RSS-feeds on CSDbSupport CSDb Commodore 64 Scene Database
You are not logged in 
CSDb User Forums


Forums > CSDb Entries > Release id #167152 : Krill's Loader, repository version 164
2018-08-13 21:37
Krill

Registered: Apr 2002
Posts: 1159
Release id #167152 : Krill's Loader, repository version 164

If no problems emerge (i know they will, but anyways)... I can explain a bit about the full on-the-fly GCR block read+decode+checksumming.
 
... 36 posts hidden. Click here to view all posts....
 
2018-08-16 06:29
Lazycow

Registered: Dec 2013
Posts: 1
Really fast! But the loadertest-c64.d64 hangs with vice 2.4 on NTSC. Emulation problem or bug? (I don't have an NTSC machine to verify)
2018-08-16 08:46
Krill

Registered: Apr 2002
Posts: 1159
Quoting Lazycow
Really fast! But the loadertest-c64.d64 hangs with vice 2.4 on NTSC. Emulation problem or bug? (I don't have an NTSC machine to verify)
The option NTSC_COMPATIBILITY is disabled for the pre-built images and binaries (because it would slightly slow down PAL performance, see loader/include/config.inc). Enabling it should make it work with both PAL and NTSC.
2018-08-16 10:02
JackAsser

Registered: Jun 2002
Posts: 1490
Quote: Really fast! But the loadertest-c64.d64 hangs with vice 2.4 on NTSC. Emulation problem or bug? (I don't have an NTSC machine to verify)

Not that it matters in this case probably, but generally don’t report bugs / problems using 2yr old emulators.
2018-08-16 10:59
Krill

Registered: Apr 2002
Posts: 1159
Quoting JackAsser
2yr old emulators.
FWIW, 1541U (up to and including current versions) detection code as found in loader/src/install.s ;)
drvch1541u: .byte "m-e", .lobyte($0205), .hibyte($0205); read forward
            sei
            ldx #$ff
            stx $0300
            stx $1803; set all port pins as outputs
            lda #$a4; bit 0 may be forced to GND (1541-II) or connected to track 0 sensor (1541-C, normally 0 = not on track 0)
            sta $1801
            cmp $1801
            bne is1541u
            anc #$8a; and #imm, but no asl/rol, bit 7 of result goes to carry
            beq is1541u
            bcc is1541u
            txa
            arr #$7f; bit 6 of result goes to carry
            ror $0300
is1541u:    inc $1803; set all port pins as inputs
            cli
            rts
drvchkued:
If $0300 has a negative value after execution, 1541U detected.
2018-08-16 14:07
Groepaz

Registered: Dec 2001
Posts: 9090
Quote:
2yr old emulators

if only - 2.4 was released 2012 :)

thanks for pointing out the emulator code that can be safely removed :)
2018-08-16 14:19
Krill

Registered: Apr 2002
Posts: 1159
Quoting Groepaz
thanks for pointing out the emulator code that can be safely removed :)
If you mean the 1541U detection code, take a look at this option:
.define ONLY_1541_AND_COMPATIBLE   0 ; reduces host-side install code by omitting any native custom drive code for non-1541 compatible
                                     ; drives, treats any drive as 1541, using an incompatible drive will cause undefined behaviour
2018-08-16 15:18
Groepaz

Registered: Dec 2001
Posts: 9090
but that would remove support for 1581 etc too, i guess?
2018-08-16 15:25
Krill

Registered: Apr 2002
Posts: 1159
Quoting Groepaz
but that would remove support for 1581 etc too, i guess?
Indeed. To keep it simple, there's no option to remove detection of specific models of the 1541 family only, once that family is detected. I'm sure you can figure out what to nix for that. :)
2018-08-16 15:27
Groepaz

Registered: Dec 2001
Posts: 9090
broken emulators are not part of the 1541 family though :)
2018-08-16 15:35
Krill

Registered: Apr 2002
Posts: 1159
Yes. But you know the story. After i found out about these incompatibilities the hard way, i grudgingly decided to work around those (because 1541U is quite relevant these days, and some older firmwares for 1541U1 will not be fixed), then add 1541U as a separate drive model, which is now also detected.

The idea is that anybody using the custom drive code API could then decide to use some other code if 1541U is detected and its broken implementation of some illegals or the VIA port would prohibit use of the regular 1541 code.
Previous - 1 | 2 | 3 | 4 | 5 - Next
RefreshSubscribe to this thread:

You need to be logged in to post in the forum.

Search the forum:
Search   for   in  
All times are CET.
Search CSDb
Advanced
Users Online
bugjam
razorback/G★P
Alakran_64
WVL/Xenon
Dymo/G★P
Snabel
Sentinel/Excess
kms
hedning/G★P
redcrab/G★P
AJOT
Guests online: 39
Top Demos
1 Uncensored  (9.7)
2 Unboxed  (9.7)
3 Edge of Disgrace  (9.7)
4 Coma Light 13  (9.6)
5 Comaland 100%  (9.6)
6 Lunatico  (9.6)
7 The Shores of Reflec..  (9.6)
8 X Marks the Spot  (9.5)
9 Old Men in Used Cars  (9.5)
10 C=Bit 18  (9.5)
Top onefile Demos
1 Bad Boy  (9.7)
2 Smile to the Sky  (9.6)
3 Daah, Those Acid Pil..  (9.5)
4 Dawnfall V1.1  (9.4)
5 FMX Music Demo  (9.4)
6 Rewind  (9.4)
7 Crystal Gazer  (9.4)
8 Official X2018 Report  (9.4)
9 Arok 20 Invitation  (9.4)
10 Pandemoniac Part 2 o..  (9.4)
Top Groups
1 PriorArt  (9.7)
2 Oxyron  (9.5)
3 Booze Design  (9.4)
4 Censor Design  (9.3)
5 Performers  (9.3)
Top Swappers
1 Derbyshire Ram  (10)
2 Splatterhead  (9.8)
3 Zyron  (9.8)
4 Walker  (9.7)
5 Acidchild  (9.7)

Home - Disclaimer
Copyright © No Name 2001-2019
Page generated in: 0.065 sec.