[Coco] MM/1 question

Dean Leiber adit at 1stconnect.com
Fri Nov 7 19:24:06 EST 2003


>
>What *really* annoys me (someone tell me if I'm doing it wrong) is that the
>formatter completely ignores the settings in the descriptor. It must
>interrogate the drive, finds it has $208818 bytes, and formats it to that.
>

Well my MM/1 is currently 300 miles away, but as I recall you can 
partition a drive, but I don't remember how it formated (its been a 
while.) I do know that you can partition a drive since I did it on my 
MM/1. Why you may ask? To save space since large clusters mean larger 
minimum file sizes. From What I do recall, I had to make a custom 
descriptor(s) so you'll have to compile a new file descriptor after 
mucking with it. As memory serves (vaguely) you'll have to edit a hard 
drive file descriptor for the drive number and where the tracks start and 
end (I believe you'll have to do some calculations for drivesize.) 
Someone who has access to OSK could probably look up what parameters to 
change in the file descriptor. This may allow you to use the IGB as a 
boot drive, but obviously partitioned say as h0 and h1. Oh one thing to 
remember (although it is obvious it would be an eaasy mistake to make) is 
to be careful to make sure the tracks for H0 and H1 do not overlap (you 
can imagine the havoc.) 
  
>If the formatter wont format to less than the full size of the drive

I'm betting if you do the partitioned descriptors the formatter will 
respect the drive size, etc. in the descriptor. Any comments anyone?



More information about the Coco mailing list