Recommended Posts

When will support applications for screens with high densities. With a macbook pro Retina I find myself with applications with a font blur or appropriate.

For example, in resolution (200 DPI) GUI some applications are not well suited. (For example: Nvidia Control Panel)

Metro mode is successful.

What is the maximum resolution supported by Windows 8 for a better rendering?

I hope that the next Windows (9 or Blue) will support this type of screen!

Link to comment
https://www.neowin.net/forum/topic/1133388-windows-high-dpi-retina/
Share on other sites

The problem with 'retina' is that Apple uses pixel doubling (no increase in information) and MS does not. Both have pros/cons but you aren't going to see a fix in future versions as MS doesn't utilize the scaling tricks Apple does.

As far as apps go, anything over 150% is a outside MS's guidelines anyway. (Default for retina is 144dpi - try using the 'WinXP scaling' option so bitmaps aren't so stretched)

Up to who wrote it and what standards they decided to follow or make up I'm afraid. Lots of applications that support high DPI and many that really should by now that don't. Heck, even Windows NT 6.X doesn't scale all that well when it comes to the system tray icons.

If you're waiting for Windows to manage DPI scaling properly, you're gonna be waiting a while it seems like. As screens get higher and higher resolution, and applications like HTPC become more prevalent, I kept thinking they'd take care of it one day, but to this day it's still absolutely horrible. With the resolution screens are starting to run now though, I can't imagine they can ignore it in the next release of Windows. Pixel doubling may be just a simple trick to display to a high resolution screen clearly without actually utilizing the extra pixels, but at least it works. With Windows you get fonts falling off all over, buttons sized weird, etc. And it's not just applications written poorly, it's the OS too. The Superbar in Windows 7 doesn't even work properly in high DPI mode (stays on top full screen in some apps). This is one of the most massively neglected parts of Windows that has been bothering me for a long time. I use my computer plugged into a TV from 10 feet away, and while I have 20/20 vision and it's a 50" screen so I can read most things, I still have to squint or use the magnifier at times. Oh what I'd do for an OS that handles DPI scaling better.

  • Like 2

I think you can choose the scaling eg 100%, 125%, 150% and 200% on win8. It supposedly works well. 3rd parties are to blame for the apps that aren't made to work with hidpi displays though. There are very few displays in use so there isn't much incentive to change things at the moment for most developers.

I think you can choose the scaling eg 100%, 125%, 150% and 200% on win8. It supposedly works well. 3rd parties are to blame for the apps that aren't made to work with hidpi displays though. There are very few displays in use so there isn't much incentive to change things at the moment for most developers.

It doesn't still on Windows 7, 8, Server 2012. Examples: System tray, super bar behaviour, CMD window snap to, Nvidia control panel, anything based on a MMC.

I use 108% on my laptop @ 1080p. Any higher and it goes into fugly system tray icon mode.

On my 42" TV, I use 150% where things look roughly the same scale as they should at 720p but at 1080p. The exception is the mouse cursor which is the size of a tennis ball and the above examples.

Microsoft really needs to move over to vector art and allow users to freely scale the interface to their choosing (within reason) - by default it should scale according to physical size. Icons that currently change appearance dependent upon their size could be handled with transition points. Not only is such a change important for high-DPI displays but it's even an issue at the moment:

30" - 101 DPI - 2560x1600

27" - 109 DPI - 2560x1440

24" - 94 DPI - 1920x1200

22" - 90 DPI - 1680x1050

That means the Windows UI changes physical size depending on the display that you have, which is terribly inconsistent. By default Windows 8 uses 125% scale for my 30" display, which makes everything appear too large. Therefore I prefer to use 100% scale, which is a bit smaller than I would like. Using a custom scale looks terrible, as icons appear aliased and UI elements don't scale smoothly.

Apple has a huge advantage over Microsoft in that it controls the hardware as well as the software. Microsoft's only option is to implement a more flexible approach and vector art is the obvious way to achieve that. There was talk that Microsoft was working on this years ago - back when Vista was still in development - but unfortunately it was dropped. Now Microsoft has fallen behind. Metro is designed with alternative DPIs in mind but unfortunately it's not a replacement for desktop applications.

Microsoft really needs to move over to vector art and allow users to freely scale the interface to their choosing (within reason) - by default it should scale according to physical size. Icons that currently change appearance dependent upon their size could be handled with transition points. Not only is such a change important for high-DPI displays but it's even an issue at the moment:

30" - 101 DPI - 2560x1600

27" - 109 DPI - 2560x1440

24" - 94 DPI - 1920x1200

22" - 90 DPI - 1680x1050

That means the Windows UI changes physical size depending on the display that you have, which is terribly inconsistent. By default Windows 8 uses 125% scale for my 30" display, which makes everything appear too large. Therefore I prefer to use 100% scale, which is a bit smaller than I would like. Using a custom scale looks terrible, as icons appear aliased and UI elements don't scale smoothly.

Apple has a huge advantage over Microsoft in that it controls the hardware as well as the software. Microsoft's only option is to implement a more flexible approach and vector art is the obvious way to achieve that. There was talk that Microsoft was working on this years ago - back when Vista was still in development - but unfortunately it was dropped. Now Microsoft has fallen behind. Metro is designed with alternative DPIs in mind but unfortunately it's not a replacement for desktop applications.

+1.

Totally agreed. Having vectors, instead of pixels will allow the UI to be scaled or downscaled at the user's decision.

+1.

Totally agreed. Having vectors, instead of pixels will allow the UI to be scaled or downscaled at the user's decision.

Correct me if I'm wrong here but I'm sure that's just what they do, to a extent, with the new metro UI and apps. The start screen and all the other new UI elements scale automatically depending on the size of your screen and apps can as well. MS had a nice long blog post about this iirc.

That said, the problem is that the old desktop side of things doesn't do this, at this point. I dunno what they'll do with it going forward but at some point the desktop as we know it won't be around.

Correct me if I'm wrong here but I'm sure that's just what they do, to a extent, with the new metro UI and apps. The start screen and all the other new UI elements scale automatically depending on the size of your screen and apps can as well. MS had a nice long blog post about this iirc.

That said, the problem is that the old desktop side of things doesn't do this, at this point. I dunno what they'll do with it going forward but at some point the desktop as we know it won't be around.

Only one big problem with Metro. It scales and all automatically, but you don't get much control over it. Scaling to a 1920x1080 screen is nice and all, but when I'm 10 feet away and need it a little bigger to read text, you can't really change that in Metro without having to set ease of access settings to "I'm blind". If anything Windows 8 just made DPI scaling even worse because now the desktop and metro both act differently and neither do a good job.

  • Like 3

The problem with 'retina' is that Apple uses pixel doubling (no increase in information) and MS does not. Both have pros/cons but you aren't going to see a fix in future versions as MS doesn't utilize the scaling tricks Apple does.

As far as apps go, anything over 150% is a outside MS's guidelines anyway. (Default for retina is 144dpi - try using the 'WinXP scaling' option so bitmaps aren't so stretched)

Apple doesn't use pixel doubling unless the app simply doesn't support high DPI modes, and in that case the results match Windows (It does the scaling within the DWM in that case)

I really don't see the issue with Windows. It's supported scaling fine since Vista, it's just the programs that have yet to support it. Most of Microsoft's programs support high DPI modes. Yes some of the built in management tools don't but I personally don't think that's a huge issue (though I do believe it should be fixed for the next version of Windows). Most people don't ever go into those nooks and crannies of the OS and they're still usable, even though they're a bit blurry if you don't scale to 200%.

My Windows system tray icons in Windows 7 and 8 look fine on 150% on my HTPC. What is the issue you are all having? Third party programs often have only standard DPI icons, but I hide everything other than network, volume, and battery anyways. All the built in windows programs in the start menu support high DPI and so does Microsoft Office and all the latest web browsers.

I've also noticed Notepad++ works fine, Adobe Reader, VLC, XBMC, Chrome, FireFox are DPI-aware. Nearly everything I commonly use is.

The problem with 'retina' is that Apple uses pixel doubling (no increase in information) and MS does not. Both have pros/cons but you aren't going to see a fix in future versions as MS doesn't utilize the scaling tricks Apple does.

As far as apps go, anything over 150% is a outside MS's guidelines anyway. (Default for retina is 144dpi - try using the 'WinXP scaling' option so bitmaps aren't so stretched)

If you set it to 200% then Windows will do pixel doubling. Pixel doubling is just 200% scaling. When scaled to 200% then one pixel turns into 4 pixels and looks better than anything that isn't an integer multiple. Apple supports non pixel-doubling mode in their latest OS, too. They function pretty much the same in terms of scaling.

According to this page on MSDN, Microsoft recommends having images for 100%, 125%, 150%, and 200%.

Microsoft really needs to move over to vector art and allow users to freely scale the interface to their choosing (within reason) - by default it should scale according to physical size. Icons that currently change appearance dependent upon their size could be handled with transition points. Not only is such a change important for high-DPI displays but it's even an issue at the moment:

30" - 101 DPI - 2560x1600

27" - 109 DPI - 2560x1440

24" - 94 DPI - 1920x1200

22" - 90 DPI - 1680x1050

That means the Windows UI changes physical size depending on the display that you have, which is terribly inconsistent. By default Windows 8 uses 125% scale for my 30" display, which makes everything appear too large. Therefore I prefer to use 100% scale, which is a bit smaller than I would like. Using a custom scale looks terrible, as icons appear aliased and UI elements don't scale smoothly.

Apple has a huge advantage over Microsoft in that it controls the hardware as well as the software. Microsoft's only option is to implement a more flexible approach and vector art is the obvious way to achieve that. There was talk that Microsoft was working on this years ago - back when Vista was still in development - but unfortunately it was dropped. Now Microsoft has fallen behind. Metro is designed with alternative DPIs in mind but unfortunately it's not a replacement for desktop applications.

Why is changing physical size so bad? That's how it's always been, even on Mac OS.

I really don't see the issue with Windows. It's supported scaling fine since Vista, it's just the programs that have yet to support it. Most of Microsoft's programs support high DPI modes. Yes some of the built in management tools don't but I personally don't think that's a huge issue (though I do believe it should be fixed for the next version of Windows). Most people don't ever go into those nooks and crannies of the OS and they're still usable, even though they're a bit blurry if you don't scale to 200%.

My Windows system tray icons in Windows 7 and 8 look fine on 150% on my HTPC. What is the issue you are all having? Third party programs often have only standard DPI icons, but I hide everything other than network, volume, and battery anyways. All the built in windows programs in the start menu support high DPI and so does Microsoft Office and all the latest web browsers.

If you set it to 200% then Windows will do pixel doubling. Pixel doubling is just 200% scaling. When scaled to 200% then one pixel turns into 4 pixels and looks better than anything that isn't an integer multiple. Apple supports non pixel-doubling mode in their latest OS, too. They function pretty much the same in terms of scaling.

Why is changing physical size so bad? That's how it's always been, even on Mac OS.

I just changed the DPI on my work computer to verify that the same massively annoying bug still exists in Windows 7 DPI scaling. If you change your DPI, the superbar won't ever hide behind an app that's full screen. You have to change the superbar to autohide to get it to go away. This is incredibly annoying on an HTPC that frequently has full screen apps that you don't want to superbar hanging out on. This is more annoying than any of the blurry third party issues. Plus, regardless of who is to blame, there are so many inconsistencies when using high DPI mode in Windows that it's just hard to seriously use. They need to push third parties to update their apps with all these higher resolution screens coming out. It'll be impossible to use an HTPC on a 4k screen without DPI scaling.

I just changed the DPI on my work computer to verify that the same massively annoying bug still exists in Windows 7 DPI scaling. If you change your DPI, the superbar won't ever hide behind an app that's full screen. You have to change the superbar to autohide to get it to go away. This is incredibly annoying on an HTPC that frequently has full screen apps that you don't want to superbar hanging out on. This is more annoying than any of the blurry third party issues. Plus, regardless of who is to blame, there are so many inconsistencies when using high DPI mode in Windows that it's just hard to seriously use. They need to push third parties to update their apps with all these higher resolution screens coming out. It'll be impossible to use an HTPC on a 4k screen without DPI scaling.

Odd, it hides XBMC, WMC, VLC, and KMP just fine on my HTPC when full-screen. My HTPC is set to 150%. That's both on Windows 7 and on Windows 8 which I just upgraded to a month ago.

Maybe other people use some odd programs but any program I use with regularity seems to scale fine. This is with XP-style scaling deselected (gets deselected by default at 150%). A few programs don't advertise that they are DPI-aware but work fine with XP style scaling (so Vista+ will stretch). For these programs you can revert to XP style scaling individually in the programs compatibility settings.

Why is changing physical size so bad? That's how it's always been, even on Mac OS.

Before getting my 30" (2560x1600) display I tried a 27" (2560x1440) display and found the Windows UI elements to be far too small, as I had previously been using a 24" (1920x1200) display. The DPI increase of 15% made everything look noticeably smaller but the 125% scale was too much and using it makes applications - especially Chrome - look very different (not in a positive way).

Displays have been increasing the DPI over the years and we're about to see massive jumps with 4K / 8K displays. Microsoft just hasn't done enough.

Before getting my 30" (2560x1600) display I tried a 27" (2560x1440) display and found the Windows UI elements to be far too small, as I had previously been using a 24" (1920x1200) display. The DPI increase of 15% made everything look noticeably smaller but the 125% scale was too much and using it makes applications - especially Chrome - look very different (not in a positive way).

Displays have been increasing the DPI over the years and we're about to see massive jumps with 4K / 8K displays. Microsoft just hasn't done enough.

Interesting. I barely notice the change from my 23" 1080p monitor to my 30" 2560x1600 monitor. How has Microsoft not done enough? Windows fully supports scaling. If 125% is too much set a custom scaling. You can change it by individual percentage points. They've been recommending all programs be DPI-aware since Vista came out.

Interesting. I barely notice the change from my 23" 1080p monitor to my 30" 2560x1600 monitor.

That's because that's a jump from 94 DPI to 101 DPI, rather than to 109 DPI. You should have noticed a difference but it wouldn't have been as pronounced as a 27" display.

How has Microsoft not done enough? Windows fully supports scaling. If 125% is too much set a custom scaling.

Because that scaling is pretty nasty. With Windows XP style disabled it's certainly better but a lot of applications will appear blurry - I couldn't put up with it for more than a few minutes. Whereas vector art scales without issue.

The key issue on Windows is a lot of applications report to Win32 that they are "DPI Aware", meaning that they tell Windows they are capable of scaling their UIs depending on the DPI, even though they actually can't. It seems to be the default in most development environments (e.g. .Net WinForms, C++ MFC) which means a lot of applications are unintentionally developed with poor DPI support. If they don't report to Windows they are DPI aware, then the system scales the apps in a similar way to how Mac OS treats non-Retina apps.

It doesn't help that most developers work using the standard DPI, and therefore don't realise the issues. I myself have only started recently running my apps in a high DPI virtual machine as part of the testing process. This means a lot of the blame should really be placed in the developers hands (although as mentioned a lot of MS apps are just as guilty). The Win 8 UI was designed to solve this issue, which it does, just as mentioned it can't (yet) be customised.

That's because that's a jump from 94 DPI to 101 DPI, rather than to 109 DPI. You should have noticed a difference but it wouldn't have been as pronounced as a 27" display.

Because that scaling is pretty nasty. With Windows XP style disabled it's certainly better but a lot of applications will appear blurry - I couldn't put up with it for more than a few minutes. Whereas vector art scales without issue.

This is up to the developer to fix. You don't need vector art which is computationally expensive. If the program developer followed Microsoft guidelines the program would look good. They suggest to have bitmaps for 100%, 125%, 150%, and 200% which are then shrunk to fit sizes in between. Even if vector art was supported, I don't see why the developers who have still not fixed their programs will suddenly update them to support vector art

Programs that are designed to be DPI aware look great. The programs which aren't DPI-aware and when using Vista style scaling will look blurry because you're not increasing them in an integer multiple. There is nothing the OS can do to fix this issue. Take any screenshot with text and put it in an image editor and increase the size by anything other than integer multiples and it will look bad. If you have a really high resolution screen you can set it to 200% and it would look the same as when Mac OS pixel doubles older programs which aren't DPI-aware.

Here is a comparison between 100% and 125%. I think the 125% looks great. The only issue I notice is the Microsoft Word icon in the taskbar. But this is Office 2007, Office 2013 doesn't have this issue and I don't think 2010 does.

Edit: And here is a photo of Windows 8 at 125% on my laptop. Office 2013's icon looks fine. Only thing wrong with this screenshot is the Skype icon and the TPFanControl system tray icon. Skype really needs to fix that, but at least the program itself is DPI-aware.

This is up to the developer to fix. You don't need vector art which is computationally expensive.

It's not just the developer, as not even Microsoft designed elements work properly when you use anything but a few preset scaling options. As for computing power, that's minimal - most elements remain static for the majority of the time they're on screen.

Edit: And here is a photo of Windows 8 at 125% on my laptop. Office 2013's icon looks fine. Only thing wrong with this screenshot is the Skype icon and the TPFanControl system tray icon. Skype really needs to fix that, but at least the program itself is DPI-aware.

That's exactly what I'm talking about. All the icons are warped - Chrome, Skype and even Paint (a Microsoft app!). And that's with one of the preset scaling options. With vector art you would be able to freely scale the interface and it wouldn't look terrible.

It's not just the developer, as not even Microsoft designed elements work properly when you use anything but a few preset scaling options. As for computing power, that's minimal - most elements remain static for the majority of the time they're on screen.

That's exactly what I'm talking about. All the icons are warped - Chrome, Skype and even Paint (a Microsoft app!). And that's with one of the preset scaling options. With vector art you would be able to freely scale the interface and it wouldn't look terrible.

Hmm I didn't notice paint. I guess it is a little distorted. Even so, it's still up to the developers to fix this issue. You can't even get them to support 4 presets, you think they will suddenly support vector graphics? If they supported these 4 presets then it should look fine. When I get home I will try some custom scaling options on my 30" monitor and post photos. I think those icons look bad because they're being scaled UP. Scaling down works a LOT better.

Hmm I didn't notice paint. I guess it is a little distorted. Even so, it's still up to the developers to fix this issue. You can't even get them to support 4 presets, you think they will suddenly support vector graphics? If they supported these 4 presets then it should look fine.

The problem is that preset bitmaps don't have flexibility. What happens when the next resolution bump happens? Then developers will have to maintain 8 different presets. And what happens to all the resolutions that fall inbetween? Then you end up with UI elements that appear different sizes physically (as they appear on screen) or are badly scaled. The point is I can't scale the Windows interface to the size I feel is appropriate and the size I used to have on my previous display. It's far from the end of the world but it's something Microsoft simply hasn't addressed adequately.

This topic is now closed to further replies.
  • Posts

    • Russia was able to invade Crimea because of those people. But my point is that I've personally heard how great it was to be "back in Russia" right afterwards - look how great it is now. I've asked you a question in another comment which you haven't answered, so I'll ask it again: is it better now without "Europrats"?
    • ZimaBoard 2 1664 Starter Kit review: it's a cool and affordable DIY NAS by Steven Parker IceWhale Technology reached out to me asking if I was interested in testing the ZimaBoard 2, and after convincing them to send me the Starter Kit, it arrived at my doorstep in May. A bit of background: it is a Shanghai-based Chinese company founded in 2020, which specializes in single-board servers and personal cloud solutions. From searching around online, user feedback on the company and ZimaOS is mostly positive, so we're off to a good start. In addition, I should probably point out that although they do not have a large portfolio of NAS devices, with just four of what they do offer, they seem to have covered everything from a relatively low-priced entry point with the ZimaBoard 2, right up to the high end, with the ZimaCube 2 Creator Pack that even includes an NVIDIA RTX PRO 2000. Anyway, as already mentioned, what we have today is the ZimaBoard 2 Starter Kit, and here are the full specifications: ZimaBoard 2 Model 832, 1664 CPU Intel Core N150 (4x E Cores/Threads, Max burst up to 3.6 GHz) TDP: 6W (Base) 10W (Max) Graphics Intel UHD Graphics 24 EUs (1.00 GHz) Memory 8 GB, 16 GB DDR5 4800MT/s non ECC SODIMM (soldered) Disk Capacity 60 TB (30 TB x 2) Supported RAID Types TRAID, TRAID +, RAID0, RAID1, RAID5, RAID 6, RAID 10 Storage 2 x SATA 3.0 6Gb/s Ports with Power Bootloader 32 GB, 64 GB eMMC Network 2x RJ-45 2.5 GbE PCIe 1 x PCIe 3.0 (via LPC) USB Ports 2 x USB-A 3.1 (5 Gbps) Display Mini-DisplayPort 1.4 (4K@60Hz) Hardware Transcoding Engine H.264, H.265, MPEG-4, VC-1 Maximum resolution: 4K (4096 x 2160); Maximum FPS: 60 Virtualization Intel® AES New Instructions Intel® Virtualization Technology (VT-x) Intel® Virtualization Technology for Directed I/O (VT-d) Size (H/W/D) 140mm x 83mm x 31mm Weight 0.4 kg (only ZimaBoard 2 device) Power 12v 5A Power Supply Warranty 1 year (Global) 2 Years (EU) OS ZimaOS v1.6.1 MSRP $339, $399 ($548.60) As you can see above, there are two variants of the ZimaBoard 2. The lesser variant has half the eMMC storage and 8 GB less RAM, although it also costs $60 less than the top variant we are testing today. The above pricing is only for the ZimaBoard 2. I put the MSRP of the Starter Kit next to it in brackets, although as of publishing, it is discounted to $534.50. The ZimaBoard 2 started life on Kickstarter and shipped to backers in August last year. It became available via the official website in late 2025 and Q1 2026. This hobbyist NAS contains the still relatively new N150 Intel CPU released in the first quarter of 2025, with support for DisplayPort 1.4, HDMI 2.1, although in this case, the memory is integrated into the board itself, so it will not be possible to upgrade or expand the amount. It also supports AV1 decoding, as well as H.264, VP8, VP9, H.265 (8 bit), and H.265 (10 bit). The different capabilities in the Alder Lake-N (and Twin Lake) series are listed below. Processor E-cores L3-cache Turbo clock GPU GPU-clock TDP Intel N355 8 6 MB 3.9 GHz 32 EUs 1.35 GHz 9 W Intel Core 3 N350 3.9 GHz 1.35 GHz 7 W Intel Core i3-N305 3.8 GHz 1.25 GHz 9 W Intel Core i3-N300 3.8 GHz 1.25 GHz Intel N250 4 3.8 GHz 1.25 GHz 6 W Intel Processor N200 3.7 GHz 0.75 GHz Intel N150 3.6 GHz 24 EUs 1 GHz Intel N97 1.2 GHz 12 W Intel Processor N100 3.4 GHz 0.75 GHz 6 W The CPU is part of the Twin Lake series that sits near the bottom of the N-series, designed for low- powered systems and entry-level laptops, and as such has a base level TDP of just 6W. As I have noted before, we are seeing another NAS with a great amount of RAM. It's important to mention that the ZimaBoard 2's memory is integrated into the base board (which is why they have two variants of it). As a reminder, up until a couple of years ago, it was commonplace to only get 2 or 4GB max on a flagship Synology or QNAP home NAS. Ever since the likes of TerraMaster and more have entered the market with ample RAM sizes included in their NAS offerings, it has gone a long way in forcing the hands of the traditional makers to up their game a bit. First impressions The Starter Kit came in one outer box with several packages inside it (shown above). I forgot to take pics of it because when it arrived, it wasn't clear what was inside, and I had to confirm with my contact that I received the entire Starter Kit. In the box ZimaBoard 2 ZimaBoard 2 HDD Expansion Bracket + PCIe card frame Zimaboard Mini DisplayPort Male to HDMI Female Cable 4K 60Hz Zimaboard PCIe 3.0 x4 to Dual NVMe M.2 SSD Adapter Card Quick guide [full online guide] Limited warranty notice Screws Design Where to start? You'd be forgiven for mistaking it as an SSD enclosure if not for all the ports on it. It is completely made out of metal, and the top is an entire heatsink. It has a premium feel about it, but it definitely looks like a hobby device. As you will see, the completed build looks like it belongs in a server or meter closet rather than as a showpiece on someone's desk. On what I am calling the rear, there's a Mini DisplayPort (1.4), two 2.5 GbE ports, with Type A 3.1 USB ports, and then the barrel connector port. Around the front, there are two SATA6 ports with a power connector in the middle. Left side Right side One side is completely free of ports. On the other there's a slit that allows for the feed of a CPU fan cable, and a PCIe 3.0 X4 slot. Top Bottom The top is entirely made up of a heatsink except for the extended height for the I/O on the rear. Around the other side, you can find the ZIMA branding and some regulatory information stamped near the bottom. As you may see from the bottom of the ZimaBoard 2, it scratches quite easily from just moving it around on my Ikea island. Teardown Before we get started, let's have a look at this thing on the inside. The steps to get to the board are as follows: Remove the four smaller Torx screws on the bottom of the ZimaBoard 2; Remove the four larger Torx screws on the sides of the device; Carefully unstick the CMOS battery from the PCB; Remove two Phillips screws on the PCB; Lift out the PCB. Yes, as you can tell from the instructions, you need three different tools to remove Torx and Phillips screws (10 in total), and unhelpfully, one of the screws is located under the CMOS battery, which is stuck onto the PCB. Building Now comes the fun part. Because the ZimaSpace website does not provide any guidance on how to put the Starter Kit together. They only have guidance for connecting the CPU fan. However, they did upload a video to their YouTube channel that shows the entire process. To install the fan, first remove the four screws on the bottom of the ZimaBoard 2, then on the inside, there is a CPU FAN connector where you can attach the fan, reattach the ZimaBoard 2 frame, and feed the fan cable through the provided slit. Then remove the nearest screw on the side and attach the fan frame to the side of the device using the same screw. ZimaBard 2 screws Aligning the screws Bottom view Remember those four screws we removed to access the CPU FAN? Longer screws are provided in the box with the HDD Expansion Bracket, which is what you will now need to attach the ZimaBoard 2 to it. Helpfully, the orientation on how to attach it is made obvious when the frame can only be screwed on at the same overall length as the ZimaBoard 2. If you do it the wrong way around (which is what I did initially) one side hangs off the frame, and it becomes difficult to attach the PCIe Adapter Card cable. PCIe card frame Other side PCIe slot connector Next, it's time to attach the PCIe card frame, which is fastened with the help of 3.5-inch SATA HDD (3 screws). These are toolless screws that you can just use your fingers to fasten them with. Then it is time to connect the provided PCIe cable with the slot connector on one side of the ZimaBoard 2, feed it through the bottom of the HDD frame, and fasten it with two standoffs. Both bracket options 2280 standoffs with 2x 4TB MP44Q The PCIe 3.0 X4 card comes with a short bracket option, handy if you decide to place it inside a different NAS or rack server, but here we need the long bracket. Oddly enough, the M.2 standoffs were preinstalled into the 22110 position, but extra standoffs are included in the box, which I installed at the 2280 position for our use. I added a couple of MP44Q M.2 PCIe 4.0 SSDs (2 x 4TB) that can be availed on Amazon for $478.99 (the lowest price for 3 months) that TEAMGROUP supplied us with Then we have the almost completed build, you just need to push the card into the PCIe slot. Unfortunately, IceWhale Technologies did not provide a screw for the PCIe card frame (this is also apparent in their own video). Here it is at several different angles, with the last pic showing the SATA Y-Cable connected to the two WD Red Plus 4TB drives. Setup and Usage Next, you connect your cables to the I/O, and the ZimaBoard 2 powers on automatically, as there is no power button on the device. Power is controlled through the Settings in ZimaOS. BIOS The ZimaBoard 2 includes an Aptio BIOS from American Megatrends [1, 2, 3], and you can setup pretty much everything here including the boot order, which is locked to the UEFI OS, however above that choice you can enable or disable booting to a SATA/USB bootloader so this would still allow you to switch to an alternative bootloader and boot from it, or disable it to instead always start from the first disk with an OS installed on it. Initial Setup Upon connecting to the LAN and booting up, the ZimaBoard 2 can be reached by navigating to the IP address (shown if you have a monitor connected), or you can find it using the ZIMA Client desktop application, which is essentially a Zima device finder. Initializing the ZimaBoard 2 The ZimaOS setup process is pretty straightforward, through a wizard, and in full above, it basically consists of setting up an account and some handy tips, and that's that! Post Setup (ZimaOS update) Upon first boot, you are alerted that there is a ZimaOS update from 1.5.0 to 1.6.1, which I applied; the full process is shown above with the changelog. ZimaBoard 2 Storage Setup Next, it is time to set up the storage. ZimaOS actually throws everything onto the eMMC flash drive; it is also the default location of AppData, which is definitely something to be wary about, as the 45GB available storage could fill up quickly. HDDs I first attempted to create a Storage Pool using the two 4TB WD Red Plus NAS drives, and got an error message: After several attempts and then looking online, I discovered it was a bug with ZimaOS where the fix was simply to reboot ZimaOS and then try again, this time I was able to create a RAID mirror using the two drives. SSDs I did the same for the SSDs, as you will see in the above gallery, when I created the second Storage Pool, it only allowed me to select available drives. ZimaBoard 2 AppData ZimaOS comes with an App Store that includes a repository of almost 400 apps, so you will be able to find most of what you'll need for a NAS (although after a quick search, I wasn't able to find a Surveillance Manager), and now comes the important part: moving the default AppData location off the 45GB eMMC and onto a larger volume: Open Settings Then Apps Then, in the Select a new location field, click on the new Storage volume you want to move it to (in my case, the Apps Storage Pool), which is the SSD RAID mirror. Confirm the Migration warning Be praised! You can also do this for Docker (which by default installs onto the 45GB eMMC flash drive) and the User database. Plex Setup Next, I tested the configuration by installing the Plex Server app from the App Store. The library folders must already exist (which I placed into the Storage Pool). Plex Server setup is straightforward and requires very little configuration. In my case, all I had to do was add the media path I just created, which you can also browse to using the folder icon in the path field. In addition, you can now map the new Media library in Windows Explorer using the Zima Client. Oddly enough, it is not possible to access the ZimaBoard 2 over the Network Neighborhood; you must map drives using the client, which is shown in the last image in the above gallery. I watched one of my Blu-Ray rips, which is Dolby Vision with Dolby Atmos, and the content played fine with no stuttering or buffering, which is what anyone needs in this scenario. ZimaBoard 2 Zima Client mobile app There's also a client for mobile. It is pretty barebones, as shown in the above gallery, for example, the Apps screen launches the WebUI for that app, and the Backup must be done manually. On opening Backup, you can select internal storage folders on your phone to backup to the ZimaBoard 2's storage, and although this is constantly scanned, the backup action itself must be manually triggered. There is an option to allow foreground backup (last image in the above gallery), but this basically means the queued backup gets triggered when you manually open the app. Benchmarking SATA PCIe 3.0 X4 A CrystalDiskMark test on a mapped network drive from within a Windows 11 25H2 PC (image above) connected over a 2.5 GbE was well within acceptable ranges. Writes were generally better on the SSD RAID mirror. SATA PCIe 3.0 X1 I also ran the NAS Performance tester, which tests the link speed performance. As you can see, it pretty much maxes out the 2.5GbE connection. Of course, you can also opt to bond the two 2.5 GbE connections for a bit more umph, but I didn't do that. Thermals Top PCIe card SATA HDDs Next, I measured some hotspots while playing content on Plex. It's fair to say this will perform better than a NAS that is enclosed in a metal or plastic case, as almost everything storage-wise is exposed! Anyway, the ZimaBoard 2 did not break a sweat with Plex streaming or disk benchmarks. ZimaOS Factory Reset ZimaOS does not include a factory reset option. Instead, you have to download the ZimaOS image and flash it to the eMMC manually. The flashing process is shown in the above gallery. The steps to do so are listed below: Download the ZimaOS image here; Open BalenaEtcher (Run as Administrator) and select the image; Select your inserted USB drive (min 8 GB) Flash to it; Connect your USB drive, monitor, keyboard, USB hub (optional), mouse (optional), and network cable (recommended) to the ZimaBoard 2; Connect power and press F11 continuously; Select your USB drive starting with UEFI in the boot device menu; Press Enter on the Install ZimaOS option; Select /dev/mmcblk0 (MMC) flash drive as target; Confirm with (three times) to wipe the target disk; Wait a couple of minutes while ZimaOS installs; Remove the USB drive and confirm with a reboot; Your ZimaBoard 2 has been factory reset. However, you don't have to stick with ZimaOS, in fact the company also offers official CasaOS images, that are based on Debian; or as they say themselves, put anything you want on this "hackable single board server" it's up to you. Conclusion I had a lot of fun putting this together. I've custom-built all my own PCs and servers since the 90s, and this is the first time I have had to put a NAS together. Even if the actual base ZimaBoard 2 was already a completed build, it still feels pretty custom. I just wish that IceWhale Technology included a getting-started guide in the box for the Start Kit, which would have really completed this kit. Instead, I had to search for the official video on the YouTube channel to make sure I wasn't doing anything wrong. So who is this for? Definitely the hobbyist who is comfortable building their own PC and servers. It also has a much smaller footprint than its nearest equivalent (in terms of specs), like the Beelink Me Pro, which is another NAS I will be testing soon. Although the Beelink does not come with the PCIe 3.0 X4 expansion, the ZimaBoard 2 Starter Kit suddenly looks to be a great bargain, even if it only offers the two 3.5-inch bays over the four in the other example. It makes a lot of sense to use Intel's N150 chip inside a NAS; it is more than capable of doing what the ZimaBoard 2 is intended for, media streaming and backup. It also looks like the IceWhale Technology staff are quite active in the official forums helping people with issues they come across with ZimaOS and the devices, peer support seems to be good as well, I was quickly able to find why I was not able to create a new Storage Pool in ZimaOS v1.6.1 even though that is quite a serious bug, hopefully it will be fixed in the next update. If you are comfortable with the command line and Docker, you'll be fine. You can do great things with this hardware. This was my first time with ZimaOS. It seems a bit barebones in comparison to the likes of Synology DSM, TOS, and UGOS, but it has a ton of apps to get you started with your home or small business NAS. Where to buy As of publishing, IceWhale Technology is running a discount of up to 5% for the Starter Kit. If you opt to get just the ZimaBoard 2 itself, it does come with a SATA Y-Cable, so you will be able to connect up to two 3.5-inch HDDs to it. ZimaBoard 2 1668 Starter Kit for $534.50 on Amazon US (was $548.60) ZimaBoard 2 832 Starter Kit for $372.88 on Amazon US (was $390.60) Zimaboard 2 1668 (16GB+64GB) for $419.90 on Amazon US Zimaboard 2 832 (8GB+32GB) for $359.90 on Amazon Disclosure: IceWhale Technology provided a free sample without any editorial input or review pre-approval. Good to know The Amazon link is U.S. specific, and not available in other regions unless specified. We only use first-party seller links (at the time of article publishing); ensure that you purchase from a first-party seller link only. Check out Today's Deals on Amazon | or our recent tech deals. Become a Prime member (for Students or SNAP) via Neowin Get Prime Access - Prime for half price (for qualifying Medicaid, EBT, SNAP) Subscribe to Prime Video, Audible Plus, Music Unlimited or Kindle Unlimited via Neowin As an Amazon Associate, when you purchase through links on our site, we earn from qualifying purchases.
    • It's in the Insider's group so yes it's technically beta, though these days it's hard to see much of a difference unless you opt for the most extreme beta builds, which I don't. When I moved here from the Release Preview channel I did so primarily because I wanted to see how well the restored taskbar functionality (restored from Win10, and earlier) is working and whether it was time to finally abandon SAB--and it is--working fine, so far. Not as polished as SAB, but it'll do for me.
    • I've been using MWB Premium for a number of years so that along with Windows updates and updated browser should be fine. Thanks for that.
  • Recent Achievements

    • Week One Done
      flexorcist earned a badge
      Week One Done
    • One Month Later
      Woland13 earned a badge
      One Month Later
    • Week One Done
      Woland13 earned a badge
      Week One Done
    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      488
    2. 2
      +Edouard
      222
    3. 3
      PsYcHoKiLLa
      147
    4. 4
      Steven P.
      74
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!