Jernej Simon?i? wrote:
>That's the exact reason - the strings have to be present in the
>correct memory region. You can use SLICToolkit (in SLP1.0 tab) to
>verify if the strings are present at the right address.
Alright then, do you know how to modify those values in qemu?
Brian
On Friday, December 23, 2011, 7:11:08, in...@expertcomputerrepair.com wrote:
> I think the key is those specific
> memory addresses I mentioned earlier.
That's the exact reason - the strings have to be present in the
correct memory region. You can use SLICToolkit (in SLP1.0 tab) to
verify if the
Why not just buy a non-OEM version ?
They are surely not tied to a specific piece of hardware and its
licence should allow to run on "arbitrary PC HW you happen to want to
install/run it on once activated"
On Fri, Dec 23, 2011 at 5:11 PM, wrote:
>
>
>>"My patch" does not produce any SLIC at a
>"My patch" does not produce any SLIC at all. The instructions mentions
>using SLIC from your machine - "my patch" is just a way to _embed_ a given
>data into VM, not a way to "produce" anything. You get in your VM what
>you have outside, either in a file or in your own BIOS, depending on where
>
On 22.12.2011 08:44, in...@expertcomputerrepair.com wrote:
[]
>> WinXP requires "SLIC version 1.0", which is reduced to just having a string
>> with the name of your OEM in the bios (one possible place is the SLIC table).
>> More recent version of SLIC (2.1 I think) is needed to activate windows7.
Michael,
Thanks for the response. Since you wrote the patch I'm using I'd say
you are the most qualified to answer questions about it. :)
>Note that for winXP, the only thing needed from the bios is to _mention_ -
>anywhere in its memory - name of your manufacturer. That is, you can
>add any ta
On 20.12.2011 22:23, in...@expertcomputerrepair.com wrote:
> Sorry, I don't normally use this email and didn't realize it was set to
> html.
>
> I've been trying for several days now to get my OEM copy of Windows XP
> to pre-activate properly in Qemu-kvm. I saw the instructions for
> patching the
Sorry, I don't normally use this email and didn't realize it was set to
html.
I've been trying for several days now to get my OEM copy of Windows XP
to pre-activate properly in Qemu-kvm. I saw the instructions for
patching the seabios here:
http://lists.gnu.org/archive/html/qemu-devel/2011-03/msg
On Tue, Dec 20, 2011 at 12:09:41AM -0700, in...@expertcomputerrepair.com wrote:
> I've been trying for several days now to get my OEM
> copy of Windows XP to pre-activate properly in Qemu-kvm. I saw the
> instructions for patching the seabios here: href="http://lists.gnu.org/archive/html/qemu-de
I've been trying for several days now to get my OEM copy of Windows XP to pre-activate properly in Qemu-kvm. I saw the instructions for patching the seabios here:http://lists.gnu.org/archive/html/qemu-devel/2011-03/msg03080.htmlThat seems to have worked as expected. When I boot, it shows the newl
Hi. SLIC table can be fed dynamically by utilize the existing fw_cfg interface.
Something like this. (This requires your qemu patch.)
This is just for showing the idea.
thanks,
diff --git a/src/acpi.c b/src/acpi.c
index 6428d9c..e0815bd 100644
--- a/src/acpi.c
+++ b/src/acpi.c
@@ -627,6 +627,7 @@
Here's a quick-n-dirty howto about running OEM version
of windows7 or vista in qemu/kvm, assuming you own a
computer with pre-installed OEM version of such operating
system so you have rights to run it there.
Windows 7 & Vista OEM activation are based on a special
OEM marker in BIOS in a form of o
12 matches
Mail list logo