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

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

[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.

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1314667

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

Status in QEMU:
  New

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"
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1314667/+subscriptions

[Qemu-devel] [Bug 1314667] Building a USB-Drive with EasyToBoot (E2B) and PMPrebUSB

[Ohlerth Hans]

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.
>


** Attachment added: "email to Steve Si -USB-Boot-E2B-RMPrepUSB.doc"
   https://bugs.launchpad.net/bugs/1314667/+attachment/4105689/+files/email%20to%20Steve%20Si%20-USB-Boot-E2B-RMPrepUSB.doc

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1314667

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

Status in QEMU:
  New

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"
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1314667/+subscriptions

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

[Thomas Huth]

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?

** Changed in: qemu
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1314667

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

Status in QEMU:
  Incomplete

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"
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1314667/+subscriptions

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

[Launchpad Bug Tracker]

[Expired for QEMU because there has been no activity for 60 days.]

** Changed in: qemu
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1314667

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

Status in QEMU:
  Expired

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"
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1314667/+subscriptions