Well, that has its own section in the description, and you need to do
those two things; diskd.img and the geometry in .bochsrc have to go hand
in hand.
The default geometry we have in there right now is:
diskc: file=diskc.img, cyl=40, heads=8, spt=64
meaning 40*8*64 sectors, each sector is 512 big, so => 10MB
So when Bochs boots, it virtually sees an IDE drive with that geometry.
ZEROFILE is used to create/wipe out the image of this IDE drive that
Bochs sees.
If you change it to say
diskd: file=diskd.img, cyl=128, heads=8, spt=64
that means 128*8*64 sectors, each sector is 512 big, so => 32MB
Iulian
Post by William Francis CladekI don't see why we need to change the disk geometry. Shouldn't changing
the number of blocks in the $(ZEROFILE) variable be enough? The second
line in "How to create an arbitrarily big diskd.img" seems to imply that
changing the variable to 65536 is sufficient to make it 32MB. I never
heard anything about the matter in the discussions I attended, though.
Any confirmation on this, Iulian?
Will
Post by Joe BarrettI don't see why it would be "individual knowledge" - I don't think we
have any grading tests based on the ability to handle 32MB files - do we?
Joe