getting some sort of graphics device that x11 / ms
windows can display larger resolutions than 640x480 and
can select video memory would be good, along with 16
and 24 bit colour depths.
also, disk images that can grow and shrink would be
good. this could be accomplished by splitting the image
into 4MB chunks. each time data is written to a new
chunk, it is added to the end of the variable size
file, and a second file which simply contains a list of
the order of the chunks would be written to showing
where in the disk file that chunk lies. an option could
then be put into the bochs configure menu to search
through the disk image file and remove any unused
chunks (blocks - whatever you want to call them).
obviously any unwritten chunks would by default contain
nothing but zeros for reading purposes and would not
need to be created into the disk until something other
than zero's is written to them. this may be slightly
slower, but it does save disk space. note that the file
which describes where the chunks lie in the actual disk
data file need only be constructed of say 4-byte values
(to allow for huge disk sizes) and would mean that one
extra byte of disk space would be required for every
megabyte of the disk size - aka a 5gigabyte image file
would need about a 5k description file. hope that
explains it clearly - sorry not so good with words.
mjjw.
Logged In: YES
user_id=376477
24 and 32 bpp graphics modes and sparse/ growable disk
support are present in Bochs 2.1.1.