Recommended Posts

Wasn't Vista close enough to one? I mean I know it wasn't entirely, but you still had a new audio engine, new network engine, new security features, new graphics engine...you get the idea.

I wouldn't mind a new non-compatible OS project as long as I could guarantee the old OS couldn't read the new filesystem and therefore mess with it, but for MS that would be a hard thing to convince people to get unless it was cheap and had some really convincing reasons to snag it.

And likewise really hard to spend the money and time developing, especially when it'd be competing even more directly with alternative OSes, which are getting fairly well fleshed out at the moment. On that note it'd be competing with Windows itself, which would be just as painful for MS.

Windows 7 is really just going to be Vista Second Edition......

QFT

"You've let us know you don't want to face the kinds of incompatibility challenges with the next version of Windows you might have experienced early with Windows Vista. As a result, our approach with Windows 7 is to build off the same core architecture as Windows Vista so the investments you and our partners have made in Windows Vista will continue to pay off with Windows 7. Our goal is to ensure the migration process from Windows Vista to Windows 7 is straightforward," Veghte stated.

Source

QFT

Source

That doesn't mean anything!

Just because a new car's engine is kinda similar to the old cars engine .. does that mean the new car is a copy-paste of the old one?

No... because cars arent just engines ... they also have body shells, suspension, brakes, handling, chasis, interior design .. even the leather trim may differ...

Just because the kernel won't be rewritten, that doesn't mean Windows 7 will be Vista SP1. Just because they will be more compatible and use same guidelines .. doesn't mean they will be the same.

Microsoft started with a lot of new guidelines and principles with Windows Vista (on many fronts .. UI, networking, security...). By doing this they broke their own development cycle and released the os "3 years too late". They got a lot of critic on this but now it will pay off as they now have a new foundation to build on with the new principles with Windows Vista.

Also .. we know nearly nothing about Windows 7... Windows 7 information isn't public yet and people who do know what they are talking about can't just yet.

So till PDC you can speculate all you want but talking about 7 before ANY public information is out is just plain stupid and speculation.

Conclusion ... saying Windows 7 is Vista SP2 is just stupid as you (or anyone else in the public) know NOTHING about Windows 7 itself...

That was a CPU architecture change -- Not an OS architecture change. OSX is still fundamentally the same, just compiled for a different OS.

What you seem to want is a switch like Apple did from OS9 to OSX....but that's just silly. Apple had to do it. OS9 was a mess compared to more modern operating systems like Linux/Windows NT. It had no protected memory, multitasking, security concepts, etc.

There's no reason for Microsoft to make that kind of switch. Microsoft upgraded or flat out replaced many of the systems with Vista (Networking, security, audio, video, media, and so on) and look at how much people complained about that.

This.

There isn't a reason for MS to re-write Windows from scratch, Vista had a few components overhauled (including proper security elevation for users) and people whined and bitched about it constantly.

Re-writing Windows from scratch would break backwards compatibility, and love it or hate it, it's the reason Windows is so popular.

I expect the virtualization stuff getting so popular will offer MS interesting ways to mess around with compatibility problems though.

Virtualization isn't anywhere near the point as to be accessible to the casual user.

Try building a softgrid package. It's neither easy nor straightforward.

Try explaining installing why she should or how to install a guest OS in a virual machine. She'll look at you like you're crazy and wonder why she needs another windows to run her programs.

It doesn't have to be accessible to the enduser at all if it's part of the OS. Vista already does some virtualization.

You certainly don't have to make a guest OS of Vista within Vista for it to use its virtualization.

So I'm guessing you didn't quite catch my drift.

That doesn't mean anything!

Just because a new car's engine is kinda similar to the old cars engine .. does that mean the new car is a copy-paste of the old one?

No... because cars arent just engines ... they also have body shells, suspension, brakes, handling, chasis, interior design .. even the leather trim may differ...

Just because the kernel won't be rewritten, that doesn't mean Windows 7 will be Vista SP1. Just because they will be more compatible and use same guidelines .. doesn't mean they will be the same.

Microsoft started with a lot of new guidelines and principles with Windows Vista (on many fronts .. UI, networking, security...). By doing this they broke their own development cycle and released the os "3 years too late". They got a lot of critic on this but now it will pay off as they now have a new foundation to build on with the new principles with Windows Vista.

Also .. we know nearly nothing about Windows 7... Windows 7 information isn't public yet and people who do know what they are talking about can't just yet.

So till PDC you can speculate all you want but talking about 7 before ANY public information is out is just plain stupid and speculation.

Conclusion ... saying Windows 7 is Vista SP2 is just stupid as you (or anyone else in the public) know NOTHING about Windows 7 itself...

My god you just do not read. Nobody said its going to be SP2. The reference made is that its basically going to be like Win98 was to Win95. No major fundamental differences, because it is built on the same core. Your not going to see a Win98 to XP style jump, is the point that is being made.

but hey.... didn't Apple do it? Isn't Mac OS X coded from scratch on FreeBSD as opposed to MacOS 9 or older being just RISC-type stuff? well I guess yea it is trouble; they had it standard to dual-boot between OS X and OS 9 until developers had time to make new Aqua-themed OS X-compatible apps..... imagine that happening on a Windows scale where it's the most used OS on Earth..... yea..... chaos...... meh......... i STILL think Windows from scratch would be a golden opportunity to make things right.... hmm... or maybe escape through the "window" into the "sky" and release a new OS called Microsoft Skies alongside Windows..... ok i'm rambling now so cya later lol but wait then you can't have application windows; you would have fluffy cloudy application skies; ok omg ok bye! lol

Do you actually realise how monolithic the windows platform is? Completely rewrite the OS from scratch? You're kidding me right?

Windows is compatible with thousands of devices, do you realise how long it would take to achieve the same level of compatibility with a rewrite? What about software? One of the reasons Microsoft took so long with Vista is because they need to maintain the greatest percentage of backwards compatibility. Could you really imaging them brining out a complete rewrite, and half the worlds devices just didn't work, and even more software failed too.

And you can't compare Apple's OSX. Apple have been working on basically the same finely tuned hardware platform for years. A handful of specifically chosen devices work with it, so development time for ensuring compatibility is drastically cut down.

As far as I can tell three pain areas are partitioning tools (Vista really hates some,) RAID drivers (likewise,) and older development tools (which can be expensive to replace.)

For the first six-nine months I could understand that XP was just all around easier to get along with, while the drivers and app compatibility stabilized. Now, though, I can't imagine ever using XP again.

It doesn't have to be accessible to the enduser at all if it's part of the OS. Vista already does some virtualization.

You certainly don't have to make a guest OS of Vista within Vista for it to use its virtualization.

So I'm guessing you didn't quite catch my drift.

Oh I caught it, you just have no idea what you're talking about. The only "virtualization" in Vista is a bit of write re-direction so applications don't **** the bed when they suddenly can't write to certain parts of the FS/registry, what you want is a whole different beast entirely

It's pretty obvious you've never really used a virtualization solution. We had several deployed in my last workplace. Virtual PC/Virtual Server is pretty much what you see, but try explaining why your grandma needs to boot up ANOTHER OS to write an email or do some trivial task ala the classic enviornment in OSX. Don't forget to mention that she needs to shell out for another OS license, btw. I'm sure she'll be thrilled aobut that.

SoftGrid... well, heck, softgrid needs a virtual machine itself (or at the very least a spare real machine) to do the capturing, then you have to repackage and deploy the software. Oh whats that? You needed to install something to the context menu or interact with just about any other component on your system? Tough ****, ain't happening.

I don't know anything about Kidaro but I'm sure it's not that much simpler. My point is this is all way too advanced for your average user. They simply won't do it just to write a document or balance their checkbook. Buying a mac or even installing Linux is much less hassle.

It would be a massive undertaking to overcome these problems. It's easy to say they should, its a whole nother thing to actually go and do it. And to what benefit? So you can toss Win32 out of the system? You can already do that; Win32 is just a subsystem that runs on top of the NT kernel, which has been proven by pretty much anyone who knows anything about OS kernels to be fast, reliable, and extremely well designed. And if the whole point of virtualization is to keep compatibility with Win32 apps, well, why the hell don't you just leave the subsystem in there until you don't need it anymore and not take the performance and complexity hit virtualization incurs?

And while you're throwing away compatibility for virtualization, don't forget that you'll need an entirely new set of drivers. Don't worry, its no big deal. It's not like anyone had any problems with drivers when Vista was released.

People are claiming the Vista is bloated and blaming all this "compatiblity code" for taking up all the resources in their systems. Guess what? There's about 4 MB of compat code on your hard disk, and none of it is loaded until its needed. And outside of one check call, it doesn't have anything to do with kernel. What's taking up all the resources in Vista (mainly sucking up your RAM) is the new features in Vista: desktop search, SuperFetch and even the DWM. Turn off those features and you wind up with something like... oh I don't know, Windows Server 2008 which has received pretty much nothing but praise.

Edited by y_notm

Just give Vista time and then it will be loved as much as XP.

In time drivers will catch up as companies revisit and rewrite them.

I mean anyone else remember when Win2k came out or NT3.5 came out. It took a while for drivers to really be written for them that worked and were stable 100% of the time.

And what happened to blackcomb --- As the vision changed so did the code name-- I mean don't we all wish we had a dime for all the code names that never was... Anyone else remember Neptune?

http://www.winsupersite.com/showcase/ac_preview.asp

also here is the wiki on it

http://en.wikipedia.org/wiki/Windows_Neptune

I fail to see what's wrong with just expanding the implementation of the compatibility shims that XP and Vista already use (The Application Compatibility tab).

It seems like a much more elegant and lightweight solution than virtualizing a whole OS.

Edited by MioTheGreat

Now this is a topic that could help make the push to 8,000,000. Posts .

I do agree Windows 7 is not the vision blackcomb was.

In fact I think isn't it this Ski resort...

http://en.wikipedia.org/wiki/Whistler-Blackcomb

Just a thought what if it was not a Windows version plan but instead a location for the next business meeting to discuss the next Windows. (The Whistler which became XP). And someone only heard what they wanted to hear.

That is just my thought.

My god you just do not read. Nobody said its going to be SP2. The reference made is that its basically going to be like Win98 was to Win95. No major fundamental differences, because it is built on the same core. Your not going to see a Win98 to XP style jump, is the point that is being made.

Windows 95 (without IE4) to Windows 98 was actually a pretty considerable leap. You might be surprised how much was missing if you go back to 95. No quick launch, no drag-and-drop in the start menu, and the entire Explorer was very basic with far less extensibility.

I remember installing the Desktop Update with IE4.0 for Win95 and NT4.0 which gave it some if not all of what Win98 had... It also had preview in the side.

But yes it was a big leap... Though the question is have you ever installed Windows 95 using the old Windows 3.1 desktop. Instead of the Start menu-?

What Windows 98 had that Windows 95 did not have was better support for higher memory and drive sizes as well as Fat32 support.

I remember installing the Desktop Update with IE4.0 for Win95 and NT4.0 which gave it some if not all of what Win98 had... It also had preview in the side.

But yes it was a big leap... Though the question is have you ever installed Windows 95 using the old Windows 3.1 desktop. Instead of the Start menu-?

What Windows 98 had that Windows 95 did not have was better support for higher memory and drive sizes as well as Fat32 support.

Yeah but all the stuff that came with IE4 was basically the Windows 98 shell.

so i just caught up on what was said on this thread i started

Singularity: it's not something like a desktop O/S; it's just a small lil thingy for hardware and software geeks to go "Neee!!!" over lol :blink:

Neptune: yes; it's based on the old age Microsoft Encarta UI and navigation and it was soooooo cool! Just like the Longhorn concept video is cool today, Neptune was just as cool back in those days.... But of course they didn't go through with it; maybe they didn't want the whole OS to look like one big website hehe.

many posts are regarding the question WHY recode it from scratch? i could think of MANY reasons.... like i'm tired of how some developers release software that sticks its stupid driver(s) right at the very native boot opportunity and risk preventing Windows from starting, or just slow down the boot! A re-coded Windows with an appropriate loading time for such drivers would have a boot time of like three seconds!!! When Windows starts, the ONLY drivers that should be loaded are functional (i.e. filesystem, CPU, power management), and user experience (i.e. peripherals, audio, video) -- NOTHING ELSE! Why the f**k does Alcohol 120% want its stupid SPI CD-ROM driver thing to load during the Windows boot logo screen at the very beginning?!? They're just too lazy to make their stuff work by loading it later on when Windows starts that's why, and it's Microsoft that allows developers access to shove drivers there. Have any of you ever noticed that booting up after a clean Vista or XP install is only like 2 or 3 runs of the loading meter? And then after you install let's say the nVidia ForceWare drivers and you reboot, it is eternally gonna take about 6 or 7 runs of the loading meter! How annoying!

that's just ONE reason.

Anyway; I'm saying that re-coding from scratch is an excellent opportunity to do things right with no BS. Knowledge of how to make software work with today's hardware technology is exponentially more advanced, and it's limited by the current platform. For example I don't know about everyone else but the new "low-latency" Vista audio stack is laggy/choppy! I've gone through like 5 motherboards and 3 sound cards and like 6 installations of Vista ever since it was released, and no matter what, the problem persists! It's totally gone if you have a really suped up computer though, but even now with my X-Fi Fatal1ty Pro sound card, 2 gigs DDR2 RAM, etc. etc. and Windows Experience Index of 5.9, in Windows Media Player when I enable the crossfader, it's choppy doing the fading between songs!!!! Like COME ON!!! That's what happens when you remove the functionality of the audio stack from the kernel itself like it always has been. The whole architecture is just totally messed up. They NEED a fresh start!

Some posts express worry about compatibility with hardware devices and stuff. I'm sure that the thousands of beta testers would squish most all of such bugs. There could be a separate dev. team for the coded-from-scratch Windows and have it developed for like eight (8) years while regular Windows is being released on the side.

Yeah but all the stuff that came with IE4 was basically the Windows 98 shell.

For all the customization forums we have at neowin, you would be surprised by the flexibility of the IE4 shell update. Awergh's NT4 Visual Update packages are good example of it. You can get an XP/Vista'ish desktop out of a 95/NT4 interface.

http://www.msfn.org/board/NT4-Visual-Updat...html&st=100

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • 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!