Date   : Mon, 10 Sep 2007 01:05:35 +0100
From   : jgh@... (Jonathan Graham Harston)
Subject: IDE Interface and Level 3

>Message-ID: <2f806cd70709070301i7c40f317y609ce7af84e4633b@...>
 
J.G.Harston wrote:
> > Not sure on this one; I know I had problems with the GoMMC, but never
> > really followed those up.
> 
> Again, that could be the drive initialisation. The file server
> program only ever uses OSWORD &72/&08 and &72/&0A - read and write
> - but the initialiser calls OSWORD &72/&1A expecting to be told
> the drive geometry. If the GoMMC driver doesn't return anything
> suitable then that could be the problem.
 
At http://mdfs.net/Apps/Networking I've just uploaded a tweeked
WFSInit program that reads the disk size if it can't read the disk
geometry. I've tested it on a 258M IDE drive - god, it takes ages
to initialise, but it works. It may also work for a GoMMC drive.
 
As it reads the disk size from the ADFS free space map, it needs
to be run on a completely blank freshly initialised drive. Once
WFSInit has been run it reduces the claimed disk size, so if you
run it twice, the second time it will think it's using a 32K hard
drive!
 
-- 
J.G.Harston - jgh@...                - mdfs.net/User/JGH
BBC BASIC for Windows and Internationalisation
  See http://mdfs.net/Software/BBCBasic/Windows/ProgTips