search for: us_10130

Displaying 4 results from an estimated 4 matches for "us_10130".

2015 Jun 29
2
Windows 10 tech preview build 10130
On Mon, 2015-06-29 at 13:47 -0700, Greg Bailey wrote: > I've installed it on a KVM guest on a CentOS 7 host. I was hoping it wasn't going to come to that. That is, I hope it's not a CentOS 6 issue. > I've always had more success using the drivers obtained from running the > spice guest tools vs. the virtio-win stuff. I use: > >
2015 Jun 30
2
Windows 10 tech preview build 10130
On Mon, 2015-06-29 at 18:50 -0700, ToddAndMargo wrote: > I suspect your ISO is corrupted. Run your sha1sum against it. > > 5EF5A65B474D63BC3DF46CC84D47064B142AA800 > Windows10_InsiderPreview_x64_EN-US_10130.iso Damn it, I didn't consider that. I'm assuming you meant sha1sum because I ran it and sure enough, no match. I'm downloading it again. Hopefully I have better luck this time. Thanks for the tip! -- Kanwar R.S. Sandhu
2015 Jun 30
0
Windows 10 tech preview build 10130
...e what for!! WTF. Hi Ranbir, I have Son-of-Frankenstein (SOF, or W10) on Scientific Linux 6.6 under KVM. I am currently on 10130. And I am downloading 10158. I suspect your ISO is corrupted. Run your sha1sum against it. 5EF5A65B474D63BC3DF46CC84D47064B142AA800 Windows10_InsiderPreview_x64_EN-US_10130.iso Here is the latest English 64 bit iso: http://windows.microsoft.com/en-us/windows/preview-iso-update-1504 Product key: 6P99N-YF42M-TPGBG-9VMJP-YKHCF And this is my qemu run string, if it helps: $ ps ax | grep -i [w]10 16031 ? Sl 29:48 /usr/libexec/qemu-kvm -name KVM-W10 -S -M...
2015 Jul 04
0
Windows 10 tech preview build 10130
On 06/30/2015 06:02 AM, Kanwar Ranbir Sandhu wrote: > On Mon, 2015-06-29 at 18:50 -0700, ToddAndMargo wrote: >> I suspect your ISO is corrupted. Run your sha1sum against it. >> >> 5EF5A65B474D63BC3DF46CC84D47064B142AA800 >> Windows10_InsiderPreview_x64_EN-US_10130.iso > > Damn it, I didn't consider that. I'm assuming you meant sha1sum because > I ran it and sure enough, no match. > > I'm downloading it again. Hopefully I have better luck this time. > > Thanks for the tip! > Did it work? -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~...