Hi, The error line is: *** STOP: 0x0000007B (0xF789AA94, 0xC0000034, 0x00000000, 0x00000000) Nothing more! (Of course there are some inrelevant text line about chkdsk, etc.)> Basically, what's required is the "STOP:" line + the image where it > fails (so, the line below). Image being likely to be NTOSKRNL.EXE >Nothing about NTOSKRNL.EXE on the blue screen!> > I don't want Virtio. I want to boot my image first. As I mentioned > > I can't use the mergeide.req on the physical machine but I can do > > anything with the image (if I don't het error messages from the > > virt-win-reg). > > Well, then, you can mount the image in a Linux machine and use the > chntpw tool to edit manually the registry and add the missing driver > information? >Yes, I think.> Basically, most you're missing here is linking some hardware classes > to proper device (likely intelide.sys) so that your Windows can > properly setup its storage stack. >I think this is the problem. How can we solve it? TIA, Ruzs
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/07/2015 20:01, Ruzsinszky Attila wrote:> The error line is: *** STOP: 0x0000007B (0xF789AA94, 0xC0000034, > 0x00000000, 0x00000000)Perfect, this is what was expected. This should be easy to fix.>>> I don't want Virtio. I want to boot my image first. As I >>> mentioned I can't use the mergeide.req on the physical machine >>> but I can do anything with the image (if I don't het error >>> messages from the virt-win-reg). >> >> Well, then, you can mount the image in a Linux machine and use >> the chntpw tool to edit manually the registry and add the missing >> driver information? >> > Yes, I think.Great, then, it opens possibilities. Let's try the following: - - Install chntpw - - Mount your disk on Linux - - Move to Windows/System32/config (beware the case!) - - Now, start registry editor: chntpw -e sam system security software (beware the case, again!) The following commands are to type in chntpw prompt: - - hive 1 (to move to system) - - cd ControlSet001 - - cd Control - - cd CriticalDeviceDatabase - - Check you have the following keys: primary_ide_channel, secondary_ide_channel, pci#ven_8086&dev_7010, pci#ven_8086&dev_7111 keys. Some will be missing (otherwise, you'd boot ;-)). - - Add the missing ones. For example: 'nk pci#ven_8086&dev_7111' followed by: 'cd pci#ven_8086&dev_7111' followed by 'nv 1 Service' (1 for REG_SZ) followed by 'ed Service' and type intelide. Proceed like that will all the missing keys & values[1], 'cd ..' when you're done with all the values of a key, to proceed for the others - - cd .. (you're now in Control) - - cd .. (you're now in ControlSet001) - - cd Services - - Check you have the following keys: atapi and intelide - - Add the missing ones[2]. REG_DWORD type is 4 when doing nv. (like nv 4 ErrorControl) - - You're done, so: q to quit chntpw (of course, reply 'y' to write hives) Back to your linux term: - - cd ../drivers/ - - Check you have atapi.sys and intelide.sys. In case you don't, extract them from the cab file you can find in Windows\Driver Cache\i386 - - Umount - - Try to boot again, and report. What did you do? You just added the missing hardware ClassGUID for Intel IDE (which is what Qemu uses) to Windows registry. When installing, Windows just sets the strictly minimalistic ones to match your hardware. And then, you defined the associated drivers with these ClassGUID. These are defined as service to allow defining how they boot. When Start is set to 00000000, it means that you want them to be started at boot: when Windows needs to find its boot device. I hope this helped! [1]: key {value(type): data} primary_ide_channel { ClassGUID(REG_SZ): {4D36E96A-E325-11CE-BFC1-08002BE10318} Service(REG_SZ): atapi } secondary_ide_channel { ClassGUID(REG_SZ): {4D36E96A-E325-11CE-BFC1-08002BE10318} Service(REG_SZ): atapi } pci#ven_8086&dev_7010 { ClassGUID(REG_SZ): {4D36E96A-E325-11CE-BFC1-08002BE10318} Service(REG_SZ): intelide } pci#ven_8086&dev_7111 { ClassGUID(REG_SZ): {4D36E96A-E325-11CE-BFC1-08002BE10318} Service(REG_SZ): intelide } [2]: atapi { ErrorControl(REG_DWORD): 00000001 Group(REG_SZ): SCSI miniport Start(REG_DWORD): 00000000 Tag(REG_DWORD): 00000019 Type(REG_DWORD): 00000001 DisplayName(REG_SZ): Standard IDE/ESDI Hard Disk Controller ImagePath(REG_SZ): system32\drivers\atapi.sys } intelide { ErrorControl(REG_DWORD): 00000001 Group(REG_SZ): System Bus Extender Start(REG_DWORD): 00000000 Tag(REG_DWORD): 00000004 Type(REG_DWORD): 00000001 ImagePath(REG_SZ): system32\drivers\intelide.sys } - -- Pierre Schweitzer <pierre at reactos.org> System & Network Administrator Senior Kernel Developer ReactOS Deutschland e.V. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJVoXrMAAoJEHVFVWw9WFsLnqoQAJlqZtukxBpQvsLF5H5Us0SN MmzH2szJbwz3G+i5jHl2lq+Gg0pP1dD3WBTxuzNZy91XT99hIUlyxW59KVvCk9XK KQmghUUGW3zHqxH/mQoS9NV9t1jZhtHmFOy7RC5dbIoF3WaMPIWxEhTP9SFuSRUs Ec/hcrfYKZ7yr1GSermvV7DdoaHbMc+ris+zCRL6xKydfWODzMhS+VuDiWTqA9Jn s6FFpJnTRWR+nmTOEcBThTy5PhbjIVd/RS762vHKlx9hizkMVBGfoT+KmZQ8oI2+ 5xnYwIkloBR1WFC2/OIlymbWmusTWuXLrYcYiEB0pOweW13Mt6EH13PXG/cZpyGb ByS+ymtkDCHRZWMMnzbsnM2lkIMf7VvIisNDy1Ap0jW8siMLPcvBEcGWtlq607Rm E1YTBA/2nRbD9SxQGp+K42WgnigKMGqAG+mbaG4HEE96unPN3ia0opc/JzCPLhE7 UvMd8LNtb8I6lKYFe9NvaSdVKDi38rnfpH3xO03dIKqL0ZA0iuO90G9buAN7hnBC g6XsWQ0EEqoTLZeoNBFV7tk7jHirEGkEkZiZRsB8/LcB9sQZ4b+6gWiguxkeTkcm EtUDpWFmLYDDFz+IuxV/T+Brgu2SFAYs6vu6knrhO+mjdgHyBmfoua+3G3d6736X ySk7BjS1lfpB9OVqX2hM =0+5z -----END PGP SIGNATURE-----
Hi Pierre, On 11/07/2015 20:01, Ruzsinszky Attila wrote:> > The error line is: *** STOP: 0x0000007B (0xF789AA94, 0xC0000034, > > 0x00000000, 0x00000000) > > Perfect, this is what was expected. This should be easy to fix. >Good news! ;-)> Great, then, it opens possibilities. Let's try the following: > - - Install chntpw >Is that a Linux program? I use Ubuntu 14.04 64 bit.> - - Mount your disk on Linux >Clear.> - - Move to Windows/System32/config (beware the case!) >OK.> - - Now, start registry editor: chntpw -e sam system security software >"system security software" is parameters?> The following commands are to type in chntpw prompt: > - - hive 1 (to move to system) > - - cd ControlSet001 > - - cd Control > - - cd CriticalDeviceDatabase > - - Check you have the following keys: primary_ide_channel, > secondary_ide_channel, pci#ven_8086&dev_7010, pci#ven_8086&dev_7111 > keys. Some will be missing (otherwise, you'd boot ;-)). >I think I'll find SATA something, because the original image was taken from a SATA system.> - - Add the missing ones. For example: 'nk pci#ven_8086&dev_7111' >What does it mean "'nk"?> followed by: 'cd pci#ven_8086&dev_7111' followed by 'nv 1 Service' (1 >... and "'nv"?> for REG_SZ) followed by 'ed Service' and type intelide. Proceed like > that will all the missing keys & values[1], 'cd ..' when you're done > with all the values of a key, to proceed for the others > - - cd .. (you're now in Control) > - - cd .. (you're now in ControlSet001) > - - cd Services > - - Check you have the following keys: atapi and intelide > - - Add the missing ones[2]. REG_DWORD type is 4 when doing nv. (like nv > 4 ErrorControl) > - - You're done, so: q to quit chntpw (of course, reply 'y' to write hives) >Maybe I'll have question with registry. Tomorrow morning I'll try your steps. Can I a backup file from the registy before I start the procedure? And how?> Back to your linux term: > - - cd ../drivers/ > - - Check you have atapi.sys and intelide.sys. In case you don't, > extract them from the cab file you can find in Windows\Driver Cache\i386 > - - Umount > - - Try to boot again, and report. >Now I copied the virtio drivers to the ./Drivers directory. I understand the 1st goal is booting from IDE. What about SATA? Thanks for your howto! I think I'll ask you about registry. Question not just for you: Why did I get error message "permission denied" for vir-win-reg command? TIA, Ruzsi
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 07/13/2015 09:58 AM, Ruzsinszky Attila wrote:>> Here is the first problem. I can't mount sdi1! sdi1 not >> existent. >>> :-( >> >> What if you partprobe /dev/sdi? >> > Nothing. Empty output.When partprobe properly works (ie encounters no error), it doesn't print anything to console, it just adds the appropriate entries in /dev. (I guess some answers got lost on libvirt-users, sorry about that). - -- Pierre Schweitzer <pierre@reactos.org> System & Network Administrator Senior Kernel Developer ReactOS Deutschland e.V. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJVo4GDAAoJEHVFVWw9WFsLEpAP/jXOTqFf+Uog9/J5iuBh9ktU X4tEPEBa6j2V8Pkyv5YHKFe1T4JWvZw0AcbAuEQMS0glt3PUY7lsKFmqcYzJEukB w95vqMbvtguRneMh1G9tbEdOk47/T0zEnDXBz6/wyHGxkz3xGNqkoD6gxL0w2gui 5WAAdv8CPKptUZKKWGxABdZBxMobUNwtowTL0/Ir5BEiMl9wCHbgq6NOrU4Aungm kjLfR6BcecUkYh9lFeiyakYuENohNkZiP1f+zA8AlsZQDwAZP5Qe/J1vvfdawLiW pmYOT8Cmb6lp+O9iZhIQCAcE8EgZ9I6O0+J1vbVESSb+s4V1p1/Psu5zNqYMHMZJ 3He9X1Jj8vD0qliPW/YpRVMyRde77H7NNHSuX9QU/3Z2RFMLLT5Hx0ywElDLYJI/ aYiQgD1+bEp8T6frpmaowj1jXt7OraLnblaa92md4vwMm0Bl/Oui7y+kr5XO1gjD yri+YxAtptdge6nm2evLorQFrRi5DaVbjx0WPPHY2UJActo9lCHMciCyzAnUpsz3 c99Vlvk8jc2gTywst/rRgs7Ww9S+rxIRJZ6vck/lIjMjviIViH3aN0sQRB0cynLp DPhkB/Yedmj8PpNQstl8srg1D34Itir80Ve/uk7/vdlZp1D1670r7nXN6p46IGh5 Fn3/SNUE5Hfa0DBSqo9o =ovns -----END PGP SIGNATURE-----
Hi, Yes, there are the partitions: sdi1; sdi2 and sdi5. I have never used partprobe. ;-) TIA, Ruzsi
Hi Pierre, I'm here now: root@amd1:/mnt1/WINDOWS/system32/config# chntpw -e SAM system security software chntpw version 0.99.6 110511 , (c) Petter N Hagen Hive <SAM> name (from header): <on1\WINDOWS\system32\config\sam> ROOT KEY at offset: 0x001020 * Subkey indexing type is: 666c <lf> File size 262144 [40000] bytes, containing 8 pages (+ 1 headerpage) Used for data: 339/26696 blocks/bytes, unused: 12/5816 blocks/bytes. Hive <system> name (from header): <\WINDOWS\system32\config\system> ROOT KEY at offset: 0x001020 * Subkey indexing type is: 686c <lh> File size 3145728 [300000] bytes, containing 673 pages (+ 1 headerpage) Used for data: 50122/2904016 blocks/bytes, unused: 1232/27664 blocks/bytes. openHive(security) failed: No such file or directory, trying read-only openHive(security) in fallback RO-mode failed: No such file or directory Unable to open/read a hive, exiting.. root@amd1:/mnt1/WINDOWS/system32/config# Is that a problem or I can forget 'software' parameter? TIA, Ruzsi
On 07/13/2015 03:25 PM, Ruzsinszky Attila wrote:> - - cd ControlSet001 >> - - cd Control >> - - cd CriticalDeviceDatabase >> - - Check you have the following keys: primary_ide_channel, >> secondary_ide_channel, pci#ven_8086&dev_7010, pci#ven_8086&dev_7111 >> keys. Some will be missing (otherwise, you'd boot ;-)). >> > Here is my keys: > ... > <pci#cc_0600> > <pci#cc_0604> > <pci#ven_8086&dev_244e> > <pci#ven_8086&dev_27b8> > <pci#ven_8086&dev_27c0> > <pci#ven_8086&dev_27d0> > <pci#ven_8086&dev_27da> > <pci#ven_8086&dev_27df> > <pci#ven_8086&dev_27e0> > <pci#ven_8086&dev_27e2> > <pci#ven_9005&dev_0080&subsys_e2a09005> > <primary_ide_channel> > ... > > Can I remove them and add the new ones what you wrote me?Let the one already in place, and just add the missing ones. Existing ones won't cause troubles.> Do I type in the registy entries under [1] and [2] exactly using copy paste?Yup.> I'll check those vendor IDs above. > > How can I check the ones what Qemu using? (IDE/SATA/SCSI/Virtio)One easy way to find out is to use lspci -nn in a Linux host running Qemu with your target configuration. For instance, for the IDE bus, you'll get something like: 00:01.1 IDE interface [0101]: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] [8086:7010] -- Pierre Schweitzer <pierre@reactos.org> System & Network Administrator Senior Kernel Developer ReactOS Deutschland e.V.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 25/07/2015 13:55, Ruzsinszky Attila wrote:> Hi Pierre, > > I got enough inspiration typing in the needed reg. keys. > > Here is a difference: What you wrote me: > > intelide >> { ErrorControl(REG_DWORD): 00000001 Group(REG_SZ): System Bus >> Extender Start(REG_DWORD): 00000000 Tag(REG_DWORD): 00000004 >> Type(REG_DWORD): 00000001 ImagePath(REG_SZ): >> system32\drivers\intelide.sys } >> > > My reg. keys: > > \ControlSet001\Services\IntelIde> ls Node has 0 subkeys and 5 > values size type value name [value if > type DWORD] 4 REG_DWORD <ErrorControl> 1 > [0x1] 40 REG_SZ <Group> 4 REG_DWORD <Start> > 4 [0x4] 4 REG_DWORD <Tag> 4 [0x4] 4 > REG_DWORD <Type> 1 [0x1] > > \ControlSet001\Services\IntelIde> cat Group Value <Group> of type > REG_SZ, data length 40 [0x28] System Bus Extender > > Do I have to change? Start and ImagePath are different.Let ImagePath, it should match your system more closely (and differences might be just in case, so no real matter). But you absolutely have to change Start. If Start isn't at 0x0, then, the driver will not be loaded at boot, and you won't be able to boot your Win2k3. - -- Pierre Schweitzer <pierre at reactos.org> System & Network Administrator Senior Kernel Developer ReactOS Deutschland e.V. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJVs6/oAAoJEHVFVWw9WFsL8vcQAMd0C5zPHdwzoANR5peBl9mJ Z/9jY9/mF7E29yAmwKm0d3vXKgtja7v5vWar5rbyvSDpNKnUjQlwVdJEiGWwpcko 21xP7dC/IGGeEtn38wtfKOVZ0OQOAE1zs6YqbTDYSm1WgtTKNHvWjYQiPCwPmIYi cWqmXxF0SF2ADEiRjYlqZT2cd5Ersu+hy+bRlYGUxi4t2KhQf5vnz3kqZeY2BbDZ pG6xKRTvMDRqKiFdd3arUQ8ewJGjKvmKnGWz1ZgCvo75uzGoiuGmKDkIF6FJb3/+ +8nnFdYjd5b2NhryhIawxeZphAyMfIgt6Le1mFGgg2EBOD6xhFWv3WOLGSV775uu 29Q0+tPTE1+o8Ed1mtgaS1mRB/huPCMOMJtJS4sZ70wRdCz6i1pcYhQgXr44O1lz JzZxhnl79Zz0v/rlRIX2EF7t41rvIf//wgoA6jIhI7B15eGPlfGUaU2tMGGf8yGu yTcmuPKzfR1g8GJzYpNT8wFawEFOe3x2dRjA2kUdvUR1FziNdrUNxwpVOOBuOlX5 efVLf2ms+OOyIOnbSyzMOXL55K7a4HnHacCEjEvzvt60m4ZM7hcRGEE5L8Hi9LGP z2eDwRtefK6bL4Pg3hjkpBtsG42Pr6y5904MRGtLqwvmtWlTF+txafwahXQALpSi 5QEdWTWMQdI/LBZ/1LWz =tFUM -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Regarding product activation, there's nothing I can do. You've to call Microsoft to re-activate your W2k3 licence. This is due to hardware change on virtualization. Regards, On 25/07/2015 20:54, Ruzsinszky Attila wrote:> Hi Pierre, > > I think the boot is working! ;-) I changed my image to IDE disk and > W2k3 started booting but wants Product Activation ... What can I do > with this? I can't login. I think it is a loop when I click on OK > button in the warning window. > > TIA, Ruzsi >- -- Pierre Schweitzer <pierre at reactos.org> System & Network Administrator Senior Kernel Developer ReactOS Deutschland e.V. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJVtLm1AAoJEHVFVWw9WFsLyUsQAKv0EnHnYZ+PkWMuRPvCS4xa WnvnEkwIBxqrSXIG/b8mZ676mb+3ba9nZO22HZTKqqAndCrxQ46vsC87YSw9akcX +Dt1EC+BWMwclG4x/LSFM44uN6ZuqRqXNWIHL1B/fZ4DUO41RQDzX0yokc16+lxE OwzQQ5Rf8gYqHRBP/CdbrrPbgVnoa08ejRt0uwWhrMJtWwcFYz4YmPHBDSJV+GM7 lp6uU835mWDRR2DzIQ7gpDAAu3f1O2TPy15wFlidVn6XqjIcxIF9QqDj+ktQmyk+ im+PeVeqTGL75H2hyQMcx8z/kJm3ZktuqlTWbY4JvpNqBSodTYjVM9QnDsGf9JR7 Wvb6iEvxkLzGODXQ+YS2NOF4NJfTV0Wg1aodx5y+seMVlmAmFapq9QgNU39JTjg/ reMcVqjj3Es3DrQWWTZw0Mcvg2E/zxM3I58zg4Flylfxb/Krd3W4GRchwSx+/3u5 pA2Xb+Qq6Db/rWljVKHjN+LYW9llhr+/yu/W9+FYv2qJl0zZnHui+uDgljx1Byax urjYE2XCfSzDXvayVo7xTbSzpBi7MX0NlJZoK7kY7i4f7IV4ZSQZ+7owa05pH05v KQwjZzuSClFItIKARQ3JqXhi1ybmCH3jsoRbls6grX/tfkpzBrn1KspCFGMq7Fl/ LmU5uWVuO0o5YmQppckz =VNFx -----END PGP SIGNATURE-----