Bios Mod vs Daz Loader engineers perspective

The loaders advantage over a BIOS mod is that it works on older systems and newer systems, allows you to easily ignore problematic SLIC's and change the location of where the SLIC gets placed. It's result is the same as a BIOS mod (loads a SLIC into memory) but it's done without making any hardware changes.

As you've said, if you buy a new system then it will probably get some BIOS updates so if you go the BIOS mod route then each time theres an update released you'd have to re-modify your BIOS if you wanted to update. This isn't a problem with the loader. The only problem the loader has is with Windows 7 setup to use UEFI. It changes the disk to GPT and no classic 'BIOS' is emulated so theres nothing there for the loader to work with. With that said the loader will work on UEFI hardware as long as you setup Windows to use MBR instead.

Basically the BIOS mod is permanent and secure but the loader is more flexible and appeals to a wider audience. That's not to say the loader isn't secure, in fact it's avoided every single system and service pack update

 

Both activation methods have merit. A fundamental difference is that Daz's loader poses no risk of bricking your motherboard. To say both methods can not be detected i think is a little hasty. Whilst MS have not detected the loader yet does not mean they will not do so in the future no matter how unlikely it may seem right now. Also the BIOS mod could potentially be detected using hardware checks / bios dates etc. Its simply a matter of choice. For ease of use go with the loader, its simple to use and highly successful. The BIOS mod also successful but there are risks.

As for UEFI BIOS, to my knowledge it isnt possible right now to insert a slic table due to digital signature. So if you have UEFI then go with the loader.

 

It's documented in the latest version of the loaders read me file

 

@ YangerD
As far as I know you'd select to boot the USB without UEFI instead.

@ Whazzupsuperfly
Some might risk flashing a BIOS on new hardware but some might not dare to try. As you said it's their personal choice

We probably could patch stuff from the loader. In fact in the latest version we even have table spoofing

 

The loader can work on UEFI systems but only when the drive is setup to use MBR.

Code:

##########################################################################
#   4   -   UEFI motherboards
##########################################################################
The loader doesn't work when the systems using GPT via UEFI. The workaround is to pre-format your hard drive so that it uses MBR instead.

From your BIOS select to boot the Windows DVD without UEFI, go to the repair options, select command prompt and then enter this:

diskpart
list disk
select disk 0
clean
convert mbr
create partition primary
select partition 1
format fs=ntsf quick

Boot the Windows DVD the same way you did the first time and then continue with the installation of Windows. Once complete you can install the loader.

 

Lets say you add a SLIC and it has a different OEM ID or OEM Table ID, like this:

Code:

BIOS Information: 
  ACPI Table NameOEMID ValueOEMTableID Value
  APICDELL  M07    
  FACPDELL  M07    
  HPETDELL  M07    
  BOOTDELL  M07    
  MCFGDELL  M07    
  SLICDELL  WN09   
  SSDTPmRefCpuPm

With the option enabled to patch OEM table ID's it will make it look like this:

Code:

BIOS Information: 
  ACPI Table NameOEMID ValueOEMTableID Value
  APICDELL  WN09   
  FACPDELL  WN09   
  HPETDELL  WN09   
  BOOTDELL  WN09   
  MCFGDELL  WN09   
  SLICDELL  WN09   
  SSDTPmRefCpuPm

It's not enabled by default because some systems don't like other tables being adjusted. That's also why table sorting is disabled by default.