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 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

Notes about A Philosophy of Software Design

My notes about the book by John Ousterhout. It is quite a short book. Originally I made a mistake of reading just the Conclusions of the chapters but there is a lot of contents not in the Conclusions. After really reading the whole book, I started to like the Red Flags and other small pieces of hints. Chapter 2 - The Nature of Complexity Complexity is anything related to the structure of a system that makes it hard to understand or modify. Isolating complexity in a place where it will almost never be seen or touched is almost as good as removing it. There are many symptoms of complexity: Change amplification - when change requires modification in many places.  Cognitive load - how much a developer must know in order to make a change. Sometimes more code is simpler than less code because of cognitive load. Unknown unknowns - it is not obvious which places should be modified or what knowledge the developer must have to make a change. Complexity is caused by 2 things - dependencies and o
Read more