Mercury 水星 5HP~30HP 二行程船外機冷車啟動步驟說明
Version 2.18.1 (21800100) suggested Added on 2021-07-26
As you probably know, in order to be able to store files on a hard drive, it needs to be prepared just right: it needs to be initialized, partitioned, and formatted just the right way. If you’ve bought an external drive in a store, the preparation has probably been already done by the drive manufacturer. However, what if you want the drive to be prepared differently? For example, you may want to re-format the drive, or change the partitions that it has. The way to do such tasks in Windows is to use the Disk Management tool that comes preinstalled with Windows.
To get to the Disk Management tool, click on the Start button, right-click on Computer, and choose Manage from the menu:
If you use Windows 10, right-click on the Start button, and choose Disk Management from the menu instead.
Before you continue, first things first: Disk Management is a very powerful tool, and with great power comes great responsibility! If you are not very experienced with computers, you can look, but better not touch and let someone more knowledgeable to do the job. Because with Disk Management it’s very easy to destroy your partitions and lose your files, if you don’t know what you are doing.
The most important thing when using the Disk Management tool is to make sure you can identify the disk you want to manage in the list. Usually you can do it by the total size of the disk displayed, although it may be confusing. For example, in this example, a hard drive that’s described as a 60 GB drive by the manufacturer, is shown to have only 55.89 GB by Windows. (Apparently, the disk manufacturers and Windows have a different understanding of what a “gigabyte” is.) Also, if you have several disks of the same size attached, it may get even more confusing. If in doubt, better unplug all external drives except for the one you actually want to work with, to make sure you are not accidentally erasing data on a wrong disk!
In our case, the 60 GB disk (shown as 55.89 GB disk in the list) is Disk 4 (let’s remember this number, we will need it a bit later.) It has two partitions, one is a 200MB EFI partition that has no drive letter assigned, and another NTFS partition of the size 55.69 GB, that has the label test and the drive letter F:. Although these two partitions looks similar, they are treated very differently by Windows. If you right-click on the normal NTFS partition, you should see the normal menu that lets you perform various tasks on that partition, including the Delete Volume command:
However, if we right-click on the first EFI partition, the menu we get is completely disabled:
As you can see, the system partition is protected in such a way that even the powerful Disk Management tool cannot do anything to it. Note that it’s not because the partition is EFI, it’s because the tool that created that partition had marked it in a way that prohibits other tools to tamper with it. However, what if we want to delete the EFI system partition and re-initialize the disk from scratch?
While the Disk Management tool is helpless in this situation, fortunately Windows offers yet another tool, DISKPART, that can do things to the disks that Disk Management can’t. The tricky part is, that DISKPART is a command-line tool, that requires us to type commands into its command prompt to make it do what we want.
To get access to the DISKPART tool, first let’s open the Windows command prompt in the “administrator” mode. We can do that by clicking the Start button and entering cmd in the search box:
(If you use Windows 8 that has no Start Menu, you can get our StartFinity utility to get the Start Menu back.)
Make sure that cmd is highlighted on the menu above, but do not press the Enter key yet! Instead, press the Ctrl and Shift keys together, and while keeping them depressed, press Enter. The Ctrl+Shift combination makes the command prompt to open in the “administrator” mode. To start the DISKPART tool, enter the diskpart command into the command prompt window:
This should display the DISKPART command prompt. The first command we should use is list disk that should display the list of the disks currently connected to the computer:
Again, it’s very important to properly identify the disk we want to work with in the list. Our 60 GB disk is still listed as Disk 4 with the capacity 55 GB. Once we are sure that this is the disk we want to re-initialize, we need to select it, by entering the command select disk 4 (yes, that’s how selection is usually done when using the command line tools!). Then, let’s use the list disk command again, to confirm that the disk in question is indeed now selected:
After double-checking that Disk 4 is now selected (it should have the star character * in front of its label), it’s time to finally issue the command that will erase everything on the disk 4, including the protected partition. The command that does that is clean. Note that this command erases everything on the selected disk, all partitions, protected or not. If you still have files on other partitions of disk 4 that you want to keep, you should exit now and backup those files, because after using the clean command all such files will be erased without a trace!
After the clean command is done (it should take no more than a few seconds), we get a fresh disk with all partitions erased. We can exit the DISKPART command prompt (by typing exit into its command line), and go back to the Disk Management tool (see above how to open it.) When it starts, it automatically detects the presence of the clean disk and prompts us to initialize it:
Press OK and the newly cleaned disk will appear in the list. The difference is, the protected EFI partition is gone! (The normal NTFS partition that used to be on the disk 4, is gone, too.) The disk is now ready for you to start creating partitions, formatting them, and do other things as needed:
Note that if you are trying to erase the system disk that hosts the C: drive where Windows itself is installed and running, then even the powerful DISKPART command can’t work: Windows simply refuses to erase the drive from which it is running. To erase such a disk, you need to physically remove it from the computer, attach it to another computer as an external drive, and then use DISKPART on that computer to erase the disk.
Happy disk managing!
xli@abyss00123-vm:~$ getnet Sorry, command-not-found has crashed! Please file a bug report at: https://bugs.launchpad.net/command-not-found/+filebug Please include the following information with the report: command-not-found version: 0.3 Python version: 3.8.5 final 0 Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal Exception information: unable to open database file Traceback (most recent call last): File "/usr/lib/python3/dist-packages/CommandNotFound/util.py", line 23, in crash_guard callback() File "/usr/lib/command-not-found", line 90, in main cnf = CommandNotFound.CommandNotFound(options.data_dir) File "/usr/lib/python3/dist-packages/CommandNotFound/CommandNotFound.py", line 79, in __init__ self.db = SqliteDatabase(dbpath) File "/usr/lib/python3/dist-packages/CommandNotFound/db/db.py", line 12, in __init__ self.con = sqlite3.connect(filename) sqlite3.OperationalError: unable to open database file xli@abyss00123-vm:~$
sudo chmod ugo+r /var/lib/command-not-found/commands.db*
Create a file with the encrypted server password:
In Powershell, enter the following command (replace myPassword with your actual password):
"myPassword" | ConvertTo-SecureString -AsPlainText -Force | ConvertFrom-SecureString | Out-File "C:\EmailPassword.txt"
Create a powershell script (Ex. sendEmail.ps1):
$User = "usernameForEmailPassword@gmail.com" $File = "C:\EmailPassword.txt" $cred=New-Object -TypeName System.Management.Automation.PSCredential -ArgumentList $User, (Get-Content $File | ConvertTo-SecureString) $EmailTo = "emailTo@yahoo.com" $EmailFrom = "emailFrom@gmail.com" $Subject = "Email Subject" $Body = "Email body text" $SMTPServer = "smtp.gmail.com" $filenameAndPath = "C:\fileIwantToSend.csv" $SMTPMessage = New-Object System.Net.Mail.MailMessage($EmailFrom,$EmailTo,$Subject,$Body) $attachment = New-Object System.Net.Mail.Attachment($filenameAndPath) $SMTPMessage.Attachments.Add($attachment) $SMTPClient = New-Object Net.Mail.SmtpClient($SmtpServer, 587) $SMTPClient.EnableSsl = $true $SMTPClient.Credentials = New-Object System.Net.NetworkCredential($cred.UserName, $cred.Password); $SMTPClient.Send($SMTPMessage)
Automate with Task Scheduler:
Create a batch file (Ex. emailFile.bat) with the following:
powershell -ExecutionPolicy ByPass -File C:\sendEmail.ps1
Create a task to run the batch file. Note: you must have the task run with the same user account that you used to encrypted the password! (Aka, probably the logged in user)
That’s all; you now have a way to automate and schedule sending an email and an attachment with Windows Task Scheduler and Powershell. No 3rd party software and the password is not stored as plain text (though granted, not terribly secure either).
The easiest way to clear address bar history is to use the quick and easy file explorer right click option. With just a couple of clicks, Windows will clear the file explorer’s address bar history.
If the above two methods did not work for some reason, you can try editing the registry to clear windows explorer address bar. You see, all the history items in the file explorer are stored as an individual value within the registry editor. By deleting those values, you can delete the file explorer address bar history.
Also, since the history items are stored as individual values, you can delete specific keys to clear specific items from the address bar history. For instance, maybe you don’t want a specific folder address to appear in the address bar history. In those situations, deleting specific registry value will get the job done.
For this specific purpose, though editing registry is fairly easy, I’d recommend you back up the registry so that you can restore in case of any mishaps.
regeditand click on the “Ok” button to open the Windows Registry Editor.
Found a very useful software to do direct boost from ISO/WIM/IMG/VHD(x)/EFI files. It will be much easier for the IT to install OS via USB. As you can get all the ISOs in to a single USB drive, and keep just a single drive. Also, you can directly boot from VHD image, very useful.
Of cause, there are many bugs, as it is still young.
sudo apt-get install git
git clone https://github.com/AdnanHodzic/displaylink-debian.git
cd displaylink-debian/ && sudo ./displaylink-debian.sh
will update my instruction shorlty
Modify the file /etc/systemd/resolved.conf
add “Domains=xxxx.xxxxx” to the file
xli@xxxxxxx-vm:~$ more /etc/systemd/resolved.conf
xli@xxxxxx-vm:~$ nslookup rds