Windows itself should have no problem with moving a 230 MB file (assuming you are using a reasonably modern version). I've moved 2GB+ files around recently without incident (Windows offline image files, which tend to be a bit portly). Also, Windows doesn't know or care what's in the file, it just moves the bits as directed and has no idea whether the file is corrupted or not. I presume the message you are getting is from Acrobat.
The amount of RAM shouldn't matter. Windows, like all modern operating systems, uses virtual memory. If you are trying to use more memory than you have available RAM, it just uses the swap hard-drive for the excess. Virtual memory is a lot slower than RAM, but otherwise works in much the same way (the exceptions aren't relevant here). It sounds more like one or more of your pictures got corrupted by the image capture software, or by Acrobat, or perhaps by the storage drivers for your memory stick (the in-box drivers are pretty reliable, but some storage devices use their own drivers). Personally, I prefer to avoid working with such large files. They aren't always handled nicely by the programs you use to manipulate them. At a minimum, they take forever to open and are generally difficult to work with. I like to keep my files to no more than maybe 10 MB, preferably less (although I work mainly with text, not graphics). BTW, I assume that you can reopen the file in its original location. Can you successfully copy the file to another location on the hard drive? another medium like a CD-ROM, or perhaps even another flash drive? That might tell you something about where the file is getting corrupted. Guy -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Saturday, September 22, 2007 11:12 AM To: [email protected] Subject: [LUTE] Re: [OT] More on PDF's On Sat, Sep 22, 2007, "G. Crona" <[EMAIL PROTECTED]> said: > Hi Guys! > > I've been toying with Adobe professional and have encountered a perplexing > problem which I wonder if any others have also had. I scanned a huge book > (442 pages) in 300 dpi. The resulting file was 230 Mb. a suspicous number. > But here's the crunch: If I copy the > file to a memory stick or any other drive, it won't open! as far as I know, .pdf files are standalone, there is nothing else to go with them, except fonts if they werent embeded (and arent on the target system. A straight copy of the one obvious file should be sufficient; and if fonts show up missing, thre are procedures to reconcile that, the messages you are getting suggest the file is corrupted during the copy. It is conceivable that windoze is having trouble handling a file that large. Try splitting the file into smaller pieces (use acrobat). It is conceivable that the problem is with one particular page, if so this will help isolate it quickly (divide the problematical portion in half continually, 412,206,103,52,26,13,7,4,2,1 after 10 splits at most you will have the culprit, assuming just one). > I have only 256 Mb RAM well, some of that is used by core portions of the operating system, and more by whatever programs are loaded; what was available at the time you tried to do this work is what is of concern. On an older mac there is a utility program that ships with the system which could tell you in large scale how memory is being used, not sure if windoze has anything similar. It is conceivable that limiting the loaded programs will enable the copy to happen both faster and smoothly. Dunno why the copy didnt discover it was mucking up and tell you. Humongous pdf files are inconveniant in use, please consider splitting this one up into smaller parts; chapters, gathers, whatever. -- Dana Emery To get on or off this list see list information at http://www.cs.dartmouth.edu/~wbc/lute-admin/index.html
