Error on opening any file

[rojer_31]

Okay, just installed Filealyzer, and I keep getting this error whether I use the context menu or open from the program itself.

Here's the error message screenshot:
http://forums.spybot.info/attachment.php?attachmentid=109&stc=1&d=1134852903

This error pops up twice while opening up any file. Folders have no such problem. I'm using the latest version available for download.

Any help would be appreciated.

[LonnyRJones]

Hi rojer_31
I'm not sure what would cause that, Patric or another team member will be around when they can, in the meantime what operating system is it you have and which service packs are installed ?
Are you in an account that has administrative rights ?

[rojer_31]

I'm using Win 2000, SP4

Yes I am using an admin account.

256MB Ram, P4 2.4GHz.

Take your time, I would definitely like to solve the problem.

[paradj]

same problem i started having...
also on win2k sp4 [5.0.2195]

Machine Specs:
i810e trigem lomita
1.3ghz celeron
256Mb Ram
11Gb free contiguous harddrive space
MsIE 6.0.2800.1106IS
Office XP 2000
Office 2003

screenshot available here (http://www.hp-h.com/p/paradj/tshootimg/FileAlyzer_001.jpg)

altho FoldAlyzer seemingly has no problems

[PepiMK]

Seems to be the same as the other topic...

Is this on FAT32 or NTFS?
With normal or easy security settings (when choosing file properties, does the Security tab exist)?

According to Microsoft, this function is available on Windows 2000, the function that reads the ACL (GetFileSecurity) as well...

I'll provide a fix as soon as I located the source of the problem... which seems to be a missing DACL (discretionary access control list (http://msdn.microsoft.com/library/en-us/secgloss/security/d_gly.asp)).

[paradj]

Seems to be the same as the other topic...

Is this on FAT32 or NTFS?
With normal or easy security settings (when choosing file properties, does the Security tab exist)?

According to Microsoft, this function is available on Windows 2000, the function that reads the ACL (GetFileSecurity) as well...

I'll provide a fix as soon as I located the source of the problem... which seems to be a missing DACL (discretionary access control list).

FAT32
...and, um, what other topic?:confused:

Machine Specs:
i810e trigem lomita
1.3ghz celeron
256Mb Ram
11Gb free contiguous harddrive space
Windows 2000 Sp4 [5.00.2195]
MsIE 6.0.2800.1106IS
Office XP 2000
Office 2003

[paradj]

!doh! ..just read the other...
as for the "No Security tab on Property Sheet" this would only apply to the NTFS wouldn't it?


Machine Specs:
i810e trigem lomita
1.3ghz celeron
256Mb Ram
11Gb free contiguous harddrive space
Windows 2000 Sp4 [5.00.2195]
MsIE 6.0.2800.1106IS
Office XP 2000
Office 2003

[rojer_31]

using fat32. Idon't know about the security settings. But there is no security tab and am logged in as administrator.. (in win2000 sp4)

Do you need any other details?

[pinkydoo]

I am the one from other thread. Maybe this minor detail matters. On my system I have two keyboards installed. The other one is for a Right to Left written language. Does it hamper the functionality of FileAlyzer?

[PepiMK]

The keyboard should not have any effect on that. And I think I found and fixed the problem :)
Will release something to test asap...

[pinkydoo]

Thats great. Waiting anxiously. :D

[4S082LTJWV]

Dear M. PepiMK

I have same issue as the other forum posters. That is, I have a problem with alliteration.....oops....um....(Oops...I wasn't supposed to tell anyone but the doctors that stuff)....

I meant to say..... FileAlyzer 1.4 freezes when I open any file.

Win 2000, Serv Pack 4. NTFS.
have a Security tab on Property Sheet.
both I, as 'Adminstrator; and the 'System' have full permissions

I even tried to analyze very small .txt files. I had no problem using FileAlyzer 1.1 on these files. Because I am a big fan of yours and your Safer Networking effort, I was saddened to see this problem in FileAlyzer 1.4.



I noticed that so far it only seems to be affecting Win 2K users. So, just looking around a bit, here is what I found for you to consider.

It may be an issue of matching method to platform.

As you know, ConvertStringSecurityDescriptorToSecurityDescriptor can be used in Win2000
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/secauthz/security/convertstringsecuritydescriptortosecuritydescriptor.asp

However, ConvertSecurityDescriptor method (is for AD) and requires Vista or XP. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adsi/adsi/iadssecurityutility_convertsecuritydescriptor.asp




Just so you know, I may be completely off base. I am not a programmer, I just manage 'em. That makes me like the pointy haired boss in Dilbert.

So, if you would like, instead of calling me by my proper username of 4S082LTJWV, you can call me "Pointy Haired Guy", or "Pointy" for short.

I hope this helps, (at least for a laugh).


respectfully

4S082LTJWV (aka Pointy)



PS. Next week, I will be requesting an antigravity feature. My marketing people tell me that we could use "Gravity-Alesser" to sound similar to your other programs. By the way, did I say next week. I meant to say tomorrow........ by noon. Good......It's settled then. I'll bring the press in for a demo over a working lunch.


PPS. Could we make it breakfast? ...

I have a 1pm tee-time...


.