CFP 3.0.21.329 Released

[Guest]

[Josh123]

Quick Question.

I was never able to update to the last release it kept coming up with error 119, will this now be fixed?

Do have to update manaually through CFP or will it do it automatically.

Thanks

I am getting the 119 error message too. Only solution for me was to uninstall Comodo, Reboot, and do a fresh install

Other then that, Thanks for the release!

Josh.

[ei4ia]

Making double posts wont get your answer and sooner.

Wrong. For example see ultramon.exe story - issue was reported continuosly since 2007 (and without feedback from staff as usualy). On march 2008 one guy has repeated the same question at another topic (where Melih was at moment); further: -- gimme link -- there is... after hour (HOUR! not week, month or half year) message from staff: -- yeah, issue reproduced & fixed - piece of cake - will be in next update. Huh? Three month of hemorrhoid and one hour for solution!
So. "Making double (triple... etc.) posts" may be effective 

BTW I have shut down most XP services that are not needed and I also use Windowblinds with a patched uxtheme. If I ran CHDSK I would get tons of errors but yet there is nothing wrong with my Windows install.

You entangled certainly: CHKDSK doesn't check OS system files (SCANDSK does), chkdsk checks file system (integrity, descriptors and such) - when any file or MFT record or cluster becomes corrupt, OS (not you) marks disk as 'dirty' and calls offline chkdsk procedure and if this unsuccessful, procedure scheduled again and again, entropy grows up, till bye-bye partition 

there are priorities. Most bug fixes are fixes that are important to the overall integrity of the program

I'm sure priority #1 is overall integrity of the system - just like incoming policy - global rules first

[Vettetech]

I know your right ei4ia. I know the difference between the 2. Sorry I didn't make my point more clear. But like I said I have never ever had to use CHKDSK. Did you make a bug report?

[ei4ia]

Did you make a bug report?

Already reported at Bugs/BSODs of course

[roberta]

Making double posts wont get your answer and sooner. I am sure Melih is aware of the problem but there are priorities. Most bug fixes are fixes that are important to the overall integrity of the program and being sure its lock tight against attacks. I have never ever used CHDSK is all my years of owing a pc (well over 15) nor have I ever had to. If Windows runs fine then leave it be. Hopefully your problem will be fixed soon but till then enjoy  one of the best free firewalls around. BTW I have shut down most XP services that are not needed and I also use Windowblinds with a patched uxtheme. If I ran CHDSK I would get tons of errors but yet there is nothing wrong with my Windows install.

Vettetech Please put your brain into gear before shooting off, Particularly when You Are Wrong....
Unfortunately, your attitude is Rather Tiresome.....

Thank You,
Have a Nice day,

Roberta

PS:
Btw, its long overdue for You to learn how CHKDSK works, & how important it is....
You have really been missing a great deal.....

[Vettetech]

I bow down. But prove to me where CHKDSK is extremely important and I will start using it.Instead of always complaining about when CHKDSK is going to be fixed try helping out others the way I do. Melih and other modders have giving thanks to me for helping out in the forums the way I do.

[egemen]

Already reported at Bugs/BSODs of course

Hi guys,

This is in our top priority list guys. It is being analyzed and will be fixed. Not a trivial bug(from reproducing to analysing) and thats why it is taking some time.

Sorry for the inconvenience this might have caused,

Egemen

[Vettetech]

Hi guys,

This is in our top priority list guys. It is being analyzed and will be fixed. Not a trivial bug(from reproducing to analysing) and thats why it is taking some time.

Sorry for the inconvenience this might have caused,

Egemen

 

[Leopard19]

thought the bug didn't matter that much in your opinion, what's up now OK that said you cannot seriously run Vista, XP or 2000 and ignore CHDSK at the same time, when data corruption occurs for example, and CHDSK recovers  stuff that has become unreadable for some reason, among other cases. Can't tell you how many times CHDSK has fixed stuff on my HDD. CHKDSK IS a major maintenance feature in Windows, and if there was a bug with CFP and CHKDSK, it was a priority to fix it. And I'm really glad that the devs have fixed that.

[Ehgreg]

Well of course its an important bug when after scheduling chkdsk after reboot you end up having to use "Last known good configuration to get back into windows". Anyway, someone please enlighten me as to how good or important chkdsk is when it first tell you there is some problems with the file system and when you DO allow chkdsk to fix these problems (/f), you find out there seems to be No REAL problem because all it ever does is report Cleaning up ____ unused index entries from index $SII of file 0x9, ($SDH of file 0x9) And mentions something about some free space in the Master file table... Over and Over and over.

Thx

[Ragwing]

Anyway, someone please enlighten me as to how good or important chkdsk is

Probably not too important, since I've been fine without for around 1 year, and not a single BSoD caused because I haven't ran it
I'm not 100% sure, but I think that it'll also restore missing/corrupt system files (?).

Cheers,
Ragwing

[Vettetech]

5 years on the same install of XP and not 1 BSOD or anything. Always boots up and runs great. I agree with Ragwing. BTW I was clapping and people happy for the users of CHKDSK. Not myself.

[egemen]

Hi Guys,

The problem seems to be related to FAT32 filesystems. As a temporary fix, converting FAT32 filesystem to a more stable and secure NTFS would fix the problem until we identify the root cause of the issue. This issue happens to be reproducable in *some* windows XP systems and reproducing is somehow difficult.

To convert a FAT32 disk into NTFS, the following steps can be followed:

1 - Go to Start->Run, type "cmd" and then press enter.
2 - type "CONVERT C: /FS:NTFS" to convert the volume "C:" into NTFS filesystem.
3 - press "Y"es to approve the messages shown and restart your PC.

After you restart your PC, your volume will be in NTFS file system and will be much stable and secure. This should fix the related BSOD problems too.

Hope this helps,

Egemen

[SS26]

The problem seems to be related to FAT32 filesystems

Maybe that's why i didn't succeed when tried to reproduce issue on my ntfs partitions.

[bey]

Hi Guys,

The problem seems to be related to FAT32 filesystems. As a temporary fix, converting FAT32 filesystem to a more stable and secure NTFS would fix the problem until we identify the root cause of the issue. This issue happens to be reproducable in *some* windows XP systems and reproducing is somehow difficult.

To convert a FAT32 disk into NTFS, the following steps can be followed:

1 - Go to Start->Run, type "cmd" and then press enter.
2 - type "CONVERT C: /FS:NTFS" to convert the volume "C:" into NTFS filesystem.
3 - press "Y"es to approve the messages shown and restart your PC.

After you restart your PC, your volume will be in NTFS file system and will be much stable and secure. This should fix the related BSOD problems too.

Hope this helps,

Egemen

Wrong!

I'm using NTFS and have the problem 

You can ask me anything related to the configuration or something to help you find the possible culprit, just send a PM or something!

Also, unlike some of the complaining users my problem isn't solved with second reboot or Last Known config. Only restoring a previous partition backup solves the problem. I get the session 5 BSOD and if i try to try a Last Known config i'll get a different BSOD as reported in the other thread.


Anyway i'm glad you're taking on this issue.

Cheers 

[Tags:]