Subject: Graphics Cards | July 4, 2015 - 02:39 PM | Tim Verry
Tagged: zotac, maxwell, gtx 980ti, factory overclocked
Zotac recently unleashed a monstrous new GTX 980Ti AMP! Extreme graphics card featuring a giant triple slot cooler and a very respectable factory overclock.
Specifically, the Zotac ZT-90505-10P card is a custom card with a factory overclocked NVIDIA GTX 980Ti GPU and GDDR5 memory. The card is a triple slot design that uses a dual fin stack IceStorm heatsink with three 90mm temperature controlled EKO fans. The cooler wraps the fans and HSF in a shroud and also uses a backplate on the bottom of the card. The card is powered by two 8-pin PCI-E power connectors and display outputs include three DisplayPort, one HDMI, and one DL-DVI.
Zotac was able to push the Maxwell GPU with its 2,816 CUDA cores to 1,253 MHz base and 1,355 MHz boost. Further, the 6GB GDDR5 memory also has a factory overclock of 7,220 MHz. These clockspeeds are a decent bump over the reference speeds of 1,000 MHz GPU base, 1,076 MHz GPU boost, and 7,012 MHz memory.
We’ll have to wait for reviews to know for sure, but on paper this card looks to be a nice card that should run fast and cool thanks to that triple fan cooler. The ZT-90505-10P will be available shortly with an MSRP of $700 and a 2 year warranty.
Definitely not a bad price compared to other GTX 980Ti cards on the market.
Subject: General Tech | July 5, 2015 - 04:20 PM | Scott Michaud
Tagged: windows 10, microsoft
Early this week, Microsoft released a pair of new builds into the Windows Insider Fast Ring. Back to back, Build 10158 was released on Monday and 10159 followed it on Tuesday. These two updates fixed several hundred bugs, officially branded Project Spartan as Microsoft Edge, introduced the new default wallpaper to the desktop and lock screen, and tweaked a few more interface elements since 10130. After an uneventful Wednesday, Build 10162 arrived on Thursday with ISOs released later that evening, which was great for me because I couldn't get the build through Windows Update. Sad face.
I was a Slow Ring user for the last few releases, and I honestly intend to continue with that pace going forward. This is my production machine, but switching to Fast was tempting in hopes that the new build would fix the few problems that I had. Namely, StarCraft II was flickering terribly since 10074 when played in windowed mode. Thankfully, StarCraft II can reliably alt+tab without crashing, but it excludes playing a slow-paced Arcade mod in another monitor while doing something else. Mount & Blade: Warband had similar issues, especially when the monitor and game are set to 120 Hz. It seems to be just DirectX 9 titles, too. Either way, they are still unfixed for me. Some of our viewers may want to know my experience.
The first thing that I noticed was a seemingly new upgrade screen between asking to reboot and actually rebooting. This was something that I only remember experiencing with Windows Updates, not whole new Windows builds. Perhaps this was a big one for some reason? It did try to install an anti-malware definition alongside it, so maybe it was just a weird interaction between Windows Update and the Windows 10 in-place build upgrade. Maybe it's something new though.
The lock screen is the next obvious change. It contains the new Windows branding that was announced a couple of weeks ago. The slanted window was made out of glass, fog, and projected light. Even though it fits the previous branding, Microsoft made a big deal out of it.
The major change occurs once logged in. Microsoft Edge is no longer referred to as “Project Spartan”, and it is basically a full-fledged web browser now. Its performance is great, and it is nice to see the light at the end of the tunnel when it comes to browser compatibility. I do feel that the interface is kind-of ugly, though. Granted, the soft fonts are probably easier to scale between high and low DPI monitors, but I would prefer something more crisp. Likewise, the big, featureless, rectangular UI elements are likely a compromise for touch displays, but I've always thought they were placeholder during development builds. Then again, I find basically every browser to be bland, so there's that.
Other UI elements were altered as well. For instance, while I don't pay too much attention to elements in the notification tray, I am pretty sure that Quiet Hours and the OneNote shortcut are new. While “Note” is obvious, it opens OneNote, Quiet Hours apparently gives a toggle to disable notifications. This is not a new feature, dating back to Windows 8 and Windows Phone apparently, but it has a new home in the notification area.
We're getting close to the July 29th “release” date and might see several builds before then, too. Builds are mostly merging work into a stable core at this point. According to BuildFeed, fbl_impressive, the branch of Windows 10 that is given to Windows Insiders, is up to build 10164, which was created on July 1st. We're not going to see every build of course, some are destined to partners for instance, but the distance between QA-approved builds is shrinking. Unless something is broken that you hope Microsoft will fix or you can afford the time to upgrade, it might be useful to switch to slow until launch. You could always flip to Fast if something cool comes up, although there is sometimes a lag before Windows Update changes your branch if you do that.
Subject: General Tech | July 5, 2015 - 06:00 PM | Scott Michaud
Tagged: windows 10, microsoft
A couple of days ago, Paul Thurrott wrote an editorial about Microsoft's Windows 10 reservation system. His point was that, while Microsoft claimed users of Windows 7 or 8.1 could upgrade on July 29th, they might not get it until later. Upgrades will start rolling out on the 29th of July, but the actual queue is expected to take several days. According to Microsoft's blog post, which shows blatant disrespect for the Oxford Comma, “Each day of the roll-out, we will listen, learn and update the experience for all Windows 10 users.”
Paul linked this backtrack to an episode of Seinfeld, one where Jerry reserves a rental car; his reservation was held, but a car was not. He stated that the availability date was clearly stated as July 29th, and not everyone will get it then. I can see his point, and I agree with it. Microsoft really should provide what they claim on the date that they claim it.
On the other hand, it is possible that Microsoft saw the whole reservation system as reserving your spot in line. That is, it might be that upgrade requests will be processed in reservation order, at least mostly, when devices are available. I imagine a “take a number” system where slots will be assigned for anyone below a threshold that increases as upgrades are fulfilled. Again, this is hypothetical, but I cannot really see any other reason for a reservation system in the first place, apart from pure marketing.
Either way, some may need to wait until after July 29th to experience Windows 10, and Microsoft botched their announcement.
Subject: Networking | July 5, 2015 - 07:17 PM | Scott Michaud
Tagged: ipv6, ipv4, arin
While the IP system allows for about 4.3 billion addresses, not all of those are available to actual devices. There are some that are designed for private network use, so a router can assign them without worrying that it is blocking traffic to some external resource. Another big drain was wasted addresses, where organizations would purchase a big chunk of the public address space and use a tiny fraction of it. Beyond that, we just have a lot of devices, from cell phones, to home networks, to the servers they contact. Microsoft is trying to reach a billion devices with Windows 10, and the vast majority of them are expected to be online.
I'm mentioning it now because the American Registry for Internet Numbers (ARIN) announced that they will be unable to fulfill some requests for IPv4 blocks. All they have left at the moment are /23 and /24 chunks, which are bundles of 512 and 256 public addresses. As of the time of publishing, 46 chunks of 512 and 431 chunks of 256 are available, which is 133,888 total public numbers.
Of course, it's not as simple as saying “let's move to IPv6 then”. There will be some pain when the switch happens. For instance, Unreal Engine 4 has only been IPv6-compliant for a year, with the launch of Unreal Engine 4.2 in June 2014. This poses a significant problem for older games that rely upon IPv4 addresses for multiplayer, and that doesn't even consider other online software.
- 2 of 2