Log inRegister an accountBrowse CSDbHelp & documentationFacts & StatisticsThe forumsAvailable RSS-feeds on CSDbSupport CSDb Commodore 64 Scene Database
  You are not logged in 
Fileload V2.1.2   [2013]

Fileload V2.1.2 Released by :
Nostalgia [web]

Release Date :
21 January 2013

Type :
C64 Tool

AKA :
Fload V2.1.2

User rating:**********  10/10 (11 votes)   See votestatistics

Credits :
Code .... 6R6 of Nostalgia, SHAPE

Download :
http://csdb.dk/getinternalfile.php/112907/Fload_v2.1.2.rar (downloads: 950)
http://csdb.dk/getinternalfile.php/174037/Fload_v2.1.2_TASS153.rar (downloads: 40)

Look for downloads on external sites:
 Pokefinder.org


User Comment
Submitted by Krill on 17 February 2019
Setting a bunch of store watchpoints in regular VICE would be enough to catch offending code, though. But that list of locations better be complete. :)
User Comment
Submitted by Knight Rider on 17 February 2019
Quote:
And if it doesn't exist yet, there should be a best-practice document somewhere online. :)


I second this. I am fairly sure there is a custom build of VICE that can monitor each ZP value for each KERNAL call. Much easier/reliable than ploughing through the listing by hand for sure.
User Comment
Submitted by Krill on 17 February 2019
"So the moral of the story is to backup/restore ZP values $90-$98 and $b7-$bc when using KERNAL routines. This is in addition to the 8 ZP values used by the depack routine."

I'd like to add that according to my sources, ZP variables which must not be touched during load are $9a (output device variable DFLTO) and $a4 (serial bus shift counter BSOUR1). There may be more. And if it doesn't exist yet, there should be a best-practice document somewhere online. :)
User Comment
Submitted by Knight Rider on 17 February 2019
I had issues with KERNEL load when doing a flex address loader with exomizer 2.09.

There is no bcs error after jsr $ffc0, when added it was obvious that something had gone wrong when opening the file. This was on a SD2IEC on a real C64 (not recreatable in VICE), so many hours of ploughing through the KERNAL listing I discovered that $94 and $98 need to be 00 (ie saved, initialized and restored). The value in $94 > $80 leads to a 'device not present error' and a value greater than $0a in $98 leads to 'too many files open' error.

So the moral of the story is to backup/restore ZP values $90-$98 and $b7-$bc when using KERNAL routines. This is in addition to the 8 ZP values used by the depack routine.
User Comment
Submitted by soci on 16 February 2019
That's a good workaround and modernization as other parts of this code already used logical/here instead.

However this was a bug in r1864.

I've noticed that in some corner case "*=" was not behaving as expected.

However what was not noticed that ".offs" never really did the right thing, not even in the 6502tass days.

The former behaviour was used to mask the latter .offs bug, great.

Anyway, from r1896 on it should compile fine again as .offs is now matching the C64 behaviour so this old-school relocation construct works as it originally did.
User Comment
Submitted by Knight Rider on 14 February 2019
it won't build with 64TASS 1.54.1864

1582.tas needs changing:

;         *= $0900		;0500
;         .offs code81-*
.logical $0900

.
.
.

;         *= code81+end81-begin81
;         .offs 0
.here
User Comment
Submitted by Knight Rider on 27 October 2018
Added a version with changes needed for TASS1.53

fload_installer.tas
fload_sloader.tas
setup.tas
User Comment
Submitted by Didi on 5 October 2018
Exomizer decruncher works with versions up to 2.0.9. It fails to decrunch files packed with 2.0.10 or 2.0.11.
I don't judge this as a goof because these versions were released way after this package.
User Comment
Submitted by Didi on 13 November 2017
Works fine with 64tass 1.46 for me.
User Comment
Submitted by Knight Rider on 13 November 2017
Anyone have any working complete example source ? The one in the ZIP is incomplete. Additionally won't assemble with newer versions of 64TASS (.includes and .proc are giving errors)
User Comment
Submitted by 6R6 on 2 February 2013
@Comos.. Fileload and Nosdos has some similar installation/detection and get_byte routines.
Fileload allows you to use kernal load/save routines. In Nosdos the drive routine is always present in the disk drive.
User Comment
Submitted by Comos on 2 February 2013
Is there any difference between Fileload and NOSDOS? Looks very similar...
User Comment
Submitted by 6R6 on 25 January 2013
No, It doesn't detect the MMC.
It would be nice with support. But from what I have seen and experienced it will take a lot of memory. Which is bad.
User Comment
Submitted by Monte Carlos on 25 January 2013
Does this work also with MMC Replay (it wasn't listed in the manual).
User Comment
Submitted by TheRyk on 23 January 2013
Yeah, just to prevent unnecessary work, if anyone already "ACME-fixed" this, it'd be great if you upload the sources here.
User Comment
Submitted by Da Snake on 23 January 2013
Excellent, thanks for this!
User Comment
Submitted by Yogibear on 22 January 2013
Good work!
User Comment
Submitted by Burglar on 22 January 2013
cool u released the source, especially with support for all those devices.
Search CSDb
Advanced
Navigate
Prev - Random - Next
Detailed Info
· Summaries (1)
· User Comments (18)
· Production Notes
Fun Stuff
· Goofs
· Hidden Parts
· Trivia
Forum
· Discuss this release
Sponsored links
Support CSDb
Help keep CSDb running:



Funding status:




About this site:
CSDb (Commodore 64 Scene Database) is a website which goal is to gather as much information and material about the scene around the commodore 64 computer - the worlds most popular home computer throughout time. Here you can find almost anything which was ever made for the commodore 64, and more is being added every day. As this website is scene related, you can mostly find demos, music and graphics made by the people who made the scene (the sceners), but you can also find a lot of the old classic games here. Try out the search box in the top right corner, or check out the CSDb main page for the latest additions.
Home - Disclaimer
Copyright © No Name 2001-2019
Page generated in: 0.078 sec.