| 1 |
|
| 2 |
Basilisk II, Version 0.7 |
| 3 |
A free, portable Mac II emulator |
| 4 |
|
| 5 |
Copyright (C) 1997-1999 Christian Bauer et al. |
| 6 |
Freely distributable |
| 7 |
|
| 8 |
|
| 9 |
License |
| 10 |
------- |
| 11 |
|
| 12 |
Basilisk II is available under the terms of the GNU General Public License. |
| 13 |
See the file "COPYING" that is included in the distribution for details. |
| 14 |
|
| 15 |
|
| 16 |
Overview |
| 17 |
-------- |
| 18 |
|
| 19 |
Basilisk II is a free, portable, Open Source 68k Mac emulator. It requires |
| 20 |
a copy of a Mac ROM and a copy of MacOS to run. Basilisk II is freeware and |
| 21 |
distributed under the GNU General Public License. |
| 22 |
|
| 23 |
Basilisk II has currently been ported to the following systems: |
| 24 |
- BeOS R4 (PowerPC and x86) |
| 25 |
- Unix (tested under Linux, Solaris 2.5, FreeBSD 3.x and IRIX 6.5) |
| 26 |
- AmigaOS 3.x |
| 27 |
- Windows NT 4.0 (mostly works under Windows 95/98, too) |
| 28 |
|
| 29 |
Some features of Basilisk II: |
| 30 |
- Emulates either a Mac Classic (which runs MacOS 0.x thru 7.5) |
| 31 |
or a Mac II series machine (which runs MacOS 7.x, 8.0 and 8.1), |
| 32 |
depending on the ROM being used |
| 33 |
- Color video display |
| 34 |
- CD quality sound output |
| 35 |
- Floppy disk driver (only 1.44MB disks supported) |
| 36 |
- Driver for HFS partitions and hardfiles |
| 37 |
- CD-ROM driver with basic audio functions |
| 38 |
- Ethernet driver |
| 39 |
- Serial drivers |
| 40 |
- SCSI Manager (old-style) emulation |
| 41 |
- Emulates extended ADB keyboard and 3-button mouse |
| 42 |
- Uses UAE 68k emulation or (under AmigaOS) real 68k processor |
| 43 |
|
| 44 |
The emulator is not yet complete. See the file "TODO" for a list of |
| 45 |
unimplemented stuff. |
| 46 |
|
| 47 |
|
| 48 |
Requirements and Installation |
| 49 |
----------------------------- |
| 50 |
|
| 51 |
Please consult the file "INSTALL" for a list of system requirements and |
| 52 |
installation instructions. |
| 53 |
|
| 54 |
|
| 55 |
Configuration |
| 56 |
------------- |
| 57 |
|
| 58 |
Basilisk II is configured via the preferences editor that appears on startup. |
| 59 |
If you have a version without preferences editor (e.g. because of missing GTK+ |
| 60 |
under Unix), you have to edit the preferences file manually. |
| 61 |
|
| 62 |
The settings are stored in a text file: |
| 63 |
|
| 64 |
BeOS: |
| 65 |
/boot/home/config/settings/BasiliskII_prefs |
| 66 |
|
| 67 |
Unix: |
| 68 |
~/.basilisk_ii_prefs |
| 69 |
|
| 70 |
AmigaOS: |
| 71 |
ENV:BasiliskII_prefs |
| 72 |
|
| 73 |
Windows: |
| 74 |
BasiliskII_prefs (in the same directory as the executable) |
| 75 |
|
| 76 |
If no preferences file is present, Basilisk II will create one with the |
| 77 |
default settings upon startup. |
| 78 |
|
| 79 |
|
| 80 |
Preferences File Format |
| 81 |
----------------------- |
| 82 |
|
| 83 |
The preferences file is a text file editable with any text editor. |
| 84 |
Each line in this file has the format "keyword value" and describes |
| 85 |
one preferences item. For each keyword, the meaning of the "value" |
| 86 |
string may vary across platforms. The following keywords exist: |
| 87 |
|
| 88 |
disk <volume description> |
| 89 |
|
| 90 |
This item describes one MacOS volume to be mounted by Basilisk II. |
| 91 |
There can be multiple "disk" lines in the preferences file. Basilisk II |
| 92 |
can handle hardfiles (byte-per-byte images of HFS volumes in a file on |
| 93 |
the host system) as well as HFS partitions on hard disks etc. (but Basilisk |
| 94 |
II doesn't know about MacOS partition tables; it relies on the host OS to |
| 95 |
handle this). The "volume description" is either the pathname of a hardfile |
| 96 |
or a platform-dependant description of an HFS partition or drive. If the |
| 97 |
volume description starts with an asterisk ("*"), the volume is write |
| 98 |
protected for MacOS (and the "*" is discarded). |
| 99 |
|
| 100 |
BeOS: |
| 101 |
To specify an HFS partition, simply specify its path (e.g. |
| 102 |
"/dev/disk/scsi/0/1/0/0_3"). If you don't specify any volume, Basilisk II |
| 103 |
will search for and use all available HFS partitions. |
| 104 |
|
| 105 |
Unix: |
| 106 |
To specify an HFS partition, simply specify its path (e.g. |
| 107 |
"/dev/sda5"). |
| 108 |
|
| 109 |
AmigaOS: |
| 110 |
Partitions/drives are specified in the following format: |
| 111 |
/dev/<device name>/<unit>/<open flags>/<start block>/<size>/<block size> |
| 112 |
"start block" and "size" are given in blocks, "block size" is given in |
| 113 |
bytes. |
| 114 |
|
| 115 |
Windows: |
| 116 |
To define a logical volume (Windows NT only), specify its path (e.g. "c:\"). |
| 117 |
To define a physical volume (NT and 9x), additionally give the "physical" |
| 118 |
keyword (E.g. "physical c:\"). For safety reasons, volumes are mounted as |
| 119 |
read-only. This is due to the bugs in PC Exchange. If you don't specify |
| 120 |
any volume, the files *.hfv and *.dsk are searched from the current |
| 121 |
directory. Note that in this case, Basilisk II tries to boot from the first |
| 122 |
volume file found, which is random and may not be what you want. |
| 123 |
|
| 124 |
floppy <floppy drive description> |
| 125 |
|
| 126 |
This item describes one floppy drive to be used by Basilisk II. There |
| 127 |
can be multiple "floppy" lines in the preferences file. If no "floppy" |
| 128 |
line is given, Basilisk II will try to automatically detect and use |
| 129 |
installed floppy drives. The format of the "floppy drive description" |
| 130 |
is the same as that of "disk" lines. |
| 131 |
|
| 132 |
cdrom <CD-ROM drive description> |
| 133 |
|
| 134 |
This item describes one CD-ROM drive to be used by Basilisk II. There |
| 135 |
can be multiple "cdrom" lines in the preferences file. If no "cdrom" |
| 136 |
line is given, Basilisk II will try to automatically detect and use |
| 137 |
installed CD-ROM drives. The format of the "CD-ROM drive description" |
| 138 |
is the same as that of "disk" lines. |
| 139 |
|
| 140 |
scsi0 <SCSI target> ... scsi6 <SCSI target> |
| 141 |
|
| 142 |
These items describe the SCSI target to be used for a given Mac SCSI |
| 143 |
ID by Basilisk II. Basilisk II emulates the old SCSI Manager and allows |
| 144 |
to assign a different SCSI target (they don't even have to be on the |
| 145 |
same SCSI bus) for each SCSI ID (0..6) as seen by the MacOS. "scsi0" |
| 146 |
describes the target for ID 0, "scsi1" the target for ID 1 etc. |
| 147 |
The format of the "SCSI target" is platform specific. |
| 148 |
|
| 149 |
BeOS: |
| 150 |
The "SCSI target" has the format "<bus>/<unit>" (e.g. "0/2"). |
| 151 |
Due to a bug in BeOS, using SCSI with Basilisk II may cause the |
| 152 |
SCSI bus to hang. Use with caution. |
| 153 |
|
| 154 |
Linux: |
| 155 |
The "SCSI target" has to be the name of a device that complies to |
| 156 |
the Generic SCSI driver API. On a standard Linux installation, these |
| 157 |
devices are "/dev/sg0", "/dev/sg1" etc. Note that you must have |
| 158 |
appropriate access rights to these devices and that Generic SCSI |
| 159 |
support has to be compiled into the kernel. |
| 160 |
|
| 161 |
FreeBSD: |
| 162 |
The "SCSI target" has the format "<id>/<lun>" (e.g. "2/0"). |
| 163 |
|
| 164 |
AmigaOS: |
| 165 |
The "SCSI target" has the format "<device name>/<unit>" (e.g. |
| 166 |
"scsi.device/2"). |
| 167 |
|
| 168 |
Windows: |
| 169 |
Ignored. Basilisk II scans for all SCSI devices and the first 6 found |
| 170 |
devices are made visible to the MacOS. You cannot explicitly enable a |
| 171 |
device, but you can disable a device (see the "disablescsi" command). |
| 172 |
|
| 173 |
screen <video mode> |
| 174 |
|
| 175 |
This item describes the type of video display to be used by Basilisk II. |
| 176 |
If you are using a Mac Classic ROM, the display is always 1-bit 512x342 |
| 177 |
and this item is ignored. The format of the "video mode" is platform |
| 178 |
specific. |
| 179 |
|
| 180 |
BeOS: |
| 181 |
The "video mode" is one of the following: |
| 182 |
win/<width>/<height> |
| 183 |
8-bit color display in a window of the given size. This is the |
| 184 |
default. |
| 185 |
scr/<mode> |
| 186 |
Full-screen display in BWindowScreen. <mode> is the bit number of |
| 187 |
the video mode to use (see headers/be/interface/GraphicsDefs.h). |
| 188 |
E.g. 0 = 640x480x8, 1 = 800x600x8 etc., 10 = 640x480x24, |
| 189 |
11 = 800x600x24 etc., 18 = 640x480x15, 19 = 800x600x15 etc. |
| 190 |
15 bit modes are preferable to 16 bit modes (which may show false |
| 191 |
colors on PowerPC machines). |
| 192 |
When you run in full-screen mode and switch to another Workspace, |
| 193 |
Basilisk II is put in "suspend" mode (i.e. MacOS will be frozen). |
| 194 |
|
| 195 |
Unix: |
| 196 |
The "video mode" is one of the following: |
| 197 |
win/<width>/<height> |
| 198 |
Color display in an X11 window of the given size. The color depth |
| 199 |
(8/15/24 bit) depends on the depth of the underlying X11 screen. |
| 200 |
This is the default. |
| 201 |
dga |
| 202 |
Full-screen display using the X11 DGA extensions. The color depth |
| 203 |
(8/15/24 bit) depends on the depth of the underlying X11 screen. |
| 204 |
For DGA to work, Basilisk II must be compiled with DGA support |
| 205 |
enabled (selectable in the configure script). |
| 206 |
|
| 207 |
AmigaOS: |
| 208 |
The "video mode" is one of the following: |
| 209 |
win/<width>/<height> |
| 210 |
Black-and-white display in a window of the given size on the |
| 211 |
Workbench screen. This is the default and will also be used when |
| 212 |
one of the other options (PIP/screen) fails to open. |
| 213 |
pip/<width>/<height> |
| 214 |
15-bit truecolor display in a Picasso96 PIP. This requires |
| 215 |
Picasso96 as well as a PIP-capable graphics card (e.g. Picasso IV). |
| 216 |
scr/<hexadecimal mode ID> |
| 217 |
8/15/24-bit fullscreen display on a Picasso96 screen with the given |
| 218 |
mode ID. This requires Picasso96. For 15 and 24 bit, the frame buffer |
| 219 |
format must be QuickDraw-compatible (big-endian, xRGB 1:5:5:5 or |
| 220 |
xRGB 8:8:8:8). The screen size will be the default size for that |
| 221 |
mode ID. |
| 222 |
|
| 223 |
Windows: |
| 224 |
The "video mode" is one of the following: |
| 225 |
win/<width>/<height>/<bits per pixel> |
| 226 |
A refreshed screen mode that uses Windows GDI calls to write to the |
| 227 |
screen. You may have other windows on top of Basilisk II. |
| 228 |
dx/<width>/<height>/<bits per pixel> |
| 229 |
A refreshed DirectX mode (minimum version 5.0). There are ways to |
| 230 |
install DirectX 5 on NT 4. Some new display adapters work fine even |
| 231 |
with DirectX 3. |
| 232 |
fb/<width>/<height>/<bits per pixel> |
| 233 |
A non-refreshed video mode that works only on NT. It accesses the |
| 234 |
linear frame buffer directly (best performance of all three modes). |
| 235 |
Use the hotkey Control-Shift-F12 to switch between Windows and Mac |
| 236 |
displays. Fast task switch (Alt-Tab) and Explorer start menu |
| 237 |
(Control-Esc) are disabled, Control-Alt-Del is enabled. |
| 238 |
<width> and <height> can be either zeroes (uses current screen values), |
| 239 |
or something else. "win" mode can use almost anything, for other modes |
| 240 |
there must be a corresponding DirectX mode. |
| 241 |
<bits> is ignored for mode "win" (uses current screen values). |
| 242 |
If the mode is "win" and the dimensions are different than the desktop |
| 243 |
dimensions, windowed mode is used. The window can be moved around by |
| 244 |
dragging with the right mouse button. This mode remembers window positions |
| 245 |
separately for different dimensions. |
| 246 |
The supported values are 8,15,16,24,32. It is possible that some of them |
| 247 |
do not work for you. In particular, it may be that only one of the |
| 248 |
two modes, 15 and 16, is suitable for your card. You need to find out |
| 249 |
the best solution by experimenting. |
| 250 |
Basilisk II checks what display mode you are currently running and uses |
| 251 |
that mode. The screen is always full screen. When you switch to another |
| 252 |
application via Alt-Tab, Basilisk II is put in "snooze" mode (i.e. MacOS |
| 253 |
is frozen). |
| 254 |
|
| 255 |
seriala <serial port description> |
| 256 |
|
| 257 |
This item describes the serial port to be used as Port A (Modem Port) |
| 258 |
by Basilisk II. If no "seriala" line is given, Basilisk II will try to |
| 259 |
automatically detect and use installed serial ports. The "serial port |
| 260 |
description" is a platform-dependant description of a serial port. |
| 261 |
|
| 262 |
BeOS: |
| 263 |
Either specify the name of a serial port (e.g. "serial1") or one of |
| 264 |
"parallel1", "parallel2" or "parallel3". See below for more information |
| 265 |
about parallel ports. |
| 266 |
|
| 267 |
Unix: |
| 268 |
Specify the device name of a serial port (e.g. "/dev/ttyS0") or a |
| 269 |
parallel "lp" port (e.g. "/dev/lp1"; this only works under Linux and |
| 270 |
FreeBSD). See below for more information about parallel ports. |
| 271 |
|
| 272 |
AmigaOS: |
| 273 |
You have to specify the name of the serial device and the device unit |
| 274 |
as "<device name>/<unit>" (e.g. "serial.device/0"). If the given device |
| 275 |
is not compatible to serial.device, Basilisk II will crash. If the |
| 276 |
device name starts with an asterisk (e.g. "*parallel.device/0"), the |
| 277 |
device is treated as a parallel.device compatible device. See below for |
| 278 |
more information about parallel ports. |
| 279 |
|
| 280 |
Windows: |
| 281 |
Specify "COM1" or "COM2" for com port 1 or 2, respectively. |
| 282 |
|
| 283 |
Parallel ports: If you select a parallel port it will look like a serial |
| 284 |
port to MacOS but Basilisk II will only allow data output and ignore baud |
| 285 |
rate settings etc. You should be able to get some printers to work with |
| 286 |
this method (provided that you have the right printer driver, like |
| 287 |
"Power Print" (see www.gdt.com)). |
| 288 |
|
| 289 |
serialb <serial port description> |
| 290 |
|
| 291 |
This item describes the serial port to be used as Port B (Printer Port) |
| 292 |
by Basilisk II. If no "serialb" line is given, Basilisk II will try to |
| 293 |
automatically detect and use installed serial ports. The format of the |
| 294 |
"serial port description" is the same as that of the "seriala" option. |
| 295 |
|
| 296 |
ether <ethernet card description> |
| 297 |
|
| 298 |
This item describes the Ethernet card to be used for Ethernet networking |
| 299 |
by Basilisk II. If no "ether" line is given, Ethernet networking is disabled |
| 300 |
(although the Ethernet driver of Basilisk II will behave like a "dummy" |
| 301 |
Ethernet card in this case). If you are using a Mac Classic ROM, Ethernet |
| 302 |
is not available and this setting is ignored. The "ethernet card description" |
| 303 |
is a platform-dependant description of an ethernet card. |
| 304 |
|
| 305 |
BeOS: |
| 306 |
It doesn't matter what you give as "ethernet card description", Basilisk II |
| 307 |
will always use the first Ethernet card it finds as long an an "ether" |
| 308 |
line exists (e.g. say "ether yes"). As Basilisk II requires the sheep_net |
| 309 |
net server add-on from SheepShaver, you can only use Ethernet on PowerPC |
| 310 |
machines. |
| 311 |
|
| 312 |
Linux: |
| 313 |
The "ethernet card description" is the name of an Ethernet interface. |
| 314 |
There are two approaches to networking with Basilisk II: |
| 315 |
1. Direct access to an Ethernet card via the "sheep_net" driver. |
| 316 |
In this case, the "ethernet card description" must be the name |
| 317 |
of a real Ethernet card, e.g. "eth0". It also requires the "sheep_net" |
| 318 |
driver to be installed and accessible. This approach will allow you |
| 319 |
to run all networking protocols under MacOS (TCP/IP, AppleTalk, IPX |
| 320 |
etc.) but there is no connection between Linux networking and MacOS |
| 321 |
networking. MacOS will only be able to talk to other machines on |
| 322 |
the Ethernet, but not to other networks that your Linux box routes |
| 323 |
(e.g. a second Ethernet or a PPP connection to the Internet). |
| 324 |
2. Putting Basilisk II on a virtual Ethernet via the "ethertap" device. |
| 325 |
In this case, the "ethernet card description" must be the name |
| 326 |
of an ethertap interface, e.g. "tap0". It also requires that you |
| 327 |
configure your kernel to enable routing and the ethertap device: |
| 328 |
under "Networking options", enable "Kernel/User netlink socket" and |
| 329 |
"Netlink device emulation", under "Network device support", activate |
| 330 |
"Ethertap network tap". Next, see /usr/src/linux/Documentation/ |
| 331 |
networking/ethertap.txt for information on how to set up /dev/tap* |
| 332 |
device nodes and activate the ethertap interface. Under MacOS, |
| 333 |
select an IP address that is on the virtual network and set the |
| 334 |
default gateway to the IP address of the ethertap interface. This |
| 335 |
approach will let you access all networks that your Linux box has |
| 336 |
access to (especially, if your Linux box has a dial-up Internet |
| 337 |
connection and is configured for IP masquerading, you can access |
| 338 |
the Internet from MacOS). The drawback is that you can only use |
| 339 |
network protocols that Linux can route, so you have to install and |
| 340 |
configure netatalk if you want to use AppleTalk. |
| 341 |
|
| 342 |
AmigaOS: |
| 343 |
You have to specify the name of the SANA-II Ethernet device and the device |
| 344 |
unit as "<device name>/<unit>" (e.g. "ariadne.device/0"). If the given |
| 345 |
device is not a SANA-II device, Basilisk II will crash. If the device is |
| 346 |
not an Ethernet device, Basilisk II will display a warning message and |
| 347 |
disable Ethernet networking. |
| 348 |
|
| 349 |
rom <ROM file path> |
| 350 |
|
| 351 |
This item specifies the file name of the Mac ROM file to be used by |
| 352 |
Basilisk II. If no "rom" line is given, the ROM file has to be named |
| 353 |
"ROM" and put in the same directory as the Basilisk II executable. |
| 354 |
|
| 355 |
bootdrive <drive number> |
| 356 |
|
| 357 |
Specify MacOS drive number of boot volume. "0" (the default) means |
| 358 |
"boot from first bootable volume". |
| 359 |
|
| 360 |
bootdriver <driver number> |
| 361 |
|
| 362 |
Specify MacOS driver number of boot volume. "0" (the default) means |
| 363 |
"boot from first bootable volume". Use "-62" to boot from CD-ROM. |
| 364 |
|
| 365 |
ramsize <bytes> |
| 366 |
|
| 367 |
Allocate "bytes" bytes of RAM for MacOS system and application memory. |
| 368 |
The value given will be rounded down to the nearest multiple of 1MB. |
| 369 |
If you are using a Mac Classic ROM, the maximum available value is 4MB |
| 370 |
and higher values will be ignored. The default is 8MB. |
| 371 |
|
| 372 |
frameskip <frames to skip> |
| 373 |
|
| 374 |
For refreshed graphics modes (usually window modes), this specifies |
| 375 |
how many frames to skip after drawing one frame. Higher values make |
| 376 |
the video display more responsive but require more processing power. |
| 377 |
The default is "8". |
| 378 |
|
| 379 |
modelid <MacOS model ID> |
| 380 |
|
| 381 |
Specifies the Model ID that Basilisk II should report to MacOS. |
| 382 |
The default is "5" which corresponds to a Mac IIci. If you want to |
| 383 |
run MacOS 8, you have to set this to "14" (Quadra 900). Other values |
| 384 |
are not officially supported and may result in crashes. MacOS versions |
| 385 |
earlier than 7.5 may only run with the Model ID set to "5". If you are |
| 386 |
using a Mac Classic ROM, the model is always "Mac Classic" and this |
| 387 |
setting is ignored. |
| 388 |
|
| 389 |
nosound <"true" or "false"> |
| 390 |
|
| 391 |
Set this to "true" to disable all sound output. This is useful if the |
| 392 |
sound takes too much CPU time on your machine or to get rid of warning |
| 393 |
messages if Basilisk II can't use your audio hardware. |
| 394 |
|
| 395 |
nocdrom <"true" or "false"> |
| 396 |
|
| 397 |
Set this to "true" to disable Basilisk's built-in CD-ROM driver. |
| 398 |
The only reason to do this is if you want to use a third-party CD-ROM |
| 399 |
driver that uses the SCSI Manager. The default is "false". |
| 400 |
|
| 401 |
nogui <"true" or "false"> |
| 402 |
|
| 403 |
Set this to "true" to disable the GUI preferences editor and GUI |
| 404 |
error alerts. All errors will then be reported to stdout. The default |
| 405 |
is "false". |
| 406 |
|
| 407 |
For additional information, consult the source. |
| 408 |
|
| 409 |
|
| 410 |
System-specific configuration |
| 411 |
----------------------------- |
| 412 |
|
| 413 |
Unix: |
| 414 |
|
| 415 |
keycodes <"true" or "false"> |
| 416 |
keycodefile <Keycode file path> |
| 417 |
|
| 418 |
By default, the X11 event handler in Basilisk II uses KeySyms to |
| 419 |
translate keyboard event to Mac keycodes. While this method is very |
| 420 |
compatible and ought to work with all X servers, it only works well |
| 421 |
if your keyboard has a US layout. If you set "keycodes" to "true", |
| 422 |
Basilisk II will use raw keycodes instead of KeySyms. The keycode |
| 423 |
depends only on the physical location of a key on the keyboard and |
| 424 |
not on the selected keymap. Unfortunately it depends on the X server |
| 425 |
being used and possibly also on the type of keyboard attached. So |
| 426 |
Basilisk II needs a table to translate X keycodes to Mac keycodes. |
| 427 |
This table is read by default from /usr/local/lib/basilisk_ii_keycodes |
| 428 |
unless you specify a different file with the "keycodefile" item. |
| 429 |
A sample keycode file ("basilisk_ii_keycodes") is included with |
| 430 |
Basilisk II. |
| 431 |
|
| 432 |
AmigaOS: |
| 433 |
|
| 434 |
sound <sound output description> |
| 435 |
|
| 436 |
This item specifies what method to use for sound output. The only choice |
| 437 |
is currently AHI, but you can specify the AHI mode ID to be used. The |
| 438 |
"sound output description" looks like this: |
| 439 |
|
| 440 |
ahi/<hexadecimal mode ID> |
| 441 |
|
| 442 |
Windows: |
| 443 |
|
| 444 |
noscsi <"true" or "false"> |
| 445 |
|
| 446 |
Completely disables SCSI Manager support when set to "true". |
| 447 |
Note that currently all SCSI operations are executed synchronously, |
| 448 |
even if Mac application has requested asynchronous operation. What this |
| 449 |
means is that the control is not returned to the application until the |
| 450 |
command is completely finished. Normally this is not an issue, but when a |
| 451 |
CDR/CDRW is closed or erased the burner program typically wants to wait in |
| 452 |
some progress dialog The result may be that the application reports a |
| 453 |
time-out error, but the operation completes all right anyway. |
| 454 |
|
| 455 |
nofloppyboot <"true" or "false"> |
| 456 |
|
| 457 |
Set this to "true" to disable booting from a floppy. |
| 458 |
|
| 459 |
replacescsi <"Vendor1"> <"Model1"> <"Vendor2"> <"Model2"> |
| 460 |
|
| 461 |
This command tricks the Mac to believe that you have a SCSI device Model2 |
| 462 |
from vendor Vendor2, although your real hardware is Model1 from Vendor1. |
| 463 |
This is very useful since many devices have almost identical ATAPI and SCSI |
| 464 |
versions of their hardware, and MacOS applications usually support the SCSI |
| 465 |
version only. The example below is typical: |
| 466 |
|
| 467 |
replacescsi "HP" "CD-Writer+ 7100" "PHILIPS" "CDD3600" |
| 468 |
|
| 469 |
Note the use of quotes. |
| 470 |
|
| 471 |
disablescsi <"Vendor"> <"Model"> |
| 472 |
|
| 473 |
Disables this vendor/model combination. You may need this simply because |
| 474 |
you have more than 6 SCSI devices, or the particular device has problems |
| 475 |
under BasiliskII. E.g. |
| 476 |
|
| 477 |
disablescsi "HP" "CD-Writer+ 7100" |
| 478 |
|
| 479 |
Again, note the use of quotes. |
| 480 |
|
| 481 |
ntdx5hack <"true" or "false"> |
| 482 |
|
| 483 |
You may need this on NT if your display adapter driver has a bug in DirectX |
| 484 |
palette support. Black and white are reversed. It fixes the palette issue |
| 485 |
by using GDI palette instead of D3D palette. Default is false. |
| 486 |
|
| 487 |
|
| 488 |
Usage |
| 489 |
----- |
| 490 |
|
| 491 |
Quitting: |
| 492 |
The right way to quit Basilisk II is to select the "Shut Down" menu item |
| 493 |
from the Finder's "Special" menu. You should not kill it from the shell |
| 494 |
unless it hangs. Under Unix, pressing "Esc" while holding the Ctrl key will |
| 495 |
also quit Basilisk II (in case you are using it in DGA mode and it crashed). |
| 496 |
Under Windows, try Alt-F4 (or Control-Alt-Del to log off and back on again |
| 497 |
if it crashes really badly). |
| 498 |
|
| 499 |
Suspending: |
| 500 |
The Unix version of Basilisk II can be suspended while running in DGA mode |
| 501 |
by pressing "Tab" while holding the Ctrl key. Pressing "Space" in the |
| 502 |
"suspended" window will resume the emulation. Under BeOS, switching to |
| 503 |
a different Workspace when BasiliskII is in full-screen mode will also |
| 504 |
suspend the emulation. |
| 505 |
|
| 506 |
Keyboard: |
| 507 |
On PC-style keyboards, "Alt" is the Mac "Command" key, while the "Windows" |
| 508 |
key is the Mac "Option" key. |
| 509 |
|
| 510 |
Floppy: |
| 511 |
Basilisk II can only handle 1.44MB MFM floppies. Depending on your platform, |
| 512 |
flopyy disk changes might not be detected automatically. Under Linux, press |
| 513 |
Ctrl-F1 to mount a floppy. Under BeOS, select the appropriate "Mount" menu |
| 514 |
item or press Ctrl-F1 to mount a floppy. Under Windows, press Ctrl-Shift-F11. |
| 515 |
|
| 516 |
HFS partitions: |
| 517 |
Having HFS partitions mounted for read-write access under Basilisk II while |
| 518 |
they are also mounted on the host OS will most likely result in volume |
| 519 |
corruption and data losses. Unmount your HFS volumes before starting |
| 520 |
Basilisk II. |
| 521 |
|
| 522 |
ZIP drives: |
| 523 |
Iomega ZIP disks can be mounted either with the "disk" prefs item or (on |
| 524 |
platforms that support the SCSI Manager emulation of Basilisk II) by |
| 525 |
installing the IomegaWare on the Mac side. Do not use both ways |
| 526 |
simultaneously! |
| 527 |
|
| 528 |
Hardfiles: |
| 529 |
In addition to plain images of HFS volumes, Basilisk II can also handle |
| 530 |
some types of Mac "disk image" files, as long as they are uncompressed |
| 531 |
and unencoded. |
| 532 |
|
| 533 |
Mac Classic emulation: |
| 534 |
Sound output and Ethernet are not supported if you are using a Mac Classic |
| 535 |
ROM. Also, the video display is fixed to 512x342 in monochrome. The AmigaOS |
| 536 |
and BeOS/PPC versions of Basilisk II cannot do Mac Classic emulation. |
| 537 |
|
| 538 |
Sound output: |
| 539 |
Sound output under Basilisk II requires Sound Manager 3.0 or later. This |
| 540 |
is included starting with MacOS 7.5 and available as a system extension |
| 541 |
for earlier MacOS versions. Sample rate, bit resolution and mono/stereo |
| 542 |
can be selected in the Sound control panel (section "Sound Out"). |
| 543 |
|
| 544 |
Ethernet: |
| 545 |
Basilisk II supports all Ethernet protocols. Running a protocol under |
| 546 |
Basilisk II that already runs within the host operating system on the same |
| 547 |
network card (e.g. running MacTCP under Basilisk II on a BeOS machine) may |
| 548 |
or may not work (generally, it should work, but some specific things like |
| 549 |
"ping" may not). If you have problems with FTP, try setting your FTP client |
| 550 |
to passive mode. |
| 551 |
|
| 552 |
LocalTalk: |
| 553 |
LocalTalk is not supported by Basilisk II. There is no way of getting |
| 554 |
LocalTalk to work with the serial drivers of Basilisk II. Any attempt to |
| 555 |
activate LocalTalk will either result in a crash or revert to Ethernet. |
| 556 |
|
| 557 |
Serial: |
| 558 |
You can use the serial ports in Basilisk II to connect to the Internet |
| 559 |
with a modem and "MacPPP". |
| 560 |
|
| 561 |
|
| 562 |
Technical Documentation |
| 563 |
----------------------- |
| 564 |
|
| 565 |
Please see the included file "TECH" for a technical overview of the emulator. |
| 566 |
|
| 567 |
|
| 568 |
Acknowledgements |
| 569 |
---------------- |
| 570 |
|
| 571 |
Contributions by: |
| 572 |
- Bernd Schmidt <crux@pool.informatik.rwth-aachen.de>: UAE 68k emulation |
| 573 |
- Marc Hellwig <Marc.Hellwig@uni-mainz.de>: audio output, BeOS video code |
| 574 |
and networking |
| 575 |
- Lauri Pesonen <lpesonen@nic.fi>: Windows NT port |
| 576 |
- Orlando Bassotto <future@powercube.mediabit.net>: FreeBSD support |
| 577 |
- Brian J. Johnson <bjohnson@sgi.com>: IRIX support |
| 578 |
- Marc Chabanas <Marc.Chabanas@france.sun.com>: Solaris sound support |
| 579 |
- Bill Huey <billh@mag.ucsd.edu>: 15/16 bit DGA and 15/16/32 bit X11 |
| 580 |
window support |
| 581 |
- David Lawrence <davidl@jlab.org>: incremental window refresh code |
| 582 |
|
| 583 |
Special thanks to: |
| 584 |
- Bernd Schmidt for letting me use his UAE 68k emulation |
| 585 |
- Daniel Bobbert who printed dozens of pages from the THINK Reference for |
| 586 |
me years ago |
| 587 |
- All ShapeShifter and SheepShaver users and beta testers |
| 588 |
- Apple Computer Inc., who made writing a Macintosh emulator a child's play |
| 589 |
|
| 590 |
|
| 591 |
Bug reports |
| 592 |
----------- |
| 593 |
|
| 594 |
You found a bug? Well, use the source, fix it and send the fix to |
| 595 |
<Christian.Bauer@uni-mainz.de> |
| 596 |
for inclusion in the next release of Basilisk II. |
| 597 |
|
| 598 |
|
| 599 |
Author |
| 600 |
------ |
| 601 |
|
| 602 |
You can contact me at <Christian.Bauer@uni-mainz.de>. Don't send bug |
| 603 |
reports, send fixes. Ports to other platforms are also very welcome. |
| 604 |
Please contact me before you intend to make major changes to the source. |
| 605 |
You might be working on something that I have already done or I may have |
| 606 |
different ideas about the Right Way to do it. |
| 607 |
|
| 608 |
Questions about ROM files will not be answered. There is also no point in |
| 609 |
sending me questions etc. that are specific to the Windows port of |
| 610 |
Basilisk II. I don't have Windows and can't say anything about that. |
| 611 |
Ask Lauri Pesonen instead. |
| 612 |
|
| 613 |
|
| 614 |
Support |
| 615 |
------- |
| 616 |
|
| 617 |
The official Basilisk II home page is at |
| 618 |
http://www.uni-mainz.de/~bauec002/B2Main.html |
| 619 |
|
| 620 |
There is no user-level support for Basilisk II at the moment. |
| 621 |
|
| 622 |
|
| 623 |
History |
| 624 |
------- |
| 625 |
|
| 626 |
Please consult the file "ChangeLog" for the release history. |
| 627 |
|
| 628 |
|
| 629 |
Christian Bauer |
| 630 |
<Christian.Bauer@uni-mainz.de> |
