📄 dot-bochsrc
字号:
# You may now use double quotes around pathnames, in case# your pathname includes spaces.#=======================================================================# CONFIG_INTERFACE## The configuration interface is a series of menus or dialog boxes that# allows you to change all the settings that control Bochs's behavior.# There are two choices of configuration interface: a text mode version# called "textconfig" and a graphical version called "wx". The text# mode version uses stdin/stdout and is always compiled in. The graphical# version is only available when you use "--with-wx" on the configure # command. If you do not write a config_interface line, Bochs will # choose a default for you.## NOTE: if you use the "wx" configuration interface, you must also use# the "wx" display library.#=======================================================================#config_interface: textconfig#config_interface: wx#=======================================================================# DISPLAY_LIBRARY## The display library is the code that displays the Bochs VGA screen. Bochs # has a selection of about 10 different display library implementations for # different platforms. If you run configure with multiple --with-* options, # the display_library command lets you choose which one you want to run with.# If you do not write a display_library line, Bochs will choose a default for# you.## The choices are: # x use X windows interface, cross platform# win32 use native win32 libraries# carbon use Carbon library (for MacOS X)# beos use native BeOS libraries# macintosh use MacOS pre-10# amigaos use native AmigaOS libraries# sdl use SDL library, cross platform# svga use SVGALIB library for Linux, allows graphics without X11# term text only, uses curses/ncurses library, cross platform# rfb provides an interface to AT&T's VNC viewer, cross platform# wx use wxWidgets library, cross platform# nogui no display at all## NOTE: if you use the "wx" configuration interface, you must also use# the "wx" display library.## Specific options:# Some display libraries now support specific option to control their# behaviour. See the examples below for currently supported options.#=======================================================================#display_library: amigaos#display_library: beos#display_library: carbon#display_library: macintosh#display_library: nogui#display_library: rfb, options="timeout=60" # time to wait for client#display_library: sdl, options="fullscreen" # startup in fullscreen mode#display_library: term#display_library: win32, options="legacyF12" # use F12 to toggle mouse#display_library: wx#display_library: x#=======================================================================# ROMIMAGE:# The ROM BIOS controls what the PC does when it first powers on.# Normally, you can use a precompiled BIOS in the source or binary# distribution called BIOS-bochs-latest. The ROM BIOS is usually loaded# starting at address 0xf0000, and it is exactly 64k long.# You can also use the environment variable $BXSHARE to specify the# location of the BIOS.# The usage of external large BIOS images (up to 512k) at memory top is# now supported, but we still recommend to use the BIOS distributed with# Bochs. Now the start address can be calculated from image size.#=======================================================================romimage: file=$BXSHARE/BIOS-bochs-latest, address=0xf0000#romimage: file=mybios.bin, address=0xfff80000 # 512k at memory top#romimage: file=mybios.bin # calculate start address from image size#=======================================================================# CPU:# This defines cpu-related parameters inside Bochs:## COUNT:# Set the number of processors when Bochs is compiled for SMP emulation.# Bochs currently supports up to 8 processors. If Bochs is compiled# without SMP support, it won't accept values different from 1.## IPS:# Emulated Instructions Per Second. This is the number of IPS that bochs# is capable of running on your machine. You can recompile Bochs with# --enable-show-ips option enabled, to find your workstation's capability.# Measured IPS value will then be logged into your log file or status bar# (if supported by the gui).## IPS is used to calibrate many time-dependent events within the bochs # simulation. For example, changing IPS affects the frequency of VGA# updates, the duration of time before a key starts to autorepeat, and# the measurement of BogoMips and other benchmarks.## Examples:# Machine Mips# ________________________________________________________________# 2.1Ghz Athlon XP with Linux 2.6/g++ 3.4 12 to 15 Mips# 1.6Ghz Intel P4 with Win2000/g++ 3.3 5 to 7 Mips# 650Mhz Athlon K-7 with Linux 2.4.4/egcs-2.91.66 2 to 2.5 Mips# 400Mhz Pentium II with Linux 2.0.36/egcs-1.0.3 1 to 1.8 Mips#=======================================================================cpu: count=2, ips=10000000#=======================================================================# MEGS# Set the number of Megabytes of physical memory you want to emulate. # The default is 32MB, most OS's won't need more than that.# The maximum amount of memory supported is 2048Mb.#=======================================================================#megs: 256#megs: 128#megs: 64megs: 32#megs: 16#megs: 8#=======================================================================# OPTROMIMAGE[1-4]:# You may now load up to 4 optional ROM images. Be sure to use a # read-only area, typically between C8000 and EFFFF. These optional# ROM images should not overwrite the rombios (located at# F0000-FFFFF) and the videobios (located at C0000-C7FFF).# Those ROM images will be initialized by the bios if they contain # the right signature (0x55AA) and a valid checksum.# It can also be a convenient way to upload some arbitrary code/data# in the simulation, that can be retrieved by the boot loader#=======================================================================#optromimage1: file=optionalrom.bin, address=0xd0000#optromimage2: file=optionalrom.bin, address=0xd1000#optromimage3: file=optionalrom.bin, address=0xd2000#optromimage4: file=optionalrom.bin, address=0xd3000#optramimage1: file=/path/file1.img, address=0x0010000#optramimage2: file=/path/file2.img, address=0x0020000#optramimage3: file=/path/file3.img, address=0x0030000#optramimage4: file=/path/file4.img, address=0x0040000#=======================================================================# VGAROMIMAGE# You now need to load a VGA ROM BIOS into C0000.#=======================================================================#vgaromimage: file=bios/VGABIOS-elpin-2.40vgaromimage: file=$BXSHARE/VGABIOS-lgpl-latest#vgaromimage: file=bios/VGABIOS-lgpl-latest-cirrus#=======================================================================# VGA:# Here you can specify the display extension to be used. With the value# 'none' you can use standard VGA with no extension. Other supported# values are 'vbe' for Bochs VBE and 'cirrus' for Cirrus SVGA support.#=======================================================================#vga: extension=cirrus#vga: extension=vbevga: extension=none#=======================================================================# FLOPPYA:# Point this to pathname of floppy image file or device# This should be of a bootable floppy(image/device) if you're# booting from 'a' (or 'floppy').## You can set the initial status of the media to 'ejected' or 'inserted'.# floppya: 2_88=path, status=ejected (2.88M 3.5" floppy)# floppya: 1_44=path, status=inserted (1.44M 3.5" floppy)# floppya: 1_2=path, status=ejected (1.2M 5.25" floppy)# floppya: 720k=path, status=inserted (720K 3.5" floppy)# floppya: 360k=path, status=inserted (360K 5.25" floppy)# floppya: 320k=path, status=inserted (320K 5.25" floppy)# floppya: 180k=path, status=inserted (180K 5.25" floppy)# floppya: 160k=path, status=inserted (160K 5.25" floppy)# floppya: image=path, status=inserted (guess type from image size)## The path should be the name of a disk image file. On Unix, you can use a raw# device name such as /dev/fd0 on Linux. On win32 platforms, use drive letters# such as a: or b: as the path. The parameter 'image' works with image files# only. In that case the size must match one of the supported types.#=======================================================================floppya: 1_44=/dev/fd0, status=inserted#floppya: image=../1.44, status=inserted#floppya: 1_44=/dev/fd0H1440, status=inserted#floppya: 1_2=../1_2, status=inserted#floppya: 1_44=a:, status=inserted#floppya: 1_44=a.img, status=inserted#floppya: 1_44=/dev/rfd0a, status=inserted#=======================================================================# FLOPPYB:# See FLOPPYA above for syntax#=======================================================================#floppyb: 1_44=b:, status=insertedfloppyb: 1_44=b.img, status=inserted#=======================================================================# ATA0, ATA1, ATA2, ATA3# ATA controller for hard disks and cdroms## ata[0-3]: enabled=[0|1], ioaddr1=addr, ioaddr2=addr, irq=number# # These options enables up to 4 ata channels. For each channel# the two base io addresses and the irq must be specified.# # ata0 and ata1 are enabled by default with the values shown below## Examples:# ata0: enabled=1, ioaddr1=0x1f0, ioaddr2=0x3f0, irq=14# ata1: enabled=1, ioaddr1=0x170, ioaddr2=0x370, irq=15# ata2: enabled=1, ioaddr1=0x1e8, ioaddr2=0x3e0, irq=11# ata3: enabled=1, ioaddr1=0x168, ioaddr2=0x360, irq=9#=======================================================================ata0: enabled=1, ioaddr1=0x1f0, ioaddr2=0x3f0, irq=14ata1: enabled=1, ioaddr1=0x170, ioaddr2=0x370, irq=15ata2: enabled=0, ioaddr1=0x1e8, ioaddr2=0x3e0, irq=11ata3: enabled=0, ioaddr1=0x168, ioaddr2=0x360, irq=9#=======================================================================# ATA[0-3]-MASTER, ATA[0-3]-SLAVE## This defines the type and characteristics of all attached ata devices:# type= type of attached device [disk|cdrom] # mode= only valid for disks [flat|concat|external|dll|sparse|vmware3]# mode= only valid for disks [undoable|growing|volatile]# path= path of the image# cylinders= only valid for disks# heads= only valid for disks# spt= only valid for disks# status= only valid for cdroms [inserted|ejected]# biosdetect= type of biosdetection [none|auto], only for disks on ata0 [cmos]# translation=type of translation of the bios, only for disks [none|lba|large|rechs|auto]# model= string returned by identify device command# journal= optional filename of the redolog for undoable and volatile disks# # Point this at a hard disk image file, cdrom iso file, or physical cdrom# device. To create a hard disk image, try running bximage. It will help you# choose the size and then suggest a line that works with it.## In UNIX it may be possible to use a raw device as a Bochs hard disk, # but WE DON'T RECOMMEND IT. In Windows there is no easy way.## In windows, the drive letter + colon notation should be used for cdroms.
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -