[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] [Bug 1314667] Re: PMPrebUSB - appcrash of qemu in Win-7-64b

From: Steve Si
Subject: [Qemu-devel] [Bug 1314667] Re: PMPrebUSB - appcrash of qemu in Win-7-64bit
Date: Thu, 01 May 2014 08:40:40 -0000

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.

You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

  PMPrebUSB - appcrash of qemu in Win-7-64bit

Status in QEMU:

Bug description:
  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"
  HARD DISK IMAGE=harddisk.img
  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
    Problemereignisname:        APPCRASH
    Anwendungsname:     qemu.exe
    Anwendungszeitstempel:      4f478c16
    Fehlermodulname:    qemu.exe
    Fehlermodulzeitstempel:     4f478c16
    Ausnahmecode:       40000015
    Ausnahmeoffset:     00053b06
    Betriebsystemversion:       6.1.7601.
    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

To manage notifications about this bug go to:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]