New instrumentation call for DMA transfers
Implemented in git
[PATCH] rewrite eth_fbsd.cc (using netgraph)
obsolete, if you have updated one - please submit in github
Display Host/Guest mode on GUI debugger
Implemented different way now
Save and restore window positions
Rejecting, nobody asked this single 2009. If still required - open github ticket
What the report says, against current code PCI interrupts do still reach two I/O APIC inputs: pci_set_irq() drives input 16 + pirq (pci2isa.cc:224). The routed ISA IRQ then goes through DEV_pic_set_irq_level(). raise_irq() and lower_irq() forward it to I/O APIC input X (pic.cc:498, pic.cc:474). The recent fixes didn’t change this dual routing. They are 79b10b2b9 (Remote IRR, moving asserted PIRQ lines when the routing changes), 862acecfa (a level-triggered entry whose line is already high is pending)...
Sending EOI to Local APIC acts that all interrupts is complete
Fixed by 4e4a0f309 and 79b10b2b9 / 1cd5b8d5e
emulate MacOSX in Bochs
duplicate
ACPI table additions to satisfy Mac OS X
Superseded: processor objects (legacy BIOS SSDT and UEFI tables, 40b0ed066), Apple SMC ACPI device (392cb8186), and HPET/RTC are in the current DSDT. The remaining parts copy machine-specific Mac firmware data and don’t apply to Bochs
Snapshot on magic CPUID
there is CPUID instrumentation call, in instrumentation module you can do whatever you want, including snapshots
bochs debugger gui do not switches to 'magic breaked' CPU
Fixed in master
MACRO of USER_CS has a wrong value
Fixed in master
add ability to turn on instruction trace
Enabled with ability to turn on debugger on demand
Give us a small gui to configure / .bochsrc
Bochs supplies small GUI for building .bochsrc configure is run so rarely that it should not require any separate GUI
let bochs sleep when the simulation is idle
Seems like most of the request is already implemented If you want to escalate what is left - please open github issue, this issue tracking is deprecated
Second window and copy option for debugger
Second window and copy option for debugger
closed as duplicate if want to escalate - please reopen as github issue
fixed bochs info tab for 64 bit FAST.
fixed bochs info tab for 64 bit FAST.
already implemented
Adjustable sleep rate for emulator slowdown
Already implemented with slowdown timer
verbose information about hardware states and processes
EFI, TPM...
EFI is supported, TPM support present in another request on github
I’ve been experimenting with Bochs and I’m interested in using it for older Windows games and software. One thing I like about emulation is being able to recreate an older environment instead of trying to make every legacy application work directly on a modern operating system. For anyone who has experience with Bochs, how to run old Windows games with Bochs on a modern PC reliably? Are there particular CPU, VGA, memory, or BIOS settings that you normally recommend for better compatibility? I’m especially...
File no longer needed here.
Minor developer doc fixes.
Updated some sections of the developer doc.
Test commit.
Added bochsdoc.tar.gz to sfsite GIT.
Two sections of the developer doc needs to be updated.
Small developer doc update.
Test
rename getcurrent.html to force website update
fix "View the Source" link to point on github
more update
updates after Bochs 3.1 release
updates after Bochs 3.1 release
add documentation (docbook) in the same form it appear in website
updates after Bochs release 3.1
updates to sfsite
Bochs 3.1 released
Remove the 2GB host memory size limit
Already implemented
AMD PauseFilterThreshold support
Already supported in Bochs
Everybody is in github, this forum is obsolete
Hi everyone, I've been reading about how BIOS firmware interacts with emulators, and one thing that seems easy to overlook is that a BIOS image is not always interchangeable between different systems. The emulator has to reproduce enough of the expected hardware environment for the firmware to initialize correctly. This also comes up when comparing different console emulators, where BIOS versions and regions can affect compatibility and startup behavior. I found [this BIOS and emulation resource]...
Hi everyone, I've been reading about how BIOS firmware interacts with emulators, and one thing that seems easy to overlook is that a BIOS image is not always interchangeable between different systems. The emulator has to reproduce enough of the expected hardware environment for the firmware to initialize correctly. This also comes up when comparing different console emulators, where BIOS versions and regions can affect compatibility and startup behavior. I found [this BIOS and emulation resource]...
Interesting discussion, especially the later point about BIOS compatibility depending on the hardware Bochs is emulating. It’s a good reminder that a BIOS image isn’t just generic boot code — it can expect particular chipsets, peripherals, memory layouts, and firmware behavior. For anyone researching BIOS images and how they relate to emulation, I’ve also been collecting some background material . The site focuses mainly on PlayStation BIOS and emulation rather than Bochs, so it’s more of a general...
Lack of repeatability
Debugged memtest failure last week - was perfectly repeatable, even up to level that failure happened always on the same time tick on every run
Support for (U)EFI
support for UEFI was finally added
The limitations of the RFB gui are documented. It doesn't support connections with > 8 bpp color depth, but your VNC viewer requests 24 bpp. Please set up your VNC viewer to use the formats RGB332 or BGR233. If you need support for > 8 bpp, or you'd like to use Bochs in a web browser you should try with the 'vncsrv' gui that requires the libvncserver library. You should visit the Bochs page on GitHub to follow the development.
The limitations of the RFB gui are documented. It doesn't support connections wit > 8 bpp color depth, but your VNC viewer requests 24 bpp. Please set up your VNC viewer to use the formats RGB332 or BGR233. If you need support for > 8 bpp, or you'd like to use Bochs in a web browser you should try with the 'vncsrv' gui that requires the libvncserver library. You should visit the Bochs page on GitHub to follow the development.
Hi Latest mac os with homebrew This works : ./configure --enable-debugger --enable-x86-64 --enable-all-optimizations --with-x11 This can't. : ./configure --enable-debugger --enable-x86-64 --enable-all-optimizations --with-rfb g++ -o bochs -fpascal-strings -fno-common -Wno-four-char-constants -Wno-unknown-pragmas -Dmacintosh -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -DBX_SHARE_PATH=\"/usr/local/share/bochs\" logio.o main.o config.o pc_system.o osdep.o plugin.o crc.o bxthread.o -framework IOKit -framework...
hi all I built bochs by ./configure --enable-debugger --disable-debugger-gui --with-rfb --disable-readline --with-sdl2 --enable-fpu --enable-show-ips I start bochs by bochs -q -f bochsrc.txt ############################################################### # bochsrc.txt file for DLX Linux disk image. ############################################################### # how much memory the emulated machine will have megs: 32 # filename of ROM images romimage: file=$BXSHARE/BIOS-bochs-latest vgaromimage:...
Could you add Hercules text and optional graphics mode support?
beware, that so called "software bug report" is malware
AGP or PCI Express support
AGP is WIP, For PCI-Express where is another request open in github. Closing this as duplicate
Add "Run To Cursor" command to debug
New 'rla' command was added to debugger exact to do that mentioned Run to linear address. GUI debugger support (another feature request) is next step
Bochs should use the OSX toolbar
Seems like outdate, if the request still relevant - please reopen on github
compressed harddisc image format
new FreeDOS BOchs image
Already become obsolete
Utilities to mount bochs images as hard disks
Not a Bochs request, tools like WinImage already able to manipulate disk images from Bochs
VPN client
Should be already possible. Not a Bochs request.
I haven't tried compiling Bochs I will admit that. Would rather just use the product. I use wsl2 on windows and the wsl terminal to compile my os but I use Bochs and when I choose Bochs debugger to run the os or floppy, it will not let me copy the information from the Bochs debugger. You run the os on that Bochs screen right? That Bochs screen is representing a monitor. When making an os I think it would be fun to test having a second monitor or Bochs screen so you can move apps around from screen...
PocketPC support
Windows CE is dead and obsolete
Ok, thanks, at least you know what I am talking about now lmao!!
I haven't tried compiling Bochs I will admit that. Would rather just use the product. I use wsl2 on windows and the wsl terminal to compile my os but I use Bochs and when I choose Bochs debugger to run the os or floppy, it will not let me copy the information from the Bochs debugger. You run the os on that Bochs screen right? That Bochs screen is representing a monitor. When making an os I think it would be fun to test having a second monitor or Bochs screen so you can move apps around from screen...
Request for 2nd monitor (2nd emulated montitor) already present even here. Multi-Head support: https://sourceforge.net/p/bochs/feature-requests/15/ It is probably hard to do so nobody tries. If you want to highlight it more - better to open another request on github. But one request for one feature.
I haven't tried compiling Bochs I will admit that. Would rather just use the product. I use wsl2 on windows and the wsl terminal to compile my os but I use Bochs and when I choose Bochs debugger window to run the os or floppy, it will not let me copy the information from the Bochs debugger. You run the os on that Bochs screen right? That Bochs screen is representing a monitor. When making an os I think it would be fun to test having a second monitor or Bochs screen so you can move apps around from...