Help me build a mini-ITX system


Recommended Posts

I would like to build something to play console emulators on my TV with HDMI output for convenience. I have built plenty of desktop systems, but i'm not privy on mini ITX hardware...like compatabilities, options..etc.

Idealy, i would love to beable to use 2 controllers, i think most emulators allow that, but not really sure as i never looked into this, but obviously the purpose for this is to have a multi console via emulation so i have everything i need in a box solution for 2 players.

Not sure what controller i'll end up using, perhaps my arcade stick, i'm not going for replicating the original experience of course.

So basically i need a board and to know what CPU/GPU/RAM i can use that should run most emulators with ease...mostly MAME, if it can run that i'll be happy, NES and Sega emulation should be easy compared to that.

I can find a case myself, but i'm looking for something "consolish" ya know, small and something that may feel nostalgic perhaps, i may even modify my Genesis or buy a broken console to house all the wares in...i'm decent with modding stuff.

I'll probably use my Velociraptor HD only because it's unused and should be large enough for my ROM collection. So basically i just need the main stuff that's capable of runnning MAME

thanks

Link to comment
https://www.neowin.net/forum/topic/1132776-help-me-build-a-mini-itx-system/
Share on other sites

H77 is slightly cheaper, but limited overclocking options. If you want the latter, a Z77 board will be what you want.

Intel Core i3-3225 Ivy Bridge 3.3GHz LGA 1155 w/Intel HD Graphics 4000

http://www.newegg.com/Product/Product.aspx?Item=N82E16819116774

G.SKILL Ripjaws Series 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600

http://www.newegg.com/Product/Product.aspx?Item=N82E16820231277

What about a PSU? For a build like this you don't have to go crazy and get a 1000W, but a good decent 400-500W from Seasonic/Antec/Corsair and the like should be fine. Don't skimp on this, seen too many that do and then come back to tell the horror story.

My laptop has a i3-2330M/HD3000 and 4Gb ram. It runs MAME and NEStron fine, not sure about using two controllers (only used one) but I don't see why it wouldn't/shouldn't work.

Also a important factor is your budget? What are you looking to spend MAX?

Isn't that a bit overkill? I mean my old Netbook i used to have back in 2008 could run emulators. I'm thinking 32 bit OS, 2 gb of ram and some mobile type CPU would likely work if an Atom based Netbook can run the emu's i'm wanting to run.

My PSP can run all the 16 bit era emulators, it really does not take much power to do so...i was thinking more of AMD mobile or something with built in GPU core.

PSU's usually come with cases, not sure about ITX ones as i havnt looked yet but 400 watts sounds insane for my purpose.

Buy one of these and mod it into a NES chassis:

http://www.newegg.co...N82E16813157228

You'll obviously need some RAM and probably a SSD to go with it.

It would be a fun project that would definitely set you apart from everybody else.

There's lots of guides out there from people that have done the same sort of thing.

Buy one of these and mod it into a NES chassis:

http://www.newegg.co...N82E16813157228

You'll obviously need some RAM and probably a SSD to go with it.

It would be a fun project that would definitely set you apart from everybody else.

There's lots of guides out there from people that have done the same sort of thing.

thanks for link, i'll look into it. I thought about the NES chasis but i always preferred the look of the Master System for some reason. I'll probably just use an ITX case if i find one that looks nice.

SSD won't be necessary, i won't need the fastest loading, i was thinking of RT7lite of a windows 7 down to bare bones and just use Steam big screen mode to boot with...then i simply link games on steam to run their respective emulator and add my own image to display on Steam. That will take time to do for each game...but i think it's better than just opening an emulator then loading the game cause the requires a mouse, my way i won't need to use a mouse or keyboard once it's all setup. So Steam boots, i select Mario World or whatever with the gamepad and have it set to open in Snes emulator and voila. Plus Steam works with gamepads however i'm not sure if it works with any gamepad...still have to research more.

thanks for link, i'll look into it. I thought about the NES chasis but i always preferred the look of the Master System for some reason. I'll probably just use an ITX case if i find one that looks nice.

SSD won't be necessary, i won't need the fastest loading, i was thinking of RT7lite of a windows 7 down to bare bones and just use Steam big screen mode to boot with...then i simply link games on steam to run their respective emulator and add my own image to display on Steam. That will take time to do for each game...but i think it's better than just opening an emulator then loading the game cause the requires a mouse, my way i won't need to use a mouse or keyboard once it's all setup. So Steam boots, i select Mario World or whatever with the gamepad and have it set to open in Snes emulator and voila. Plus Steam works with gamepads however i'm not sure if it works with any gamepad...still have to research more.

This is a nice ITX case:

http://www.newegg.com/Product/Product.aspx?Item=N82E16811119261

I've used it before for a build, and it was really nice. Just make sure you get a modular power supply otherwise stuffing all the wires in there will be tough.

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

    • No registered users viewing this page.
  • Posts

    • The machines are starting to fight back any way they can.
    • No news articles about the Arch Linux repo being majorly infected with malware?!?
    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
  • Recent Achievements

    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • One Year In
      Skeet Campbell earned a badge
      One Year In
    • One Month Later
      Sharbel earned a badge
      One Month Later
    • First Post
      BizSAR earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      598
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      79
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      70
  • Tell a friend

    Love Neowin? Tell a friend!