Recommended Posts

After quite a lengthy experimentation process I have discovered what the "Tweak Gurus & PC Geeks" don't tell you in their posts on the subject of cleaning the Prefetch folder.

This guide has not been plagiarized. It is totally compiled by me and was once posted by me at the SoftZone Forums.I decided that I did not wan't to be a member of that comunity because they have more rules than posts so I removed this post and others I had made and canceled my membership.So if you have seen it before that is where it came from.

I hope it can be of assistance to some of you that have cleaned your Prefetch folder because you have been told it will speed XP up. But now "like I did" you find that after you have cleaned the prefetch folder your PC now suffers from slow boot up's and general lack of performance. Here is the real deal about the Prefetch Folder

DO NOT REMOVE OR DELETE THE ->(layout.ini)<- FILE WHICH RESIDES IN XP'S PREFETCH FOLDER OR YOU WILL SLOW DOWN YOUR PC AT START UP AND WHEN YOU OPEN WINDOWS PROGRAMS. Once it is gone it can stay gone on some PC'S (like mine) for ever and your Prefetch Folder will never work again no matter what you do in the registry to try to rectify the problem.

If this has happened to your prefetch folder DON'T WORRY because I will now show you in 5 easy steps how you can rebuild the -> (layout.ini) <- file again.

1): make sure that the task scheduler is enabled.If you are un sure go to-> Start/Contrl Panel/Administrative Tools/ Click on Services/ Then in the list of services make sure the Task Sheduler is enabled & restart the service by clicking on Start. Close the Services Folder & go back to desktop.

2): Then go to START/RUN/ and TYPE IN/->cmd<-(without the arrows) CLICK OK. This will bring up the DOS Command screen.

3):You will need to copy and paste this entry in at the flashing cursor

-> rundll32.exe advapi32.dll,ProcessIdleTasks <-(without the arrows) and press ENTER.

4):Now reboot three times and your Prefetch folder will be rebuilt.(It takes 3 reboots for the prefetch folder to work out what it needs)

5):Then go BACK to ->Start/Contrl Panel/Administrative Tools/ / Services/ Once again find TASK SHEDULER in the list and stop the service and then set it to disabled.This will stop any more entries going into your Prefetch folder.

If you need to leave your task sheduler enabled,(No Drama) you will just have to clean out your Prefetch folder manually from time to time.Just remember not to remove the layout.ini file

You should only clean out files ?other than Windows Start up files? in the Prefetch folder.

If you clean out the standard Windows entries you will CRIPPLE & SLOW DOWN the Windows XP Quick starts and also slow down opening windows processes.

No one bothers to tell you the consequence of deleting the (layout.ini file) in all the tips I have seen about cleaning out the Prefetch folder.

Also if you use one of the many programs that are availabe to clean the prefetch folder you will find that they delete the layout.ini file also.

I have now tried about 50 of these so called Prefetch clean programs and they all disable the Prefetch folder completely and for ever which is a crazy thing to do.The Prefetch is one of the best things about XP.

The truth is that only people who don't know what the Prefetch folder is actually for and don't know how it works say that it is useless.

All I can say is that there must be a lot of people with a verry sluggish XP Windows PC's around,,especially at Boot up.

Edited by adamzapple
Link to comment
https://www.neowin.net/forum/topic/331072-repair-xp-prefetch-folder/
Share on other sites

HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Session Manager \ Memory Management \ PrefetchParameters

dword value = EnablePrefetcher

0 = Disable,

1 = App launch prefetch

2 = Boot Prefetch

3 = Both (recommended)

Task Scheduler is needed for Prefetch to work.

Not sure what the rest is needed for...unless I've just never bumped into that particular problem.

I personally do purge my Prefetch folder every so often, including the Layout.ini file.

If you open the Layout.ini file and scroll through it, chances are you're going to see a lot of things that are long gone on your system, including file and folder paths. The Layout.ini file is pointing to those things upon boot.

Ever disable a Service and have DCOM errors spring up all over the place in the Event Viewer? Sometimes, (not always), the errors are coming from the Layout.ini file pointing to that disabled Service.

The Layout.ini file will usually rebuild itself after a couple of reboots and in about 20 minutes of idle time. (Pre SP2, the Layout.ini file would rebilut itself in exactly 13 minutes...a little Pre SP2 trivia...lol )

Thats not 100% correct Iron200,, delete everything in your prefetch folder including the layout.ini file and see what happens. It will not always come back as you say.Once the layout ini file is deleted it has to be rebuilt manually using the comand prompt in DOS.

Bold fortune that Registry tweak you have posted only works when you have still got a working Prefetch folder.If you delete the Layout.ini file and clean out the Prefetch folder that tweak does nothing and it won't just magically rebuild itself once the Prefetch folder has been stripped bare.

Yes you are correct on the fact that you must have the Task Shedular enabled to use bootvis.

Whenever I've gone to clear out the Prefetch folder, I've done a "Ctrl+A", "Shift+Del". Unless the prefetcher is disabled or the Scheduled Tasks service is disabled, the files have always come back on all the computers I'd done this on (several times...).

The Prefetch folder will rebuild itself when it is empty. If it isn't working, then you've got a bigger problem than what's been outlined here. How do you think that the system keeps track of files that it should prefetch? It keeps adding to the list (but not removing...) with the new programs that are run.

If it isn't working, then you've got a bigger problem than what's been outlined here

That is what I have just shown you how to do: REPAIR IT WHEN IT'S NOT WORKING.I wish you people would read the original post.

All I said was if you clean out your prefetch folder not to clean out your Standard Windows Startup files and to leave the layout.ini file in the folder.Do not delete these files or you will slow down your PC especially when windows XP boots up.

If you do delete these files and you find Like I did and hundreds of other XP users that your PC runs slow because the Prefetch folder now doesn't work and that it stays empty no matter how much Registery tweaking you do.I have shown you how to rebuild the layout.ini file and the process involved in repairing the Prefetch folderit so it will work properlyagain OK.Nothing more.

To all the other users that have a PC with an automatic prefetch repair,,Good luck to you and I wish I had one too.

That is what I have just shown you how to do: REPAIR IT WHEN IT'S NOT WORKING.I wish you people would read the original post.

All I said was if you clean out your prefetch folder not to clean out your Standard Windows Startup files and to leave the layout.ini file in the folder.Do not delete these files or you will slow down your PC especially when windows XP  boots up.

If you do delete these files and you find Like I did and hundreds of other XP users  that your PC runs slow because the Prefetch folder now doesn't work and that it stays empty no matter how much Registery tweaking you do.I have shown you how to rebuild the layout.ini file and the process involved in repairing the Prefetch folderit so it will work properlyagain OK.Nothing more.

To all the other users that have a PC with an automatic prefetch repair,,Good luck to you and I wish I had one too.

586061299[/snapback]

No need to get hasty here... we're just trying to put our input here as well.

Your method does work for the situation where something has gone buggered and the Prefetch system isn't working, but if that's the case, then there's most likely an underlying problem. The Prefetcher shouldn't stop working because the folder is empty.

All I'm saying is that I've never run into troubles with the prefetch folder from deleting its entire contents. All the files that are needed, including layout.ini are recreated. Yes, I will say that after you delete the contents of the Prefetch folder, the system will take a bit longer to boot for the next few boots, but that's because (as you yourself said) it takes three full reboots for Windows to track all the files needed on startup.

Thats not 100% correct Iron200,, delete everything in your prefetch folder including the layout.ini file and see what happens. It will not always come back as you say.Once the layout ini file is deleted it has to be rebuilt manually using the comand prompt in DOS.

586052755[/snapback]

actually, i've deleted everything (including the layout.ini file) and they were all re-created.

of course, this is a useful tweak for people with messed up prefetching.

I just found this with a Google Search. (I should have bookmarked where...darnit.)...

After deleting files out of the prefetch directory you should run the command

Rundll32.exe advapi32.dll,ProcessIdleTasks

So, I went ahead and opened my Prefetch folder and deleted its entire contents, including the Layout.ini file.

While leaving the now empty Prefetch folder open for my view, I typed in the above command to my Run Box.

..I'll be buggered...the Layout.ini file was re-created IMMEDIATELY! No need to even reboot the 3 times as prescribed.

Well, I think we all learned something from this thread.

This just keeps getting more interesting. By doing what I did above, it shaved 2 seconds off my complete, round-trip, reboot time.

I compared the new Layout.ini file with my old Layout.ini file from my drive's image. The new one looks sooo clean compared to the old one.

The old Layout.ini file has about a zillion entires and weighs in at 123 KB. The new one is only 5.81 KB...and only lists the basics.

Incidentally, that old Layout.ini file was one re-created after I had manually deleted it and it had re-created itself after 20 minutes of idle time. But, it was never re-created as clean as this new Layout.ini file.

If you clean out the standard Windows entries you will CRIPPLE & SLOW DOWN the Windows XP Quick starts and also slow down opening windows processes.

I cleaned out everything in my prefetch folder, including the .ini file, and disabled it in the registry to no performance detrement at all!

i understand that doing this makes things faster.. but what excatly is prefetch and what am i doing to make things go faster?

586069575[/snapback]

The prefetcher is a feature in Windows that "pre-fetches" parts of programs that you use often. When you start your computer, parts of the programs are loaded into memory so that when you go to run the program itself, it starts up quicker.

It will make your boot time a little bit slower though since there's more work to do here.

The guide is more for people who are having troubles with their Prefetchers. Sometimes - due to viruses and other bad stuff mostly - the prefetcher will stop working altogether.

My recommendation for the prefetcher is based on the amount of RAM that you have:

128MB - Disabled (reg value 0)

256MB - Boot only (reg value 1)

512MB or more - Both (reg value 3)

Hope this helps.

Prefetch Parameters

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\PrefetchParameters]

"EnablePrefetcher"=dword:00000005

First, I fail to see where any advantage is gained by messing with the prefetch settings. While disabling the prefetch service (or only using setting 1 or 2) can speed boot times it only hurts overall system performance.

Most tweak guides and popular tweaking programs use a setting of ?5?. There is no documentation to suggest that this setting works. MS states that valid values are 0,1,2,3 and that this setting is ?anded?. The default value is ?3?. I tested using a setting of ?5? on 3 occasions and there was no real improvement in boot times and hard drive activity was longer at boot.*

Prefetching is a good thing, leave it alone. In addition well written disk defrag utilities such as Raxco?s Perfect Disk use the layout.ini information for its optimizations.

Source

I always thought the layout.ini file was only actually processed by defrag to determine where best to place files. Therefore, it shouldn't matter if it's MBs in size, since the defrag task is only run when your computer is idle (or you force it with Rundll32.exe advapi32.dll,ProcessIdleTasks).

  • 1 year later...

After quite a lengthy experimentation process I have discovered what the "Tweak Gurus & PC Geeks" don't tell you in their posts on the subject of cleaning the Prefetch folder.

This guide has not been plagiarized. It is totally compiled by me and was once posted by me at the SoftZone Forums.I decided that I did not wan't to be a member of that comunity because they have more rules than posts so I removed this post and others I had made and canceled my membership.So if you have seen it before that is where it came from.

I hope it can be of assistance to some of you that have cleaned your Prefetch folder because you have been told it will speed XP up. But now "like I did" you find that after you have cleaned the prefetch folder your PC now suffers from slow boot up's and general lack of performance. Here is the real deal about the Prefetch Folder

DO NOT REMOVE OR DELETE THE ->(layout.ini)<- FILE WHICH RESIDES IN XP'S PREFETCH FOLDER OR YOU WILL SLOW DOWN YOUR PC AT START UP AND WHEN YOU OPEN WINDOWS PROGRAMS. Once it is gone it can stay gone on some PC'S (like mine) for ever and your Prefetch Folder will never work again no matter what you do in the registry to try to rectify the problem.

If this has happened to your prefetch folder DON'T WORRY because I will now show you in 5 easy steps how you can rebuild the -> (layout.ini) <- file again.

1): make sure that the task scheduler is enabled.If you are un sure go to-> Start/Contrl Panel/Administrative Tools/ Click on Services/ Then in the list of services make sure the Task Sheduler is enabled & restart the service by clicking on Start. Close the Services Folder & go back to desktop.

2): Then go to START/RUN/ and TYPE IN/->cmd<-(without the arrows) CLICK OK. This will bring up the DOS Command screen.

3):You will need to copy and paste this entry in at the flashing cursor

-> rundll32.exe advapi32.dll,ProcessIdleTasks <-(without the arrows) and press ENTER.

4):Now reboot three times and your Prefetch folder will be rebuilt.(It takes 3 reboots for the prefetch folder to work out what it needs)

5):Then go BACK to ->Start/Contrl Panel/Administrative Tools/ / Services/ Once again find TASK SHEDULER in the list and stop the service and then set it to disabled.This will stop any more entries going into your Prefetch folder.

If you need to leave your task sheduler enabled,(No Drama) you will just have to clean out your Prefetch folder manually from time to time.Just remember not to remove the layout.ini file

You should only clean out files ?other than Windows Start up files? in the Prefetch folder.

If you clean out the standard Windows entries you will CRIPPLE & SLOW DOWN the Windows XP Quick starts and also slow down opening windows processes.

No one bothers to tell you the consequence of deleting the (layout.ini file) in all the tips I have seen about cleaning out the Prefetch folder.

Also if you use one of the many programs that are availabe to clean the prefetch folder you will find that they delete the layout.ini file also.

I have now tried about 50 of these so called Prefetch clean programs and they all disable the Prefetch folder completely and for ever which is a crazy thing to do.The Prefetch is one of the best things about XP.

The truth is that only people who don't know what the Prefetch folder is actually for and don't know how it works say that it is useless.

All I can say is that there must be a lot of people with a verry sluggish XP Windows PC's around,,especially at Boot up.

This worked a treat! Thank you!!! I'm forever tinkering with Windows XP, and after a recent purge using System Mechanic, I noticed my Prefetch folder no longer was in use, and thanks to Google and your post, I have rectified the problem and my PC is running nice and fast again!

Thanks a million!

DO NOT REMOVE OR DELETE THE ->(layout.ini)<- FILE WHICH RESIDES IN XP'S PREFETCH FOLDER OR YOU WILL SLOW DOWN YOUR PC AT START UP AND WHEN YOU OPEN WINDOWS PROGRAMS. Once it is gone it can stay gone on some PC'S (like mine) for ever and your Prefetch Folder will never work again no matter what you do in the registry to try to rectify the problem.

First time I heard that..I clear out my prefetch folder weekly :unsure:

the prefetch files are "defragged" every 3 days, so depending on when you clear out your prefetch folder, it could take anywhere from minutes to days for the layout.ini to be recreated.

And yes it's safe to delete the file, it's automatically created when the files are "defragged".

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!