Recommended Posts

On top of new hardware, today's Samsung event will apparently see the launch of an exclusive Flipboard app, which marks the first time the visual reading app has appeared on Android. Unfortunately for everyone using a current Android device, Flipboard for Android will be exclusive for a time to the Galaxy S III, according to Slashgear. Their early hands-on with the device shows that it's much like the iOS version, with the added ability to browse your news via a large homescreen widget.

Flipboard also just launched a teaser page saying the app "will be available on select Android mobile phones" in the coming months.

http://www.theverge....-iii/in/2760821

So I guess they saw how Instagram exploded on Android and have finally realized that Android is the platform to be on. Rush rush to Android Flipboard guys, that's where the gold is :D

So I guess they saw how Instagram exploded on Android and have finally realized that Android is the platform to be on. Rush rush to Android Flipboard guys, that's where the gold is :D

I think you will find more and more apps becoming available for Android. Considering the Android OS has the majority of the market, devs would be fools not to put forth a little extra effort (if they are having that many problems) and write more for Android.

http://www.theverge....-iii/in/2760821

So I guess they saw how Instagram exploded on Android and have finally realized that Android is the platform to be on. Rush rush to Android Flipboard guys, that's where the gold is :D

Or because it was insanely popular on iOS it's bound to do well on other platforms from free advertising...

Or because it was insanely popular on iOS it's bound to do well on other platforms from free advertising...

Nah.. gaining 30 million users in a month is hardly because of advertising. It definitely helped because new Android found out about it's availability, but the fact is that they were at a specific number on iOS and weren't moving this rapidly. It only happened when they came out on Android. It's more of the fact that sheer number of Android users wanted it and bam, this is what happens. It's a case study on why Android is far better platform for developers and popularity of startups.

I mean seriously, they more than doubled their users in a month that it took them 18 months previously. There is no advertising and good press that can shift these numbers this much.

Nah.. gaining 30 million users in a month is hardly because of advertising. It definitely helped because new Android found out about it's availability, but the fact is that they were at a specific number on iOS and weren't moving this rapidly. It only happened when they came out on Android. It's more of the fact that sheer number of Android users wanted it and bam, this is what happens. It's a case study on why Android is far better platform for developers and popularity of startups.

I mean seriously, they more than doubled their users in a month that it took them 18 months previously. There is no advertising and good press that can shift these numbers this much.

/face palm

First off, that reasoning of yours was argued and proven many times opposite in another " coming to android" thread you created.

Also FlipBoard has been requested to be Android since FlipBoard came out, if your reasoning was correct, it wouldn't be an exclusive for the Gal SIII, and it wouldn't be for " select Android ". It would have been out concurrently with the other versions.

And above all it is from advertising that it has it's popularity, the advertising of " word of mouth ". The many and many of people since FlipBoard came out it has been requested ( it's just about on every App to Get list, as well as Android App Request list ), it is just now coming out, as an exclusive. Which to me at least, says that they didn't care enough until somebody wrote a fat check.

As far as moving this rapidly,, you do realize that when one of the most requested apps on mobile's comes to another platform, it's expected it's not going to be slow. Because many people have been waiting for it from the start, as well as the Word Of Mouth Advertising and recommendations from Websites reviews. So yes it's userbase is going to jump rapidly, but from the apps quality, not androids, as it could go to PC/OSX and it would still jump higher then when it first came out for iOS

Why the hell are you lot arguing about why it's going to Android. Who the hell cares!!! It's a friggin app that's popular, why would ANY developer need a reason other than "They have lots of users". Seriously, this is probably the most pointless, nerdy and friggin stupid argument of read on Neowin.

Exclusive to the Galaxy SIII? WTF? Android really doesn't need forced fragmentation due to business deals like this on top of the fragmentation issues that already exist :(

I am sure this is on a temp/promotional thing going on here. It will come to all of Android probably soon after.

http://www.theverge....-iii/in/2760821

So I guess they saw how Instagram exploded on Android and have finally realized that Android is the platform to be on. Rush rush to Android Flipboard guys, that's where the gold is :D

Available on select android handsets.... What was that thing android wasn't again...

I think it will be a subset of android phones that get flipboard not all Android phones.

Hopefully all of them get it, I think a majority of it is server side anyway ( page layout and feed retrieval )

FlipBoard is an Awsome app, the more that can use it the more official feeds it will get ( like Engadget and couple others )

Kinda doubt that. They will lose out on a lot of money if they limit the phones. No reason to limit it really.

They could be doing how they did it when it first came out, was invite only, had to sign up on a list so they could upgrade their back end as they went, not mad house all at once.

They could be doing the Gal first, upgrading capacity as needed, then same with other phones, then with the rest.

That's not what select handsets mean.

Don't know if that's a reply to me or somebody else.

If me, it could be like it was originally, select limited release so they could upgrade backed as needed

Available on select android handsets.... What was that thing android wasn't again...

Maybe if you understood what's happening in the development process you would realize why they are doing it this way.

Flipboard is a very specific type of app that tied their UI to the single resolution with the animations and layout. It is a bit harder to target the same type of UI on various devices and different resolutions due to the way they designed it, not because Android is fragmented.

The bottom line is how you designed the app. The reason they are launching with Galaxy S3 is publicity but I can guarantee you that the same app will work on Galaxy Nexus due to the screen resolution. They are most likely trying to port their existing UI and it's not as flexible to work with different resolution and scale properly.

They wouldn't have had this problem if they designed the app from the ground up for Android first.

When you design for Android, and follow the guidelines and not work with absolute layouts in your UI the app will work on all devices just fine. That's why Android deals with views and units in DPs (density independent pixels) and SPs instead of standard pixels and has attributes on objects like weight and deals with linear, relative and other types of layouts.

Maybe if you understood what's happening in the development process you would realize why they are doing it this way.

Flipboard is a very specific type of app that tied their UI to the single resolution with the animations and layout. It is a bit harder to target the same type of UI on various devices and different resolutions due to the way they designed it, not because Android is fragmented.

.

You just said, they do it because fragmentation makes it harder to develop the app, but android isn't fragmented. you have to decide.

Umm, yes they would.

Based on what? I am building Android apps. I never had a problem with any of the apps to run on various Android devices. The only limitation is where you target a minimum SDK which today is really Android 2.x. And there are things like Android Compability Libraries that work ICS 4.0 APIs (http://developer.and...ty-library.html) that allows you to use ICS features and code that works fine on older versions of Android too (it even goes down to Android 1.6).

Tell me specifically why they would have problems? Give me examples. Because from my perspective as a developer I don't really see it.

EDIT: Now, there are specific APIs you can use for TouchWiz (Samsung Android devices) or MotoBlur (for Motorola devices) or HTC Sense (HTC android devices) but those are specific manufacturers based APIs that are meant to tap into their specific UI abilities of their Android modifications. But even that's not a problem. You can choose to use it or not and you can check whether or not an Android device is supporting any of those APIs before you use them.

That was RIM BS that was being tossed out. RIM called android a cesspool concerning piracy.

That is not accurate at all. Many developers have spoken out about the insanely high piracy rates on Android and some of those have said they are no longer willing to develop apps for the platform as a result. This article in Wired posted just one day ago shows a developer that had a 90% piracy rate of their brand new football manager game on Android. http://www.wired.com/gamelife/2012/05/wired-uk-android-game-piracy/

various devices and different resolutions due to the way they designed it, not because Android is fragmented.

That's what people mean by fragmented.

And you say it's not, yet Epic and a host of AAA Developers say it is. You keep saying your a developer, what have you developed? Have you just downloaded the SDK, or actually published something

As far as FlipBoard, I would have to say its just a staggerd launch, why they are spitting up the devices like they are. Because I think the majority of stuff is server side the actual app has to do verry little. If they did all devices at once, I feel the increase in load would put their servers down, from day 1 they didn't like that thought.

What they are doing now is the same as when they brought out the app for IOS, except with iOS they couldn't hold off devices and had to do invites, as for iOS they were all the same, where with android they can limit it based on device instead of signups

*edit - and FlipBoard doesn't use Absolute layouts, the layout is dynamic based on the content it's pushing. Even changing each time it's opened. So it can't be how you think it is working.

Based on what? I am building Android apps. I never had a problem with any of the apps to run on various Android devices. The only limitation is where you target a minimum SDK which today is really Android 2.x. And there are things like Android Compability Libraries that work ICS 4.0 APIs (http://developer.and...ty-library.html) that allows you to use ICS features and code that works fine on older versions of Android too (it even goes down to Android 1.6).

Tell me specifically why they would have problems? Give me examples. Because from my perspective as a developer I don't really see it.

EDIT: Now, there are specific APIs you can use for TouchWiz (Samsung Android devices) or MotoBlur (for Motorola devices) or HTC Sense (HTC android devices) but those are specific manufacturers based APIs that are meant to tap into their specific UI abilities of their Android modifications. But even that's not a problem. You can choose to use it or not and you can check whether or not an Android device is supporting any of those APIs before you use them.

Density independent pixels and scalable graphics and all that are great, if you don't care about your app looking like **** and conforming to different size devices.

For a good app it needs to be specifically designed for the device, for high res devices you need the proper size images for the proper size "buttons", then some of those devices with the same res can be up to 2 inches different in size, so one of them would have fewer and bigger but higher density thumbs which needs to be coded, but can to some degree be done with intelligent scaling algorithms.

Tis same problem recurs with every different resolution and screen size. Resolutions reasonably close can be fit into the same GUI, just be using flow and filling in white space and padding. But you gave to take physical screen size into account separately. A 3.5 inch device and a 4.5 inch device with the same res can't use the same layout, either one would have to big buttons or the other to small, or one would have to much padding while the other the icons would be on top of each other, one would have shap graphics, the other blurry.

Vectors would fix some of these problems, but they wouldn't work for flipboard and it's graphics anyway. And would just fix the blurriest, not the size and screen size and layout issues.

This topic is now closed to further replies.
  • Posts

    • 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!