How to install OS for simple user

My procedure when installing OS for simple user:
  1. Optional: Create system and data partitions with appropriate sizes.
  2. Install OS to system partition.
  3. Optional: Install newest drivers from the Internet or alternately from drivers CD.
  4. Install programs (Chrome, VLC Media Player, Office Suite, Skype, Total Commander / FreeCommander, JRE), e.g. using chocolatey script below.
  5. Optional: Update OS (Windows Update).
  6. Optional: Set up OS
    7. (through the Control Panel).
  7. Optional:Move users' settings folders to the data partition.
  8. Optional: Hide dangerous folders (system, backups).
  9. Set up programs (home page, bookmarks, Skype account, ICQ account, TC panels).

    10. Chocolatey script for installing all necessary programs (run in Admin cmd):

    @powershell -NoProfile -ExecutionPolicy Bypass -Command "iex ((New-Object System.Net.WebClient).DownloadString('https://chocolatey.org/install.ps1'))" && SET "PATH=%PATH%;%ALLUSERSPROFILE%\chocolatey\bin"
    @choco install googlechrome -y
    @choco install vlc -y
    @choco install skype -y
    @choco install freecommander-xe -y
    @choco install javaruntime -y
    @choco install libreoffice-still -y
Chocolatey script for additional programs that I use:

choco install 7zip -y
choco install foxitreader -y
choco install git -y
choco install gradle -y
choco install intellijidea-ultimate -y
choco install maven -y
choco install notepadplusplus -y
choco install correttojdk -y
choco install postman -y
choco install qbittorrent -y
choco install tortoisegit -y

Comments

Post a Comment

Popular posts from this blog

Notes about the Clean Architecture book

The first look into the contents of the book was a bit scary. Some of these things were already explained in Robert Martin's previous books. Then I found out they are explained from a different (software architect's) perspective. Overall, I liked this book better than Clean Coder, but it was less useful for me than Clean Code book of the same author. Part I - Introduction The foreword contained two useful antipatterns: Too authoritative and rigid architecture. Speculative generality in software architecture. The main point of the preface is that not much changed for the last 50 years in software architecture. The rules of software architecture are the same regardless of any variable (time, type of project, ...). When you get the architecture of the software right, you magically don't need horde of programmers maintaining it. Chapter 1 - What is Design and Architecture? There is no difference between software design and architecture. There is a continuum of...
Read more

Notes about The Pragmatic Programmer

Chapter 1 - Pragmatic Philosophy There is a repeated pattern at the start of the book (tip 2), which its authors, Hunt and Thomas, use regularly. They think about their work while they are doing it and try to improve it. It is about e.g. repetitive stuff, which could be automated. Tip 3 is about the attitude to business requirements. As a developers, we should be actively searching for ways to make business requirements possible, instead of giving lame excuses, why it is not possible. What would we think about a bank officer who makes lame excuses why he cannot do what we ask? Tip 4 is about a theory, that technical debt is like broken windows in cities. Those are small problems, which, left unfixed, can raise to become huge problems. We should be fixing even small technical debt as soon as it is found. We should also think about, what is the root cause, that this technical debt happened at all. Tip 7 elaborates whether software quality should be part of the requirements. The most of t...
Read more

Notes about the Building Microservices

These are notes for my future self about Sam Newman's book, Building Microservices 2nd edition.  Preface Microservices are an approach to distributed applications that use finely-grained services and change, deploy and release them independently. Microservices have become the default go-to architecture when designing system, which Newman finds hard to justify #surprised and want to share his view on why. Foundation Chapter 1 - What are Microservices? Microservices are independently releasable services modeled around a business domain . They are kind of SOA, but the one which is opinionated about how service boundaries should be drawn and where independent deployability is the key. Microservices should implement information hiding and expose their API in some way, e.g. via REST/JSON API or by emitting events. They should have their own database schema. To highlight that the services are as independent as possible, Newman draws them as hexagons, a homage to Alistair Cockburn's H...
Read more