• 0

foxit vs adobe reader 9


Question

Recommended Posts

  • 0

Foxit is an absolutely wonderful product. I install it on any new system I build for anyone. Though, I have to confess, personally I use Adobe PDF Reader. I just deal with so many super sensitive PDF documents, that I haven't brought myself to trust in Foxit rendering every last bit and byte correctly.

  • 0

If this were Adobe Reader 8 vs FoxIt, FoxIt hands down. However, Adobe Reader 9 blows 8 out of the water and is comparable to FoxIt. It literally opens as fast as FoxIt on my system, and since performance was the biggest complaint, Adobe Reader 9 for me. I just recently started using FoxIt and have already ditched it because there really isn't a good reason to avoid Adobe Reader 9. The bloat simply does not appear when you use it.

  • 0

Adobe is fast, but it also adds a startup process (which you can disable through msconfig) and also adds another process even when adobe reader isn't running. It's also memory heavy. So, I prefer Foxit for this and other reasons

  • 0

adobe reader 9 lite as it renders pdfs great and starts fast,if foxit had the rendering capability then i would use it but the only thing foxit has over adobe is smaller size but adobe reader 9 lite blows foxit away.

  • 0
Adobe is fast, but it also adds a startup process (which you can disable through msconfig) and also adds another process even when adobe reader isn't running. It's also memory heavy. So, I prefer Foxit for this and other reasons

Same here, I use Vista and I have enough services running, I don't need another one to just read a .pdf file. There is nothing that Adobe can do that Foxit can't AFAIK.

  • 0
Same here, I use Vista and I have enough services running, I don't need another one to just read a .pdf file. There is nothing that Adobe can do that Foxit can't AFAIK.

If you open the preferences window of both the readers, you'll get to know of plenty more features that Adobe Reader has over Foxit.

--

Personally though, I couldn't care much less about the features. I prefer using Adobe Reader as it's simply faster and works better (for me). Adobe is much better in handling large/complex PDF files and it's rendering speed and quality surpasses Foxit and similar readers. I switched over to Foxit when Adobe 7 came out, but I've now switched back to Adobe (9) as it's a much better product. The UI is also much more elegant and refined than Foxit's.

The only reason why one might want to use Foxit or similar is to have on a USB key/avoid installation. On the other hand, I use my own portable Reader 9 which is a self contained exe @ 20MB.

--

Btw, the only background "service" that runs is reader_sl.exe, which is the preloader - but you can remove it as even without it Adobe Reader 9 now loads as fast as Foxit. (Tested on a PIII - 450, Celeron 1Ghz)

And if you want to reduce the memory consumption, just remove the plugins you don't need. The only critical plugins that are needed are EScript.api, reflow.api, Search.api and Search5.api.

  • 0
200, which is still ridiculous but you are waaaay off.

Nope:

  • 1.3GHz or faster processor
  • Microsoft? Windows? XP Home, Professional, or Tablet PC Edition with Service Pack 2 or 3 (32-bit and 64-bit); Windows Server? 2003 (with Service Pack 2 for 64-bit); or Windows Vista? Home Basic, Home Premium, Business, Ultimate, or Enterprise with or without Service Pack 1 (32-bit and 64-bit)
  • Internet Explorer 6.0
  • 512MB of RAM2.35GB of available hard-disk space
  • 1,024x768 screen resolution
  • DVD-ROM drive
  • Video hardware acceleration (optional)

The download itself for pro extended is like 900mb...

  • 0

adobe 9

installer - 33 MB - install folder - 210 MB

firefox plugins required to download the installer - 1

startup entries -1

foxit reader

installer - 2.13 MB - install folder - 5.03 MB

firefox plugins required to download the installer - 0

startup entries - 0

if anyone cares foxit uses less ram as well.

  • 0

^ Why would anyone need a firefox plugin to download the installer? It makes no sense :s

Just enter the URL in your download manager/browser and download..

http://ardownload.adobe.com/pub/adobe/reader/win/9.x/9.0/enu/AdbeRdr90_en_US.exe

And I've already mentioned that the startup entry is completly optional and unnecessary. Also, the installer folder can be brought down by deleting the copy of setup files. Finally, you can reduce the RAM usage by removing unnecessary plugins.

You really shouldn't compare Foxit and Adobe Reader though. It's like comparing Apples to Oranges. Just choose what fits your requirements.

Edited by [deXter]
  • 0

i don't get it, what are people installing? I downloaded the version from Adobe and yeah it's 33MB but it didn't put any special shortcuts on my start menu or anything. (edit - OOPS - i see it now :) lil bugger)

Right now i go to start, click Adober Reader 9 and it opens in less than 1 second.

MOV_0001.3gp

Ok so people say that's just opening a blank thing which will open fast. So here's me opening this document:

http://cob.fsu.edu/tech/printermanuals/las...s/HPLJ2600n.pdf

Which is full of graphics and all that.

MOV_0002.3gp

(yes i restarted after each test)

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

    • No registered users viewing this page.
  • Posts

    • 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.
    • And with SO much better perf than the laggy mess that is Files.
  • Recent Achievements

    • One Month Later
      Sharbel earned a badge
      One Month Later
    • First Post
      BizSAR earned a badge
      First Post
    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB 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!