Re: - WinXp as VHD in VBox on Win7 ==> BSOD
Posted: 6. Jan 2016, 02:21
Since English is a foreign language for me, I know that I am exposed to multiple errors of expression and understanding. Nevertheless I do my best to improve my command of English. For that reason I would like to ask you what made me deserving the expression "even if you were agreeable" that, as I was taught, suggests that I am not?
Of course, if my understanding is wrong, I beg your pardon for the question. Otherwise, was it due to my usage of the word "tinkering"?
Note please, if I do something that I don't understand well, for me it's "my tinkering". For that reason I was initially so reserved with respect to applying MergeIDE that seemed to me overwriting Registry keys and not only adding new ones. It's important for me to leave my physical XP system only as a source of disk images, excluding any patches or reconfigurations. But I totally agree with you that I can tinker with SILVER.VDI - notwithstanding that I have very weak competences in this respect.
Back to technical subjects.
1. Downloading the Evaluation copy of VBox, I was glad to have my personal physical XP system as probably challenging test case; up to now the case continue to challenge VBox. What interests me on longer term are appliances under VBox Enterprise licenses.
2. I don't see any reason that you waste your time to do anything beyond your role of this Oracle-sponsored forum Moderator. Within this role you
- approved my usage of Disk2Vhd,
- advised to apply MergeIDE,
- advised to use CloneVDI to convert VHD to VDI.
As I understood, from your perspective SILVER.VDI was ready to boot.
But it didn't boot.
Since VBox Manual - seems excellent, BTW - states that VBox supports XP guests on Win7 hosts, where is the reason of the failure?
In WinXP?
In Disk2Vhd?
In MergeIDE?
In CloneVDI?
In VBox?
Or at last, in Win7?
I don't see you as the person in charge of such investigation.
But I see the VirtualBox Team as potentially the most concerned by the case.
They and Microsoft should know tools to produce logs showing what failed during the boot.
3. As for your steps-to-follow indication concerning VM
saying "If this worked ...".
The other indication
Kind regards,
JK
Of course, if my understanding is wrong, I beg your pardon for the question. Otherwise, was it due to my usage of the word "tinkering"?
Note please, if I do something that I don't understand well, for me it's "my tinkering". For that reason I was initially so reserved with respect to applying MergeIDE that seemed to me overwriting Registry keys and not only adding new ones. It's important for me to leave my physical XP system only as a source of disk images, excluding any patches or reconfigurations. But I totally agree with you that I can tinker with SILVER.VDI - notwithstanding that I have very weak competences in this respect.
Back to technical subjects.
1. Downloading the Evaluation copy of VBox, I was glad to have my personal physical XP system as probably challenging test case; up to now the case continue to challenge VBox. What interests me on longer term are appliances under VBox Enterprise licenses.
2. I don't see any reason that you waste your time to do anything beyond your role of this Oracle-sponsored forum Moderator. Within this role you
- approved my usage of Disk2Vhd,
- advised to apply MergeIDE,
- advised to use CloneVDI to convert VHD to VDI.
As I understood, from your perspective SILVER.VDI was ready to boot.
But it didn't boot.
Since VBox Manual - seems excellent, BTW - states that VBox supports XP guests on Win7 hosts, where is the reason of the failure?
In WinXP?
In Disk2Vhd?
In MergeIDE?
In CloneVDI?
In VBox?
Or at last, in Win7?
I don't see you as the person in charge of such investigation.
But I see the VirtualBox Team as potentially the most concerned by the case.
They and Microsoft should know tools to produce logs showing what failed during the boot.
3. As for your steps-to-follow indication concerning VM
thank you for it but I don't imagine practically how to follow it. Probably for that reason you doesn't seem sure of the result... dump the extended partition to a raw file then convert the raw file to a VDI then you'd almost have a bootable disk: you'd just need to attach it to a VM and run fixmbr. CloneVDI has a feature that lets you dump a portion of a VDI as a raw file, and can make it a VDI again.
If this worked you would end up with a disk containing two primary partitions: just about every Linux has that, so I know for a fact that VirtualBox supports it.
The other indication
doesn't concern VM and the answer to the question it contains is "No". Those applications - because there are two of them - are out-dated client-server apps interconnected, via Registry, with obsolete database engines and data providers. The apps have to be upgraded (rewritten) before migrating to a new environment. I'm too busy to do that now.... would the app in question work if the executable folder was simply copied to a new XP installation? Many will, though you may have to manually set up file associations etc.
Kind regards,
JK