Recommended Posts

It could just be the way they're marketing it, but this is sounding an awful lot better than the current version of PerfectDisk.

Hmmmm, I may be tempted to switch!

It's not. I tried out v10 after using v9 since it came out...and 10 was bad enough that I switched to PerfectDisk.

edit: "Why is it crucial to defrag your drives daily?" you've GOT to be kidding me. What a stupid marketing idea :no:

That's a bad marketing idea? What should they say? "Defragging your hard drive is worthless. Don't buy our product!" I don't think you'd last long as a marketing manager.

PerfectDisk is way better

Vanilla Ice Cream is even better. :yes:

How do you back up your argument? As a prospective customer looking to buy either product I want you to tell me (as an experienced PerfectDisk advocate) how and why it's better than the competition, which I gather you have obviously tested? Clearly you must have to come to your conclusion, right?

Vanilla Ice Cream is even better. :yes:

How do you back up your argument? As a prospective customer looking to buy either product I want you to tell me (as an experienced PerfectDisk advocate) how and why it's better than the competition, which I gather you have obviously tested? Clearly you must have to come to your conclusion, right?

I can tell you why. Diskeeper does not consolidate the free space on the hard drive by writing all the current files so they are contiguous leaving no free space between them. When Diskeeper defragments it leaves gaps between the existing files. So, what do you think happens when new files get written to the disk? They get broken up into FRAGMENTS and written into those empty spaces that Diskeeper left behind. Why do you think they want to continuously defrag your hard drive?

Perfectdisk uses a different strategy. It rewrites your files so that not only are they optimally placed for operation, but they are written contiguously, leaving no gaps for further fragmentation within existing files. Of course with normal use files get changed and deleted, but with regular scheduled defragmention, Perfectdisk will have less to do with each subsequent process.

Huge UI improvement over 9 IMO.

Also, the I-FAAST technology is really cool.

I can tell you why. Diskeeper does not consolidate the free space on the hard drive by writing all the current files so they are contiguous leaving no free space between them. When Diskeeper defragments it leaves gaps between the existing files. So, what do you think happens when new files get written to the disk? They get broken up into FRAGMENTS and written into those empty spaces that Diskeeper left behind. Why do you think they want to continuously defrag your hard drive?

Perfectdisk uses a different strategy. It rewrites your files so that not only are they optimally placed for operation, but they are written contiguously, leaving no gaps for further fragmentation within existing files. Of course with normal use files get changed and deleted, but with regular scheduled defragmention, Perfectdisk will have less to do with each subsequent process.

In Diskeeper 10, this is not true. You can configure the type of defragmentation so that it consolidates free space. This might not have been true of older versions of Diskeeper, but it is now.

This version also includes I-FAAST, which does similar optimization to what PerfectDisk does, and it also allows you to pad the MFT so that fragmentation occurs less frequently. I'm not saying PerfectDisk is no good, it's fine. but your statement above is no longer really accurate. IMO, both products are pretty much equal, but I'd rather use Diskeeper because i find it offers more control than PD.

For those who want to test it before purhasing: you can get a trial version of Diskeeper 10 from FileForum (among many other similar sites of course).

"Diskeeper is an automatic disk defragmenter that features scheduling and a high level of configuration ability, and can defragment even critical system files. Fragmentation occurs during normal Windows operation, as files are broken up in pieces and saved on different parts of the hard disk. This increases the amount of time it takes to access single files, and bogs down system performance."

Kind of sad that Diskeper rolls this out for sale prior to making it available to people who pay for a maintenance contract that entitles them to free updates. Guess they just don't care about their existing customers.

They're probably trying to avoid honoring some of the maintaince contracts. It just shows how much those are worth. Thankfully I purchased Diskeeper 9 two months ago thinking that Diskeeper would be avaliable soon based off how frequently Executive Software releases new versions of Diskeeper. Hopefully they'll start distributing diskeeper 10 to customers within the next ten months. If they do, I get it for $7.49, which is the cost of the maintaince contract. :D

I can tell you why. Diskeeper does not consolidate the free space on the hard drive by writing all the current files so they are contiguous leaving no free space between them. When Diskeeper defragments it leaves gaps between the existing files. So, what do you think happens when new files get written to the disk? They get broken up into FRAGMENTS and written into those empty spaces that Diskeeper left behind. Why do you think they want to continuously defrag your hard drive?

Perfectdisk uses a different strategy. It rewrites your files so that not only are they optimally placed for operation, but they are written contiguously, leaving no gaps for further fragmentation within existing files. Of course with normal use files get changed and deleted, but with regular scheduled defragmention, Perfectdisk will have less to do with each subsequent process.

It is not necessarily a good strategy to cram all data into one section of the drive. What happens when an existing file needs to grow? If it has room to expand, no fragmentation. If it's crammed in with other files...instant fragmentation. Where will this happen? System files like the registry, swap files, game data...etc. In fact, total space consolidation only makes sense if you're planning on saving a file so large it consumes all the free space on the drive. The average small document or system file will hardly be affected.

In my own experience, Diskeeper has been hundreds of times faster than PD, and has much better scheduling options. I have yet to try version 10, however.

It is not necessarily a good strategy to cram all data into one section of the drive. What happens when an existing file needs to grow? If it has room to expand, no fragmentation. If it's crammed in with other files...instant fragmentation.

Sorry but I don't agree with that. Just think what happens when copying, moving or adding files if there are holes in disk's free space. All added or moved files will be fragmented across disk.

Freespace fragmentation also makes disk heads moving all time seeking for contiguous free block. That's why computers seem faster after been defragmented with PerfectDisk.

In my own experience, Diskeeper has been hundreds of times faster than PD, and has much better scheduling options. I have yet to try version 10, however.

Comparing programs using different defrag strategies isn't that fair. When PerfectDisk is configured not to use "SmartPlacement" or "Agressive free space consolidation" it is as fast as Diskeeper if not faster. Offline defragment is a different story, PerfectDisk is times faster than DK.

That doesn't mean Diskeeper isn't an excellent defragger, it is. But PerfectDisk does noticeably better job when performance is considered.

Edited by ssb

hmm, i simply got a Single PC, with 80 GB SATA HD, 2 partitions, one of 10 GB & rest as the other partition, running Windows XP SP2, & NTFS, I m currently using Diskeeper 8, do u guys think there will be anybenifit from upgrading to Diskeeper 10, for just a single PC, & 2 partitions

Well let's twist this up...

I have been using perfectdisk for about 3? weeks and yes it speeds the system up a little.

It even made BF2 load faster and I didn't even have the 5 min lag when I joined a server anymore.But> World of warcraft went berserk with even more loading time. Now when I use the normal defrag again that is a part of windows BF2 has gone back to lag but WoW is doing a lot better.

Do you think that this is a coincidence or is it really affected by the defragmentation program?

Sorry but I don't agree with that. Just think what happens when copying, moving or adding files if there are holes in disk's free space. All added or moved files will be fragmented across disk.

Not true at all. Most of the "holes" are plenty large enough to store new files, while still allowing existing files to expand. I like how you skipped quoting my point that the only time your strategy is necessary is when creating files so large that they'll actually consume the remainder of the free space. Of course there are exceptions in either case, but percentage-wise you'll create more fragmentation with no free space for files to grow than with some "holes" in the order.

Perhaps you would like to explain to the group how many Linux/Unix based filesystems (ie ext3) can avoid fragmentation by design. Here's a hint...it's not total free space consolidation. :)

Got another vote for PerfectDisk! I am not trying to say bad about Diskeeper in its own thread. But, after installing DK 10 and make the proper defragmantation, I didnt notice so much different in perfomance wise. Good thing about diskeeper is, it uses 'english' when it analyzes.

Perfect Disk always gives customers a bunch of numbers and figures which some of us might not be able to understand.

So, next time PD wants to update..make sure it's more user friendly..at least make the interface as good as DK. DK has been doing a great job in interface.

Huge UI improvement over 9 IMO.

Also, the I-FAAST technology is really cool.

In Diskeeper 10, this is not true. You can configure the type of defragmentation so that it consolidates free space. This might not have been true of older versions of Diskeeper, but it is now.

This version also includes I-FAAST, which does similar optimization to what PerfectDisk does, and it also allows you to pad the MFT so that fragmentation occurs less frequently. I'm not saying PerfectDisk is no good, it's fine. but your statement above is no longer really accurate. IMO, both products are pretty much equal, but I'd rather use Diskeeper because i find it offers more control than PD.

Just wanted to thank you for calling to my attention the I-FAAST feature in the Premier version of Diskeeper 10. I downloaded Diskeeper 10 Professional, but not the Premier version so I originally missed out on the I-FAAST feature. I thought the new Diskeeper to be no big deal, but your post caused me to download the Premier edition. What a difference I-FAAST feature makes! I've been a big fan of O&O 8 with the access defrag strategy, but this beats O&O 8. I also own Perfect Disk 7 build 46 and so far I think the Premier version takes PD 7. I used to rank the major defraggers this way: O&O 8, Perfect Disk 7, VoptXP 7.22, then Diskeeper 9. I think Diskeeper Professional Premier 10 just might take the cake now.

Not true at all. Most of the "holes" are plenty large enough to store new files, while still allowing existing files to expand. I like how you skipped quoting my point that the only time your strategy is necessary is when creating files so large that they'll actually consume the remainder of the free space. Of course there are exceptions in either case, but percentage-wise you'll create more fragmentation with no free space for files to grow than with some "holes" in the order.

Perhaps you would like to explain to the group how many Linux/Unix based filesystems (ie ext3) can avoid fragmentation by design. Here's a hint...it's not total free space consolidation. :)

The following is a quote from this Microsoft article

A partially full disk contains unused space, known as free space. Ideally, this space would be available in a few contiguous portions of the disk. And while it?s good to have free space, it?s not good if it?s fragmented. Free space fragmentation refers to file space that?s broken into small pieces, rather than joined together. This type of fragmentation results in slowed performance because of the time it takes for the disk head to move to different points on the disk to find free space and then write the file. Fragmented free space also increases the possibility of file fragmentation; when a file is larger than the space it?s being written to, the file fragments.

Linux and BSD file systems are designed to be less prone to file and free space fragmentation than NTFS. When such an fs writes a file, it does some rearranging to file blocks to prevent fragmentation.

That soin theory,heory, but file and free space fragmentation is inevitable even with these file systems.

It is not necessarily a good strategy to cram all data into one section of the drive. What happens when an existing file needs to grow? If it has room to expand, no fragmentation. If it's crammed in with other files...instant fragmentation. Where will this happen? System files like the registry, swap files, game data...etc. In fact, total space consolidation only makes sense if you're planning on saving a file so large it consumes all the free space on the drive. The average small document or system file will hardly be affected.

In my own experience, Diskeeper has been hundreds of times faster than PD, and has much better scheduling options. I have yet to try version 10, however.

That is why PD optomizes file placement. Unlike Diskeeper, PD doesn't run a background service to conststantly monitor file usage. Instead it runs a scheduler that you have control over which will run to perform an analysis of your drives files. Of course the more frequent the analysis the more accurate the information it has to use, so I have mine scheduled to run every other day, and I don't have the overhead of Diskeepers background service.

For those of you that haven't noticed. One of the greatest drawbacks to background defragmentation is the interferance from antivirus applications! When you have a program or a background service that suddenly starts scanning and rearranging all the files on your drive, an antivirus program gets very interested and you should notice a signifigant hit in performance. If you don't believe me, next time you do a manual defrag, wait until after it's started and then disable or kill your antivirus application. You should notice a signifigant increase in your defragmenters performance.

The best argument I can think of for sticking to manual or scheduled only defragmentation. Because if you have a product like Diskeeper that tries to defrag in the background, you will take a performance hit. And unless the makers of Diskeeper have taken the advice I gave them a couple years back (some of which they did, like the screen saver mode) I doubt that they have integrated a feature I sugessted as a "user assignable, do not activate on dection" list. One of my biggest gripes with Diskeeper was that it would start a defragmentation WHENEVER! it didn't matter what I was doing, I could be in the middle of editing a megepixel image and there goes Diskeeper. So I suggested to them that it would be great if DK would simply check running applications before it kicks in, and if one of the programs on the list is running then it should delay launch by a user specified time.

Have they done this? Or how about the other idea of optomizing the registry as part of a boot time optomization. Have they done that? I sent these ideas to the regional sales manager, she forwarded to the head of engineering and she replied to me with his reply..."These are very good ideas, I'll send them to the team and see what happens".

Edited by teckels

I've used the last few versions if DK, and I have never had a problem with it defragmenting "whenever". It was perfectly easy to schedule it to run at a set time, during the screen saver, or manually. As at least one other person mentioned here, DK has arguably better (more powerful) scheduling features than PD...

Freespace consolidation does not equal improved performance or reduced fragemtation. The NTFS file system by design leaves space for files to grow. Perfectdisk effectively works against the file system.

All the other Defragmenters waste system resources and time constantly consolidating free space by default. Diskeeper is the only program that by default defragments until disk peformance is optimized. You can select Freespace consolidation if you wish, it was also available in v9. Performance in the end is all anyone cares about.

Neither Registry "optimization" or cleaning for that matter effect performance in anyway.

I would also like to back up the fact that Diskeeper running in the background does NOT effect performance. v9 and v10 include I/O smart which will stop the defragmentation engine should you start accessing the HD. I have AV running and have seen no reduced performance in regards to Diskeeper running in the background. I can testify to this with Avast, Computer Associates, Trend Micro and Norton AV. It is possible other AVs may have a problem but that sounds like a problem with the AV.

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

    • No registered users viewing this page.
  • Posts

    • AMD RX 9070 GRE AI, Blender benchmarks vs 9070 XT, 7800XT, Nvidia RTX 5070, 4070 by Sayan Sen Earlier this week, we shared the first part of our review of AMD's new RX 9070 GRE. It was about the gaming performance of the GPU, and we gave it an 8 out of 10. As a follow-up, similar to how we did with the 9070 XT and non-XT, we are doing a dedicated productivity review for the RX 9070 GRE as well, where we compare it against the 9070 XT, 9070, 7800 XT, as well as Nvidia's 5070 and 4070. This will include AI, rendering, compute, and more benchmarks. AI performance, especially, is a very important metric in today's world, and AMD also promised big improvements thanks to its underlying architectural improvements. We will be pitching it against the data we already have for the RX 9070, and RX 9070 XT, but also the Nvidia 5070 FE, MSI GeForce RTX 4070 VENTUS 2X 12G, and Gigabyte Radeon RX 7800 XT GAMING OC 16G as they are in a similar price class, but also because we do not have a comparable 5060 Ti card lying around here that we can compare it against. Before we get underway, this is a collaboration between Sayan Sen and Steven Parker, who lent me his test bed. Also, there was no editorial input from AMD. First up, the specs of the RX 9070, 9070 XT, and 9070 GRE, which were given to us by AMD: Radeon RX 9070 GRE Radeon RX 9070 Radeon RX 9070 XT Boost Clock: Game Clock: up to 2.79GHz up to 2.20GHz up to 2.52GHz up to 2.07GHz up to 2.97GHz up to 2.40GHz Stream Processors 3,072 (48 CU) 3,584 (56 CU) 4,096 (64 CU) Ray Accelerator 48 56 64 AI Accelerator 96 112 128 ROPs 96 128 Texture Mapping Units 192 224 256 Memory 12 GB GDDR6, 18Gbps Clock, 192-bit Bus 432 GB/s 16 GB GDDR6, 20Gbps Clock, 256-bit Bus Effective Memory Bandwidth: 640 GB/s Infinity Cache 48 MB (3rd Gen) 64 MB (3rd Gen) Card Bus PCI-E 5.0 X16 Output 2x HDMI 2.1b 2x DisplayPort 2.1a Power consumption 220W 304W Recommended PSU 650W 750W Slot width 2x 3x Price (SEP) $549 $599 As you can see from the specs above, it is less than the standard RX 9070 in every way that counts, except for slightly higher Boost and Game clock speed. Design Moving on, the RX 9070 GRE we were given is an XFX Swift triple-fan, dual-slot design with two 8-pin connectors. At 30cm (self-measured), it will fit in most systems easily. There is no RGB either. The AMD Radeon RX 9070 GRE by XFX from all angles. Test system Our test system consists of the following: Lian Li O11 Dynamic Mini V2 Flow (Amazon|Newegg) ASUS Z890 ProArt Creator WiFi (Amazon|Newegg) Intel Core Ultra 7 270K Plus (Amazon|Newegg) Thermal Grizzly KryoSheet - 44x37 (Amazon|Newegg) 2x 16GB G.Skill Trident Z5 RGB (7200 MT/s in XMP) (Amazon|Newegg) Sabrent Rocket4 Plus 2TB SSD (Amazon) Windows 11 25H2 (Build 26200.8246) AMD shared a press driver based on the recently released Adrenaline 26.5.2 that we were required to use. We now move on to our benchmarks. First up, we have Geekbench AI running on ONNX. For some reason, the 9070 GRE does exceptionally well here in both half-precision (FP16) and single-precision (FP32). It manages to beat the RTX 5070 and RX 9070 non-XT, and is only behind the 9070 XT. Since Geekbench runs in short bursts instead of continuously hammering the graphics card, it seems the GRE's faster boost clocks are helping here. Next up, we move to the UL Procyon AI test suite, starting with the image generation benchmark. We chose the Stable Diffusion XL FP16 test since it is the most intense workload available on Procyon. The Nvidia cards do very well here, as even the 4070 out-muscles AMD's best fairy easily. The positive thing about the GRE is that it gets quite close to the 9070 non-XT in this test; this indicates that the VRAM does not play a very big role here, as SD XL relies on float16 (FP16). So this is something to keep in mind again. If you wish to work with float32 AI workloads, graphics cards with larger than 12 GB buffers would likely emerge as victors. Regardless, the gains are still massive on AMD's 9000 series compared to the 7000 series. Following image generation, we move to the text generation benchmark. This is one test where the 9070 GRE struggled, quite a lot. It seems that the 12 GB VRAM and lower memory bandwidth of the new Radeon 9070 GRE are hurting it quite a bit; the split is massive, especially in a test like Llama2, which packs 13 billion parameters. As such, in all the tests, the 9070 GRE is the slowest of the lot. Next, we tried Blender, and here the AMD GPUs were beaten by Nvidia. Rendering is something the Green team has always had a lead over the Red side, and it has not changed so far. On the positive side, though, the 9070 GRE shows significantly better results than the 7800 XT, which means AMD is on the right path. Catching up to Nvidia, though, will require a lot more effort. And we hope HIP and ROCm can keep improving. Wrapping up AI testing, we measured OpenCL throughput in the Geekbench compute benchmark. The RX 9070 GRE alongside the 9070 did not fare well here at all, even falling behind the 7800 XT. Interestingly, even the RTX 5070 could not beat the 4070 on OpenCL, so perhaps this suggests that OpenCL optimization may not have been a priority for either AMD or Nvidia in the modern era. Conclusion We reached the end of our productivity performance review of the 9070 GRE, and we have to say it's a mixed bag. Unlike the 9070 and 9070 XT, the GRE excels in some areas while losing ground fairly easily in others. Similar to how it happened in gaming, any time the card's memory subsystem gets hammered, it tends to fall behind the others. This was the case with text generation, wherein we saw the VRAM sometimes hit its maximum available 12 GB of usage with larger model sizes. So what do we make of the RX 9070 as a productivity hardware? It can certainly be used, but you have to know it has its limitations. For those looking for a GPU that can deal with more, AMD recently unveiled the Radeon AI PRO R9700, which is essentially a 32 GB refresh of the 9070 XT with some additional workstation-based optimizations. On a similar note, the new Ryzen AI Halo platform is something you can consider if you want to set up a local AI processing station. Considering everything, we rate AMD's Radeon RX 9070 GRE a 7.5 out of 10 for its productivity performance. Price is less of a factor for those looking at productivity cases compared to those considering the GPU for gaming, and as such, we felt it did quite decently on many occasions and can be handy if you need a 12 GB GPU and, for some reason, don't want to get Nvidia. Purchase links: RX 9070 / XT / GRE (Amazon US) As an Amazon Associate, we earn from qualifying purchases.
    • Does anyone here know if these updates are integrated into the UUP dump isos?
    • Motrix Next 3.9.4 by Razvan Serea Motrix Next is a modern, open-source cross-platform download manager built as the official next-generation successor to the original Motrix project. It has been completely rewritten using Tauri 2, Vue 3, TypeScript, and Rust, while still relying on the powerful Aria2 download engine for high-speed multi-protocol transfers. The app supports HTTP, HTTPS, FTP, BitTorrent, ED2K and magnet links, offering advanced features like multi-connection acceleration, task scheduling, bandwidth control, and batch download management. With a significantly reduced install size (around 20MB), it focuses on being lightweight, fast, and resource-efficient compared to traditional Electron-based download tools. Designed for Windows, macOS, and Linux, Motrix Next delivers a clean, modern UI inspired by Material Design 3 principles, with smooth animations and a minimal workflow. It improves usability through better download organization, system tray integration, and enhanced torrent handling including selective file downloads and tracker management. Motrix Next features: Multi-protocol downloads — HTTP, FTP, BitTorrent, Magnet, .torrent, ED2K, and Metalink tasks BitTorrent — Selective file download, DHT, peer exchange, encryption controls, metadata caching, GeoIP peer flags, and tracker probing Browser extension integration — Embedded Extension API with independent authentication, download confirmation, smart auto-submit, filename hints, referer/cookie forwarding, and real-time controls (Chrome Web Store · Edge Add-ons) Safe filename handling — Content-Disposition, RFC 2047, non-UTF-8, percent-encoded, and extensionless URL resolution with path traversal sanitization Download organization — Favorite and recent folders, optional file-type categorization, stale-record cleanup, and completed history backed by SQLite Concurrent downloads — Independent controls for active tasks, HTTP connections per server, segments per file, and BT peer limits Speed control — Global and per-task upload/download limits with day-of-week and time-of-day scheduling System integration — Tray operation, optional tray speed display, macOS Dock badge/progress, protocol handlers for magnet://, thunder://, and motrixnext:// Lightweight mode — Destroys the WebView on minimize-to-tray while Rust keeps the engine, task monitor, notifications, history, and extension routing alive Notifications and power options — Native task start/complete/failure notifications, keep-awake during downloads, and optional shutdown after completion Network controls — Scoped proxy support for downloads, app updates, and tracker updates, plus system proxy detection Auto-update channels — Stable, Beta, and Latest Across Channels policies with separate download and install phases Diagnostics — Structured logs, exportable diagnostic ZIPs, database integrity checks, automatic DB rebuild, and Linux GPU rendering fallback Personalization — Light/dark/system theme, 10 color schemes, 26 languages, and first-launch system language detection Motrix Next 3.9.4 changelog: Motrix Next 3.9.4 promotes the 3.9.4 beta cycle to stable. This release refreshes bundled engine binaries, improves task detail readability and copy actions, expands link handling for magnet and ED2K workflows, polishes responsive navigation and text wrapping, updates browser extension documentation, and refines network preference controls. New Features Task Detail copy actions — Added copyable values for task metadata and reusable render functions for long text fields. Magnet and ED2K lifecycle support — Added task lifecycle handling for magnet and ED2K links. History cleanup for deleted tasks — Deleted tasks can now remove matching history records. User-Agent management — Added user-agent management and improved related network preference controls. Browser extension documentation — Added the Firefox Add-ons link for the Motrix Next extension. Improvements Engine binaries — Updated bundled binaries for supported architectures. Task Detail readability — Long task names, URLs, tracker values, and copyable metadata now render more clearly. Deletion messaging — Refined localized task deletion text for clarity and consistency. Text wrapping — Improved URI input wrapping and task name multiline display. Navigation layout — Improved sub-navigation responsiveness. Disk allocation default — Changed the default file allocation method to trunc. Proxy controls — Improved proxy button styling in network preferences. Download: Motrix Next 64-bit | ARM64 | macOS ~20.0 MB (Open Source) Links: Website | macOS / Linux | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • NVIDIA officially supports Ubuntu, as linked above with the GeForce NOW Hands on I did in collaboration with Paul Hill.
    • TO be clear I am not running linux today, however I keep thinking about it. And I want to make sure there are minimal obstacles if I decide to make that switch in the coming months.
  • Recent Achievements

    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
    • Dedicated
      Mark Spruce earned a badge
      Dedicated
    • Collaborator
      conkir earned a badge
      Collaborator
  • Popular Contributors

    1. 1
      +primortal
      479
    2. 2
      PsYcHoKiLLa
      244
    3. 3
      Steven P.
      72
    4. 4
      FloatingFatMan
      66
    5. 5
      +Edouard
      66
  • Tell a friend

    Love Neowin? Tell a friend!