- Joined
- Mar 2, 2014
- Messages
- 1,778
- Motherboard
- Gigabyte Z390 I AORUS PRO WIFI
- CPU
- i9-9900K
- Graphics
- RX 580
- Mac
-
- Classic Mac
-
- Mobile Phone
-
Four Hacks in house were excessive, and daughter #2 needed one, but is a Windows user. So I converted my "Mini-ITX 1" Haswell listed below to a Windows 10 Pro machine. This was my first experience with Windows. It was very hard to do that... didn't expect so much trouble. Rants below; maybe you want to skip, that's okay.
Using my Hack at left, I downloaded a Windows 10 ISO image from Microsoft. On instructions from a Guru, formatted a USB 16 GB flash drive in FAT32/GPT/GUID since I had read that a UEFI installation needed that format. Opened the ISO image and copied all its files except its "sources" folder to the USB. Reason was that one file in there was too large for the FAT32 format, which can only handle files up to 4 GB, and "install.wim" was 5.15 GB.
Rant 1: Why would Microsoft require its installer be FAT32, and then stick a 5.15 GB file in there?
So I learned that the large file could be split by a program called "WIMB." But in order to run that on my Hack, I needed "Homebrew." So using the Terminal commands required, I started downloading "Homebrew." About halfway through the download it stopped with an error and some text explaining that Homebrew is a "shallow clone," and I needed to use a program "unshallow" to "unshallow it." That was done in Terminal and took quite a while. But then Homebrew finished, and I had it. Then again using Terminal I stuck in some obscure command to download WIMB, which refused to download because Homebrew's certificate had expired and I was not allowed to use it.
Rant 2: Why recommend a program whose certificate was not current?
So I messed around and found a way for WIMB to disregard the expired certificate, and then I downloaded WIMB. Running it split "install.wim" into 2 files. The first was 4.19 GB, and the second was 5.15-4.19= 0.96 GB. Not good, but I was on a roll. so with a sources folder that now contained the two split files, plus others, I attempted to install Windows on one of my two 1 TB Sandisk SSDs. No go. The installer "ran," but only about halfway. Later I found out that it was incorrectly formatted and needed to be FAT32/Master Boot Record. In the process I changed the pre-made "split" number in WIMB from 4000 MB to 2048 MB which split "install.wim" into three parts, 2.15 GB, 2.15 GB, and 0.85 GB. Now the installer went completely through, and I had a copy of Windows 10 Pro. Then I was introduced to the Microsoft Windows UI. (Yech.)
I downloaded a Windows 10 Gigabyte graphics driver for my Nvidia GT 1030, and to check whether it worked, I downloaded "Heaven" and "Valley" Unigine benchmarks (which I use on my Hacks with no problems). But neither would run, claiming they could not find "MSVCP100.dll." So I found that on the Net and downloaded it. I kept trying putting it in different folders (again Yech) until finally I guess I got the right one, and then both programs ran and I knew the driver worked properly.
Rant 3: If an app needs a file, why doesn't it carry it?
I found out that MSVCP100.dll is a C++ file, and Windows OS didn't have it. That seems very odd to me. I noticed there was a MSVRT100 file, but I guess that one was a no-go.
That's as far as I got on Windows, and it took hours over 3 days to get there. Hoping to pass this computer off in the next few days, if I get over this head cold. She wants it and she can deifinitely have it!
Using my Hack at left, I downloaded a Windows 10 ISO image from Microsoft. On instructions from a Guru, formatted a USB 16 GB flash drive in FAT32/GPT/GUID since I had read that a UEFI installation needed that format. Opened the ISO image and copied all its files except its "sources" folder to the USB. Reason was that one file in there was too large for the FAT32 format, which can only handle files up to 4 GB, and "install.wim" was 5.15 GB.
Rant 1: Why would Microsoft require its installer be FAT32, and then stick a 5.15 GB file in there?
So I learned that the large file could be split by a program called "WIMB." But in order to run that on my Hack, I needed "Homebrew." So using the Terminal commands required, I started downloading "Homebrew." About halfway through the download it stopped with an error and some text explaining that Homebrew is a "shallow clone," and I needed to use a program "unshallow" to "unshallow it." That was done in Terminal and took quite a while. But then Homebrew finished, and I had it. Then again using Terminal I stuck in some obscure command to download WIMB, which refused to download because Homebrew's certificate had expired and I was not allowed to use it.
Rant 2: Why recommend a program whose certificate was not current?
So I messed around and found a way for WIMB to disregard the expired certificate, and then I downloaded WIMB. Running it split "install.wim" into 2 files. The first was 4.19 GB, and the second was 5.15-4.19= 0.96 GB. Not good, but I was on a roll. so with a sources folder that now contained the two split files, plus others, I attempted to install Windows on one of my two 1 TB Sandisk SSDs. No go. The installer "ran," but only about halfway. Later I found out that it was incorrectly formatted and needed to be FAT32/Master Boot Record. In the process I changed the pre-made "split" number in WIMB from 4000 MB to 2048 MB which split "install.wim" into three parts, 2.15 GB, 2.15 GB, and 0.85 GB. Now the installer went completely through, and I had a copy of Windows 10 Pro. Then I was introduced to the Microsoft Windows UI. (Yech.)
I downloaded a Windows 10 Gigabyte graphics driver for my Nvidia GT 1030, and to check whether it worked, I downloaded "Heaven" and "Valley" Unigine benchmarks (which I use on my Hacks with no problems). But neither would run, claiming they could not find "MSVCP100.dll." So I found that on the Net and downloaded it. I kept trying putting it in different folders (again Yech) until finally I guess I got the right one, and then both programs ran and I knew the driver worked properly.
Rant 3: If an app needs a file, why doesn't it carry it?
I found out that MSVCP100.dll is a C++ file, and Windows OS didn't have it. That seems very odd to me. I noticed there was a MSVRT100 file, but I guess that one was a no-go.
That's as far as I got on Windows, and it took hours over 3 days to get there. Hoping to pass this computer off in the next few days, if I get over this head cold. She wants it and she can deifinitely have it!
Last edited: