> Could you try to find out which change in qemu triggers this behaviour?
> I don't have a windows to test, and given there weren't (yet :-) loud
> complaints I figure the problem might be connected to you local setup.
Ah, found it. I guess cvs after September requires updated .bin files.
Sorry.
Am Dienstag, den 02.01.2007, 23:48 -0800 schrieb Don Kitchen:
> I just compiled CVS and have experienced a regression with some windows
> qcow images (2000 pro and server). The images work with cvs I compiled back
> in July, but current cvs produces blue screen with INACCESSIBLE_BOOT_DEVICE.
>
> I
Don Kitchen wrote:
> I just compiled CVS and have experienced a regression with some windows
> qcow images (2000 pro and server). The images work with cvs I compiled back
> in July, but current cvs produces blue screen with INACCESSIBLE_BOOT_DEVICE.
Could you try to find out which change in qemu t
I just compiled CVS and have experienced a regression with some windows
qcow images (2000 pro and server). The images work with cvs I compiled back
in July, but current cvs produces blue screen with INACCESSIBLE_BOOT_DEVICE.
I'm running under linux, with only option -hda disk.
Thanks
_
