115网盘使用aria2下载

Chrome登录脚本地址:https://github.com/kkHAIKE/fake115/raw/master/fake115.user.js

项目:https://github.com/kkHAIKE/fake115

配合使用

使用 fake115可以在chrome上登录115.详细见: https://github.com/kkHAIKE/fake115

插件下载地址

使用说明

安装插件之后,115 界面会多出导出下载和 RPC 下载的按钮。选中文件,点击按钮便可进行相应模式的下载: export

这个是 Aria2 的设置界面,按钮放在帐号设置的下面: 2015-01-28-231106_935x644_scrot

Windows 10系统免费“永久激活”(微软官方正版授权)

Windows 10被微软称之为“最好系统”,微软也在大力的推动用户升级安装Windows 10系统。

下面孤狼分享一种Windows 10系统永久激活方法就与微软推动用户升级安装的一种,微软官方正版授权,在线自动链接微软激活服务器免费永久激活,并且,重装Windows 10系统后联网自动永久激活。当然,要永久激活Windows 10系统也是有条件的,条件是要依赖当前操作系统,例如:Windows 7或Windows 8,XP系统没有试过,还不知道,当前系统也必须是永久激活状态。

永久激活Windows 10系统有两种:

1、直接在当前系统下使用“MediaCreationTool”升级到Windows 10系统,Windows 10系统安装完成后自动永久激活。(同时也把电脑硬件信息记录到微软激活服务器上,方便下次重新激活,更改主要硬件后永久激活将失效,因为电脑硬件信息与微软激活服务器上的电脑硬件信息不一致。)

2、使用Windows 10系统原版光盘镜像ISO文件里面的“gatherosstate.exe”软件收集电脑硬件信息,并生成一个“GenuineTicket.xml”。然后安装Windows 10系统完成后再将“GenuineTicket.xml”文件复制到“%ProgramData%\Microsoft\Windows\ClipSVC\GenuineTicket”目录下,Windows 10将自动永久激活。

永久激活方法一

Windows 7免费升级正版Windows 10 专业版操作系统详细过程注:这是在线升级教程。

Media Creation Tool工具下载(Windows 10在线升级/安装/下载/制作USB启动盘)注:使用Media Creation Tool下载windows 10原版系统,可以制作成U盘启动直接安装,也可以制作成ISO光盘镜像文件。

永久激活方法二

——打开Windows 10光盘镜像ISO文件,进入到“sources”文件夹里面,在英文输入法时按“ga”找到“gatherosstate.exe”文件,然后将“gatherosstate.exe”文件然后到桌面或新的文件夹里面。

——以管理员的身份运行“gatherosstate.exe”将会在当前目录下生成一个“GenuineTicket.xml”。

——然后再将GenuineTicket.xml复制到U盘中或其它分区中。

——然后就可以安装Windows 10系统了,注:孤狼只在Windows 7系统下运行“gatherosstate.exe”程序,其它系统没有试,还不知道是否能成功。

——Windows 10系统安装完成后,打开“%ProgramData%\Microsoft\Windows\ClipSVC\GenuineTicket”目录,然后再将“GenuineTicket.xml”复制到里面。 ——然后重新启动电脑,Windows 10系统将自动联网永久激活。

——打开“CMD”命令提示符,输入以下命令。

slmgr.vbs -dlv
slmgr.vbs -xpr

——提示已经永久激活。

——Windows 10系统“永久激活”成功后,微软激活服务器将记录电脑硬件信息,下次重装Windows 10系统后联网永久激活。

长江涨潮落潮时间表

日期(农历)退潮时间 涨潮时间
初一、十六 6:00 12 :12
初二、十七 6:48 13 :00
初三、十八 7:36 13 :48
初四、十九 8:24 14 :36
初五、二十 9:12 15 :24
初六、二十一 10:00 16 :12
初七、二十二 10:48 17 :00
初八、二十三 11:36 17 :48
初九、二十四 12:24 18 :36
初十、二十五 13:12 19 :24
十一、二十六 14:00 20 :12
十二、二十七 14:48 21 :00
十三、二十八 15:36 21 :48
十四、二十九 16:24 22 :36
十五、三十 17:12 23 : 24
每个农历月的初一、十五的早上六点和下午18:00潮位涨到最高,中午12:00和凌晨0:00降到最低。然后每天涨潮落潮时间往后拖延48分钟
告诉你一个口诀:初八二十三,一天两个干;初一和十五,一天两个满
干 就是落大潮,满 就是张满潮。

Windows 7 SP2(kb3125574)

Windows 7 SP2

 

1.先安装KB3020369

https://www.catalog.update.microsoft.com/search.aspx?q=KB3020369

2.安装KB3125574

https://www.catalog.update.microsoft.com/search.aspx?q=kb3125574

 

3.安装KB4474419(SHA-2 code signing support update)

https://www.catalog.update.microsoft.com/search.aspx?q=kb4474419

4.月度补丁汇总

 

https://support.microsoft.com/zh-cn/help/4009469/windows-7-sp1-windows-server-2008-r2-sp1-update-history

https://support.microsoft.com/zh-cn/help/894199/software-update-services-and-windows-server-update-services-2019

2018-02

https://www.catalog.update.microsoft.com/search.aspx?q=KB4074598

2018-03

https://www.catalog.update.microsoft.com/search.aspx?q=KB4088875

2018-06

https://www.catalog.update.microsoft.com/Search.aspx?q=KB4284826

2018-07

https://www.catalog.update.microsoft.com/Search.aspx?q=KB4338818

2018-08

月度汇总

https://www.catalog.update.microsoft.com/Search.aspx?q=KB4343900
仅安全更新

https://www.catalog.update.microsoft.com/Search.aspx?q=KB4343899

 

VirtualBox 添加Slic 2.1

ref:

https://www.virtualbox.org/manual/ch09.html

9.13. Configuring the custom ACPI table

VirtualBox can be configured to present an custom ACPI table to the guest. Use the following command to configure this:

VBoxManage setextradata "VM name"
      "VBoxInternal/Devices/acpi/0/Config/CustomTable" "/path/to/table.bin"

Configuring a custom ACPI table can prevent Windows Vista and Windows 7 from asking for a new product key. On Linux hosts, one of the host tables can be read from /sys/firmware/acpi/tables/.

在虚拟机配置文件 <ExtraData>节添加以下参数

<ExtraDataItem name="VBoxInternal/Devices/acpi/0/Config/CustomTable" value="/Path Of Slic Table/SLIC.BIN"/>

 

USB问题

ref:
http://www.virtualbox.org/manual/ch03.html#idm1637
https://www.virtualbox.org/manual/ch12.html#ts_usb-linux

3.11. USB support

3.11.1. USB settings

The “USB” section in a virtual machine’s Settings window allows you to configure VirtualBox’s sophisticated USB support.

VirtualBox can allow virtual machines to access the USB devices on your host directly. To achieve this, VirtualBox presents the guest operating system with a virtual USB controller. As soon as the guest system starts using a USB device, it will appear as unavailable on the host.

Note

  1. Be careful with USB devices that are currently in use on the host! For example, if you allow your guest to connect to your USB hard disk that is currently mounted on the host, when the guest is activated, it will be disconnected from the host without a proper shutdown. This may cause data loss.
  2. Solaris hosts have a few known limitations regarding USB support; please see Chapter 14, Known limitations.

In addition to allowing a guest access to your local USB devices, VirtualBox even allows your guests to connect to remote USB devices by use of the VirtualBox Remote Desktop Extension (VRDE). For details about this, see Section 7.1.4, “Remote USB”.

In the Settings dialog, you can first configure whether USB is available in the guest at all, and then choose the level of USB support: OHCI for USB 1.1, EHCI (which will also enable OHCI) for USB 2.0, or xHCI for all USB speeds.

Note

The xHCI and EHCI controllers are shipped as a VirtualBox extension package, which must be installed separately. See Section 1.5, “Installing VirtualBox and extension packs” for more information.

When USB support is enabled for a VM, you can determine in detail which devices will be automatically attached to the guest. For this, you can create so-called “filters” by specifying certain properties of the USB device. USB devices with a matching filter will be automatically passed to the guest once they are attached to the host. USB devices without a matching filter can be passed manually to the guest, for example by using the Devices / USB devices menu.

Clicking on the “+” button to the right of the “USB Device Filters” window creates a new filter. You can give the filter a name (for referencing it later) and specify the filter criteria. The more criteria you specify, the more precisely devices will be selected. For instance, if you specify only a vendor ID of 046d, all devices produced by Logitech will be available to the guest. If you fill in all fields, on the other hand, the filter will only apply to a particular device model from a particular vendor, and not even to other devices of the same type with a different revision and serial number.

In detail, the following criteria are available:

  1. Vendor and product ID. With USB, each vendor of USB products carries an identification number that is unique world-wide, the “vendor ID”. Similarly, each line of products is assigned a “product ID” number. Both numbers are commonly written in hexadecimal (that is, they are composed of the numbers 0-9 and the letters A-F), and a colon separates the vendor from the product ID. For example, 046d:c016 stands for Logitech as a vendor, and the “M-UV69a Optical Wheel Mouse” product.Alternatively, you can also specify “Manufacturer” and “Product” by name.

    To list all the USB devices that are connected to your host machine with their respective vendor and product IDs, you can use the following command (see Chapter 8, VBoxManage):

    VBoxManage list usbhost

    On Windows, you can also see all USB devices that are attached to your system in the Device Manager. On Linux, you can use the lsusb command.

  2. Serial number. While vendor and product ID are already quite specific to identify USB devices, if you have two identical devices of the same brand and product line, you will also need their serial numbers to filter them out correctly.
  3. Remote. This setting specifies whether the device will be local only, or remote only (over VRDP), or either.

On a Windows host, you will need to unplug and reconnect a USB device to use it after creating a filter for it.

As an example, you could create a new USB filter and specify a vendor ID of 046d (Logitech, Inc), a manufacturer index of 1, and “not remote”. Then any USB devices on the host system produced by Logitech, Inc with a manufacturer index of 1 will be visible to the guest system.

Several filters can select a single device — for example, a filter which selects all Logitech devices, and one which selects a particular webcam.

You can deactivate filters without deleting them by clicking in the checkbox next to the filter name.

3.11.2. Implementation notes for Windows and Linux hosts

On Windows hosts, a kernel mode device driver provides USB proxy support. It implements both a USB monitor, which allows VirtualBox to capture devices when they are plugged in, and a USB device driver to claim USB devices for a particular virtual machine. As opposed to VirtualBox versions before 1.4.0, system reboots are no longer necessary after installing the driver. Also, you no longer need to replug devices for VirtualBox to claim them.

On newer Linux hosts, VirtualBox accesses USB devices through special files in the file system. When VirtualBox is installed, these are made available to all users in the vboxusers system group. In order to be able to access USB from guest systems, make sure that you are a member of this group.

On older Linux hosts, USB devices are accessed using the usbfs file system. Therefore, the user executing VirtualBox needs read and write permission to the USB file system. Most distributions provide a group (e.g. usbusers) which the VirtualBox user needs to be added to. Also, VirtualBox can only proxy to virtual machines USB devices which are not claimed by a Linux host USB driver. The Driver= entry in /proc/bus/usb/devices will show you which devices are currently claimed. Please refer to Section 12.8.7, “USB not working” also for details about usbfs.

 

If USB is not working on your Linux host, make sure that the current user is a member of the vboxusers group. Please keep in mind that group membership does not take effect immediately but rather at the next login. If available, the newgrp command may avoid the need for logout/login.
如果虚拟机无法使用USB
1.安装VirtualBox extension package
2.将当前用户添加到vboxusers 组中。

Ubuntu Linux添加源实现自动更新

Debian-based Linux distributions

Add the following line to your /etc/apt/sources.list. According to your distribution, replace ‘<mydist>‘ with ‘artful‘, ‘zesty‘, ‘yakkety‘, ‘xenial‘, ‘vivid‘, ‘utopic‘, ‘trusty‘, ‘raring‘, ‘quantal‘, ‘precise‘, ‘stretch‘, ‘lucid‘, ‘jessie‘, ‘wheezy‘, or ‘squeeze‘:

deb http://download.virtualbox.org/virtualbox/debian <mydist> contrib

(Up to version 3.2 the packages were located in the non-free section. Starting with version 4.0 they are located in the contrib section.)

The Oracle public key for apt-secure can be downloaded

  • here for Debian 8 (“Jessie”) / Ubuntu 16.04 (“Xenial”) and later
  • here for older distributions.

You can add these keys with

sudo apt-key add oracle_vbox_2016.asc
sudo apt-key add oracle_vbox.asc

or combine downloading and registering:

wget -q https://www.virtualbox.org/download/oracle_vbox_2016.asc -O- | sudo apt-key add -
wget -q https://www.virtualbox.org/download/oracle_vbox.asc -O- | sudo apt-key add -

The key fingerprint for oracle_vbox_2016.asc is

B9F8 D658 297A F3EF C18D  5CDF A2F6 83C5 2980 AECF
Oracle Corporation (VirtualBox archive signing key) <[email protected]>

The key fingerprint for oracle_vbox.asc is

7B0F AB3A 13B9 0743 5925  D9C9 5442 2A4B 98AB 5139
Oracle Corporation (VirtualBox archive signing key) <[email protected]>

(As of VirtualBox 3.2, the signing key was changed. The old Sun public key for apt-secure can be downloaded  here.)

To install VirtualBox, do

sudo apt-get update
sudo apt-get install virtualbox-5.2

Replace virtualbox-5.2 by virtualbox-5.1 to install VirtualBox 5.1.30 Note: Ubuntu/Debian users might want to install the dkms package to ensure that the VirtualBox host kernel modules (vboxdrvvboxnetflt and vboxnetadp) are properly updated if the linux kernel version changes during the next apt-get upgrade. For Debian it is available in Lenny backports and in the normal repository for Squeeze and later. The dkms package can be installed through the Synaptic Package manager or through the following command:

sudo apt-get install dkms

What to do when experiencing The following signatures were invalid: BADSIG … when refreshing the packages from the repository?

# sudo -s -H
# apt-get clean
# rm /var/lib/apt/lists/*
# rm /var/lib/apt/lists/partial/*
# apt-get clean
# apt-get update

RPM-based Linux distributions

Starting with VirtualBox 3.0.12 we provide a yum-style repository for Oracle Linux/Fedora/RHEL/openSUSE. Note that 3.0.x .rpm packages are named VirtualBox-3.0.x while 3.1.x .rpm packages are named VirtualBox-3.1-3.1.x. This naming scheme allows to use the older 3.0.x packages without changing the repository.

Furthemore, all .rpm packages are signed. The Oracle public key for rpm can be downloaded here. You can add this key (not necessary for yum users, see below!) with

sudo rpm --import oracle_vbox.asc

or combine downloading and registering:

wget -q https://www.virtualbox.org/download/oracle_vbox.asc -O- | rpm --import -

The key fingerprint is

7B0F AB3A 13B9 0743 5925  D9C9 5442 2A4B 98AB 5139
Oracle Corporation (VirtualBox archive signing key) <[email protected]>

After importing the public key, the package signature can be checked with

rpm --checksig PACKAGE_NAME

Note that importing the key is not necessary for yum users (Oracle Linux/Fedora/RHEL/CentOS) when using one of the virtualbox.repo files from below as yum downloads and imports the public key automatically!

The package signature is checked by yum/zypper as well:

OA 2.x SLIC & OEMCERT Collection

来源:https://forums.mydigitallife.net/threads/oa-2-x-slic-oemcert-collection.5952/

 

Share any new SLIC 2.x bins & certs here.

Only new bins will be added if the OEMID & OEMTableID differ from the bins in the list.


** NO 2.x BIN MODDING REQUESTS **
** KEEP DISCUSSIONS ABOUT 2.x BIN SHARING-COLLECTING ONLY **

SLIC 2.0 is needed for offline activation of Windows Vista and Server 2008 OEM SLP.
SLIC 2.1 is needed for offline activation of Windows 7 and Server 2008 R2 OEM SLP.
SLIC 2.2 is needed for offline activation of Windows Server 2012 OEM SLP.
SLIC 2.3 is needed for offline activation of Windows Server 2012 R2 OEM SLP.
SLIC 2.4 is needed for offline activation of Windows Server 2016 OEM SLP.

SLICs are backward compatible, which means SLIC 2.4 still can activate Windows 7.

下载:https://forums.mydigitallife.net/attachments/oemcert_and_slics_2017-09-02-7z.42836/

 

https://resource.mking007.com/bios/OEMCERT_AND_SLICS_2017-09-02.7z

 

激活:

slmgr.vbs -ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

导入证书:

slmgr.vbs -ilc [盘符]:\[路径]\ASUS-_ASUS_-2.1.XRM-MS
slmgr.vbs -ato