⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 dot-bochsrc

📁 类unix x86平台的简单操作系统
💻
📖 第 1 页 / 共 3 页
字号:
# Depending on versions of windows and drivers, you may only be able to # access the "first" cdrom in the system.  On MacOSX, use path="drive"# to access the physical drive.## The path is always mandatory. For flat hard disk images created with# bximage geometry autodetection can be used (cylinders=0 -> cylinders are# calculated using heads=16 and spt=63). For other hard disk images and modes# the cylinders, heads, and spt are mandatory.## Default values are:#   mode=flat, biosdetect=auto, translation=auto, model="Generic 1234"## The biosdetect option has currently no effect on the bios## Examples:#   ata0-master: type=disk, mode=flat, path=10M.sample, cylinders=306, heads=4, spt=17#   ata0-slave:  type=disk, mode=flat, path=20M.sample, cylinders=615, heads=4, spt=17#   ata1-master: type=disk, mode=flat, path=30M.sample, cylinders=615, heads=6, spt=17#   ata1-slave:  type=disk, mode=flat, path=46M.sample, cylinders=940, heads=6, spt=17#   ata2-master: type=disk, mode=flat, path=62M.sample, cylinders=940, heads=8, spt=17#   ata2-slave:  type=disk, mode=flat, path=112M.sample, cylinders=900, heads=15, spt=17#   ata3-master: type=disk, mode=flat, path=483M.sample, cylinders=1024, heads=15, spt=63#   ata3-slave:  type=cdrom, path=iso.sample, status=inserted#=======================================================================ata0-master: type=disk, mode=flat, path="xv6.img", cylinders=100, heads=10, spt=10ata0-slave: type=disk, mode=flat, path="fs.img", cylinders=1024, heads=1, spt=1#ata0-slave: type=cdrom, path=D:, status=inserted#ata0-slave: type=cdrom, path=/dev/cdrom, status=inserted#ata0-slave: type=cdrom, path="drive", status=inserted#ata0-slave: type=cdrom, path=/dev/rcd0d, status=inserted #=======================================================================# BOOT:# This defines the boot sequence. Now you can specify up to 3 boot drives.# You can either boot from 'floppy', 'disk' or 'cdrom'# legacy 'a' and 'c' are also supported# Examples:#   boot: floppy#   boot: disk#   boot: cdrom#   boot: c#   boot: a#   boot: cdrom, floppy, disk#=======================================================================#boot: floppyboot: disk#=======================================================================# CLOCK:# This defines the parameters of the clock inside Bochs:##  SYNC:#  TO BE COMPLETED (see Greg explanation in feature request #536329)##  TIME0:#  Specifies the start (boot) time of the virtual machine. Use a time #  value as returned by the time(2) system call. If no time0 value is #  set or if time0 equal to 1 (special case) or if time0 equal 'local', #  the simulation will be started at the current local host time.#  If time0 equal to 2 (special case) or if time0 equal 'utc',#  the simulation will be started at the current utc time.## Syntax:#  clock: sync=[none|slowdown|realtime|both], time0=[timeValue|local|utc]## Example:#   clock: sync=none,     time0=local       # Now (localtime)#   clock: sync=slowdown, time0=315529200   # Tue Jan  1 00:00:00 1980#   clock: sync=none,     time0=631148400   # Mon Jan  1 00:00:00 1990#   clock: sync=realtime, time0=938581955   # Wed Sep 29 07:12:35 1999#   clock: sync=realtime, time0=946681200   # Sat Jan  1 00:00:00 2000#   clock: sync=none,     time0=1           # Now (localtime)#   clock: sync=none,     time0=utc         # Now (utc/gmt)# # Default value are sync=none, time0=local#=======================================================================#clock: sync=none, time0=local#=======================================================================# FLOPPY_BOOTSIG_CHECK: disabled=[0|1]# Enables or disables the 0xaa55 signature check on boot floppies# Defaults to disabled=0# Examples:#   floppy_bootsig_check: disabled=0#   floppy_bootsig_check: disabled=1#=======================================================================#floppy_bootsig_check: disabled=1floppy_bootsig_check: disabled=0#=======================================================================# LOG:# Give the path of the log file you'd like Bochs debug and misc. verbiage# to be written to. If you don't use this option or set the filename to# '-' the output is written to the console. If you really don't want it,# make it "/dev/null" (Unix) or "nul" (win32). :^(## Examples:#   log: ./bochs.out#   log: /dev/tty#=======================================================================#log: /dev/nulllog: bochsout.txt#=======================================================================# LOGPREFIX:# This handles the format of the string prepended to each log line.# You may use those special tokens :#   %t : 11 decimal digits timer tick#   %i : 8 hexadecimal digits of cpu current eip (ignored in SMP configuration)#   %e : 1 character event type ('i'nfo, 'd'ebug, 'p'anic, 'e'rror)#   %d : 5 characters string of the device, between brackets# # Default : %t%e%d# Examples:#   logprefix: %t-%e-@%i-%d#   logprefix: %i%e%d#=======================================================================#logprefix: %t%e%d#=======================================================================# LOG CONTROLS## Bochs now has four severity levels for event logging.#   panic: cannot proceed.  If you choose to continue after a panic, #          don't be surprised if you get strange behavior or crashes.#   error: something went wrong, but it is probably safe to continue the#          simulation.#   info: interesting or useful messages.#   debug: messages useful only when debugging the code.  This may#          spit out thousands per second.## For events of each level, you can choose to crash, report, or ignore.# TODO: allow choice based on the facility: e.g. crash on panics from#       everything except the cdrom, and only report those.## If you are experiencing many panics, it can be helpful to change# the panic action to report instead of fatal.  However, be aware# that anything executed after a panic is uncharted territory and can # cause bochs to become unstable.  The panic is a "graceful exit," so# if you disable it you may get a spectacular disaster instead.#=======================================================================panic: action=askerror: action=reportinfo: action=reportdebug: action=ignore#pass: action=fatal#=======================================================================# DEBUGGER_LOG:# Give the path of the log file you'd like Bochs to log debugger output.# If you really don't want it, make it /dev/null or '-'. :^(## Examples:#   debugger_log: ./debugger.out#=======================================================================#debugger_log: /dev/null#debugger_log: debugger.outdebugger_log: -#=======================================================================# COM1, COM2, COM3, COM4:# This defines a serial port (UART type 16550A). In the 'term' you can specify# a device to use as com1. This can be a real serial line, or a pty.  To use# a pty (under X/Unix), create two windows (xterms, usually).  One of them will# run bochs, and the other will act as com1. Find out the tty the com1# window using the `tty' command, and use that as the `dev' parameter.# Then do `sleep 1000000' in the com1 window to keep the shell from# messing with things, and run bochs in the other window.  Serial I/O to# com1 (port 0x3f8) will all go to the other window.# Other serial modes are 'null' (no input/output), 'file' (output to a file# specified as the 'dev' parameter), 'raw' (use the real serial port - under# construction for win32), 'mouse' (standard serial mouse - requires# mouse option setting 'type=serial' or 'type=serial_wheel') and 'socket'# (connect a networking socket).## Examples:#   com1: enabled=1, mode=null#   com1: enabled=1, mode=mouse#   com2: enabled=1, mode=file, dev=serial.out#   com3: enabled=1, mode=raw, dev=com1#   com3: enabled=1, mode=socket, dev=localhost:8888#=======================================================================#com1: enabled=1, mode=term, dev=/dev/ttyp9#=======================================================================# PARPORT1, PARPORT2:# This defines a parallel (printer) port. When turned on and an output file is# defined the emulated printer port sends characters printed by the guest OS# into the output file. On some platforms a device filename can be used to# send the data to the real parallel port (e.g. "/dev/lp0" on Linux, "lpt1" on# win32 platforms).## Examples:#   parport1: enabled=1, file="parport.out"#   parport2: enabled=1, file="/dev/lp0"#   parport1: enabled=0#=======================================================================parport1: enabled=1, file="/dev/stdout"#=======================================================================# SB16:# This defines the SB16 sound emulation. It can have several of the# following properties.# All properties are in the format sb16: property=value# midi: The filename is where the midi data is sent. This can be a#       device or just a file if you want to record the midi data.# midimode:#      0=no data#      1=output to device (system dependent. midi denotes the device driver)#      2=SMF file output, including headers#      3=output the midi data stream to the file (no midi headers and no#        delta times, just command and data bytes)# wave: This is the device/file where wave output is stored# wavemode:#      0=no data#      1=output to device (system dependent. wave denotes the device driver)#      2=VOC file output, incl. headers#      3=output the raw wave stream to the file# log:  The file to write the sb16 emulator messages to.# loglevel:#      0=no log#      1=resource changes, midi program and bank changes#      2=severe errors#      3=all errors#      4=all errors plus all port accesses#      5=all errors and port accesses plus a lot of extra info# dmatimer:#      microseconds per second for a DMA cycle.  Make it smaller to fix#      non-continuous sound.  750000 is usually a good value.  This needs a#      reasonably correct setting for the IPS parameter of the CPU option.## For an example look at the next line:#=======================================================================#sb16: midimode=1, midi=/dev/midi00, wavemode=1, wave=/dev/dsp, loglevel=2, log=sb16.log, dmatimer=600000#=======================================================================# VGA_UPDATE_INTERVAL:# Video memory is scanned for updates and screen updated every so many# virtual seconds.  The default is 40000, about 25Hz. Keep in mind that# you must tweak the 'cpu: ips=N' directive to be as close to the number# of emulated instructions-per-second your workstation can do, for this# to be accurate.## Examples:

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -