[ITEM]
07.04.2019

Proshivka Bios So Slic 21

79

Tips for better search results • Ensure correct spelling and spacing - Examples: 'paper jam' • Use product model name: - Examples: laserjet pro p1102, DeskJet 2130 • For HP products a product number. - Examples: LG534UA • For Samsung Print products, enter the M/C or Model Code found on the product label. - Examples: “SL-M2020W/XAA” • Include keywords along with product name. Examples: 'LaserJet Pro P1102 paper jam', 'EliteBook 840 G3 bios update' Need help finding your product name or product number?

SSV2: The slic is written over FF bytes in the bios file, and the slic is not part of a module. This only works for AMI BIOS, not Award. With SSV2 the system module is usually kept the same size, so all the modules in the bios remain in their original position. Most MSI AMI bioses require this method.

I can't tell you why but now I'm able to boot Windows 7 via both BootCamp on my Mac and in VBox without having to reauthenticate. What did NOT work: Pedro's method in the Howtos and Tutorials section () '[Network] Enable one adapter and set its MAC address to that of your real network card.' Well this won't work if you run VBox in bridged network mode, which I need. So I made sure they are NOT the same. 'sudo dd if=/dev/sda of=myMBR.mbr bs=512 count=1' I could not get this to work. Igri dlya portativnogo dvd release. Instead I used the tips from this site: What threw me was that when I switched from BootCamp to VBox I got the 'Must Authenticate' message so I assumed I had failed, and I had to reenter the product key.

Then I got the 'Must Authenticate By Phone' message so I thought I was really lost. But once I reauthenticated by phone it stayed authenticated between boots. I have no idea how Windows authentication works, so I can't explain it, but now I'm happy.

Posts: 4 Joined: 23. Aug 2013, 04:32.

Working Windows 7, SLIC 2.1 self activation Here's a way to get SLIC 2.1 activation to work for a Windows 7 guest in a Linux host. In my case, I'm using Ubuntu 12.04 and a current version of VirtBox [4.3.10, currently - I *think* it will work with any 4.2+ version - but not certain- if in doubt use 4.3+.] Create your Win7 VM using the OEM media. I'm using a DELL OEM install disk and my host box has an Dell OEM COA. [The method I describe works with a DELL bin file, because I'm using Dell media - thus the SLIC table matches the Certificate on the install media. If you're able to find different SLIC tables to match different install media, this should work too.] I've had a difficult time grabbing the SLIC table - in one box I tried this with, there was no SLIC table. [Perhaps on others there is. But there wasn't in this case, and I didn't want to burn 20 hours trying to figure out how to do so.] So, it's easiest for me to find a SLIC table I can grab elsewhere, instead of trying to generate my own.

So, I did some google searches with the terms 'virtualbox slic 2.1' [Since I'm not sure what I can or can not post, I'll let you find your way a bit.] There's a post on 'my digital life' that talks about a W7 guest on a W7 host - but clearly this isn't what I'm trying to do. [And I think wouldn't be technically 'legal' using a single COA/Windows License. But using a Linux host with a (single) W7 guest with a valid COA should be.] Anyway, in that thread, there's a linked zip file with the SLIC table included.

It's called Table_Dell_SLIC.BIN or something similar. You can dump all the other files - you won't need them. Use the BIN file - and move it to your Linux host box. [I generally put it in the same directory as the W7 VM files.] Once you have it there, you'll need to do the following. VBoxManage setextradata 'SomeVirtualBoxVM-Name' 'VBoxInternal/Devices/acpi/0/Config/CustomTable' '/some/path/which/has/your/bin/file/DELL_SLIC.BIN' Where A) you'll replace 'SomeVirtualBoxVM-Name' with the name of the W7 VM you created above. And B) [/some/path/which/has/your/bin/file/DELL_SLIC.BIN] will be replaced with the path and file name of the 'bin' file you'll be using.

[/ITEM]
[/MAIN]
07.04.2019

Proshivka Bios So Slic 21

86

Tips for better search results • Ensure correct spelling and spacing - Examples: 'paper jam' • Use product model name: - Examples: laserjet pro p1102, DeskJet 2130 • For HP products a product number. - Examples: LG534UA • For Samsung Print products, enter the M/C or Model Code found on the product label. - Examples: “SL-M2020W/XAA” • Include keywords along with product name. Examples: 'LaserJet Pro P1102 paper jam', 'EliteBook 840 G3 bios update' Need help finding your product name or product number?

SSV2: The slic is written over FF bytes in the bios file, and the slic is not part of a module. This only works for AMI BIOS, not Award. With SSV2 the system module is usually kept the same size, so all the modules in the bios remain in their original position. Most MSI AMI bioses require this method.

I can't tell you why but now I'm able to boot Windows 7 via both BootCamp on my Mac and in VBox without having to reauthenticate. What did NOT work: Pedro's method in the Howtos and Tutorials section () '[Network] Enable one adapter and set its MAC address to that of your real network card.' Well this won't work if you run VBox in bridged network mode, which I need. So I made sure they are NOT the same. 'sudo dd if=/dev/sda of=myMBR.mbr bs=512 count=1' I could not get this to work. Igri dlya portativnogo dvd release. Instead I used the tips from this site: What threw me was that when I switched from BootCamp to VBox I got the 'Must Authenticate' message so I assumed I had failed, and I had to reenter the product key.

Then I got the 'Must Authenticate By Phone' message so I thought I was really lost. But once I reauthenticated by phone it stayed authenticated between boots. I have no idea how Windows authentication works, so I can't explain it, but now I'm happy.

Posts: 4 Joined: 23. Aug 2013, 04:32.

Working Windows 7, SLIC 2.1 self activation Here's a way to get SLIC 2.1 activation to work for a Windows 7 guest in a Linux host. In my case, I'm using Ubuntu 12.04 and a current version of VirtBox [4.3.10, currently - I *think* it will work with any 4.2+ version - but not certain- if in doubt use 4.3+.] Create your Win7 VM using the OEM media. I'm using a DELL OEM install disk and my host box has an Dell OEM COA. [The method I describe works with a DELL bin file, because I'm using Dell media - thus the SLIC table matches the Certificate on the install media. If you're able to find different SLIC tables to match different install media, this should work too.] I've had a difficult time grabbing the SLIC table - in one box I tried this with, there was no SLIC table. [Perhaps on others there is. But there wasn't in this case, and I didn't want to burn 20 hours trying to figure out how to do so.] So, it's easiest for me to find a SLIC table I can grab elsewhere, instead of trying to generate my own.

So, I did some google searches with the terms 'virtualbox slic 2.1' [Since I'm not sure what I can or can not post, I'll let you find your way a bit.] There's a post on 'my digital life' that talks about a W7 guest on a W7 host - but clearly this isn't what I'm trying to do. [And I think wouldn't be technically 'legal' using a single COA/Windows License. But using a Linux host with a (single) W7 guest with a valid COA should be.] Anyway, in that thread, there's a linked zip file with the SLIC table included.

It's called Table_Dell_SLIC.BIN or something similar. You can dump all the other files - you won't need them. Use the BIN file - and move it to your Linux host box. [I generally put it in the same directory as the W7 VM files.] Once you have it there, you'll need to do the following. VBoxManage setextradata 'SomeVirtualBoxVM-Name' 'VBoxInternal/Devices/acpi/0/Config/CustomTable' '/some/path/which/has/your/bin/file/DELL_SLIC.BIN' Where A) you'll replace 'SomeVirtualBoxVM-Name' with the name of the W7 VM you created above. And B) [/some/path/which/has/your/bin/file/DELL_SLIC.BIN] will be replaced with the path and file name of the 'bin' file you'll be using.