Mr_Smartepants

If you mount either using a soft rubber isolator, I doubt you'd hear anything. A 7200 RPM notebook drive would give a higher pitched "whine" than one of a slower spindle speed. Also, considering you'd be streaming content, the cache wouldn't make much difference since the cache would only speed up access to the same block of data and streaming is by definition; constantly changing data. Although, a larger cache would benefit in the speed of the menus (paging back and forth). My dad loves his Popcorn Hour A110! For pure silence you could remove the drive altogether and stream from a remote NAS box or other server. The most expensive (but silent) route would be a SSD.

Not according to their FTP site. ftp://ftp.adobe.com/pub/adobe/reader/win/10.x/10.0.0/en_US/

Well, having a utility written by Russian hackers certainly does NOT boost my confidence and seems to be more trickery than actual usefulness, but that's just my opinion. N1K is correct. Simply using the /PAE switch will accomplish exactly the same thing as this phantom utility. The 32-bit limitation is how the system is limited by the addressing space, NOT the vendor. Linux is limited in exactly the same way. Any more than 4 GB RAM on a 32-bit system is just not seen by the OS, but a portion CAN be used by the BIOS. Here's the math: 2^32=4294967296 (4.29 GB) So a 32-bit system can only address roughly 4.29 GB of RAM AT THE MAXIMUM. This is a system limit, not an OS limit. If you have a motherboard with on-board video, then you can have 6 GB of RAM total and allocate 2 GB of that RAM to the video and the remaining 4 GB would be available to the OS. The OS kernel needs to reside within that 32-bit address space so it as some overhead and RAM "wastage". The PAE extension is built into all modern 32-bit OS (not needed on 64-bit for obvious reasons) and basically allows a second kernel to address the remaining RAM. More info: http://www.microsoft.com/whdc/system/platform/server/pae/paedrv.mspx http://en.wikipedia.org/wiki/Physical_Address_Extension

The great thing about the link I posted is that they are USB 2.0 backward compatible. I can foresee a USB memory card firesale this Xmas season!

How about this USB3.0 stick? 8GB for $14, 16GB for $29! :thumbsup_anim: http://www.engadget.com/2010/11/02/super-talent-intros-8gb-usb-3-0-express-duo-flash-drive-for-14/

http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=c3202ce6-4056-4059-8a1b-3a9b77cdfdda It's official! Release candidate! Not Final.

Looks like FUD can be used by both sides. I'm not a M$ fanboy. I use both Win7 & Linux. They're tools. I don't favor one brand of screwdriver for the same reasons. This article is so full of lies I don't know where to start. False. The only time a reboot is required is when the change affects the currently logged in user permissions or when a change to an in-use file is required. Linux acts in a similar way when applying patches. The changes are either applied immediately to files not in use or 'staged' for the next reboot for core system files. False. In my organization we've been mapping drive letters in the user space in our multi-user environments for at least the past 6 years. On 2k3 server/XP through 2k8 server/Vista configurations. All works perfectly fine. We always use the same 3 letters (of course others are available): O-Official, R-Restricted, S-Shared. All are available to each machine regardless of how many users are logged in at the same time. Damn, even my home network works fine mapping my two NAS shares to multiple users AT THE SAME TIME. Although I agree that hard-mapping A & B to a non-existent floppy drive is just plain stupid for a modern OS. Again false. No company "bets their future" on one technology. The phrase "all the eggs in one basket" comes to mind. I don't have time to pick out all the lies in this (old?) article but there are loads more. In fact, the whole article stinks like bullsh*t and is probably just troll-bait. Linux has one MAJOR downfall that WILL prevent it from going mainstream (if it hasn't killed it's chances yet). And that is OS fragmentation. (Android is just beginning to see this affect) If you install an app written for "MacOS" or "Windows", it will work on that platform. Try doing that for Linux and be prepared to answer way more questions than you should need to. 1) what distro? 2) what architecture? 3) what package type? 4) what package manager? etc. If Linux is to succeed, then the core upstream vendors (RedHat, Debian, Gentoo, Slackware, etc.) need to get together and UNIFY the application installer spec. I shouldn't have to care if an app is distributed as a .deb, .rpm, .tar.gz, or any other package types. Once the core vendors step in line, the rest of the downstream distros will also. I should just be able to download, click, and run. Until that happens, Linux will ultimately fail on the desktop.

Yeah Rick, but I'm not freakin' psychic! Not everyone is blessed with HDMI (nice option for future-proofing though). I don't have it on any of my rigs. What about you Rick? I don't think that card I sent you had HDMI did it? Besides, that third link is out of stock anyway.

Looks nice. All that space you have there to the left of the display and you're using a notebook slimline DVD? I like how all the fans at the top of the case are exhaust. That's going to be a lot of airflow!

XP Pro worked fine. XP MCE had an error during integration. Log: XPtsp v3.0.0.14 Patching Started: 10/17/2010 15:22 ====================================================================== Removing Read-Only Attributes from Files Starting to patch files in i386: - Patching ACCESS.CPL - Patching ACCTRES.DLL - Patching ACCWIZ.EXE - Patching ACLEDIT.DLL - Patching ACLUI.DLL - Patching ADMPARSE.DLL - Patching AHUI.EXE - Patching APPMGR.DLL - Patching APPWIZ.CPL - Patching ASCTRLS.OCX - Patching AUDIODEV.DLL - Patching BATMETER.DLL - Patching BATT.DLL - Patching BCSPRSRC.DLL - Patching BROWSEUI.DLL - Patching BTHCI.DLL - Patching CABVIEW.DLL - Patching CALC.EXE - Patching CAPESNPN.DLL - Patching CARDS.DLL - Patching CDFVIEW.DLL - Patching CERTMGR.DLL - Patching CHARMAP.EXE - Patching CIADMIN.DLL - Patching CLEANMGR.EXE - Patching CLICONFG.EXE - Patching CLICONFG.RLL - Patching CLIPBRD.EXE - Patching CLIPSRV.EXE - Patching CMD.EXE - Patching CMDIAL32.DLL - Patching CMDL32.EXE - Patching CMMON32.EXE - Patching CMPROPS.DLL - Patching CMSTP.EXE - Patching COMCTL32.DLL - Patching COMDLG32.DLL - Patching COMPATUI.DLL - Patching COMPSTUI.DLL - Patching COMRES.DLL - Patching CONF.EXE - Patching CONIME.EXE - Patching CONSOLE.DLL - Patching CREDUI.DLL - Patching CRYPTUI.DLL - Patching CSCDLL.DLL - Patching CSCRIPT.EXE - Patching CSCUI.DLL - Patching CTFMON.EXE - Patching DATACLEN.DLL - Patching DDESHARE.EXE - Patching DESK.CPL - Patching DESKADP.DLL - Patching DESKMON.DLL - Patching DESKPERF.DLL - Patching DEVMGR.DLL - Patching DFRGRES.DLL - Patching DFRGUI.DLL - Patching DIALER.EXE - Patching DISKCOPY.DLL - Patching DMDLGS.DLL - Patching DMDSKRES.DLL - Patching DPMODEMX.DLL - Patching DPVOICE.DLL - Patching DPVSETUP.EXE - Patching DSKQUOUI.DLL - Patching DSPROP.DLL - Patching DSQUERY.DLL - Patching DSUIEXT.DLL - Patching DXDIAG.EXE - Patching DXDIAGN.DLL - Patching DXMASF.DLL - Patching ELS.DLL - Patching EUDCEDIT.EXE - Patching EVENTVWR.EXE - Patching EXPLORER.EXE - Patching EXTMGR.DLL - Patching FDE.DLL - Patching FILEMGMT.DLL - Patching FLDRCLNR.DLL - Patching FONTEXT.DLL - Patching FREECELL.EXE - Patching FSQUIRT.EXE - Patching FTSRCH.DLL - Patching FXSCFGWZ.DLL - Patching FXSCLNT.EXE - Patching FXSCLNTR.DLL - Patching FXSCOVER.EXE - Patching FXSWZRD.DLL - Patching GCDEF.DLL - Patching GPEDIT.DLL - Patching GPTEXT.DLL - Patching GRPCONV.EXE - Patching HDWWIZ.CPL - Patching HELPCTR.EXE - Patching HH.EXE - Patching HHCTRL.OCX - Patching HHCTRLUI.DLL - Patching HMMAPI.DLL - Patching HNETWIZ.DLL - Patching HOTPLUG.DLL - Patching HTICONS.DLL - Patching HYPERTRM.EXE - Patching ICMUI.DLL - Patching ICWCONN1.EXE - Patching ICWCONN2.EXE - Patching ICWDIAL.DLL - Patching ICWHELP.DLL - Patching ICWRES.DLL - Patching IEAKSIE.DLL - Patching IEAKUI.DLL - Patching IEFRAME.DLL - Patching IEPEERS.DLL - Patching IERNONCE.DLL - Patching IESETUP.DLL - Patching IEXPLORE.EXE - Patching IEXPLORE.MUI - Patching IEXPRESS.EXE - Patching IIS.DLL - Patching IISUI.DLL - Patching IMSINSNT.DLL - Patching INETCFG.DLL - Patching INETCPL.CPL - Patching INETCPL.MUI - Patching INETCPLC.DLL - Patching INETMGR.DLL - Patching INETMGR.EXE - Patching INETRES.DLL - Patching INETWIZ.EXE - Patching INPUT.DLL - Patching INTL.CPL - Patching IPSECSNP.DLL - Patching IPSMSNAP.DLL - Patching IRCLASS.DLL - Patching IRPROPS.CPL - Patching ISIGN32.DLL - Patching ISIGNUP.EXE - Patching ITSS.DLL - Patching JOBEXEC.DLL - Patching JOY.CPL - Patching KEYMGR.DLL - Patching LHMSTSC.EXE - Patching LHMSTSCX.DLL - Patching LIGHTS.EXE - Patching LOCALSEC.DLL - Patching LOGONUI.EXE - Patching MAGNIFY.EXE - Patching MAIN.CPL - Patching MAPISTUB.DLL - Patching MDMINST.DLL - Patching MIDIMAP.DLL - Patching MIGLOAD.EXE - Patching MIGPWD.EXE - Patching MIGWIZ.EXE - Patching MIGWIZA.EXE - Patching MIGWIZ_A.EXE - Patching MMC.EXE - Patching MMCBASE.DLL - Patching MMCNDMGR.DLL - Patching MMCSHEXT.DLL - Patching MMSYS.CPL - Patching MNMSRVC.EXE - Patching MOBSYNC.EXE - Patching MODEMUI.DLL - Patching MORICONS.DLL - Patching MPLAY32.EXE - Patching MPLAYER2.EXE - Patching MPRUI.DLL - Patching MQSNAP.DLL - Patching MQUTIL.DLL - Patching MSCONF.DLL - Patching MSCONFIG.EXE - Patching MSDTC.EXE - Patching MSDXM.OCX - Patching MSGINA.DLL - Patching MSHEARTS.EXE - Patching MSHTA.EXE - Patching MSHTML.DLL - Patching MSI.DLL - Patching MSIDENT.DLL - Patching MSIDNTLD.DLL - Patching MSIEFTP.DLL - Patching MSIEXEC.EXE - Patching MSIHND.DLL - Patching MSIMN.EXE - Patching MSINFO32.EXE - Patching MSOBMAIN.DLL - Patching MSOERES.DLL - Patching MSOOBE.EXE - Patching MSPAINT.EXE - Patching MSRATING.DLL - Patching MSTASK.DLL - Patching MSXML.DLL - Patching MSXML2.DLL - Patching MSXML3.DLL - Patching MUCLTUI.DLL - Patching MUWEB.DLL - Patching MYCOMPUT.DLL - Patching MYDOCS.DLL - Patching NARRATOR.EXE - Patching NCPA.CPL - Patching NETID.DLL - Patching NETPLWIZ.DLL - Patching NETSETUP.EXE - Patching NETSHELL.DLL - Patching NEWDEV.DLL - Patching NMAS.DLL - Patching NMCHAT.DLL - Patching NMFT.DLL - Patching NMOLDWB.DLL - Patching NMWB.DLL - Patching NOTEPAD.EXE - Patching NOTIFLAG.EXE - Patching NSLOOKUP.EXE - Patching NTBACKUP.EXE - Patching NTKRNLMP.EXE - Patching NTLANUI2.DLL - Patching NTMSMGR.DLL - Patching NTOC.DLL - Patching NTOSKRNL.EXE - Patching NTSD.EXE - Patching NTSHRUI.DLL - Patching NUSRMGR.CPL - Patching OBJSEL.DLL - Patching OCCACHE.DLL - Patching OCGEN.DLL - Patching ODBCAD32.EXE - Patching ODBCCP32.CPL - Patching ODBCINT.DLL - Patching OEMIG50.EXE - Patching OLEDB32.DLL - Patching OOBEBALN.EXE - Patching OSK.EXE - Patching OSUNINST.DLL - Patching OSUNINST.EXE - Patching PACKAGER.EXE - Patching PERFMON.EXE - Patching PHOTOWIZ.DLL - Patching PINBALL.EXE - Patching POWERCFG.CPL - Patching PRINTUI.DLL - Patching PROGMAN.EXE - Patching PROQUOTA.EXE - Patching QUARTZ.DLL - Patching RASDLG.DLL - Patching RASPHONE.EXE - Patching RCIMLBY.EXE - Patching REGEDIT.EXE - Patching REGEDT32.EXE - Patching REGWIZC.DLL - Patching REMOTEPG.DLL - Patching RSMUI.EXE - Patching RSNOTIFY.EXE - Patching RSTRUI.EXE - Patching RTCSHARE.EXE - Patching RUNDLL32.EXE - Patching RUNONCE.EXE - Patching SAPI.CPL - Patching SAPI.DLL - Patching SCROBJ.DLL - Patching SENDMAIL.DLL - Patching SERVDEPS.DLL - Patching SETUP.EXE - Patching SETUPAPI.DLL - Patching SETUP_WM.EXE - Patching SHDOCLC.DLL - Patching SHDOCVW.DLL - Patching SHELL32.DLL - Patching SHIMGVW.DLL - Patching SHLWAPI.DLL - Patching SHRPUBW.EXE - Patching SHSCRAP.DLL - Patching SIGVERIF.EXE - Patching SMLOGCFG.DLL - Patching SMTPSNAP.DLL - Patching SNDREC32.EXE - Patching SNDVOL32.EXE - Patching SNMPSNAP.DLL - Patching SOL.EXE - Patching SPCPLUI.DLL - Patching SPIDER.EXE - Patching SRCLIENT.DLL - Patching SRRSTR.DLL - Patching STIMON.EXE - Patching STI_CI.DLL - Patching STOBJECT.DLL - Patching STRMDLL.DLL - Patching SXS.DLL - Patching SYNCAPP.EXE - Patching SYNCUI.DLL - Patching SYSDM.CPL - Patching SYSKEY.EXE - Patching SYSMON.OCX - Patching SYSOCMGR.EXE - Patching SYSSETUP.DLL - Patching TAPIUI.DLL - Hex Editing TASKMGR.EXE - Patching TASKMGR.EXE - Patching TCPMONUI.DLL - Patching TELEPHON.CPL - Patching TELNET.EXE - Patching THEMEUI.DLL - Patching TIMEDATE.CPL - Patching TSOC.DLL - Patching UNIMDM.TSP - Patching UPNPUI.DLL - Patching URL.DLL - Patching URLMON.DLL - Patching USER32.DLL - Patching UTILMAN.EXE - Patching VERIFIER.EXE - Patching W3EXT.DLL - Patching WAB.EXE - Patching WAB32.DLL - Patching WAB32RES.DLL - Patching WABFIND.DLL - Patching WABIMP.DLL - Patching WABMIG.EXE - Patching WBEMCNTL.DLL - Patching WEBCHECK.DLL - Patching WEXTRACT.EXE - Patching WIAACMGR.EXE - Patching WIADEFUI.DLL - Patching WIASHEXT.DLL - Patching WINBRAND.DLL - Patching WINCHAT.EXE - Patching WINHLP32.EXE - Patching WININET.DLL - Patching WINLOGON.EXE - Patching WINMGMT.EXE - Patching WINMINE.EXE - Patching WINNT32A.DLL - Patching WINNT32U.DLL - Patching WINNTBBA.DLL - Patching WINNTBBU.DLL - Patching WINSRV.DLL - Patching WINTRUST.DLL - Patching WMM2RES.DLL - Patching WMP.DLL - Patching WMPLAYER.EXE - Patching WMPLOC.DLL - Patching WORDPAD.EXE - Patching WPABALN.EXE - Patching WPDSHEXT.DLL - Patching WPD_CI.DLL - Patching WRITE.EXE - Patching WSCRIPT.EXE - Patching WSCUI.CPL - Patching WSECEDIT.DLL - Patching WUAPI.DLL - Patching WUAUCLT1.EXE - Patching WUAUCPL.CPL - Patching WUAUCPL.MUI MSG: Recompiling dialog in WUAUCPL.MUI.RES - Patching WUAUENG1.DLL - Patching WUCLTUI.DLL - Patching WUPDMGR.EXE - Patching WUWEB.DLL - Patching XPNETDG.EXE - Patching XPSP1RES.DLL - Patching XPSP2RES.DLL - Patching XPSP3RES.DLL - Patching ZIPFLDR.DLL Extracting contents of WMP11.CAB - Patching WMPSHARE.EXE - Patching WMSETSDK.EXE Compressing WMP11.CAB Extracting contents of DRIVER.CAB - Patching BTHCI.DLL - Patching DVDPLAY.EXE - Patching FSQUIRT.EXE - Patching IRFTP.EXE - Patching IRPROPS.CPL - Patching NTKRNLMP.EXE - Patching NTKRNLPA.EXE - Patching NTKRPAMP.EXE - Patching NTOSKRNL.EXE - Patching PS5UI.DLL - Patching STORPROP.DLL - Patching UNIDRVUI.DLL - Patching USBUI.DLL - Patching VFWWDM32.DLL Compressing DRIVER.CAB Extracting contents of MEDIACTR.CAB - Patching EHRES.DLL ERROR: Reshacker error occurred during patching! - Replacing MCBLISS.JPG - Replacing ROYALE.MST - Replacing ROYALE.THM - Replacing ROYALE_SS.DLL Compressing MEDIACTR.CAB Replacing AutoPlay program... Starting to overwrite files in the I386 folder: - Compressing BACKDOWN.JPG - Compressing BACKOFF.JPG - Compressing BACKOVER.JPG - Compressing BACKUP.JPG - Compressing BLISS.JPG - Compressing BLUE_SS.DLL - Compressing BTN1.GIF - Compressing BTN2.GIF - Compressing BTN3.GIF - Compressing CERTMGR.MSC - Compressing CIADV.MSC - Compressing CLASSIC.THE - Compressing COMEXP.MSC - Compressing COMPMGMT.MSC - Compressing DEVMGMT.MSC - Compressing DFRG.MSC - Compressing DIALUP.GIF - Compressing DISKMGMT.MSC - Compressing DNSMGMT.MSC - Compressing EVENTVWR.MSC - Compressing FINI.HTM - Compressing FSMGMT.MSC - Compressing GPEDIT.MSC - Compressing GREENSHD.GIF - Compressing GRN_BTN.GIF - Compressing HOME_SS.DLL - Compressing IDENT2.HTM - Compressing IIS.MSC - Compressing INTRO.WMV - Compressing LOGON.SCR - Compressing LUNA.MST - Compressing LUNA.THE - Compressing LUSRMGR.MSC - Compressing METAL_SS.DLL - Compressing MSLOGO.JPG - Compressing NEWBTM1.JPG - Compressing NEWBTM8.JPG - Compressing NEWMARK1.JPG - Compressing NEWMARK8.JPG - Compressing NEWTOP1.JPG - Compressing NEWTOP8.JPG - Compressing NEXTDOWN.JPG - Compressing NEXTOFF.JPG - Compressing NEXTOVER.JPG - Compressing NEXTUP.JPG - Compressing NTMSMGR.MSC - Compressing NTMSOPRQ.MSC - Compressing PERFMON.MSC - Compressing PRODKEY.GIF - Compressing QMARK.GIF - Compressing REDSHD.GIF - Compressing RSOP.MSC - Compressing SECPOL.MSC - Compressing SERVICES.MSC - Compressing SKIPDOWN.JPG - Compressing SKIPOFF.JPG - Compressing SKIPOVER.JPG - Compressing SKIPUP.JPG - Compressing TITLE.WMA - Compressing WELCOME.HTM - Compressing WMIMGMT.MSC - Compressing XPBALLN.WAV - Compressing XPBATCRT.WAV - Compressing XPBATLOW.WAV - Compressing XPBLKPOP.WAV - Compressing XPCRTSTP.WAV - Compressing XPDEF.WAV - Compressing XPDING.WAV - Compressing XPERROR.WAV - Compressing XPEXCL.WAV - Compressing XPHDFAIL.WAV - Compressing XPHDINST.WAV - Compressing XPHDREM.WAV - Compressing XPINFBAR.WAV - Compressing XPLOGOFF.WAV - Compressing XPLOGON.WAV - Compressing XPMENU.WAV - Compressing XPMIN.WAV - Compressing XPNOTIFY.WAV - Compressing XPPRINT.WAV - Compressing XPRECYCL.WAV - Compressing XPRESTOR.WAV - Compressing XPRINGIN.WAV - Compressing XPRNGOUT.WAV - Compressing XPSHUTDN.WAV - Compressing XPSTART.WAV - Compressing XPSTARTU.WAV Patching WBEMOC.INF Patching SVCPACK.INF Hex Editing SYSTEM32\SMSS.EXE Copying theme package to i386 folder... Adding Optional Components Patching Completed in 0 seconds.

Great news! I'll get to testing right away.

Thanks! I'll get to testing right away. BTW, a release today would be a binary release! 101010 in binary is 42base10 and we all know that 42 is the answer to life, the universe, and everything! :thumbsup_anim: *Edit, Resource translation and XPSP* patching is still locking up my machine, even with Symantec disabled. Unchecking both works fine.

Well, it's definitely mutated beyond the typical case. Originality +10! One plus with the L-shaped ledge is you could prop a LCD monitor on it and have it flat against the wall. Not sure I'd want one, but go for it!

I see you went with the kitchen worktop desk. That's what I did when I built my workstation area. Yours looks nicer though.

At one point I had a 21" CRT. I had to get rid of it because it was causing my desk to collapse from the weight. Good deal on the monitor! :thumbsup_anim:

No need to apologize, real life always has priority. It's best to get it right, than to rush a release.

No, it's only because rapidshare sucks.

Has there been any update to the above reported errors in 3.0.0.12? I've got three new sources on standby ready to test!

The VC10 runtime addon .ini file list doesn't match the file names and is causing a "missing file" error during dosnet filecopy. [dosnet_files] <snip> d1,mfc100cn.dll d1,mfc100de.dll d1,mfc100es.dll d1,mfc100fr.dll d1,mfc100it.dll d1,mfc100jp.dll d1,mfc100ko.dll d1,mfc100ru.dll d1,mfc100tw.dll d1,mfc100us.dll Filenames are: mfc100chs.dll (instead of mfc100cn.dll) mfc100deu.dll (instead of mfc100de.dll) etc...

'E' is for extended. Basically it's an ATX with more PCI slots (or whatever). Generally only found in servers. BTW, what software are you using for your renders? It looks similar to the 3D home design software I used to visualize our house extension to our architect before we built it. very cool.

Holy crap look at the size of that GPU! That's a beast! Be careful with the case height. In your illustration, you wouldn't be able to put the case lid back on because of the GPU power connectors on the top of the card. Cable distances might be trouble too with the board SATA connectors far from the HDDs.

This pic will illustrate what I'm talking about. With the fans as exhausts (blowing out) and having the vents too close, then the outside air gets pulled into the vents and immediately exhausted before it has a chance to do any good. Now look at the below pic with my idea. No vents on the front at all. Make two intake 120mm fans (blowing in), one on each side and one slightly more forward than the opposing fan. This will introduce swirling turbulent air in the center of the case where the northbridge sits. Hard drives don't need a lot of cooling air, but they need some. Heat will kill a drive quicker than anything else (other than dropping it). All air will exhaust to the rear either through the GPU fan, CPU fan duct, or PSU fan. This is much easier to control the dust with filters over the 120mm fans and if water-cooling is used, the 120mm fan opposite the hard drives (closest to PCI slots) can be reversed with the radiator mounted internally. Another good example of "positive-pressure" case design is the Antec NSK24** series. Two 120mm fans blowing in, hot air exhausting through the baffled ducts. Quiet.

I couldn't disagree more. The fan in the front is a huge mistake, giving a direct "line-of-sight" from the noisemaker to the listener. Also, having the vents that close to the fans will "short-circuit" your airflow and stagnate the air in the center of the case. Your design is called a "negative pressure" design. Meaning air will get sucked into the case where ever it can. It's the worst design for dust control. I'd prefer having the ducts opposite from the fans giving a more "cross-flow" effect. I'll grab my crayon and show you in a bit what I mean.

I just wanted to report back that so far everything is working fine with the new green resource theme pack. Well done!

LOL!