summary refs log tree commit diff stats
path: root/results/classifier/105/boot/1314667
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/105/boot/1314667')
-rw-r--r--results/classifier/105/boot/1314667126
1 files changed, 126 insertions, 0 deletions
diff --git a/results/classifier/105/boot/1314667 b/results/classifier/105/boot/1314667
new file mode 100644
index 00000000..d7230ee8
--- /dev/null
+++ b/results/classifier/105/boot/1314667
@@ -0,0 +1,126 @@
+boot: 0.826
+device: 0.822
+mistranslation: 0.814
+other: 0.811
+socket: 0.810
+instruction: 0.791
+assembly: 0.773
+semantic: 0.750
+vnc: 0.724
+graphic: 0.683
+network: 0.675
+KVM: 0.673
+
+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.
+
+The QEMU used in RMPrepUSB is 32-bit only - it won't run 64-bit programs. Normally, Windows will just display an error message saying it needs a 64-bit system. Use Virtual Box for 64-bit OS testing and DavidB's Virtual Machine USB Boot application - see www.rmprepusb.com Tutorial #4
+
+Hello,
+thank you for answering very fast. But in Google is advertised
+/"//RMPrepUSB/ <http://www.rmprepusb.com/>
+
+
+      www.rmprepusb.com/‎Diese Seite übersetzen
+      <http://translate.google.com/translate?hl=de&sl=en&u=http://www.rmprepusb.com/&prev=/search%3Fq%3DRMPrepUSB%2B64%2Bbit%2Bqemu%26hl%3Dde%26biw%3D905%26bih%3D508>
+
+Rating for /rmprepusb/.com .... 32-bit and /64/-/bit/ versions are fully 
+supported. ... 2 /RMPrepUSB/ Help form screenshot (includes F11 = Run 
+/QEMU/ emulator, and ...
+‎Download <http://www.rmprepusb.com/documents/release-2-0> - ‎Latest 
+RMPrepUSB versions 
+<http://www.rmprepusb.com/documents/rmprepusb-beta-versions> 
+- ‎Easy2Boot 
+<http://www.rmprepusb.com/tutorials/72---easyboot---a-grubdos-multiboot-drive-that-is-easy-to-maintain/e2bv1> 
+- ‎47 - How to install Windows 
+<http://www.rmprepusb.com/tutorials/win7onusb>"
+is that correct and valid or not? Fully supported means to me, that qemu 
+should work too on Win-7-64bit.. Or why does RMPrepUSB 
+<http://www.rmprepusb.com/documents/rmprepusb-beta-versions> not change 
+this at times of XP-64 bit, Vista-64 bit, Win-7 64 bit, Win-8  64bit, 
+Win-8.1 64bit. Thank you with kind regards
+H.Ohlerth
+
+
+
+
+
+Am 30.04.2014 20:55, schrieb Steve Si:
+> The QEMU used in RMPrepUSB is 32-bit only - it won't run 64-bit
+> programs. Normally, Windows will just display an error message saying it
+> needs a 64-bit system. Use Virtual Box for 64-bit OS testing and
+> DavidB's Virtual Machine USB Boot application - see www.rmprepusb.com
+> Tutorial #4
+>
+
+
+
+RMPrepUSB will run  ON 32-bit and 64-bit Operating Systems.
+That is not the same thing as  QEMU will run a 64-bit Operating System.
+There is a 64-bit version of QEMU but it is very buggy and won't even boot a 64-bit Vista/7 WinPE, so it is not included.
+As I said, normally when booting a 64-bit OS under QEMU, you will see a Windows message saying that the system is not a 64-bit system. For some reason you are not seeing this on your system.
+
+
+Hello Steve, I had a lot of trouble over the weekend building a 
+sufficiently working bootable "USB-Rescue-Drive". I summed it up in an 
+attached  Word-Dokument and I am sure, you have the knowledge to solve 
+my problems. For your detailed help I will expect with lots of kind regards
+
+H.Ohlerth
+
+
+Am 01.05.2014 10:40, schrieb Steve Si:
+> RMPrepUSB will run  ON 32-bit and 64-bit Operating Systems.
+> That is not the same thing as  QEMU will run a 64-bit Operating System.
+> There is a 64-bit version of QEMU but it is very buggy and won't even boot a 64-bit Vista/7 WinPE, so it is not included.
+> As I said, normally when booting a 64-bit OS under QEMU, you will see a Windows message saying that the system is not a 64-bit system. For some reason you are not seeing this on your system.
+>
+
+
+
+Looking through old bug tickets... can you still reproduce this issue with the latest (64-bit) version of QEMU? Or could we close this ticket nowadays?
+
+[Expired for QEMU because there has been no activity for 60 days.]
+