Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ntfsdiff.exe failure #176

Open
pdarragh opened this issue Mar 29, 2011 · 2 comments
Open

ntfsdiff.exe failure #176

pdarragh opened this issue Mar 29, 2011 · 2 comments

Comments

@pdarragh
Copy link
Contributor

Have been developing full negative transcripts and base loads for Windows 7 for the past several weeks, made good headway. Very basic Win 7 install, includes ESET but no auto updates of that or OS. This is 0.9.0 radmindpc toolset.
Yesterday, after getting all the regdiff and ntfsdiff done successfully, went to try my first lapply. After a ktcheck, running ntfsdiff -C led to a total crash of the executable.
Tried several times - no change. Tried ntfsdiff -1 on a few files - works. Reinstalled all radmindpc tools - no change.
This morning, reimaged test machine to the earliest image to see if I had gotten a Windows 7 update that broke it. No change.
Event logs only show the same thing I get when it crashes.
This is a rather solid brick wall.

Original comment by: dlrh

@pdarragh
Copy link
Contributor Author

Discovered that the same transcript generated by this same machine apparently, when pulled in using ktcheck (and this includes the negative transcript), must contain something that ntfsdiff does not like. In other words, there is something that presumably should be in the negative transcript that is not and it causes a very hard crash of the program.
Will try and post update when this is found.

Original comment by: dlrh

@pdarragh
Copy link
Contributor Author

pdarragh commented Apr 1, 2011

After a lot of trial and error, it turns out that the problem is the inclusion of registry transcripts in the command file that is called by ntfsdiff. As soon as I remove those, it goes fine.
I do not know if this is a bug per se - i.e. if ntfsdiff should not have this problem, so am leaving this open.

Original comment by: dlrh

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant