Bochs: dlopen falied for module 'x'

I was very happy when i saw that the Bochs-PC-Emulator was already installed with my new Knoppix.
But it does not work in the current state:
I get the message:

Code:

---

>>PANIC<< dlopen failed for module 'x': file not found

---

Reading the manpage on dlopen i learned, that this is a C-function to open dynamically linked librarys.
So i suppose the problem is that bochs does not know were the x-library is to find. To find out more about the libs bochs's needs i did

Code:

---

ldd /usr/bin/bochs

---

but i was told, that bochs was no dynamically linked executable.
I assume i just have to change some path somewhere or copy some lib to another directory to make it work, but i don't know which lib to what directory or what path to change in which config-file.
Googling for a solution i only found 2 or 3 other people with the same problem but no solution.
But since the knoppix-installation is always the same i think someone else here must have had the same problem!
Please help me!

I am using bochs running from CD and with my disk images loaded on a fat partition. Win98 is painfully slow and I can't get the networking going, but debian 3.0 works great (networking and xwindows). You may want to state the release date you're working with also. I'm using 6-6-03 for right now, just gettting ready to upgrade to the latest and greatest.

A couple of notes regarding what works for me...

First, you have to make sure you run bochs from the command prompt as root.

Second, make sure you have a working .bochsrc configuration file in the subdirectory or in ~/.bochs

You may need to post your .bochsrc file here for additional help with troubleshooting.

Here is my working copy of a linux .bochsrc file, you will need to edit for your particulars, but it works great for me.:

# You many 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 wxWindows library, cross platform
# nogui no display at all
#
# NOTE: if you use the "wx" configuration interface, you must also use
# the "wx" display library.
#================================================= ======================
#display_library: x
#display_library: sdl
#display_library: term
display_library: wx

#================================================= ======================
# ROMIMAGE:
# You now need to load a ROM BIOS into F0000-FFFFF. I've wiped
# out most of the BIOS hooks, and replace them with real BIOS
# support. Normally, you can use a precompiled BIOS in the bios/
# directory of the source tree, named BIOS-bochs-latest.
# You can also use the environment variable $BXSHARE to specify the
# location of the BIOS.
#================================================= ======================
romimage: file=/usr/share/bochs/BIOS-bochs-latest, address=0xf0000
#romimage: file=/usr/share/bochs/BIOS-bochs-2-processors, address=0xf0000
#romimage: file=/usr/share/bochs/BIOS-bochs-4-processors, address=0xf0000
#romimage: file=/usr/share/bochs/BIOS-bochs-8-processors, address=0xf0000

#================================================= ======================
# MEGS
# set this to the default number of Megabytes of memory you want
# to emulate. You may also pass the '-megs xyz' option to bochs
#
# The default is 32MB, most OS's won't need more than that.
#================================================= ======================
#megs: 256
#megs: 128
#megs: 64
megs: 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).
# It can also be a convenient way to upload some arbitary 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

#================================================= ======================
# VGAROMIMAGE
# You now need to load a VGA ROM BIOS into C0000.
#================================================= ======================
vgaromimage: /usr/share/vgabios/vgabios.bin
#vgaromimage: /usr/share/vgabios/vgabios.debug.bin

#================================================= ======================
# 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'.
#
# 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)
#
# 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 GNU/Linux. On WinNT and Win2k, use
# drive letters such as a: or b: as the path. Raw floppy access is not
# supported on Windows 95 and 98.
#================================================= ======================
floppya: 1_44=/dev/fd0, status=inserted
#floppya: 1_44=/dev/fd0H1440, status=inserted
#floppya: 1_44=$HOME/.bochs/$GUEST.fd0, status=inserted

#================================================= ======================
# FLOPPYB:
# See FLOPPYA above for syntax
#================================================= ======================
#floppyb: 1_44=/dev/fd1, status=inserted
#floppyb: 1_44=/dev/fd1H1440, status=inserted
#floppyb: 1_44=$HOME/.bochs/$GUEST.fd1, 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 address and the irq must be specified.
#
# ata0 is enabled by default, with ioaddr1=0x1f0, ioaddr2=0x3f0, irq=14
#
# 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=0x3e8, irq=11
# ata3: enabled=1, ioaddr1=0x168, ioaddr2=0x368, irq=9
#================================================= ======================
ata0: enabled=1, ioaddr1=0x1f0, ioaddr2=0x3f0, irq=14
#ata1: enabled=0, ioaddr1=0x170, ioaddr2=0x370, irq=15
#ata2: enabled=0, ioaddr1=0x1e8, ioaddr2=0x3e8, irq=11
#ata3: enabled=0, ioaddr1=0x168, ioaddr2=0x368, 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]
# 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 transation of the bios, only for disks [none|lba|large|rechs|auto]
# model= string returned by identify device command
#
# 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.
# 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, cylinders, heads, and spt are mandatory for type=disk
# The path is mandatory for type=cdrom
#
# Default values are:
# biosdetect=auto, translation=auto, model="Generic 1234"
#
# The biosdetect option has currently no effect on the bios
#
# Examples:
# ata0-master: type=disk, path=10M.sample, cylinders=306, heads=4, spt=17
# ata0-slave: type=disk, path=20M.sample, cylinders=615, heads=4, spt=17
# ata1-master: type=disk, path=30M.sample, cylinders=615, heads=6, spt=17
# ata1-slave: type=disk, path=46M.sample, cylinders=940, heads=6, spt=17
# ata2-master: type=disk, path=62M.sample, cylinders=940, heads=8, spt=17
# ata2-slave: type=disk, path=112M.sample, cylinders=900, heads=15, spt=17
# ata3-master: type=disk, path=483M.sample, cylinders=1024, heads=15, spt=63
# ata3-slave: type=cdrom, path=iso.sample, status=inserted
#================================================= ======================
ata0-master: type=disk, path="$HOME/.bochs/win98/win98.img", cylinders=1015, heads=16, spt=63
#ata0-master: type=disk, path="$HOME/.bochs/dlxlinux/hd10meg.img", cylinders=306, heads=4, spt=17
ata0-slave: type=cdrom, path="/dev/cdrom", status=inserted
#ata0-slave: type=cdrom, path="$HOME/.bochs/$GUEST.cd0", status=inserted
#ata1-master: type=disk, path="$HOME/.bochs/$GUEST.hd1", cylinders=, heads=16, spt=63

#================================================= ======================
# NEWHARDDRIVESUPPORT: enabled=[0|1]
# As of cvs version on 5/17/2001, newharddrivesupport is on by default.
#================================================= ======================
#newharddrivesupport: enabled=1

#================================================= ======================
# BOOT:
# This defines your boot drive.
# 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: floppy
boot: disk
#boot: cdrom
#boot: c
#================================================= ======================
# 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=1
floppy_bootsig_check: disabled=0

#================================================= ======================
# LOG:
# Give the path of the log file you'd like Bochs debug and misc. verbage
# to be written to. If you really don't want it, make it /dev/null. :^(
#
# Examples:
# log: ./bochs.out
# log: /dev/tty
#================================================= ======================
log: /dev/stdout
#log: /dev/null
#log: /tmp/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 cpu0 current eip
# %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=ask
error: action=report
info: action=report
debug: action=ignore

#================================================= ======================
# 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.out
debugger_log: -

#================================================= ======================
# com1:
# This defines a serial (COM) port. 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.
#================================================= ======================
com1: enabled=1, dev=/dev/ttyS0


#================================================= ======================
# PARPORT1:
# 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 GNU/Linux,
# "lpt1" on win32 platforms).
#
# Examples:
# parport1: enabled=1, file="parport.out"
# parport1: enabled=1, file="/dev/lp0"
# parport1: enabled=0
#================================================= ======================
parport1: enabled=1, file="/dev/lp0"
#parport1: enabled=1, file="parport.out"

#================================================= ======================
# 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=only 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-continous sound. 750000 is usually a good value. This needs a
# reasonably correct setting for IPS.
#
# For an example look at the next line:
#================================================= ======================

sb16: midimode=1, midi=/dev/midi00, wavemode=1, wave=/dev/dsp, loglevel=2, log=/dev/stdout, dmatimer=600000

#================================================= ======================
# VGA_UPDATE_INTERVAL:
# Video memory is scanned for updates and screen updated every so many
# virtual seconds. The default is 300000, about 3Hz. This is generally
# plenty. Keep in mind that you must tweak the 'ips:' directive
# to be as close to the number of emulated instructions-per-second
# your workstation can do, for this to be accurate.
#
# Examples:
# vga_update_interval: 250000
#================================================= ======================
vga_update_interval: 300000

# using for Winstone '98 tests
#vga_update_interval: 100000

#================================================= ======================
# KEYBOARD_SERIAL_DELAY:
# Approximate time in microseconds that it takes one character to
# be transfered from the keyboard to controller over the serial path.
# Examples:
# keyboard_serial_delay: 200
#================================================= ======================
keyboard_serial_delay: 250

#================================================= ======================
# KEYBOARD_PASTE_DELAY:
# Approximate time in microseconds between attempts to paste
# characters to the keyboard controller. This leaves time for the
# guest os to deal with the flow of characters. The ideal setting
# depends on how your operating system processes characters. The
# default of 100000 usec (.1 seconds) was chosen because it works
# consistently in Windows.
#
# If your OS is losing characters during a paste, increase the paste
# delay until it stops losing characters.
#
# Examples:
# keyboard_paste_delay: 100000
#================================================= ======================
keyboard_paste_delay: 100000

#================================================= ======================
# FLOPPY_COMMAND_DELAY:
# Time in microseconds to wait before completing some floppy commands
# such as read/write/seek/etc, which normally have a delay associated.
# I had this hardwired to 50,000 before.
#
# Examples:
# floppy_command_delay: 50000
#================================================= ======================
floppy_command_delay: 500

#================================================= ======================
# IPS:
# Emulated Instructions Per Second. This is the number of IPS that bochs
# is capable of running on your machine. Read the note in config.h
# on how to find this. Make sure to recompile after.
#
# 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
# __________________________________________________ ______________
# 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
# 166Mhz 64bit Sparc with Solaris 2.x approx 0.75 Mips
# 200Mhz Pentium with Linux 2.x approx 0.5 Mips
#
#================================================= ======================
ips: 1000000

#================================================= ======================
# PIT:
# The PIT is the programmable interval timer. It has an option that tries to
# keep the PIT in sync with real time. This feature is still experimental,
# but it may be useful if you want to prevent Bochs from running too fast, for
# example a DOS video game. Be aware that with the realtime pit option, your
# simulation will not be repeatable; this can a problem if you are debugging.
#================================================= ======================
#pit: realtime=1

#================================================= ======================
# mouse: Not used in any of the GUI specific modules, but the option
# bx_options.mouse_enabled is set to this value. The idea,
# is that the GUI code should not generate mouse events when
# not enabled. The hardware emualation itself is not disabled
# by this. This is to facilitate deterministic runs of bochs.
#
# Examples:
# mouse: enabled=1
# mouse: enabled=0
#
# I wouldn't recommend enabling the mouse by default, unless you have a
# really good reason to do so.
#================================================= ======================
mouse: enabled=0

#================================================= ======================
# private_colormap: Request that the GUI create and use it's own
# non-shared colormap. This colormap will be used
# when in the bochs window. If not enabled, a
# shared colormap scheme may be used. Not implemented
# on all GUI's.
#
# Examples:
# private_colormap: enabled=1
# private_colormap: enabled=0
#================================================= ======================
private_colormap: enabled=0

#================================================= ======================
# fullscreen: ONLY IMPLEMENTED ON AMIGA
# Request that Bochs occupy the entire screen instead of a
# window.
#
# Examples:
# fullscreen: enabled=0
# fullscreen: enabled=1
#================================================= ======================
fullscreen: enabled=0
screenmode: name="sample"

#================================================= ======================
# ne2k: NE2000 compatible ethernet adapter
#
# Examples:
# ne2k: ioaddr=IOADDR, irq=IRQ, mac=MACADDR, ethmod=MODULE, ethdev=DEVICE, script=SCRIPT
#
# ioaddr, irq: You probably won't need to change ioaddr and irq, unless there
# are IRQ conflicts.
#
# mac: The MAC address MUST NOT match the address of any machine on the net.
# Also, the first byte must be an even number (bit 0 set means a multicast
# address), and you cannot use ff:ff:ff:ff:ff:ff because that's the broadcast
# address. For the ethertap module, you must use fe:fd:00:00:00:01. There may
# be other restrictions too. To be safe, just use the b0:c4... address.
#
# ethdev: The ethdev value is the name of the network interface on your host
# platform. On UNIX machines, you can get the name by running ifconfig. On
# Windows machines, you must run niclist to get the name of the ethdev.
# Niclist source code is in misc/niclist.c and it is included in Windows
# binary releases.
#
# script: The script value is optionnal, and is the name of a script that
# is executed after bochs initialize the network interface. You can use
# this script to configure this network interface, or enable masquerading.
# This is mainly useful for the tun/tap devices that only exist during
# Bochs execution. The network interface name is supplied to the script
# as first parameter
#================================================= ======================
ne2k: ioaddr=0x280, irq=9, mac=b0:c4:20:00:00:00, ethmod=linux, ethdev=eth0
# ne2k: ioaddr=0x280, irq=9, mac=fe:fd:00:00:00:01, ethmod=tap, ethdev=tap0
# ne2k: ioaddr=0x280, irq=9, mac=fe:fd:00:00:00:01, ethmod=tuntap, ethdev=tun0, script=./tunconfig

#================================================= ======================
# KEYBOARD_MAPPING:
# This enables a remap of a physical localized keyboard to a
# virtualized us keyboard, as the PC architecture expects.
# If enabled, the keymap file must be specified.
#
# Examples:
# keyboard_mapping: enabled=1, map=gui/keymaps/x11-pc-de.map
#================================================= ======================
keyboard_mapping: enabled=0, map=/usr/share/bochs/keymaps/x11-pc-de.map

#================================================= ======================
# KEYBOARD_TYPE:
# Type of keyboard return by a "identify keyboard" command to the
# keyboard controler. It must be one of "xt", "at" or "mf".
# Defaults to "mf". It should be ok for almost everybody. A known
# exception is french macs, that do have a "at"-like keyboard.
#
# Examples:
# keyboard_type: mf
#================================================= ======================
#keyboard_type: mf

#================================================= ======================
# USER_SHORTCUT:
# This defines the keyboard shortcut to be sent when you press the "user"
# button in the headerbar. The shortcut string can be a combination of
# these key names: "alt", "bksp", "ctrl", "del", "esc", "f1", "f4", "tab"
# and "win". Up to 3 keys can be pressed at a time.
#
# Example:
# user_shortcut: keys=ctrlaltdel
#================================================= ======================
#user_shortcut: keys=ctrlaltdel

#================================================= ======================
# 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), the simulation will be
# started at the current time of the host.
#
# Examples:
# time0: 1 # Now
# time0: 315529200 # Tue Jan 1 00:00:00 1980
# time0: 631148400 # Mon Jan 1 00:00:00 1990
# time0: 938581955 # Wed Sep 29 07:12:35 1999
# time0: 946681200 # Sat Jan 1 00:00:00 2000
#================================================= ======================
#time0: 938581955

#================================================= ======================
# other stuff
#================================================= ======================
# magic_break

#load32bitOSImage: os=nullkernel, path=../kernel.img, iolog=../vga_io.log
#load32bitOSImage: os=linux, path=../linux.img, iolog=../vga_io.log, initrd=../initrd.img
i440fxsupport: enabled=0

Quote:

---

Originally Posted by pau1knopp

You may want to state the release date you're working with also. I'm using 6-6-03 for right now, just gettting ready to upgrade to the latest and greatest.

---

I am using the version, that comes with Knoppix 3.3(i think it is 2.0)
That's also why i am sure that it SHOULD be correctly installed.

Quote:

---

First, you have to make sure you run bochs from the command prompt as root.

---

i do that...

Quote:

---

Second, make sure you have a working .bochsrc configuration file in the subdirectory or in ~/.bochs

---

The file works with Bochs under Windows... I got it from www.osdever.net.
And it is in the correct dir, and Bochs tells me it is loading it.
The only wrong thing about it MIGHT be, that there are special things to add for Bochs under Linux?
Here it is:

Code:

---

# how much memory the emulated machine will have
# if you have less than 64MB of memory in your actuall computer, set this lower(16 is good)
megs: 32

# filename of ROM images
# note that if before a filename we put "../" then the file is looked
# for in the directory above that the current directory(the one the configuration
# file is in).
romimage: file=../BIOS-bochs-latest, address=0xf0000
vgaromimage: ../VGABIOS-elpin-2.40

# we want a floppy drive(called a), the disk image that we are using is called "1.44"
floppya: 1_44=1.44, status=inserted

# choose the boot disk.
boot: a

# where do we send log/error messages?
log: bochsout.txt

# disable the mouse unless your OS uses it
mouse: enabled=0

---

-Thank you for helping - i searched all the web because of this problem and the only thing i found is people with the same problem, but no answers...

EDIT:
I just read your configuration file and because my problem must have to do with the window system i added
display_library : term
to the top of my file. Now i get:
dlopen failed for module term
- the same error as before just with term instead of x.
So there must be something wrong with the display library in general.

apt-get install bochs-x
(for the 'x' library)

And

apt-get install bochs-wx
(for the 'wx' library)

Hope it helps.
Vikram