Newbies-TDS-3 CRC32-File doesn't exist

[Mr.Blaze]

for newbies with windows me

For ussers who keep geting

CRC32-File doesn't exist.

open up your note pad like this
now go and copy this files list for CRC32 testing


; System files list for CRC32 testing
%WINDIR%\win.ini
%WINDIR%\system.ini
%WINDIR%\explorer.exe
%WINDIR%\regedit.exe
%WINDIR%\taskman.exe
%WINDIR%\NETSTAT.exe
%WINDIR%\DRWATSON.exe
%WINDIR%\rundll32.exe
%WINSYSDIR%\systray.exe
%WINDIR%\taskman.exe
%WINSYSDIR%\icmp.dll
%WINSYSDIR%\regsvr32.exe
%WINSYSDIR%\netapi.dll
%WINSYSDIR%\ntdll.dll
%WINSYSDIR%\wininet.dll
%WINDIR%\winsock.dll
%WINSYSDIR%\wsock32.dll
%WINSYSDIR%\ws2_32.dll
%WINSYSDIR%\shell.dll
%WINSYSDIR%\shell32.dll
%TDSDIR%\tds-3.exe

and paste it in the notepad or some other similar blank
document like this.

[Mr.Blaze]

;D

[Mr.Blaze]

now open up your tds and select TDS
SELECT EDIT CONFIG TEXT FILES LIKE THIS

[Mr.Blaze]

PART 3
HIGHLIGHT AND SELECT CRCFILES LIKE THIS
DOUBLE CLICK ON IT AND OPEN IT

[Mr.Blaze]

PART 4
NOW SELECT ALL THE TEXT IN THAT CRC FILE AND DELET IT LIKE THIS

[Mr.Blaze]

NOW COPY FROM THE NOTE PAD YOU HAVE THE list for CRC32 testing
THAT YOU COPY OFF THE WILDERS BORD ON TO YOUR NOTE PAD ON TO THE
CRCFILES NOTE PAD AND PASTE IT IN
http://www.wilderssecurity.com/attachments/TDS5.jpg

[Mr.Blaze]

SAVE DONE

[Mr.Blaze]

mods feel free to edit this to make it better and more clear to the point

[Dan Perez]

;)

Excellent work Blaze, this will be very helpful indeed as there have been numerous question on this

Many thanks!

*Mr Blaze gets a karma cookie*

[Jan-at-A]

Heya Blaze,

Here FanJ (not at home now; will have a closer look when I'm back):
WOW Blaze, great work !

Cheers, Jan.

[Mr.Blaze]

LOL actualy it my frind jan that tought me that

i should go to tds private forum and see if i can find jans old crc test list i belive it had even more good stuff to add to the list


for those of you that have more to add to the list albove ill gladly add it just let me know

this small list is for windows me not sure about other operating systems but it sems to me mainly window me ussers have been haveing these problems

[Jan-at-A]

Well, you can add by yourself as much files as you wish.
I certainly would recommand to be sure that ALL required-system-files (required for TDS-3, with respect to YOUR version of Windows) are listed at the crcfiles.txt file.
This will alert you in case one of those files might be changed, due to any reason whatever.
In that case you certainly have to look at their file-versions to make sure for yourself that they have at least the version that TDS-3 requires.
And this IS important ! Not ANY of the required-system-files should have a lower version-number than has be stated at the DiamondCS-site where those version-numbers are posted!!!


I also would like to suggest to add your TDS3-Radius file.
So you will be surely alerted when that definitions-list is changed.
This might be a good advice for two reasons:
1- You're sure that your Radius file is updated (when you downloaded/installed the daily update).
2- You also will be alerted in case by accident your Radius file might be changed.


Lots of other suggestions can be made:
1- add the Reference-file of your Adaware (in case you use it).
2- add your HOSTS file !!!
3- add important files of your AV.
4- add important files of your firewall.
5- etc.

[Jooske]

What was again the name for the windows registry file? Maybe add that too and you might know what has changed when we are alerted for a change in the autostart. Loving the idea of an changed autostart-viewer (hight on the wishlist)
I mean:
if it was not CRC we have in the SS3 examples if i remember well or ever posted in the forum a file to compare two documents, so i hope files too.
So a next script would be --as CRC checks for changes anyway-- to display only the changes and where exactly!
Same with sys.ini and win.ini
What a terrible idea, thinking of the braincells crunching on scripts......
In many cases we do know about the programs we install ourselves, but not always the impact it has on those files.

He Blaze, great work! Looking forward to the continuing story!

[Mr.Blaze]

wow many views id say about 50 of them with this problem the rest just me viewing and those that have posted lol

really look like lots of people had problems wondering why no one has made tdscrc files for difrent os systems yet

[Logan5]

Thanks Mr.Blaze :) It worked just fine on my Win Me system.

I do have a question that hopefully someone can answer. I use NOD32 version 2 and was wondering what files I might want to add to this list.

Thanks
Logan

[Pilli]

Nice one Blazey - Have Munchy cruch on a Karme cookie :)

[Mr.Blaze]

hi Logan5 fellow newb thats a good qustion

im sure there some one with tds that owens nod in the nod forum here at wilders

that can answer that qustion it is a good one

[puff-m-d]

Logan5,

A good start is to go to your main ESET folder and add all the dll and exe files in it to your crcfile in tds.....

Regards,
Kent

[Logan5]

puff-m-d,

Hey thanks :) I'll take a look in that folder and add those
files.

Logan

[puff-m-d]

Logan5,

No problem... Just glad to be of help every now and then ;) ...

Regards,
Kent

[FanJ]

Hey, nice thread ;)


-{ Quote: " quoting: puff-m-d link=board=5;threadid=11137;start=15#msg72590 date=1057813706]
Logan5,

A good start is to go to your main ESET folder and add all the dll and exe files in it to your crcfile in tds.....

Regards,
Kent
" }-

Good suggestions Kent !!! :)

Due to the fact that I restored a backup-image awhile ago, I have at the moment only NOD32 version 1 (that restoring has nothing to do with NOD32 version 2).

Logan5,
Did you make sure that you added those files with their full path? That IS important: files in crcfiles.txt should there be listed with their full path. There are some exceptions: for example for your TDS3-directory you can use an "abbreviation" :
%TDSDIR%
See also the thread "TDS-3 CRC32-test Guidelines":
http://www.wilderssecurity.com/showthread.php?t=7200
You will see there some other "abbreviations".

For my NOD32 version 1 I have added some more (but I'm paranoid ;)). For example:
C:\Program Files\ESET\Nod32.000
C:\Program Files\ESET\Nod32.001
C:\Program Files\ESET\nod32.ini
C:\Program Files\ESET\nod32.ver
C:\Program Files\ESET\Nod32upd.000

At the moment I don't know whether those files also exist at version 2 (as I told: due to completely other reasons I restored a backup image, and I still have to install version 2 again :-[).

[Mr.Blaze]

good one budy and i can do this with any program i want to make sure nothing has been tamperd with.

but what things are good to stay alway fom

for example my norton gets virus def upgrades all the time so what things of thatt sort do i exclude?

or does it matter?

this crc stuff is great

[Logan5]

FanJ,

I will make sure I use the full path :)

Thanks
Logan

[FanJ]

-{ Quote: " quoting: Logan5 link=board=5;threadid=11137;start=15#msg72763 date=1057885547]
FanJ,

I will make sure I use the full path :)

Thanks
Logan
" }-

Hi Logan,

I myself use Powerdesk Pro from VCOM (formerly it was from Ontrack) to quickly get the full path of a file.
It is one of my most used programs: I love it !!!
But it is not free...

[FanJ]

-{ Quote: " quoting: Mr.Blaze link=board=5;threadid=11137;start=15#msg72758 date=1057884070]
good one budy and i can do this with any program i want to make sure nothing has been tamperd with.

but what things are good to stay alway fom

for example my norton gets virus def upgrades all the time so what things of thatt sort do i exclude?

or does it matter?

this crc stuff is great
" }-

Hi Blaze,

I guess you mean "include" in stead of "exclude" ;)

OK, you want to add more files of your AV (in your case NAV; alas, I don't have NAV installed here at the moment; a friend of mine has it; when I'll be there I will have a look for you).

As a "rule of thumb" you might think of those files in your AV directories for example:
.exe
.dll
.ocx
.vxd

You might also think about the virus-definitions file(s) itself.
As you have seen I have added for NOD32 version 1 for example:
c:\program files\eset\nod32upd.000
That's a file which is changed every time I install new virus-definitions for NOD32.
You might think: why did he included that file?
Well, I want to know if that file has been changed.
It might have a legal reason (I installed new definitions), it might have a not-so-nice reason (some nasty changed it).
Anyhow (hey, did I tell you that I'm paranoid ;)) I just want to know it.
For the same kind of reasons I added the reference-file of Adaware and my HOSTS file.

You have to decide for yourself how paranoid you want to be :), and how much files you want to add.
I myself have at the moment about some 125 files in it.
But my NISFileCheck (another "file integrity checker") has several thousands in its database(s) (not to talk about my ADinf32 Pro that checks every file on my system.......).