Re: Bug#98075: Update inst-methods.sgml, add suntar, hfs; update setlang sections

["Chris Tillman" <tillman@azstarnet.com>]

I figured out the reason Disk Copy grayed out Make A Floppy when I was 
trying it out, was the machine i was trying it on doesn't have a floppy
drive.

So, here's my edited version for the Writing Disk Images From MacOS section
of the patch, using root.bin as an example.

------

To create a floppy from a floppy image, for example the
<file>root.bin</file> file:
<enumlist>
<item>
Download the file from the Debian mirror in <em>binary</em> mode. Do not
allow any automatic extraction of the file after downloading. The `.bin'
extension does not stand for Macbinary, but rather just `binary' floppy
image files.
<item>
Obtain ResEdit (http://www.resexcellence.com/resedit.shtml).
<item>
Open the root.bin file with ResEdit (a resource fork will be added to the
file).
<item>
Select <tt>Get Info for root.bin...</tt> under the <tt>File</tt> menu. In
the Type field, replace whatever is there with <tt>DDim</tt>. In the Creator
field, type <tt>ddsk</tt>. The case is sensitive for Type and Creator.
<item>
Finally, check the <tt>File Locked</tt> checkbox so that MacOS will be
unable to remove the boot blocks if the image is mounted accidentally.
If the image is mounted, MacOS will helpfully remove the boot blocks,
ruining the floppy image.
<item>
Obtain Disk Copy; if you have a MacOS system or CD it will very likely be
there already, otherwise try
http://asu.info.apple.com/swupdates.nsf/artnum/n11162 .
<item>
Run Disk Copy, and select `Make a Floppy' from the Utilities menu, then
select the <em>locked</em> image file from the resulting dialog. It will ask
you to insert a floppy, then ask if you really want to erase it. When done
it should eject the floppy.
<item>
When the floppy is ejected <em>set the write protect tab</em>! Otherwise if
you accidently mount it in MacOS, MacOS will helpfully ruin it.
</enumlist>

--

Chris Tillman
tillman@azstarnet.com