however, the error messages i did get were typical of windows - very frustrating after 9 hours!:
"file name is too long... cannot copy file. Cancel or Skip?"
plus the "do this for all 479 problems?" check box.
1. If the file name is too long how was i able to create it in Windows Explorer in the first place? (the file was created on a 2TB Seagate SATA drive originally, running Windows XP (then mirrored onto a 2TB USB drive, and now copied to a new Seagate 2TB drive))
2. the error messages i got on vista were in fixed windows (could not increase size) and the file name was truncated with the three dots. how am i suppose to fix the problem if I'm not given the file name?
3. i had 479 of these errors. did you expect me to write down all 479 partial file names and go hunting this morning?! i know Microsoft doesn't like error logs, but is there one in this case somewhere?
4. whats with this file name size limitation in the first place? 4BG of memory, 64bit technology, buses out the ass, etc and we still can't handle long file names if needed?
5. is this the same in Windows 7? (or did i miss the "this is my windows and its so beautiful i make passion with it every night!" band wagon?)
(i will now update my signature to this: a billion monkeys using microsoft will eventually produce every single error message... eventually...)
This reminds me of mr burns' room of thousand monkeys. Groening should do another one:
Mr Burns: "This is my room of a thousand monkeys. Eventually they will produce every single error message on Microsoft Windows"... then he looks over at a troubled monkey faced with the blue screen of death and says "Stupid Bill! Now we have to start over!".
Edited by datastrain, 04 August 2010 - 08:25 AM.