mirror of
https://github.com/InvisibleUp/uvmac.git
synced 2024-11-22 07:31:19 +00:00
1 line
7.8 KiB
HTML
1 line
7.8 KiB
HTML
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title> Blanks </title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="canonical" href="index.html">
</head>
<body>
<div>
<i> <a href="https://www.gryphel.com/index.html">www.gryphel.com</a>/c/<a href="../../index.html">minivmac</a>/<a href="../index.html">extras</a>/blanks
- <a href="https://www.gryphel.com/c/feedback.html">feedback</a> </i>
</div>
<hr>
<h2 align=center>
Blanks
</h2>
<hr>
<p> Download </p>
<blockquote>
<p> <a href="https://www.gryphel.com/d/minivmac/extras/blanks/blanks-1.0.0.zip">blanks-1.0.0.zip</a>
(52K) </p>
</blockquote>
<p>
“blanks-1.0.0.zip” is a zip archive containing a folder
of zipped empty Macintosh disk image files of various sizes and formats.
</p>
<p>
First unzip “blanks-1.0.0.zip” to get the folder
“blanks”.
Then when you need a blank disk image, unzip one of the files
in this folder. For example, unzip “800K.zip”
to get “800K.dsk”, an 800K blank disk image, the size of
a floppy disk normally used by a real Macintosh Plus.
</p>
<p> For information about using disk images in Mini vMac,
see the '<a href="../../hardware.html#floppy_drives">Floppy Drive</a>'
section of the Hardware Reference.
To transfer files from your real
computer into and out of disk image files, see the utilities
<a href="../importfl/index.html">ImportFl</a> and
<a href="../exportfl/index.html">ExportFl</a>.
</p>
<p> The top level of the blanks folder contains 2 other disk images
in the sizes of standard Macintosh floppy disks: 400K and
1440K. A real Macintosh Plus floppy drive could use 400K disks,
but not 1440K, which came later. But Mini vMac doesn't
emulate the real floppy drive, replacing the disk driver
in ROM, and so can use any size disk image, not just 400K and 800K. </p>
<p> The “K” folder contains disk images smaller than 1 megabyte,
in powers of 2 starting at 128K (the smallest that works),
and also multiples 1.25, 1.50, and 1.75 of those powers. </p>
<p> The “M” folder contains disk images larger or equal to
1 megabyte, up to 224M. In general, it may not a good idea to
use the largest sizes, for reasons described below. </p>
<p>
The “mfs” folder contains disk images in the
MFS format (Macintosh File System).
All the other disk images in Blanks are in “HFS” format
(Hierarchical File System), the standard for a Macintosh Plus.
MFS preceded HFS. The original Macintosh 128K and 512K can only use MFS
and not HFS. A Macintosh Plus can use either.
</p>
<p> The “dc42” folder contains disk images with
the Disk Copy 4.2 header, and having file
tags and checksums. (All the other disk images in Blanks are
“raw”, containing just image data with no header
or trailer.)
Mini vMac can support
file tags with the build system option
“<a href="../../options.html#option_sony_tag">-sony-tag 1</a>”,
and can support checksums with the build system option
“<a href="../../options.html#option_sony_sum">-sony-sum 1</a>”. </p>
<p> If you're thinking of using large disk images, keep in mind
that it is not a good idea to create one giant disk image for
all your work. One reason is that the HFS file system is limited to a maximum
of 65535 allocation blocks. So the minimum block size increases for
larger disks, meaning more wasted space. (HFS Plus fixed this
problem, but isn't supported on a Macintosh Plus.) Another reason
it is bad idea is that a Macintosh Plus doesn't have the memory
protection of modern computers, so that a bug in any program
can potentially corrupt mounted disks. It is safer to have separate
disk images for separate purposes. This way Mini vMac gives
the same benefits of memory protection, and more. No matter what program
you run in the emulated machine, nothing can be harmed except
the disk images that are mounted at the time. (Unless there
was a major bug in Mi
|