File Upload Error with Directory /active

I've been slowly working my way through a "File copy failed." error I've been encountering in Acidfree, and have officially arrived at Wit's End. Or at least the point where I start asking for help.

Here's how my problem unfolds: After selecting a JPEG image and hitting 'Preview', Acidfree will upload a copy of my image to "/files/private/working/0".

This generates six files, named thusly:

----
tmp1286789787_large.jpg
tmp1286789787_small.jpg
tmp1286789787_thumb.jpg
95_large.
95_small.
95_thumb.
----

Unfortunately, when I hit the "submit" button, I get the following message:

----
File copy failed.
File copy failed.
File copy failed.
Your acidfree photo was created.
----

Thinking that I had some sort of permissions error, I tried mucking with the permissions on the 'active' folder and its two children, '0' and '1'. At this point, all three are set to 777. This didn't work.

Another oddity (at least, what I found odd) was that all of the directories that Drupal/Acidfree was relying on within /files/private needed to be created by me. Is that normal, or is Drupal supposed to create those at some point?

Finally, I did find a file called "filemanager.lck" in the /private folder; I'm not sure if it has any impact on this problem.

Does anyone have any suggestions on how to get around this file copy problem?

************

Here's my setup Information:

* I'm running Drupal 4.6.5 on a Mac OS 10.4.3 box with Apache/1.3.33 (Darwin), PHP/5.0.4 and MySQL 4.1.15 installed

* I have filemanager.module installed (and patched using the filemanager-private.patch from Dec. 8). I have the Dec. 12 build of acidfree installed as well. I also have LDAP_Integration installed.

* I have "Clean URLs" up and running.

* With in Drupal, I have the following settings:

-- Drupal Settings:

* Clean Urls: Enabled
* Cache Support: Disabled
* File system path: files
* Temporary directory: /tmp (the default)
* Download method: Private - files are transferred by Drupal.

-- Acidfree:

* I'm using all of the module's defaults, save for "Force all new images to be transferred by Drupal", which is checked.

-- Filemanager:

* Public file system path: files
* Public file system url: http://[numeric ip address]/files
* Private file system path: files/private
* Under "File areas:" both "General" and "Acidfree" are set to "Force Private"

-- "Files Directory

-- files
---- /active
------- /0
------- /1
---- /pictures
---- /private
------- /0
------- /1
---- /tmp
---- /working
------- /0
------- /1

-- Here's the result of my Acidfree self-test checklist

----
Filemanager module enabled
Latest version of Filemanager module installed
filemanager-private.patch applied
Filemanager private path set and permissions OK
Filemanager public path set and permissions OK
Filemanager database table created
Acidfree class definition files found for album, photo, video
Drupal 'Temporary directory' path set and permissions OK
Acidfree database tables created
gd image toolkit installed and properly configured
No errors were detected. But this doesn't mean that Acidfree is guaranteed to work flawlessly. It is a complex system and still under development. Please be patient while all the wrinkles are found and ironed out.

PHP configuration
Maximum file upload size is 2M (upload_max_filesize)
Maximum POST size is 8M (post_max_size)
Maximum execution time is 30 seconds (max_execution_time)
Maximum memory usage is (memory_limit)
If these limits are smaller than the files you plan on uploading, you should change the settings in your php.ini file
----

The last one is curious, reporting nothing for "Maximum memory usage" even though it's set to 16M in the php.ini; it also doesn't show up in the list of properties when I run phpinfo(), and yet everything else does appear to be running. (this lack of information about memory_limit is an oddity I haven't seen before in Unix/Linux based Apache/PHP installs, so perhaps this is my problem).