diff options
Diffstat (limited to 'results/classifier/deepseek-2-tmp/output/boot/1314667')
| -rw-r--r-- | results/classifier/deepseek-2-tmp/output/boot/1314667 | 45 |
1 files changed, 0 insertions, 45 deletions
diff --git a/results/classifier/deepseek-2-tmp/output/boot/1314667 b/results/classifier/deepseek-2-tmp/output/boot/1314667 deleted file mode 100644 index 5305b75c..00000000 --- a/results/classifier/deepseek-2-tmp/output/boot/1314667 +++ /dev/null @@ -1,45 +0,0 @@ - -PMPrebUSB - appcrash of qemu in Win-7-64bit - -I am not sure if this issue is a bug of qemu or by Win-7. -I want to test in advance with QEMU the ability if my USB-Rescue-Drive is -booting correctly. I have Win-7-64 and run qemu v.o.15.1.0 out of the installed RMPrepUSB v.2.1.719 -program. The settings for the preparation of my USB drive were FAT32 boot as -HD, bootloader WinPE/Win-7/Vista, set for running iso-files directly in %_ISO -\MAINMENU\Hiren’sBootCD.iso. When I run Qemu I get the messages in the cmd starting window it says: - -Administrator: RMPrepUSB QEMU Launcher -************************************** -EXECUTING "C:\Program Files (x86)\RMPrepUSB\qemu\STARTFROMUSB.cmd" -DRIVE NUMBER=3 -MEMORY SIZE=1000 -HARD DISK IMAGE=harddisk.img -NOWRITE= -Found OS=VISTA_OR_LATER -Sending command Start_VM.exe 3 500 qemu.exe -L . -name "RMPrepUSB Emulation -Session RAM=1000MB VirtualHDD=harddisk.i -lt+LCtrl)" -boot c -m 1000 -drive file=\\. -\PhysicalDrive3,if=ide,index=0,media=disk -hdb harddisk.img to shell... - -Win-7: in the second window appears: -*********************************** --->qemu funktioniert nicht mehr -Problemsignatur: - Problemereignisname: APPCRASH - Anwendungsname: qemu.exe - Anwendungsversion: 0.15.1.0 - Anwendungszeitstempel: 4f478c16 - Fehlermodulname: qemu.exe - Fehlermodulversion: 0.15.1.0 - Fehlermodulzeitstempel: 4f478c16 - Ausnahmecode: 40000015 - Ausnahmeoffset: 00053b06 - Betriebsystemversion: 6.1.7601.2.1.0.256.48 - Gebietsschema-ID: 1031 - Zusatzinformation 1: bf8d - Zusatzinformation 2: bf8d49108a2e5a0707fc48438e01652a - Zusatzinformation 3: b0f1 - Zusatzinformation 4: b0f155b0f1de9c5eb22bd6d100737cbe - -If somebody can understand that behaviour I appreciate everybodies help. Thank you with regards -H.O. \ No newline at end of file |