

(It's a hold over from OpenVMS' Allocation Class ) Each partition/volume also has the allocation class as the volume label, example: $1$Disk$Data is a data partition on physical disk 1.Īfter the initial installation pass and the subsequent reboot request, two new boot options are inserted into my boot record: I use the "$n$" prefix to designate the physical disk on my system. Greetings,I have a dial boot system with both boot disks running Win 10 Pro. Other Info: Macrium (Licensed), Password Safe, Office 365, Wise Disk Cleaner, Crystal Disk Info Synology NAS DS918+ 10TB, Netgear Nighthawk X8 R8500 Tri-Band

Samsung 860 EVO 1TB (Primary Data Drive),Īntivirus: Malwarebytes Premium, SuperAntiSpyware Pro (Licensed) Samsung 840 EVO 250GB (System Copy Drive), Hard Drives: Samsung M.2 NVMe 960 EVO 500GB Boot, Mouse: Logitech MX Master 3 Wireless & BluetoothĬooling: Corsair Hydro H150i, 360mm Rad & Five Corsair 140mm Pro ML Case Fans Keyboard: das Keyboard MX Brown Mechanical Switches Model DASKMKPROSIL-3G7-r1.0 Monitor(s) Displays: Asus VP279 27", Samsung BX2431 24"
