Error: "Zero Sized Reply" when accessing ADMINISTER MODULES

This is a solution, not a question. I had to do quite a bit of research to come up with a procedure to fix this headache. Hopefully this post will make it easier for the next person who gets this error.

Platform: Linux.

Problem: All of the 'Administer' pages, except 'Administer Modules', work fine. When trying to access Administer Modules, the following error occurs: "... Zero Sized Reply ..." (plus other miscellaneous, less relevant text).

Solution: Modify the php.ini file to allow more memory to be allocated to the Administer Modules script. To make the change, use a text editor such as vi, pico, or any other plain text editor. Masochists prefer emacs.

• Open the relevant php.ini file in the text editor. My php.ini file is /etc/httpd/438/php.ini (your mileage may vary).
• Scroll to the "Resource Limits" section. My "Resource Limits" section, from the top of the file, was down 20% at Line 236 of 1128 (character 10226).
  --more --
• Make of copy of the line that begins with
       no semi-colon
       memory_limit=8M
• Paste that copied line just above or just below the original line.
• Place a semi-colon at the beginning of either of the 2 identical lines.
  The leading semi-colon makes the line a comment. Comments are not executed when the ini file is read by the system.
  At this point I like to insert another comment line (beginning with a semi-colon) to date the change and explain the reason. My "reason comments" look like this:
       ; 20060726 cel
       ; modified memory_limit to allow access to module management in Drupal
       ; memory_limit = 8M ; Maximum amount of memory a script may consume (8MB)
• Modify the other of the 2 formerly-identical lines to change "8M" (or whatever yours says) to "32M" (without the quotes).
  Note: if your beginning memory_limit is higher than 32M, you'll have to experiment with numbers higher than "32".
  Keep in mind that this resource limit exists to prevent degrading performance. Don't go higher than is necessary to enable access to the Administer Module page.
• Save and close the file.
• Restart the web server service. That causes the system to re-read the php.ini.
      In my case, restart Apache(the web server service) with this command: /etc/init.d/httpd restart .
      If you prefer, you may reboot the hardware server. That will accomplish the same goal (system to re-read the php.ini)

I assume that the Administer Modules script requires more memory than all the the other "Administer Pages." It would be nice if people would RTFM, and if TFM included the above.