1 -------------------------------------------------------------
2 BOCHS TESTING FORM Version 0.4
3 -------------------------------------------------------------
5 Because of the variety of platforms and configurations that Bochs
6 supports, it is difficult for any one person to test it thoroughly.
7 This form is intended to help the Bochs developers keep track of test
8 results from different sources. To avoid confusion, this form should
9 be submitted once for each combination of host OS and guest OS you
10 try. For example: your host OS is Debian Linux and you get both Win95
11 and FreeDOS to start up. You would send one form for
12 Win95-under-Debian and a second form for FreeDOS-under-Debian. In
13 this case it would save time to fill in the host OS part, copy it a
14 few times and fill out the guest OS part for each copy.
16 To fill in a blank such as [__], replace the underlines and leave
17 the brackets. Example: [Sun Ultrasparc 10]. To fill in a
18 multiple-choice, just put an X in the brackets. Example: [X]
19 Mail completed forms to bochs-developers@lists.sourceforge.net
28 What is your email address?
31 Do you mind if your name and email address are placed on a testing results
32 web page so that people with a similar setup can write to you?
33 [ ] Ok, put it on a web page
34 [ ] No, keep my address private.
36 What type of hardware are you using, e.g. 2400 MHz Intel Pentium 4.
39 What operating system are you using? Please be specific, e.g.
40 Redhat Linux 6.2 with 2.2.16 kernel.
43 What version of bochs are you using?
44 [ ] compiled from version 2.3.7
45 [ ] compiled from version [_____]
46 [ ] I compiled it from the CVS sources from date: [__]
47 [ ] other source distribution from URL: [__]
48 [ ] binary distribution from URL: [__]
50 Please fill in the next few questions only if you compiled Bochs
51 yourself, as opposed to downloading a binary.
53 Did the configure script run ok, and detect your hardware and
56 [ ] No, configure crashed.
57 [ ] No, configure ran ok but produced a bad configuration.
58 [ ] No, I cannot run configure on my platform (win32 and mac).
60 If you used configure, what arguments did you give it? If you used a
61 .conf.* script, give the name of the .conf script instead.
64 What compiler did you use? (Please include version.)
67 Did Bochs compile clean without any hacking?
71 If you had to make changes to compile, please summarize the problems you
75 End of compile-specific questions!
77 What guest operating system are you using inside bochs?
80 Are you booting from a floppy or hard disk?
84 [ ] raw hard drive (is this even possible?)
87 Did the guest operating system boot successfully?
91 If no, what error messages do you see on the console or in the log file?
94 What applications worked under this guest operating system?
97 What applications failed under this guest operating system? Did the
98 application function incorrectly, crash Bochs, or what? If you got a
99 panic, paste in the panic message that you received with some
100 description of what was happening at the time.
103 The remaining questions are about Bochs features that you may not have
104 used. If you tried out the feature, move the X to the "works" or
108 tested ok Fails Comments?
109 x86-64 [X] [ ] [ ] [__]
110 floating point [X] [ ] [ ] [__]
112 keyboard [X] [ ] [ ] [__]
113 floppy disk [X] [ ] [ ] [__]
114 raw floppy disk [X] [ ] [ ] [__]
115 hard disk [X] [ ] [ ] [__]
116 mouse [X] [ ] [ ] [__]
117 cdrom [X] [ ] [ ] [__]
118 sb16 [X] [ ] [ ] [__]
119 ne2000 [X] [ ] [ ] [__]
120 i440FX pci [X] [ ] [ ] [__]
121 debugger [X] [ ] [ ] [__]
122 external loader [X] [ ] [ ] [__]
123 save/restore [X] [ ] [ ] [__]
125 Cirrus Logic SVGA [X] [ ] [ ] [__]
128 Thank you for your contribution in the Bochs testing effort! Please
129 mail completed forms to bochs-developers@lists.sourceforge.net