But 1013/16/63 as entered in HForm really does get me a 499MB drive, not 506MB. Unless I'm going completely madJonAbbott wrote: Tue Apr 04, 20231013/16/63 = 506MBIanJeffray wrote: Tue Apr 04, 2023 1013*16*63*512/1024/1024 = 498.5859375
Not sure how you get 503MB. So confused now.
Sectors range from 1 upward, so you need to increase the sector value by 1 to get the correct value....1013*16*64
Tell me where the calculation "1013*16*63*512/1024/1024" is wrong ?
I've just double-checked this... 63 sectors, 16 cylinders, 1013 sectors.... "Disc Size 498MB" reports IDEForm with Wizzo.
PartitionManager reports "499MB" and ShowFree reports "498MB". Bloomin' thing's given me 2K LFAU with this of course.
BTW - would be really groovy if PartitionManager would have some way of displaying the LFAU
So I ask PartitionManager to make me its default 495MB partition, and change the LFAU to 512, which I know won't work.
It "appears" to work - just gets on and creates a partition.
Except it's quietly used 1024byte LFAU, as it has to. I think that it should have thrown a tantrum really - "Can't use 512byte LFAU, best I can do is 1K, ok?" kind of thing.
So ok, delete that partition. Create another one with PM... 503MB as you say should be fine, and leave LFAU at default.
progress bar gets close to the end (95%ish) and MACHINE LOCKS SOLID.
Reboot. It's created "something". Seems to be a 502MB (according to ShowFree) with 1024byte LFAU (According to DiscInfo).
Not sure I can trust it when it crashed so hard during creation though.
Delete it.
This time quit PM.
Then create a new partition of 503MB.
No hang this time. New "502"MB drive is created. Great.
Let's have another - this is a 2GB DOM, so plenty space for more partitions...
Still good.
And another - let's ask for 504MB this time.
DiskInfo says it's still 1024byte LFAU?!
Just what's going on? PM doesn't even seem to obey its authors rules!
Let's go mad. 505MB ? Finally, a jump to 2K LFAU.
Quit Partition Manager. "Address exception at &038677A0 at line 750". Bugger. That's somewhere in MessageTrans, it looks like.
So I've gone back to three 503MB partitions and a 444MB to fill up the 2G DOM. This feels a bit funky when I'd got used to 495MB being the limit for Wizzo. I feel like I need to absolutely fill them all up and check they're all really working correctly. I have fear.
Another suggestion - since PM can set the boot flag, can it also edit it? The default is to have the boot flag enabled, so all my 4 partitions have it set, which is no issue, but I'd notionally like to "clean them up" - would be nice not to resort to the command line for this.
Rebooted. Loaded PM again, just to check the partitions, Quit PM, "Address exception at &03867594" - that's MessageTrans again.
And now PM won't load - just repeatedly gives that same exception (and no line number)
Can't get that behaviour to repeat after a reboot though. Odd.
Last observation for now - noted earlier in the above fun - 499MB + 1GB doesn't equal 2GB. I expect this is a rounding error when going from MB to GB in the unallocated part, but even a single decimal place would be nice here IMO.
- 1gig.png (3.89 KiB) Viewed 18134 times
