The Adobe PDF Reader on Windows is HUGE

  • SpinRite v6.1 Release #3
    Guest:
    The 3rd release of SpinRite v6.1 is published and may be obtained by all SpinRite v6.0 owners at the SpinRite v6.1 Pre-Release page. (SpinRite will shortly be officially updated to v6.1 so this page will be renamed.) The primary new feature, and the reason for this release, was the discovery of memory problems in some systems that were affecting SpinRite's operation. So SpinRite now incorporates a built-in test of the system's memory. For the full story, please see this page in the "Pre-Release Announcements & Feedback" forum.
    /Steve.
  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in please checkout the “Tips & Tricks” page for some very handy tips!

    /Steve.
  • BootAble – FreeDOS boot testing freeware

    To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.

    GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.

    The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.

    You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.

    (You may permanently close this reminder with the 'X' in the upper right.)

Could it be /Temp directories when the installer was unzipped? or stuff replaced or discarded in the Recycle Bin?
 
Probably because half the installer is applying patches, so over writing existing files with the patched versions further along in the installer. Bugs per megabyte of code is probably a number that is easier to get, at least that will not go into scientific notation when displayed.
 
Adobe Reader bloat has been a big problem for longer than I care to think about. When the DC version first came out I didn't like the new GUI or the increase in size from v11 (XI). At the time I looked at alternatives but always came back to the XI version - but didn't like all the extra features and forced updates. So I looked around and discovered a forum that specialised in Unpacking and then Repacking official MSI installers (termed Lite versions) using a restricted set of essential options www.wincert.net/forum/forum/198-installer-repacks/ - and I am still using a "Lite" version of Adobe Reader XI (v11.0.10.32). Works great on Win10 and has handled everything I have thrown at it including filling in official PDF tax forms (fill in the blank form onscreen with ability to save and print). The forum is not very active anymore and many of the experts have moved on to other projects.

The total size of the installed program is 140 MB
 
  • Love
Reactions: Darcon
I solved this problem back in 2013 when @Steve and @Leo's readers recommended an alternative to Adobe PDF reader or Foxit PDF reader. That is Sumatra PDF Reader.



I'm still using the 2013 version and I haven't upgraded or updated. Because, why? I just want to view PDF files. I have no need of forms. I don't want my DOCUMENTS running javascript or any other scripts. And, I don't want the reader "phoning home" or needing updates every few weeks to keep it from taking over my pc with a virus. I just want to see the stinkin' document. That's all. I've switched and never looked back. Since my needs are simplistic, it works great for me. AND, the entire install directory for the program is under 10 MB!!

Obviously, it's been a while since I installed it. Things may have changed. Management may have changed. My version is 2.4.0.0 and the new ones are 3.?.?.?. So, if you download it, you need to vet it first by looking at reviews, etc. But, I can certainly vouch for what this was 8 years ago. I love it. And I use it.

May your bits be stable and your interfaces be fast. :cool: Ron
 
@PHolder Interesting. Maybe you're blocking javascript as I do. Once I turned on javascript for the site, a menu bar appeared at the top that wasn't visible before. Then you can get to the download page as well as some others. Thanks for the tip.

May your bits be stable and your interfaces be fast. :cool: Ron
 
I solved this problem back in 2013 when @Steve and @Leo's readers recommended an alternative to Adobe PDF reader or Foxit PDF reader. That is Sumatra PDF Reader.
I have heard good things about Sumatra though have never used it.

FWIW: I have been using PDF-Xchange viewer for several years now: https://www.tracker-software.com/product/pdf-xchange-viewer

It is small and compact (45.4.MB installed), stable, and secure(?). All the things that Adobe Reader is not.

It has not been updated since Dec 2018. It works for me. Of course, YMMV applies.
 
Firefox and Edge are already installed on my PC and they do fine for displaying PDF files. The only function missing, that Adobe has, is inserting text and choosing the font, e.g., a signature.
 
Firefox and Edge are already installed on my PC and they do fine for displaying PDF files. The only function missing, that Adobe has, is inserting text and choosing the font, e.g., a signature.
In the past, not sure about now, Firefox was terrible at printing PDFs. So bad, that I disabled Firefox from rendering PDFs and have FoxIt to render them. Some family members print PDFs all the time, so this was a necessity. They accidentally tried Firefox PDF printing in 2020, and the problems still existed. I have not checked recently.
 
That is why I have a separate machine, strictly there because it is used for tax purposes, and is only plugged in for that purpose, when needed. Done because the tax office here still needs to use Flash, and no modern browser supports it any more, so they have an old version of Firefox with flash enabled, and updates disabled. Also the only Win10 machine.
 
That is why I have a separate machine, strictly there because it is used for tax purposes
You could use a physical to VHD tool (MS has one) to read that machines disk into a file to boot as a virtual machine. Then you could run it whereever you want, and virtually enable/disable it's connection to any network with ease.
 
I have to ask... how is it related to mass?

I already know the answer. It's not related to mass; "Massive" is frequently used to describe large things, although an increase in size is often accompanied by a decrease in mass (along with a decrease in density).

The "large quantity, amount, or number" sense has been used in English for around 125 years longer than the strict scientific (physics) sense (1704), but the meaning defining an irregular shaped lump or body of unshaped, coherent matter is from the late 1300s, nearly two centuries prior to the "large quantity, amount, or number" meaning.

Both uses of the word have probably been established long enough to use them in most places, but there are those whose hair rises on the backs of their necks and their shoulder muscles clench when either a large wildfire or 2 gigabytes is described as being more massive than a black hole 1 cm (or any measurement, really) in diameter.
 
Last edited:
the tax office here still needs to use Flash
Is there any tool that will, without a lot of extra work, translate flash into something more common? Isn't it probable that many Flash utilties and other interactive website designs/etc. were converted to more modern formats after Flash was officially retired.

Would it have been easier to convert them using a quickly-written utility or to recode them in HTML5 or javascript or something else? If the former was the case, I'll bet you could find many things on github/etc. for accomplishing the translation. Adobe probably has pricey tools for doing it.

But why fix what works? What could possibly go wrong?