Any reason why this modifys 93 files in root of System32 folder?

Our main issue has been not being able to run a specific compiler due to ntfs.sys being modified by this customizer. If i replace the ntfs.sys with one from the original ISO it works ok. This has me worried that our other 100 PCs with Windows 7 which seem to be ok so far in other regards may have issues down the track due to these files being changed.

Is it the WAIK that is changing these files? I just did a test iso using 7Customizer where i did not make any changes to the original iso data, no drivers hotfixes or unattended file. Still modifying these files.

Custom iso:

ntfs.sys

Digital sig:

‎Sunday, ‎15 ‎November ‎2009 10:38:41 a.m.

default iso:

ntfs.sys

Digital sig:

‎‎Tuesday, ‎14 ‎July ‎2009 1:48:37 p.m.

Is it the WAIK that is changing these files? I just did a test iso using 7Customizer where i did not make any changes to the original iso data, no drivers hotfixes or unattended file. Still modifying these files.

Custom iso:

ntfs.sys

Digital sig:

‎Sunday, ‎15 ‎November ‎2009 10:38:41 a.m.

default iso:

ntfs.sys

Digital sig:

‎‎Tuesday, ‎14 ‎July ‎2009 1:48:37 p.m.

So.. what's been modified ?

WAIK itself doesnt change anything but dism does (most of it)

Any reason why this modifys 93 files in root of System32 folder?

Our main issue has been not being able to run a specific compiler due to ntfs.sys being modified by this customizer. If i replace the ntfs.sys with one from the original ISO it works ok. This has me worried that our other 100 PCs with Windows 7 which seem to be ok so far in other regards may have issues down the track due to these files being changed.

hmmmmmm...

13. License Agreement: (blah blah blah)

7Customizer is a freeware tool. You could use it only for any personal non-commercial purposes.

Maybe he has huge home network

Perhaps he does

But this tool is only for non-commercial use, and maybe he uses it within a smaller company, sowhat? it works with all editions of 7 etc and its not being sold (as far as i know).

So you'r saying that 7C modifies 93 files in system32 folder without you making any changes at all?

Can u prove that to us?

Any reason why this modifys 93 files in root of System32 folder?

can you give us information about what are the differences between the two files? (if it works use the binary fine compare function of windows (fc /b ))

Pearhaps when dism (or some other program in WAIK) open a file has to write something iside like a date or something else.

Probably that and/or that dism/waik reads info from the dvd that way ?

Probably that and/or that dism/waik reads info from the dvd that way ?

Here is the .rar of both the original ntfs file and the one modified when using 7C:

http://stimps.orconhosting.net.nz/ntfs_issue.rar

7C config:

http://stimps.orconhosting.net.nz/default_w7_iso.txt

Binarys differ when comparing in winmerge.

So it's DISM changing these files.. official microsoft tool right, part of WAIK right?

Here is the .rar of both the original ntfs file and the one modified when using 7C:

http://stimps.orconhosting.net.nz/ntfs_issue.rar

7C config:

http://stimps.orconhosting.net.nz/default_w7_iso.txt

Binarys differ when comparing in winmerge.

So it's DISM changing these files.. official microsoft tool right, part of WAIK right?

Hello

I see that the two files are différents:

1 - ntfs_original.sys is made with version 6.1.7600.16385

inside property we can see:(win7_rtm.090713-1255)

2 - ntfs_new.sys is made with version 6.1.7600.20575

inside property we can see: (win7_ldr.091113-1530)

Weird!

Edited June 2, 201016 yr by myselfidem

Here is the .rar of both the original ntfs file and the one modified when using 7C:

http://stimps.orconhosting.net.nz/ntfs_issue.rar

7C config:

http://stimps.orconhosting.net.nz/default_w7_iso.txt

Binarys differ when comparing in winmerge.

So it's DISM changing these files.. official microsoft tool right, part of WAIK right?

Hello

I see that the two files are différents:

1 - ntfs_original.sys is made with version 6.1.7600.16385

inside property we can see:(win7_rtm.090713-1255)

2 - ntfs_new.sys is made with version 6.1.7600.20575

inside property we can see: (win7_ldr.091113-1530)

Weird!

Ah looks like one of the hotfixes i injected into the install.

http://support.microsoft.com/kb/976538/

Don't touch this one

Here is the .rar of both the original ntfs file and the one modified when using 7C:

http://stimps.orconh.../ntfs_issue.rar

7C config:

http://stimps.orconh...ault_w7_iso.txt

Binarys differ when comparing in winmerge.

So it's DISM changing these files.. official microsoft tool right, part of WAIK right?

Hello

I see that the two files are différents:

1 - ntfs_original.sys is made with version 6.1.7600.16385

inside property we can see:(win7_rtm.090713-1255)

2 - ntfs_new.sys is made with version 6.1.7600.20575

inside property we can see: (win7_ldr.091113-1530)

Weird!

Ah looks like one of the hotfixes i injected into the install.

http://support.micro....com/kb/976538/

Don't touch this one

Didn you said you didnt made ANY changes, just created the iso?

And now you say you integrated an update..

Weird!

Here is the .rar of both the original ntfs file and the one modified when using 7C:

http://stimps.orconh.../ntfs_issue.rar

7C config:

http://stimps.orconh...ault_w7_iso.txt

Binarys differ when comparing in winmerge.

So it's DISM changing these files.. official microsoft tool right, part of WAIK right?

Hello

I see that the two files are différents:

1 - ntfs_original.sys is made with version 6.1.7600.16385

inside property we can see:(win7_rtm.090713-1255)

2 - ntfs_new.sys is made with version 6.1.7600.20575

inside property we can see: (win7_ldr.091113-1530)

Weird!

Ah looks like one of the hotfixes i injected into the install.

http://support.micro....com/kb/976538/

Don't touch this one

Didn you said you didnt made ANY changes, just created the iso?

And now you say you integrated an update..

Weird!

Sorry it seems that the folder i had for the contents of the W7 stuff had the hotfix injected into it, rather than using 7C, i did create this ISO back in feb, memory fails me.

Sorry it seems that the folder i had for the contents of the W7 stuff had the hotfix injected into it, rather than using 7C, i did create this ISO back in feb, memory fails me.

Thanks for your feed back!

Sorry it seems that the folder i had for the contents of the W7 stuff had the hotfix injected into it, rather than using 7C, i did create this ISO back in feb, memory fails me.

Lol, false allarm!

I'm still waiting for blue, he has a really hard job AND/OR he wants to surprise us with some new features ! .D