File dates changed to 01-05-11

The dates of the files on an entire internal hard drive changed to 01-05-11. In addition the metadata dates in the Lightroom files on that dive also changed to 01-05-11. I just plugged my iPhone in to update the files from iTunes which are not on the first drive mentioned and it tells me that the iPhone software is up to date and it will check again on 01-05-11. When I check back in Time Machine the dates on the files appear to be correct but as soon as restore the files they show 01-05-11 as the date modified. The time and date in the system prefs is correct. I have also run Onyx to clean up the permissions.
I've scanned for viruses but come up clean. Any suggestions?

Problem solved - caused by an incorrect date format entered in the system preferences. Once the incorrect format was corrected all dates returned to the proper date.

Similar Messages

PLEASE HELP!! Why do my file dates change on import?

I'm trying to drag and drop iPhotos into Aperture or export a collection of files and then import them into Aperture, but the image date changes to a random date in the future when I do so.
What am I doing wrong?
How do I solve the problem?

hi, jan
quote: "Hmmm... the "Edit" button works for me, but it looks like the data I changed didn't actually change... even though the modified date on the .jpg file updated..."
I've been wanting to change the exposure EXIF data since I started using Aperture to make a 32bit HDR file from one photograph so as to fake bracketing of multiple photographs (with just one photo) and obtain a perfect exposure of difficult shots like forests, night city scenes, night clubs etc.
Back to the drawing board
Thanks for your help
victor

Original video file date changes when imported

When I import video files, the date of the original source file gets changed to the date of my importing it.
Premiere Pro CS4 never did that. Why is CS5.5 changing the date of the source file ??
steve

Hi Todd, --
I think you are saying my 'write xmp id to files on import' must be turned ON somehow. I did not do that, so if it is turned ON, it must be ON by default ?
It was both 'date created' AND 'date modified' that were being changed to the date of import.
Ok, I found that. It is turned ON by default, I turned it OFF. I also turned OFF the next one too - 'enable clip and xmp metadata linking'.
I just did a test import, and the 'date modified' of the video files on the hard drive has not changed. Thank you. VERY MUCH.
But, I have other problems too, with PP, and video file dates.
There's a 'date created' and a 'date modified' for video files. Plus, with Windows 7, there's a few more dates - 'date of content' etc.
My original untouched video file dates do not make any sense. 'Date Modified' is showing the date the video files were recorded. 'Date Created' is showing the date I copied the video files from the camera stick to the hard drive.
That makes no sense. They should be the reverse.
Why why why after 30 some odd years have the computer engineers NEVER made video files dates the same as digital photo files, with 'Date Taken'.
Also,
I have multiple cameras. For each event or trip or whatever I often take several 1,000 photos and videos. It's an absolute necessity to be able to mass import chronologically. The only way I can integrate / import them all in chronological order is by Date originally Taken, and then immediately drag all the files to the timeline while they are still all collectively highlighted in the order I just imported them all by date.
PP only allows for imports by 'date taken' for photos and 'date modified' for video files. And, if I don't immediately drag the imported files to the timeline while they are all still highlighted without doing anything else first, the bin window re-arranges them all by filename, and there is no way to later re-arrange them by dates.
This is extremely aggravating and impossible to work with for my need to import then later work with multiple-source recorded files chronologically.
All these 'date' problems for video files really totally screws that.
steve

File date modified on imported pictures

Hello,
I have imported a large number of pictures into iPhoto '08 from an external hard disk. Then I have checked the content of the "Originals" folder into the iPhoto Library. Some pictures have their file date changed to the date of the importation. I am not talking about the EXIF data but the files themselves.
All the pictures stored on my external hard disk have their file date set to the date of the shot. This is normal because I have transferred them from the camera to the disk then I have not modified them.
Do you know why iPhoto has changed the date of some of my pictures? Everything is fine for 99% of them, it happened only on the last pictures but I have not changed the way I transfer them...
I know that this is not a big deal because I can see the original date into iPhoto but I like to see it directly from the Finder when looking at file details.

LarryHN wrote:
Not weird at all - this is because when you import a photo into iPhoto it is copied into the originals folder - a new copy is "created" which of course sets that time as the "creation" time. The creation date is "when the finder created the file" - not at all weird
I understand and it sounds logic. But why are the other 99% of my pictures unaffected then?
Although this is probably relatively safe - I see no advantage to changing the creation date of the files since iPhoto ignores it and uses the EXIF date - and any time you make any change to any file within the iPhoto library you are risking corruption of the library
I synchronize the "Originals" folder with a Windows PC and I browse the pictures with the file explorer on that one... in "Details" mode. So, it is nice to see at first sight in the files list when the picture has been taken.
I know, it's not a big deal...

Detection Method of Date Modified fails due to copied files date modified change

I've been working through an issue for some time now and I think it's a bug with SCCM 2012 SP1. I've built literally 50 deployments in "Application Management" in SCCM 2012, but I've been chasing my tail on a few of them throwing the
"succeeded but couldn't detect" error. The few that have given me problems are all copying text files and then detect the modified date to verify that the file is there. All worked when I initially built them in Windows 8 but are now failing
randomly...even on a machine where they previously worked and I deleted the files to test the deployment again.
What I'm doing:
My java deployment requires policies which we control with the Deployment.config, deployment.properties and java.policy files. A simple script creates the directories and copies the files. I then create a deployment type for this "ConfigFileCopy.cmd"
and create a detection rule for each file that I am moving over. The detection rule looks for a "date modified" date between the beginning and end of the date for the day I modified the file. This allows me to modify the files to change our
java policies and then redeploy them with the "new" modified date as the detection rule, which forces the update.
The problem:
When I first created my deployment, everything worked pretty well. The files copy out and the script runs successfully. There were some minor tweaks I need to make to my scripts, so I did and then updated the content for the deployment type. I believe this
is where things go a little wonky. At this point, my deployment starts failing with the "0x87D00324" error.
Looking through the logs, everything looks good. The reason configuration manager is failing on detecting the modified date for those files, as it turns out, is because the modified dates don't meet the criteria. So that part is properly failing the detection.
The problem is that the modified dates are correct on the server but not the client. Looking in c:\windows\ccmcache, I can see multiple folders....presumably one for each version of the application that I updated. Looking at any of the newer content folders
for this app, the modified dates are the date and time the file was copied out to the workstation, which is incorrect as the file hasn't been modified during that process.
The odd part, is that this doesn't happen EVERY time on EVERY machine. My primary desktop is windows 8.1 and received the files correctly and installed without issue. My test win 8.1 laptop initially received them correctly, but then as I refined the scripts
it began picking up the wrong modified dates and started failing.
I found a similar issue to this existed in SCCM 2007 (http://support.microsoft.com/kb/2276865) so I suspect that this is truly just a bug that hasn't been addressed (or maybe is fixed in R2). Unfortunately
we have business reasons we can't upgrade to R2 at this time so I'm hoping someone has experienced this and has some sort of work around that might get me by for now. If someone can confirm it is fixed in R2, that would help my case to upgrade as well.
I can work around the issue by changing my logic to detect any date greater than a specific date. But I shouldn't have to do that and I'm concerned there are scenarios I haven't thought of that will cause unexpected behavior or failures with that.

This outlines the behavior. It's apparently by design.
"SCCM has a habit of changing the ‘Date Modified’ timestamp of all files it delivers when it detects an ‘upgrade’ of the source files for that application. It typically does not touch the timestamp
of the source files if it delivers a brand new install to a client that has never received the software, however if a single file in the source folder is changed for that application, then SCCM tries to use a previous version of the application in the cache
(C:\windows\ccmcache) and only downloads the new file that has change. This results in all files having their ‘Data Modified’ timestamp changing (except for the brand new file). Therefore determining if that application has delivered
successfully using ‘Date Modified’ timestamps is not recommended. The key to seeing this process in action is looking at the file properties in the
C:\windows\ccmcache\<sccm code> folder for that application, particularly before and after a file is updated in the original source SCCM application folder."
http://blog.kloud.com.au/tag/sccm/

Aperture Video Import Problem - from Lumix GH4: Imported clips have their dates changed to the import date. The files show up on the hard drive but many are not showing up in Aperture.

Aperture Video Import Problem - from Lumix GH4: Imported clips have their dates changed to the import date. The files show up on the hard drive with import date not created date, but many of these same files are not showing up in Aperture. Sometimes the clips actually show up with the current import but take on the video information from a previously imported file.

It was suggested I move this question to IPhoto or IMovie which I did.
Well moving to a different discussion group did not provide an answer to this question either. But what I finally did was import one batch of photos and videos into IPhoto for a given day at a time. Working with these I could change the date and times in order to get them in the original sequench taken. Then I would create an album with that batch. These would all be on the same day (IMove was closed for this phase). Then I would open IMovie, generate the thumbnails for that album, and select the album I had created. This was necessary because the importing process in IPhoto was using incorrect dates for my video so it was a real struggle finding them in IMove until I developed this approach.
I believe that this whole process was so screwy because I was importing from an external hard drive not a camera. I had these photos on a PC and did not have the original cameras to use to import directly which I am fairly sure would have made this easier!

PDF file size grows each time form is saved (with no data changes). Why?

I have an SAP Adobe form (PDF) and we are seeing a difference in the Save behavior between when it is viewed in Adobe Reader vs. the adobe plug-in(?) for Internet Explorer.
When the form is viewed in Internet Explorer, every time the user saves the form the file size grows (even with no data changes in the form - i.e., open the form, hit save). This is not true if the form is opened in Adobe Reader.
The form in question has multiple pages but the only fields directly bound to the SAP source are a handful of identifiers (e.g., order number) and a dynamic table. It appears from our testing that the more entries in the table when the form is created, the greater the size increase each time the file is saved. The table length is not changed after the form is first generated.
Is there a known difference in the behavior of Adobe Reader vs. the browser plug-in which would account for this difference? Our users have Adobe Reader X installed on their machines.

If this is an XFA form, as opposed to an Acroform, you should ask in the LiveCycle Desiger forum or a more relevant LiveCycle forum.

Modified Date changes to now by selecting (not opening) vmwarevm file

Yosemite OSX 10.10.2
VMware Fusion is currently not running, and it's disabled (an older version not compatible with Yosemite has not yet been upgraded) so I don't think Fusion is doing this....
I have VM files (.vmwarevm) that were not opened for months. I want to see which is which by viewing the date stamp in Finder. Clicking once shows the old date, then almost instantly it is changed to Now. Like this:
Created 2009-04-13, 1:23 PM
Modified Today, <now>
Last Opened Today, <now>
... but once changed those dates do not change again.
I found an un-clicked one and it did the same thing, with <now> as the time stamp on that one. Now I have files with slightly different "today" date stamps which is incorrect and not helpful to determine the age of these files.
It appears something (Preview?) is opening the file to access the content and generate a "recent screenshot" for the current state of the VM.
I found no other files [edit: no other file types] that behave this way.
I duplicated and renamed an odt file to .vmwarevm and it does not result in a Modified or Last Opened date change.
(one of the VMs also doesn't change so I suspect a bad file format).

Acrobat 9 makes PDF versions 4.0 and higher. You need a PDF version 5.0 to handle transparencies well. PDF version 4.0 doesn't handle transparency effects well at all.
Pagemaker needs Acrobat 5 to be able to directly export PDF's with custom job settings. It only generates a PDF version 4.0, but works for our needs in Pagemaker.
I choose to keep both Distiller versions to make our work easier. When you have 20 ads open in Pagemaker, and you send the first one as a postscript through the print window, it sets up the "File, Export" in Pagemaker to use the correct PDF job setting, and then you can just do "File, Export to PDF" for the next 19 ads and it makes perfect PDF's. Works slick instead of having to make postscripts of all 20 ads first and then run them through Distiller. If you only have Distiller 9 installed, it doesn't let you select any custom job settings from your Distiller. Crazy, I know, but that's what I've figured out we have to do to get it to work. Have to have Distiller 5.0 to control PDF settings in Pagemaker and still be able to export from the file menu directly to PDF.
Distiller 9 is used for all other more advanced design pieces created in InDesign or Photoshop that are saved as a postscript first and PDF's are made the long way in those cases (running postscript through Distiller 9 at the end).

NI unzip changes file date and time stamp

A coworker this morning asked me about the NI-Unzip VI.
It turns out that when the NI unzip VI unzips a file it changes the file dates to the date the file was unzipped.
He also noted that NI-Unzip seems to be calling the Windows touch.exe to do this.
The diagram for NI unzip is locked and password protected so his attemp to change this action blocked.
Does anyone know a way around this? Either to make the NI Unzip stop changing the file date or the passwork to teh unzip vi?
Message Edited by RTSLVU on 03-22-2010 08:01 AM

Hi,
I don't think NI will give you a password for it's protected functions...
So you can:
- use "System Exec" with a command line version of a ZIP tool of your choice to unzip files
- make your own "Unzip" VI with calls to a "unzip"-DLL of your choice
Choose the one that is easier to implement for you
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

Why is the date changed when I move files to an external drive

The date of my files is changed when I move them to my external Lacie drive.
Is there a way to prevent this?

Hi Luuk, and a Warm Welcome to Apple Discussions and the Power Mac G5 Forum!
This may be of interest
http://discussions.apple.com/thread.jspa?messageID=1463652#1463652
The date is retained in 10.4.8 here, on both a copy and a move to an external firewire drive.
Repairing Permissions in Disk Utility was another fix.

Modified date changes when just opening PM file

We use modified dates frequently at my business. We have lots of things that reoccur only once a year, and we'd like to keep the file dates listed as such in the folder views.
All the sudden, however, Pagemaker files have started updating the modified date to the moment you touch the file, even if you make no changes. If you open it, it now becomes today's date & current time. It's really messing up our method of doing things.
It's not happening with any of our CS4 files, or any Microsoft Office files. Also, it's only happening on files stored on the server. It doesn't happen when we do a test of saving a Pagemaker file locally. The problem is, we don't store anything locally. Everything is stored on the server so everyone can access the file and so it's backed up.
We have a Windows based computer environment but an Apple server with OS 10.3.8 (Tiger--- yeah, I know, old, but it's as far as we can update that server at this time and are looking at getting a new one sometime, but it might be a year or so.)
The "modified date" problem has taken place only in the past 2 weeks. We have not done anything significant for changes or updates for quite a while on either the local computer or server ends. We restarted the server recently just to refresh things, and also added another user to the server and set some permissions for that user in the past 2 weeks.
What could be causing this all of the sudden, and how can it be fixed?

Acrobat 9 makes PDF versions 4.0 and higher. You need a PDF version 5.0 to handle transparencies well. PDF version 4.0 doesn't handle transparency effects well at all.
Pagemaker needs Acrobat 5 to be able to directly export PDF's with custom job settings. It only generates a PDF version 4.0, but works for our needs in Pagemaker.
I choose to keep both Distiller versions to make our work easier. When you have 20 ads open in Pagemaker, and you send the first one as a postscript through the print window, it sets up the "File, Export" in Pagemaker to use the correct PDF job setting, and then you can just do "File, Export to PDF" for the next 19 ads and it makes perfect PDF's. Works slick instead of having to make postscripts of all 20 ads first and then run them through Distiller. If you only have Distiller 9 installed, it doesn't let you select any custom job settings from your Distiller. Crazy, I know, but that's what I've figured out we have to do to get it to work. Have to have Distiller 5.0 to control PDF settings in Pagemaker and still be able to export from the file menu directly to PDF.
Distiller 9 is used for all other more advanced design pieces created in InDesign or Photoshop that are saved as a postscript first and PDF's are made the long way in those cases (running postscript through Distiller 9 at the end).

Batch change file date to match exif date

Hi All-
I recently got a mac pro. Upon importing my photos to iPhoto, the file date for each is set to the date of the import. When using the mac photo screensaver, the date that shows up for everything is the import date, rather than the date the photo was taken.
Is there any way to batch change the pictures so that the file date matches the date the picture was taken?
(Or, a way to have the screensaver use that date
Thanks,
-jamie

Interesting, but here is what I found out. I was annoyed because when I sucked in about 1000 JPGs from my camera's memory stick, and then I copied them to my Windows boxen, the file dates were wrong. I was surprised that there isn't an easy way to do this... until your post!! Thanks. *APPLE, Please fix the way "Originals" are stored during iPhoto import*, since something is wrong here. The file dates stored on my memory stick should have been used not the moment I clicked import in iPhoto.
So I moved my jhead to /usr/bin and gave it root ownership and 755 permissions.
All of the pictures seem to be three deep here:
cd ~/Pictures/iPhoto\ Library/Originals
ls -lsGrt /*/.jpg
But that is only a small fraction of mine. Most end in .JPG
ls -lsGrt /*/.JPG
So here is the commands to do the correction of the file date and time. You don't need the find command or that script, although you might need to snoop around and make sure all of your files are here and not any deeper or in some other location. but this should be harmless to run as long as you want to alter every file date.
jhead -ft /*/.jpg
jhead -ft /*/.JPG
And that pretty much does it. I don't see any images elsewhere that were brought in by iPhoto 6 on my machine. I looked for MPG files but I don't have any. This is from a video recording camera, so I don't have any MPGs.
So jrsmobile, my mileage varied a lot, since your method missed about 95% of my photos!!

File mod date changes on all contents of user homes

I've got network home directories shared over AFP in a small office on 10.8 mac mini server. Whenever a user logs in in the morning, all the files in his/her home directory change modification dates to the time of login. Any ideas why?
Not sure what further details would be useful here - other than that it happens to all the network users, every morning they log in.

So what to do about 25,500 photos dating back to 1999 all changed to Feb 2 2010?
I can't solve your underlying problem, but I wanted to point out that there probably are utilities that will - on a batch basis - change these file dates back to whatever you want.
If you lived in the Mac world, I'd point out that iPhoto - the Mac photo cataloging application - will reset the dates and times of selected photos to whatever you want. So you could select folders or groups of pictures and reset their dates.
Go to Google and see if there is a Windows-equivalent utility. When I do a search like this on Google, I try to imagine what words or terms would be used in the product description, or on the developer's web page. Here, I'd choose "reset date" and "pictures" and "file" and "Windows".
This won't help you solve the underlying problem, but it might help you afterwards.
I've started keeping an old backup hard disk in my gun safe, and only updating it in June and December. That gives me six months to discover that something catastrophic has gone wrong with some of my files - or pictures.
I keep two other backup hard drives that I exchange on a weekly basis. I could see me corrupting the relevant files on both of my weekly backup drives before I realized that I had a problem. Hence, the need for a third long-term hard drive.
Sure, an extra hard drive will cost you $50 to $100. How much time will you have to spend trying to recover from this?

Lightroom changes file date and time

When I imported a large number of images to Lightroom, keeping the files in their original location, the dates and times of the files were updated. This is a bit of a pain because it means that about 4000 files will now be backed up again to the online backup service I use. Why does LR change the filedate when all it's doing is importing to the library?

> Alexander wrote: I believe you have set the option to "Automatically write changes into XMP" and are working with non-raw files (jpeg, tiff or dng)? In this case it is the expected behaviour as LR will write any metadata changes right into the files, thus changing the modification date of the image files.
Either uncheck the above mentioned preference setting or beg Adobe to bring us back xmp side car files for jpeg, tiff and dng.
No, I'm not stalking you :)
The following applies to Macintosh OS X, 10.4.8. I don't know if the same happens with Windows.
I had a similar problem when editing some JPEG file from my Fuji F30. When I would Export the metadata the 'Modified' date of the file changed as expected. However, for certain files, the 'Created' date also changed. I opened a case with Adobe, sent them a description of the problem and some sample files. The Technical Support person reproduced the behavior and passed the information to Engineering.
Yes, Adobe, give us XMP files for all files.

Edit metadata without changing modified file date

I'd like to use Bridge (CS4) to edit metadata in both JPEGs and RAW files, without changing the original file date/time stamp.
Any way I can do this? Thanks.

Thanks. I'm familiar with the file date utilities available (I've even written such a program myself), but it seems like an awkward solution.
Since first posting this question, I discovered that I can keep my raw files untouched, by selecting Camera Raw Preferences > Save image settings > Sidecar .xmp files.
I'd like to see a similar setting for JPEG images as well. Please?

File dates changed to 01-05-11

Similar Messages

Maybe you are looking for