Its a license embebbed in the bios.The question is where is is located, what kind of signature it use.Because al Z68 Boards with "normal Virtu" are Virtu MVP ready its its only a matter of the license.It could be extracted from a Z77 Board
It is in the dsdt. LucidLogix.h Code: Name(LUCD, Buffer(0x7d) { 0x4c, 0x75, 0x63, 0x69, 0x64, 0x4c, 0x6f, 0x67, 0x69, 0x78, 0x00, 0x68, 0x00, 0x01, 0x00, 0x01, 0x00, 0x00, 0x00, 0xe0, 0xf9, 0x65, 0x64, 0x63, 0x66, 0x38, 0x31, 0x37, 0x64, 0x61, 0x62, 0x62, 0x32, 0x39, 0x65, 0x39, 0x33, 0x38, 0x63, 0x65, 0x30, 0x39, 0x35, 0x61, 0x34, 0x63, 0x32, 0x62, 0x64, 0x64, 0x64, 0x37, 0x66, 0x30, 0x64, 0x30, 0x37, 0x30, 0x37, 0x66, 0x33, 0x30, 0x65, 0x66, 0x38, 0x30, 0x31, 0x33, 0x65, 0x34, 0x62, 0x64, 0x63, 0x33, 0x32, 0x66, 0x34, 0x31, 0x62, 0x37, 0x37, 0x61, 0x66, 0x37, 0x32, 0x30, 0x30, 0x30, 0x30, 0x32, 0x36, 0x39, 0x46, 0x63, 0x65, 0x64, 0x31, 0x36, 0x35, 0x31, 0x36, 0x33, 0x65, 0x35, 0x31, 0x65, 0x30, 0x36, 0x65, 0x30, 0x31, 0x64, 0x63, 0x34, 0x34, 0x63, 0x33, 0x35, 0x66, 0x65, 0x61, 0x33, 0x65, 0x61, 0x66 }
Tried to find this "dsdt. LucidLogix.h" entry but don't know even where I should to search for this. MMTool which I use to add newest Intel OROM or Hexedit didn't showed anything similar. Here's my UEFI for Asrock Z68E4G3 2.03 with added Intel OROM 11.1.0.1413 mediafire . com / ?iydz2jde38851rm (spaces added to link because of my posts restriction) Could anyone give me some link to guide and tools to add SLIC/SLP from Asus and lucid mvp license. Don't know which should be done first (this could be important) I suspect that should be done this way . 1.OROM (already done) 2.LUCID 3.SLIC/SLP (this one would be last becuase of some checksum check) correct my if I'm wrong. If someone could give me some tips how to do it - last 2 steps then I will make it myself and will not bothering others when new UEFI will be released. Thanx
I've changed those values in the DSDT, but in the end it didn't work for me. Maybe someone else would try it? First thing to do is open RW everything and save your DSDT table as a bin file. Open it up in a Hex Editor (I used hex workshop) and check the starting bits (DSDT) and the end bits (mine is SB_PCI0LPCBSIOWh). 1) Open Pheonix Tool 1.97 and select your BIOS file 2) Click button "Structure" 3) Tick both "Decompress..." and "Compress..." 4) Search for: Driver{9F3A0016-AE55-4288-829D-D22FD344C347}, click it and click "Extract" button 5) Open 9F3A0016-AE55-4288-829D-D22FD344C347.MOD file in a hex editor (I used Hex Workshop) 6) Press Ctrl+F, find "Text String": Lucid 7) Select from "Lucid..." to "...ea3eaf" and copy/paste values from previous post: 4c756369644c6f676978006800010001000000e0f96564636638313764616262323965393338636530393561346332626464643766306430373037663330656638303133653462646333326634316237376166373230303030323639466365643136353136336535316530366530316463343463333566656133656166 8) Recheck to make sure what you replaced is the exact same size of the copy/paste 9) Press Ctrl+F, find "Text String": DSDT 10) Go 9 offsets to the right (or count till 9, with the first D from DSDT being position 0), e.g. in my case: 44 53 44 54 08 A3 00 00 02 54, and replace that value with FF; in my case, 54 => FF (this is the checksum offset) 11) Press Ctrl+F, find "Text String": SB_PCI0LPCBSIOWh (my last string from DSDT.bin saved earlier, check yours) 12) Select everything up, from the last "h" of SB_PCI0LPCBSIOWh, to the first "D" of DSDT (i.e., select the whole DSDT table) 13) Menu "Tools" -> Generate Checksum (8-bits) on "Selection" 14) Bottom-right corner, select "1s Complement" and see what's in the Checksum/Digest column. 15) Replace the FF you wrote earlier with that value. 16) Run checksum again, and select "None" instead of "1s Complement". If you did everything right, it should be zero now. 17) Save file and exit hex editor 18) Go back to the Pheonix Tool and click button "Replace" and choose the 9F3A0016-AE55-4288-829D-D22FD344C347.MOD file you just modded. 19) All done now. Exit the Structure view, choose "Yes" to save. You now have a modded bios with the changed DSDT!
Some user suggested that license could be encrypted and my first guest was mainboard model/chipset is also somehow identified (taken from bios) during installation process and thats why it wont work. Maybe we need to edit UEFI this way that Z68E4G3 would identify itself as Z77E6 which is very similar : same PCI/E ports and has lucid MVP license/support.
There is also a copy of the DSDT table in the windows registry. You can use the Microsoft ASL compiler to change it by doing in a command prompt: "asl /loadtable DSDT.bin", where the DSDT.bin is the file saved with RW and edited. Dunno if Lucid MVP reads the hardware table, the copy in the registry, or both. Yeah, the license looks encrypted, but there seem to be some common parts, especially between same vendor boards. Anyway, for me at least, Lucid MVP has some 3D bugs in games (missing stuff), that Virtu doesn't have (working 100%) in a Z68.
I will try what you posted when I got a free time, this bugs are present when both HyperFormance and Virtual Vsync are on ?
Kind of a development on this. The folks at Guru3d have hacked the drivers: forums.guru3d.com/showthread.php?t=359795 1. Install Lucid Virtu MVP (I tried 2.1.112.214494) and restart your system, if it was previously installed then it wont start even after launching VIRTU MVP Control Panel, but it's ok. 2. Stop the "MVPControlPanel.exe" and the "Ekag20nt.exe" processes. 3. Copy "gpuEnumerator.dll" from old Lucid Virtu (NOT MVP) or from (1.2.111.19705): w w w.mediafire.com/?xi7j6wizw4zoxfw to your X:\Program Files\Lucidlogix Technologies\VIRTU MVP catalog. 4. Start VIRTU MVP Control Panel Give it a try with different combinations of Virtu and Virtu MVP drivers but I'm guessing this hack will probably be disabled in future updates. P.S. Sorry for the crappy links but since I haven't reached the right post count yet the board won't let me post proper URLs P.P.S. Many thanks to you know who
You guys just need to copy and paste the code into your DSDT with a Text Editor and recompile the DSDT! That isn't really hard to do.
hello i hope you understand me, because my english is not so good for german guy *gg* Ive edit the BIOS from my Asrock Fatal1ty Z68 Professional with the Key from z77 pro... and the guide her posted and my Lucid is still expired... but with a older mvp version 2.111 a txt is saved at C: , called lucid.txt. I think its a log file... and there was the text, "lucid key does not match with Bios/Vendor" ... so i think its not only the key you must change...
I know thread is a month old but my "trial" just ran out...any other fix found? I dont mind buying it but I cant even find that option
Hello people i know this thread is old but i have tested something and would like to share hopefull it help someone still trying after analysis found that the Lucid Logix Virtu MVP's codes related somehow to the motherboard brands like this when you open "9F3A0016-AE55-4288-829D-D22FD344C347.MOD" using Hex workshop and looking for MVP codes right side will see that the code contain 3 parts first part related to the mobo brand also kind of Lucidlogix product either Virtu MVP or Virtu second part is the serial itself third is somthing common in all for example Asus got this edcf817dabb29e938ce095a4c2bddd7f for Virtu MVP and this ea0bdd0c40f5236ffee10fc5724e8166 for Virtu Asrock got this 538e5415a8ad4e409b6c7675aa18e0e8 forVirtu MVP Gigabyte got this 5e756f0160da681e21ae2db8f92d1eda forVirtu MVP Warning unless you have dual BIOS and know well how to force switch between them Don't try this at home i have ASUS Maximus IV Z68 and couldn't post my code because it contain "@" and this not allowed since i'm newbie here Plz feedback if it worked with you mine didn't still trying
Any news!? Alex vuture, have you try other schemas/solutions? Did you find the right mod to run Virtu MVP on our mainboards? Thanks in advanced
not yet Fred hopefull for someone use my info up there to find solutions any way i will post any find i get here