<< Previous Message Main Index Next Message >>
<< Previous Message in Thread This Month Next Message in Thread >>
Date   : Mon, 07 Mar 2005 13:40:10 +0000
From   : jgh@... (Jonathan Graham Harston)
Subject: Re: Acorn Winchester unit

Chris Johns <chris.johns@...> wrote:
> On 6 Mar 2005, Jonathan Graham Harston wrote:
> > Hmmm. Wonder if I can patch my fileserver code to allow full 64M
> > partitions? As I understand the code so far, the fileserver code
> 
> You might also need to modify the FS code to know where to look for a 2nd
> partition, else it'd go looking at 61M and find no valid partition
 
I'd assumed that the FS found the next partition by looking at the
size of the current partition in bytes 062-063 of the partition's
block zero. I've only found one bit of code in "FS" that sets a
disk size, called by the format/initialise code:
 
; Get disk size
; ============
; On entry, SP -> ret, type
; On exit, HL=disk size
012EA6 E1          á    POP  HL        ; Get return address
012EA7 E3          ã    EX   (SP),HL   ; Swap ret addr with parameter
012EA8 7C          |    LD   A,H       ;
012EA9 21 30 8E    !0.  LD   HL,&8E30  ; &8E30 - 35Mb
012EAC B7          ·    OR   A         ; Disk type zero?
012EAD C0          À    RET  NZ        ; No, return with 35Mb
012EAE 21 B0 EF    !°ï  LD   HL,&EFB0  ; &EFB0 - 60Mb
012EB1 C9          É    RET            ; Return with 60Mb
 
Though, the Utility Menu has an option for modifying a disc's
Block Zero, which may be something different to a partition's
Block Zero. I would well believe that there's a partition table
before the first logical partition. I'll keep digging (on and
off).
 
-- 
J.G.Harston - jgh@...                - mdfs.net/User/JGH
Badly formed email is deleted unseen as spam
<< Previous Message Main Index Next Message >>
<< Previous Message in Thread This Month Next Message in Thread >>