I love this business card idea – simple but creative. That and it features a text editor I couldn’t do without
I used to be quite an avid F@H contributor, I ran several folding rigs and wrote a bit of code for addins to the project. I have not done any real folding since late 2007, that is until this week. I built myself an awesome gaming system last week containing an Intel Core 2 Duo 8400 CPU, 4Gb of RAM and a ATi 4870 GPU. I am extremely pleased with the way this system works and decided to try out some of the high performance clients the F@H project offers.
These essentially break down into SMP and GPU. The former, SMP (Symmetric MultiProcessing) is a client designed to spread the unit workload over the physical (or virtual) cores available on a system rather than using the single threaded normal clients. Disappointingly it doesn’t appear the cores have been modified to achieve this, instead it looks like a managed series of single threaded processes are used. I will need to investigate this further as I had some problems getting it to work – more on this hopefully at a later date. The latter takes advantage of the stream processors on the graphics cards to perform folding, it is in essence a great example of GPGPU. This client absolutely rocks on my ATi 4870’s 800 stream processors currently giving me an approximate PPD (points per day) of greater than 2200 using the Gromacs GPUv2 core.
So, to anyone interested in Folding at Home, despite not being on the ‘officially supported’ list, the ATi 4870 is a work unit crunching beast.
Despite all the problems circulating the web about Windows XP Service Pack 3, I thought I would go ahead anyway on a new installation. The installation part went fine and the system restarted properly with no lock ups, stops or looping restarts. So far so good, unfortunately I celebrated my good fortune too soon – Windows Update stopped functioning. Whilst updates were being downloaded, Windows XP would fail to actually perform the update.
I did a bit of googling and whilst I didn’t find any accounts exactly matching my problem, I decided to follow the advice on this Microsoft KB article.
First of all, stop the automatic update service from the command prompt.
1. Open up Start Menu > Run
2. Type “cmd” and press Enter.
3. In the command box, type “net stop wuauserv”, should should get the following confirmation:
Now we need to reregister the DLL involved in the Windows Update process.
4. Type in “regsvr32 %windir%\system32\wups2.dll”. The following control box should pop up after a moment:
Now we need to start the update service and hopefully all should be well again.
5. Type “net start wuauserv” which should yield this confirmation:
Thats it, updates started working for me immediately afterwards. If this didn’t do the trick for you, follow the alternative methods on Microsoft’s KB article linked above.
Yes, granted the title to this post makes no sense and basically relates to nothing, but I thought it set up this post rather well. You see, this is just a brief post to apologise for the less than usual frequency of my updates in the last couple of weeks. Its been a bit of a busy time so I have slightly taken my finger off of the pulse of the various industries I follow. Since the majority of my posts are reactionary commentaries or rants or how-tos it follows I have not been writing much.
Also, the much vaunted laptop (dv2799) I bought a couple of weeks ago has now had to be swapped a third time!! The first time it had a strange RAM corruption problem in the GFX RAM and the second laptop I received had a poorly constructed USB header which shorted the whole thing out. *sigh*. Still third time lucky I hope, its a lovely laptop, its just a shame it is let down by dubious quality control at Hewlett Packard’s end.
So, stay tuned, I have by no means lost interest in my blog! For now, I leave you with the comedy genius of Simon Amstell.
I am in the process of building a new gaming PC. Well, I should come clean, I have been in the process for almost 5 months now – I am mostly decided on the specifications but minor incompatibilities / annoyances cause me to stall. When this happens, real life typically takes over and by the time I look at my ‘final’ specification again, I normally rip it up and start from scratch due to new hardware being released or price drops. *exhale* I am finally on the verge of finalising the specification, the only things still holding me back are the graphics card (after news of ATi’s 4xx0 series) and the amount of RAM to put into my machine. The latter is heavily influenced by the Operating System I plan to run.
There are two crucial elements to any computer system which must work in harmony, the software and the hardware. Whilst this hardly an earth shattering announcement, I never cease to be amazed at the backlash in the form of blog / forum posts from people who forget this. Realistically when building (or buying) your next Gaming PC at the moment your choices are limited to Windows XP or Vista. Both Linux and Mac OSX suffer from platform compatibility issues with major new games and whilst the former enjoys fair server support for online gaming, neither really has much traction in the desktop gaming market.
The difference between Vista and XP is far more than cosmetic, whilst many are quick to criticise Vista for a number of reasons, I am actually a fan of Microsoft’s latest Operating System for a variety of reasons. Sure, it is feature-poor compared to initial designs and has it’s own annoyances, but the number of extra features and advances make it decisively the better Operating System. There is a caveat, for Vista to run comfortably for gaming purposes needs at least 1 Gb of RAM for itself. This on its own is no big deal – RAM is extraordinarily cheap at the moment, however the issue of platform (32bit/64bit) is now rearing its ugly head.
64 bit computing is nothing new, infact AMD processors have had 64bit extensions (called x86-64) for a number of years since the K8 platform back in 2003. Intel did not catch up (despite starting earlier than AMD) and produce viable 64bit chips until the Pentum 6xx series (late 2004), having stumbled initially with their IA64(T) specification developed for their Itanium platform.
Given this was four years ago, why are we not all running on 64bit XP or Vista? The answer is simple, in the same way that driver support initially crippled Vista’s adoption, 64bit drivers are fairly few and far between. What this means, is a lot less hardware will run properly under a 64bit Operating System. Given this situation, why do we even care about 64 bit computing? Why is it not relegated to high end computing and server farms? Mathematics.
Unfortunately, with a 32 bit Operating System, there is a mathematical limitation to the amount of memory the system can address. At most, Vista (or XP) in 32bit will only address 4Gb of total RAM. This includes both the graphics card and the main system memory. This brings my point about Vista comfortably using one Gb of RAM all by itself to sharp focus. Whilst Yes, the price of RAM is cheap there is something about me that dislikes buying 4Gb of RAM (to enable dual channel mode) only to have a quarter of it not accessible by the system. I wrote about this in detail in a previous post.
So what is the solution? Whilst I am huge fan of Vista (and have recently bought a Vista laptop) I do not think it is suitable for desktop gaming. With Windows XP, I have had fairly bloated a driver / runtime loaded installs using no more than 300Mb of RAM which realistically enables most PC gamers to get away with 2Gb of system RAM with no perceptible loss in gaming performance. This unfortunately would not be the case for a similar system running Vista and as such, unfortunately scuttles Vista for this market in my humble opinion.
Well, thanks to a leak covered by both electronista and the Inquirer, we know a little more about the ASUS PC that I blogged about back in March. I will be called the EBOX and still bares a remarkable similarity to a Nintendo Wii. Apart from this not much has changed, we have no new release images nor any concrete facts about the CPU. It is likely to be an Intel Atom based on murmurings surrounding the series 900 second revision (or possibly third generation EEE PCs) which would make sense. Apart from this, the unit is rumoured to contain a healthy 2Gb of RAM and a traditional spindle hard disk drive with purportedly 160Gb storage. All of this will run ASUS’s custom flavour of Xandros. Given that this is the same tailored OS that ASUS have used in the EEE PC laptop range, it is likely we will see a similar GUI / interface for the EBOX.
I am a little puzzled as to why ASUS would move away from solid state disks for the EBOX. Whilst power considerations no longer have as much importance on a desktop platform, the EBOX is unlikely to attract the ‘one pc’ crowd as it will not replace the traditional computer in the home. I think it could potentially fit very well as a satellite computer in a kitchen or other room in the house were basic surfing / computer usage is required, but this only reinforces the question, why did ASUS go for a traditional hard drive? Satellite systems are typically that, lightweight machines which almost act like thin clients for other machines or storage or services on the home (or office) network. As such and given the EBOX PC is not designed to be portable, space is not as important a commodity as it is on the EEE PC laptop.
Well enough supposition for now, official release / preview is apparently scheduled for the 3rd of June, I daresay all questions will be answered then.