[CharlotteTheHarlot]

PROBLEMCHYLD, on 25 September 2012 - 07:30 AM, said:

Run this command with TOUCH.EXE and PROCEXP.EXE in the same folder.

TOUCH.EXE /T 2006 02 08 18 46 31 PROCEXP.EXE

You will get the timestamp Wednesday, February 08, 2006, 6:46:31 PM.

Okay I knew that already! I simply misinterpreted this ...

PROBLEMCHYLD, on 24 September 2012 - 11:29 PM, said:

I use TOUCH.EXE from MS resource kit. This is what I use to give the modded/patch files their original timestamp. If you look in SP3 you will find the tool along with the commands located in the PATCHES.BAT file. Since I'm posting from a phone, I can't help with links.

I thought you were saying it could give a file its original PE timestamp ( while disregarding the current MODIFIED stamp or current system datetime )

Sorry! My bad.

[PROBLEMCHYLD]

CharlotteTheHarlot, on 25 September 2012 - 03:10 PM, said:

I thought you were saying it could give a file its original PE timestamp ( while disregarding the current MODIFIED stamp or current system datetime )

Sorry! My bad.

This is what it does. The modified date was 22-Sep-2012 10:14:50 PM, running the command gives it Wednesday, February 08, 2006, 6:46:31 PM. Or am I not understanding you? It changes the timestamp to whatever date you choose to make it. It works great in the SP because when files get patched they lose their original timestamp. So I use this tool to give patched files their original attributes. Remember that not all PE stamps are the same as the file attributes.

Example: Explorer.exe 4.72.3612.1700 PE Timestamp 2/8/1999 11:04:25 PM but the actual file timestamp is Tuesday, March 16, 1999, 11:43:06 AM.

This post has been edited by PROBLEMCHYLD: 25 September 2012 - 04:26 PM

[CharlotteTheHarlot]

PROBLEMCHYLD, on 25 September 2012 - 04:12 PM, said:

CharlotteTheHarlot, on 25 September 2012 - 03:10 PM, said:

I thought you were saying it could give a file its original PE timestamp ( while disregarding the current MODIFIED stamp or current system datetime )

This is what it does. The modified date was 22-Sep-2012 10:14:50 PM, running the command gives it Wednesday, February 08, 2006, 6:46:31 PM. Or am I not understanding you? It changes the timestamp to whatever date you choose to make it. It works great in the SP because when files get patched they lose their original timestamp. So I use this tool to give patched files their original attributes. Remember that not all PE stamps are the same as the file attributes.

Yes we are misunderstanding each other. But I see how it happened since it started with me! Let me explain:

Touch.exe requires parameters specifying the desired date/time to set the file to, as you demonstrated here ...

PROBLEMCHYLD, on 25 September 2012 - 07:30 AM, said:

TOUCH.EXE /T 2006 02 08 18 46 31 PROCEXP.EXE

The misunderstanding happened when I misinterpreted what you said earlier here ...

PROBLEMCHYLD, on 24 September 2012 - 11:29 PM, said:

I use TOUCH.EXE from MS resource kit. This is what I use to give the modded/patch files their original timestamp.

... so what I thought you were saying was that Touch.exe could give a target file its original PE timestamp ( the one contained within the file PE header ) without specifying parameters.

In other words, I thought you were describing that Touch.exe would read the target file's PE time/date ( like Dencorso's utility ) and then apply it to the file ( again, without specifying the parameters ). What Touch.exe actually does is what almost all of the TOUCH utilities do, change the modified date/time to a user specified string. The thought was to automate changing bad downloads to their original time/date without running a utility first and then needing to use a TOUCH with specified parameters.

[PROBLEMCHYLD]

I gotcha! Now we are on the same page

[dencorso]

While I may, as time permits, add a secondary optional output format, better suited for piping, to PETmStp, if you want a fast working solution, I'd suggest a batch file using the good old sed to massage the output from PETmStp before piping it into some form of touch. Cygwin v. 1.5.12 works quite well in 9x/ME and has a reliable and powerful sed command. However, as most unix utilities ported to the DOS world it changes the line-endings to unix-style, so that one'll also need to pipe through "unix2dos -D" to recover the dos-style line-endings.