As posted already support has been cancelled for ODIN a long time ago at MDL since the author moved the project away from MDL and made it to an paid activator (paid VIP access for D/L). On AMD64 operation systems ODIN patched ntoskrnl and winload to remove "Driver Signature Enforcement" & "PatchGuard". All other modifications (get a SLIC) are done in RAM ( AMD64 & x86 ) The tool installed a driver named oem-drv86.sys or oem-drv64.sys. AFAIK it did not run on I386 with PAE / Itanium64. To me it is unknown if it works with MBR only and why....one would need to know how the SLIC is introduced into ACPI namespace (EBDA for relocation of RSDP might not work/be available at GPT boot?) Is it an EBDA approach? I let this thread run for tech discussions. If one of the MDL member can help with info feel free to reply.
Actually grub bootloader used in Daz loader requires a MBR to be called, it has nothing to do with the SLIC introduction method itself. Bootchain: BIOS-->MBR---->grub loader with SLIC introduction code--->bootsector/bootmgr --->OS/OSes... w/o loader: BIOS-->MBR--->bootsector/bootmgr--->OS/OSes Btw: Why don't you try yourself if ODIN requires MBR or not?!
They suck either way, lol. I'd go for WindSLIC or even better an UEFI mod when using GPT installations which activate against a SLIC.
I agree Yen, it sucks. Any version of the activator. Btw, according to his author the latest version is uODIN-R2 never tested by me (right after 1.0.0.2) but is no longer supported by him/her. FAQs: Spoiler Requirements for Server 2008 R2: .NET Framework 3.5.1 Feature Generate Report feature - Privacy: The data included in the report does not contain private information in any way. Included in the generated package is: * HKLM\HARDWARE * HKLM\SYSTEM\CurrentControlSet * %systemroot%\Minidump\*.dmp * %systemroot%\System32\drivers\uodin.sys * MGADiag log * uODIN-R2 log(s) Does uODIN-R2 store files on my PC?: Yes, application logs and old reports are saved to %localappdata%\uODIN-R2. Can I upgrade from uODIN 1.0.0.2 to this release?: No, you need to uninstall the previous release first before applying this one. Do I really need to restart between un/install?: Yes, as otherwise your PC might stay in test-mode after a complete uninstall. In case you encounter a BSOD 1. Boot into recovery console and type: del <volume_label>:\Windows\system32\drivers\uodin.sys 2. Reboot 3. Launch uODIN-R2 and uninstall all remaining components In case you encounter any problems Sorry, no longer supported by the author.
I don't like the "In case you encounter a BSOD" part. secr9tos is assuming that tampering with system files and drivers is a messy thing.