Why bother with many SLP 1.0 strings? SLP 1.0 Hyper-V VM is only needed for Windows XP. For Server 2003/R2 is not needed, as it already contains SLP strings used by many oembios* sets (Dell, IBM, Fujitsu) Just settle on a couple of stings & be done with. Dell, HP, Acer, Asus Why would anybody need more? But your project looks very nice & useful indeed! sebus
First off, Thank You Inge001. This could be one of the handest tools available for Hyper-V users. As any of you can see from this thread, I've never managed to get this Hex editing to work. But, I'm alot handier with screw drivers than I am with code, maybe thats why I do tune/mod my own car. I don't know about the 1b module, but I've have trouble getting real AMD PC's to work with the "Genuine C&C OEMBIOS" set of files. My new Hyper-V Server is a HP Micro Server, so I'll test it out once I get it up and running. If I remember right there were around a dozen of these SVR 2003 R2 activation codes in Virtual Server, maybe theres still a few in Hyper-V 'cos I've never had any problems getting any SVR 2003 R2 to active out of the box in Hyper-V. Even less common versions like Evesham and Medion.
meant : SLP 1.0 "WinXP / 2003" and SLIC 2.0 or 2.1 or 2.2 depend by your needs "but in most cases 2.2 may work with older version"
In your lucky case where your processor reports Genuine Intel. AMD will not (obviously, and even most Intel gear will not) Code: 04 Processor Information ---------------------------------------------------------------------- Type : 04h (4) Length : 23h (35) Handle : 0005h Socket Designation : None Processor Type : Central Processor Processor Family : Intel(R) Xeon(TM) Processor Manufacturer : Intel Processor ID : 1F8BFBFF000006F6 Processor Version : Intel(R) Xeon(R) CPU 5140 @ 2.33GHz Voltage : 1.4V External Clock : 1333 MHz Max Speed : 3600 MHz Current Speed : 2333 MHz Status - CPU Socket Populated : CPU Socket Populated Status - CPU Status : CPU Enabled Processor Upgrade : None L1 Cache Handle : N/A L2 Cache Handle : N/A L3 Cache Handle : N/A Serial Number : None Asset Tag : None Part Number : None Where is it present then? But honestly, who cares? How many people would even have such media to install it in first place? If they want to install then just simply install any version that is supported out of the box already - simple & easy Honestly, never done that yet...
Please upload other places, especially what won't be blocked by overenthusiastic antivirus. suggestion: mega.co.nz
Strange. There is only a file under winsxs folder in amd64_microsoft-hyper-v-vstack-vmwp_31bf3856ad364e35_6.3.9600.16384_none_25feee5133bfaee5 and that is it.
you only have it in winsxs because you have to enable it in windows features, then you will have a vmwp.exe in the system32 that is identical to the server one. kapisch?
Yes i know what i am talking about. I also know hyper-v functionality will be enable after add features with copying files from winsxs to system32 folder. But strange thing is why it is not the exact file. I know that forexample the oldest original full file needs to be in winsxs folder, after that the newer versions are also stored with same name (as hardlinks) but only differences for to gain space. At least there needs to be original full file in somewhere. I want to use hyper-v functionality in windows 8.1 to activate windows xp and never ones. Maybe i need to ask the main question, where need to put that file inside install.wim for not to need to change vmwp.exe file after setup. (if it is same file with server one)
FYI vmwp.exe file to mod is into C:\Windows\system32 (NOT winsxs) W8.1 vmwp file and 2012R2 file are the SAME file (same size, version, and CRC) Mod can be applied in both OS flawlessly... Beware when replacing original file : because of security changes (due to takeown and cacls commands), replaced modded vmwp.exe file might not have correct rights... (HyperV will complain when starting any VM ) Please do as i do to avoid any problem : - 1st keep a copy from original vmwp.exe (say vmwp.exe_BAK) - 2nd stop service, then run takeown and cacls commands (see above) - 3rd DELETE vmwp.exe file (you have a copy ) - last, COPY (don't move) modded vmwp.exe_DELL22_blah-blah.exe to vmwp.exe This way you make sure modded file will get inherited rights from \windows\system32 and everything further will be OK...
Server 2008 R2 vmwp v6.1.7601.18231 I've been reading the thread for some hours in order to mod the new vmwp.exe myself. Unfortunately I'm one of those dummies that fail at it. Could someone mod the exe for me with Dell slic? Or point me to a step-by-step how to so I can do it myself from now on? I'v uploaded the previous and working modded version and the new unmodded one here. Thanks a lot! hxxp://rghost.net/48740743 (deleted) MD5: 0D823602242886328E38B3CF38AA2607