Code: Select all
pfloppy->offset = 0;
pfloppy->write_protect = wp ? 1 : 0;
pfloppy->max_sector = pformat->sectors >> 1;
pfloppy->max_sector0 = pformat->sectors >> 1;
pfloppy->max_track = pformat->tracks - 1;
pfloppy->byte_p_sector = SECTOR_SIZE;
pfloppy->byte_p_track0 = pformat->sectors * SECTOR_SIZE;
pfloppy->byte_p_track = pformat->sectors * SECTOR_SIZE;
pfloppy->type = TYPE_CONTAINER | TYPE_DSK_CONTAINER;
Code: Select all
This is the layout of the SIR:
The first 16 bytes are not used (all zeros)
offset(hex) size(hex) contents
----------- --------- -------------------------
$10 $0B Volume Label
$1B $01 Volume Number High byte
$1C $01 Volume Number Low byte
$1D $01 First User Track
$1E $01 First User Sector
$1F $01 Last User Track
$20 $01 Last User Sector
$21 $01 Total Sectors High byte
$22 $01 Total Sectors Low byte
$23 $01 Creation Month
$24 $01 Creation Day
$25 $01 Creation Year
$26 $01 Max Track
$27 $01 Max Sector
Code: Select all
[snip 16 bytes]
10:56 V
11:46 F
12:4C L
13:45 E
14:58 X
15:30 0
16:39 9
17:00
18:00
19:00
1A:00
1B:00 |
1C:01 |- Vol 1
1D:0D First User Track = 0D (I think this is the first free track)
1E:09 First User Sector = 09 (I think this is the first free sector)
1F:22 Last Free track = 22, Means this was a 35 Track Disc - quite standard.
20:0A Last Free Sector on that track = 10.
21:00 |
22:D6 |- Total Sectors on Disc = 214 (53k capacity)
23:05 May
24:17 17th
25:6F 111? Is that 2011? who knows...
26:22 &22 tracks
27:0A &0A sectors per trackI assume you will share your new drivers ...RobC wrote: I've managed to build the sources (using a09) and write the terminal I/O and disk drivers (using OSWORD &7F).
I'm very interested in this software, once I get my Atom6809 up and running, so if you please want to share it ... ?
Yes - I'll be happy to share but I do want to at least test them properly first! At the moment, I can't even get to the Flex prompt with the co-proroland wrote:I assume you will share your new drivers ...
Thanks. To be honest, I haven't done a huge amount: the terminal IO drivers just hook into the entry points defined in JGH's client source and the disk drivers are just wrappers to the relevant OSWORD &7F calls.danielj wrote:Brilliant work!
There is a bug in 0.23 according to the other thread:
http://www.stardot.org.uk/forums/viewto ... 77#p103277
Could that be causing your problems?
, 6809 and FLEX is all new to me 
)](./images/smilies/eusa_wall.gif "Brick wall"){kind=small}
Code: Select all
$ bbcbasic
PDP11 BBC BASIC IV Version 0.45
(C) Copyright J.G.Harston 1989,2005-2024
>_As I was drifting off to sleep my subconscious started working on it. Hmm... 180K is 18 times 40 tracks. Hmm... Do I remember Dragon disks being 18 sectors? This morning a slight tweek to make the number of sectors/track be imagesize DIV tracks*bytepersector. Making some progress!.danielj wrote:If you have a poke at that image and look at what should be sector 3 (although there's a whole load of other gumpf in there), it looks to me like it says the disk is &27 tracks with &12 sectors/track? I'm just working backwards from where the disk title text is...
So that's a double density dragon disk, although it's possible the first track will be single density?
VDK header is lying to you.
Code: Select all
$ bbcbasic
PDP11 BBC BASIC IV Version 0.45
(C) Copyright J.G.Harston 1989,2005-2024
>_
It would be a great source for software.
Think it's fufu-subscribe@flexusergroup.com but I've not had a response back yet.danielj wrote:Hehe - I'll happily join the mailing list - who should I email?
Wonderful! Well done!RobC wrote:As I mentioned in the OmniFlop thread, I've managed to get Flex up and running.
I had to upgrade the 6809 code to v0.25 but it will now boot, run commands and read a Flex system disk:
I'd recommend "our" standard format: 256 bytes per sector, 10 sectors per track, starting at sector 0, tracks counting up side 0, then counting up side 1 (400K for 80T-doublesided). As things progress we can add 16-sector tracks if the host's controller supports them (640K for 80T-doublesided) or even 720K using a DOS physical format.RobC wrote:As Flex doesn't seem to mandate a particular disk setup, I'd also welcome feedback on what this should cater for - I'm currently using two drives: one to hold the DFS disk with the BFLEX code and the other to hold the Flex system disk.
The Flex disk format reserves the first 512 bytes of the filesystem for system-specific data boot sector data. I'd recommend that we put a standard DFS catalog in that first 512 bytes - ie sector 0/00/0 and 0/00/1 - and put two files in that catalog: !BOOT and FLEX, both of which point to boot code to load the Flex system either with *FLEX or Shift-Break.RobC wrote:I could put the BFLEX routine in ROM and then leave both drives free to hold Flex disks. Or I could put a delay in the Flex boot process to allow for the swapping of disks. Both options would then allow for use with single drive setups.
Code: Select all
0000 EQUS "FLEX DIS"
0008 EQUS "!BOOT $"
0010 EQUS "FLEX $"
0020 Boot code
...
0100 EQUS "K ":EQUB 0:EQUB &10:EQUW &0220
0108 EQUW &C100:EQUW &C100:EQUB &0200:EQUB &0000
0110 EQUW &C100:EQUW &C100:EQUB &0200:EQUB &0000
0120 more boot codeCode: Select all
>[b]*EX[/b]
FLEX DISK Option 2 (Run)
$.!BOOT 00C100 00C100 000200 0000
$.FLEX 00C100 00C100 000200 0000Code: Select all
$ bbcbasic
PDP11 BBC BASIC IV Version 0.45
(C) Copyright J.G.Harston 1989,2005-2024
>_This should do it. The system boot filename is replaceable, and the disk access code does double-sided disk access.RobC wrote:Next up I'll test the double sided operation and then look at the boot loader code.
Code: Select all
$ bbcbasic
PDP11 BBC BASIC IV Version 0.45
(C) Copyright J.G.Harston 1989,2005-2024
>_