[Official] Call of Duty: Modern Warfare 2


Recommended Posts

To tell you the truth, I don't find camping to be such a big issue; not like it is in games like Halo 2 & 3, or even the original MW. MW2 campers are fairly easy to flush or pick out. I've found the respawn to be random enough not to make camping too big of an issue, as well.

You think camping is worse in H2/3? I never had any problem with camping when I played either in multiplayer although I saw more of it in doubles than any other playlist; The same can be said for a few of the gametypes in COD4/MW2 as well.

It's just a matter of knowing where people and staying more alert.

Then again I played a lot of custom MLG gametypes and once MLG playlist was added I never left those.. Camping is usually not a problem especially considering there's no radar either.

My "senses" from that ported on over to MW2. Occasionally I'll die from someone sitting back literally hiding behind the most minute object but other than that I never have any problems. I've always been more support versus pushing forward all the time too so that makes a huge difference in gameplay and how often I don't die from stupid crap.

Spawning isn't random until both teams screw it up. So long as you maintain coverage in areas, you won't force a spawn to change. You have your whole team (or theirs) space out all over the map, of course spawns will be random.

---------------------

@Tech Star - I know it's not your video but I'm not sure how that's really an exploit. One Man Army is essentially the same as scavenger pro if you're sticking with the entirely same class. Which is why it's odd you'd stick with One Man Army but I guess that works out more if you plan on staying back versus rushing in / being near dead bodies to grab ammo.

An exploit would be purposefully finding a flaw in the game and using it how it wasn't designed for eg: using the javelins after button mashing. Not sure how using One Man Army + Danger Close Pro is an exploit. It's purpose is just that, ****ing **** up! If anything I do agree that perhaps the veracity of danger close pro can be tamed much like how the Akimbo 1887s were fixed.

If anything it just shows you to.. LOOK OUT FOR PEOPLE WITH LARGE STREAKS >AND< always make sure you either have a secondary vehicle launcher or at least a class you can switch to to equip it. I'm always carrying an AT4 or Stinger (preferably stinger) to shoot UAVs and other air vehicles down. I know at least a couple other people on my team do as well since we want to keep things as minimal as possible for the other team.

Especially if someone is going on a high streak, we don't want a counter-UAV to screw us over. That and I'd rather not have my boyfriend get ****ed when he gets killed by some random running around with marathon/lightweight/commando and his tact knife.

You think camping is worse in H2/3? I never had any problem with camping when I played either in multiplayer although I saw more of it in doubles than any other playlist; The same can be said for a few of the gametypes in COD4/MW2 as well.

It's just a matter of knowing where people and staying more alert.

Then again I played a lot of custom MLG gametypes and once MLG playlist was added I never left those.. Camping is usually not a problem especially considering there's no radar either.

My "senses" from that ported on over to MW2. Occasionally I'll die from someone sitting back literally hiding behind the most minute object but other than that I never have any problems. I've always been more support versus pushing forward all the time too so that makes a huge difference in gameplay and how often I don't die from stupid crap.

Definitely. I'm referring to spawn-camping, in particular. Spawn-camping was/is often an issue in both Halo 2 & 3, especially in objective gametypes, and is part of the reason I don't play those very often, anymore. I've never come across this issue in either CoD4, or MW2 because the spawn is random enough (despite coverage area by either team) and the maps are generally complicated enough to avoid it, as opposed to the simple, territorial maps such as Halo 3's Construct.

Camping is probably just as prevalent in MW2 as in Halo 2 & 3, but it's much less of an issue or exploit, in my experience.

Spawning isn't random until both teams screw it up. So long as you maintain coverage in areas, you won't force a spawn to change. You have your whole team (or theirs) space out all over the map, of course spawns will be random.

Also, note: Spawning is rarely ever completely random, and I certainly didn't imply as much. I completely understand the spawning rules of the game. Rarely, however, are you dropped on top of an entire group of teammates being massacred only to die with them and spawn again in the same gunfire over and over again. It certainly wasn't uncommon at all for this type of thing to happen in Halo 2, in particular. Though you generally spawn near your team in MW2, the spawning is less predictable than it was in the Halo games. That's why I said "I've found the respawn to be random enough not to make camping too big of an issue"

An exploit would be purposefully finding a flaw in the game and using it how it wasn't designed for eg: using the javelins after button mashing. Not sure how using One Man Army + Danger Close Pro is an exploit. It's purpose is just that, ****ing **** up! If anything I do agree that perhaps the veracity of danger close pro can be tamed much like how the Akimbo 1887s were fixed.

I agree with a lot of what you said, but not all of it. First of all, I don't think the javeline issue was so much an exploit as much as a glitch, which is why they patched it; it was something that shouldn't have been allowed to happen in the first place.

exploit

verb |ikˈsploit| [ trans. ]

make full use of and derive benefit from (a resource)

• use (a situation or person) in an unfair or selfish way

• benefit unfairly from the work of (someone), typically by overworking or underpaying them

What you explained as an exploit is probably just as correct as well. In fact, in this situation I can see where using One Man Army + Danger Close Pro could be considered an exploit by your definition. I can't imagine these two classes were intended to be combined to help noob-tubers constantly reload and reap kill after kill with one of the easiest one-shot weapons in the game.

Edited by Emily_June
Definitely. I'm referring to spawn-camping, in particular. Spawn-camping was/is often an issue in both Halo 2 & 3, especially in objective gametypes, and is part of the reason I don't play those very often, anymore. I've never come across this issue in either CoD4, or MW2 because the spawn is random enough (despite coverage area by either team) and the maps are generally complicated enough to avoid it, as opposed to the simple, territorial maps such as Halo 3's Construct.

Camping is probably just as prevalent in MW2 as in Halo 2 & 3, but it's much less of an issue or exploit, in my experience.

Spawn camping is quite different from just simply camping. I wouldn't say it was an issue in Halo 2/3 as so much as a tactic. I admit that I constantly spawn camped as often as I could; If we were able to adjust our tactics and gameplay to setup the team for being spawn killed, then we did it. Truthfully, it's only ever an issue when you're on the receiving end of it. It does suck to have that happen to you but that's what happens when you've got people who know everything about the map from player spawns, weapon spawn times, etc.

It's not hard to see where spawns are going and know where they will always go so long as you stay within that limit before you go too far to switch them behind you.

Construct wasn't nearly as bad for spawn camping as Narrows was. I mean it was so noticable that Bungie made changes to the playlist to alleviate the issue it had.. And even with changing the original spawns, you were still able to use it against your team.

As for spawn camping in MW2, I haven't seen as much as I did with Halo, so if you want to refer to spawn camping ONLY then yeah, I'd agree it is "worse" in Halo 2 & 3. As far as camping goes? Wouldn't really say it's worse (or better). Either that or I just don't die enough to notice camping.

Spawn camping is quite different from just simply camping. I wouldn't say it was an issue in Halo 2/3 as so much as a tactic. I admit that I constantly spawn camped as often as I could; If we were able to adjust our tactics and gameplay to setup the team for being spawn killed, then we did it. Truthfully, it's only ever an issue when you're on the receiving end of it.

...

As for spawn camping in MW2, I haven't seen as much as I did with Halo, so if you want to refer to spawn camping ONLY then yeah, I'd agree it is "worse" in Halo 2 & 3. As far as camping goes? Wouldn't really say it's worse (or better). Either that or I just don't die enough to notice camping.

No, I'm not referring only to spawn-camping (spawn-camping is still very much a version of camping, it's just being taken a step further.), but it's certainly what made camping, overall, such an issue in Halo 2 & 3 for me; and it was very much an issue, despite which team was doing it. Either you're on the team being killed--in which case you don't have a chance--or you're on the team doing the killing--in which case, there's absolutely zero challenge or enjoyment to the rest of the game--unless winning is the only pleasure you get out of the multiplayer. It definitely put me off of the game, and I know it did a lot of other people as well. Unfortunately, it just sucked a lot of the fun out of the game.

In MW2, I don't see camping as any kind of issue at all. It can become frustrating from time to time, but it seems like more of a tactical strategy than it was in Halo

It does suck to have that happen to you but that's what happens when you've got people who know everything about the map from player spawns, weapon spawn times, etc.

Learning the map, player spawns, and weapon spawns is insanely easy in Halo, which is my entire point. That's what makes camping (every kind of camping) such an easy exploit in the game. The maps are more complicated, player spawns are (in my experience) less predictable, and weapon spawn isn't even a consideration in MW2, which makes camping less of a negative for a lot of people, including myself. In fact, I do plenty of camping, myself, when the game calls for it.

Construct wasn't nearly as bad for spawn camping as Narrows was. I mean it was so noticable that Bungie made changes to the playlist to alleviate the issue it had.. And even with changing the original spawns, you were still able to use it against your team.

Spawn-camping isn't as common in Construct, but camping the lifts is. In a lot of Halo's maps, it's maddeningly easy to dominate the high-ground and pick off anyone trying to enter from the two or three only entrances in. Certainly not so much a negative issue, but much more noticeable than in MW2.

I don't believe I said camping was "worse" in Halo than it is in MW2, but it was certainly much more noticeable in my experience. Everyone is going to experience these games differently, which is why there are always mixed reviews on every game.

As I was saying from the start, I noticed the campers in Halo a lot more and found it to be much more of a negative aspect of the game than I do in MW2; I'm not entirely sure whether you're trying to convince me that this isn't my personal experience, or if you're just trying to share your own for the sake of sharing.

In Halo, as with MW2, camping is still just a part of the game and everyone has the opportunity to do it. It wasn't the kind of thing I couldn't adapt to, it was just the kind of thing that made it less enjoyable the more I did adapt. Instead of sticking around and whining about it to anyone who'd listen in-game, I chose to move on to a different game. I do still enjoy those games from time to time, but not as much as I once did.

Edited by Emily_June
Quarry hasn't been too bad for me. I like utilizing the rocks up facing C and tossing up a sentry gun on 'em and getting loads of kills.

Rocks are key for that map. Too many people head to the buildings and run around the outside. If two players can work together and lock down the middle it is easy to control the map, to include the crane. HCTM of course.

Wow. And people say this game is balanced. :D

I think this guy did a truly awesome thing by releasing that video. I know for a fact people will use the very same tactics that he uses in that video, but I think that will have to force IW to fix some things, as it truly shows that things are way off balance.

I think this guy did a truly awesome thing by releasing that video. I know for a fact people will use the very same tactics that he uses in that video, but I think that will have to force IW to fix some things, as it truly shows that things are way off balance.

It will be intresting of how they fix it. They will have to get a bit creative on this one.

I think this guy did a truly awesome thing by releasing that video. I know for a fact people will use the very same tactics that he uses in that video, but I think that will have to force IW to fix some things, as it truly shows that things are way off balance.

So I decided to actually try that out last night. Truthfully, it wasn't impressive nor did it have the veracity I was expecting. I was able to get chopper gunner about 6 or so times but it did not seem any different with danger close pro as he's making it out to be. Was his video setup with a bunch of morons running around?

Obviously the factors with this are: Are people on the other team equipped with a Stinger/AT4/Javelin? Is the map primarily full of buildings?

This just does not have the same impact that the javelin glitch had nor is it as bad as the Akimbo 1887's before IW lowered their range.

This video = worthless.

Wow the people in the above video are well...I've got no way to say it nicely. He makes a great point that the setup he is using is easy to get kills on (although I wasn't familar with One Man Army switching that fast which seemed odd).

That's because you need One Man Army Pro which is for fast-swapping.

Encountered somebody today trying to "boost" or whatever. I noticed that a green arrow was appearing right next to somebody firing repeatedly so I went over and investigated. I ended up killing the opposing booster and waited until he TI'ed to kill him again! :D I noticed the same group trying to do it later in the match as well and continued killing the booster. After that I think he was a little frustrated at me because the guy on my team trying to boost just followed me around the rest of the match and tried to get me killed (it didn't work). Really a funny experience.

Encountered somebody today trying to "boost" or whatever. I noticed that a green arrow was appearing right next to somebody firing repeatedly so I went over and investigated. I ended up killing the opposing booster and waited until he TI'ed to kill him again! :D I noticed the same group trying to do it later in the match as well and continued killing the booster. After that I think he was a little frustrated at me because the guy on my team trying to boost just followed me around the rest of the match and tried to get me killed (it didn't work). Really a funny experience.

haha sucks for him! Good work (Y)

Update .177 is up for PC. If you are on Steam you should be updated. Check your version number in the corner.

Fixes:

Call of Duty: Modern Warfare 2

1. Care Package, Emergency Airdrop, and Sentry Gun marker grenades sprint speed normalized

2. Sentry Guns: Improved placement detection, preventing cases of Sentry Guns inside geometry

3. Model 1887: Bling using Akimbo and FMJ combination now has same range and damage as non-Bling Model 1887s

4. Improved player collision removing cases of getting into geometry and 'elevators'

5. Mouse latency tweaks for more mouse movement consistency

6. Fixes to prevent various texture and XP hacks

The game is a lot more playable without speed/care package glitchers and overall feels a bit more even. The connection issues though are still frustrating and now I can say that I can play it with a bit more positive attitude before BF:BC2 comes out :)

Yesterday, I was playing a match and a guy on sub-base was able to protect himself in the corner with a claymore at the top of the stairs. Now I was thinking if you're close to your own claymore and it goes off, you die but apparently not, you can't get killed by your own claymore yet all other stuff such as grenades do. IW need to fix this. Also noticing a huge increase in double shotguns again, IW need to stop this as most shotguns require two hands to use!

Just updated the front article, not that it often gets read anymore, added all killstreaks, all perks and pro version descriptions, updates and patches too.

Cheers, helps newbies like me :yes:

PC Update -

* Care Package, Emergency Airdrop, and Sentry Gun marker grenades sprint speed normalized
* Sentry Guns: Improved placement detection, preventing cases of Sentry Guns inside geometry
* Model 1887: Bling using Akimbo and FMJ combination now has same range and damage as non-Bling Model 1887s
* Improved player collision removing cases of getting into geometry and 'elevators'
* Mouse latency tweaks for more mouse movement consistency
* Fixes to prevent various texture and XP hacks

New Hack - Negative XP - Reduces your rank back to 1

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
      220
    3. 3
      PsYcHoKiLLa
      147
    4. 4
      Steven P.
      74
    5. 5
      FloatingFatMan
      70
  • Tell a friend

    Love Neowin? Tell a friend!