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


Forums > CSDb Entries > Release id #90210 : Format II
2018-01-22 21:35
TCE

Registered: Sep 2011
Posts: 29		 Release id #90210 : Format II

Documentation heads up, for those interested in a quick start with this excellent facility.

Within "README.txt", under "STAND-ALONE EXAMPLE" the JSR instruction should be corrected: it's not $ffba we need to JSR to, but $ffbd (set filename properties).

Furthermore, a complete example could look like this:

        processor 6502
        include "format2_runtime.i"

        org	$080d

start:
        ldx	#<fmt_cmd
        ldy	#>fmt_cmd
        lda	#9
        jsr	$ffbd
        lda	#0
        jsr	fmt2_format   ; format disk
        rts
fmt_cmd:
        dc.b	"N0:TLR,00"
 
... 10 posts hidden. Click here to view all posts....
 
2018-02-06 17:34
tlr

Registered: Sep 2003
Posts: 1714		 Quote: Re: "just be extra sure to make the stepper bits the right state when at the first track."
I shall be testing all the time with this one.

Re: "forcing a reload of the BAM on the next operation."
OK, I back-ported the change, and I am testing the code as per below:
fj_ex1:
	lda	#18
	jsr	seek_track

	lda	#$01	; format ok!

fj_ex2:	sta	$1c	; flag the disk as changed

	rts	; jmp $fddb


When leaving through fj_ex2, i.e. read error, A is 0x06, which I guess is still a suitable value for $1c?

When can we expect to see "Format III" published then, roughly? I can do some testing on RH if you need a hand with that.

There's some code in the DOS that uses an lsr $1c for test and clr so it needs to be $01.

I'm kind of busy with other stuff at the moment so format III will have to wait a bit. I might take up your offer for testing though. ;)
2018-02-10 19:35
TCE

Registered: Sep 2011
Posts: 29		 Might be handy to have visibility on something I am testing at the moment, so I will post it here. No action required.

Because I am using the Format II code through my IECHost device, the drive code is stored entirely in ROM and cannot be patched before being sent to the drive. I'd have to copy configurable sections to RAM first, patch and send that instead, but I'd rather proceed as per below.

I created a C64 demonstrator that sends the drive code to the 1541 unchanged, by means of a one-bit bootloader, running in the drive's RAM, within page #1. However, the bootloader does not execute the main drive code: In fact, I patch the drive's RAM starting at $06fc with a "M-W" loop, setting the number of tracks, etc. Finally, I execute the main drive code with a "M-E" (at $0300).
Previous - 1 | 2 - 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
Nordischsound/Hokuto..
Jetboy/Elysium
Alakran_64
Scooby/G★P/Light
machete
Brataccas/HF
Guests online: 151
Top Demos
1 Next Level  (9.8)
2 Mojo  (9.7)
3 Coma Light 13  (9.7)
4 Edge of Disgrace  (9.6)
5 Comaland 100%  (9.6)
6 No Bounds  (9.6)
7 Uncensored  (9.6)
8 Wonderland XIV  (9.6)
9 Bromance  (9.6)
10 Memento Mori  (9.6)
Top onefile Demos
1 It's More Fun to Com..  (9.7)
2 Party Elk 2  (9.7)
3 Cubic Dream  (9.6)
4 Copper Booze  (9.5)
5 Rainbow Connection  (9.5)
6 TRSAC, Gabber & Pebe..  (9.5)
7 Onscreen 5k  (9.5)
8 Wafer Demo  (9.5)
9 Dawnfall V1.1  (9.5)
10 Quadrants  (9.5)
Top Groups
1 Oxyron  (9.3)
2 Nostalgia  (9.3)
3 Booze Design  (9.3)
4 Censor Design  (9.3)
5 Crest  (9.3)
Top Crackers
1 Mr. Z  (9.9)
2 S!R  (9.9)
3 Antitrack  (9.8)
4 Mr Zero Page  (9.8)
5 OTD  (9.8)

Home - Disclaimer
Copyright © No Name 2001-2024
Page generated in: 0.036 sec.