BSOD after upgrade to 1.4

[rinkejas]

Fujitsu laptop - P4, 768MB ram, WinXP SP1

Was running Filealyzer 1.1. Installed 1.4 without uninstalling 1.1.

Right clicking on a file and selecting Filealyzer instantly causes BSOD.

I have uninstalled all (I think) remnants of 1.1 and 1.4, including cleaning up registry with Registry Mechanic.

Restarted laptop, installed 1.4. Upon attempted use I got BSOD. So I went through uninstall exercise again and tried installing 1.2. Tried to use it and got BSOD.

I've installed same 1.4 on my tower PC and it works fine, so the file must be ok.

BTW, nothing else on my laptop has ever caused BSOD.

Help please!

[tashi]

Hello rinkejas

Are you still experiencing the same problem?

[rinkejas]

Hi Tashi,
Problem still exists, I've tried load/remove 1.4 a number of times on the laptop. As soon as I try to view a file, it crashes the machine with BSOD. Something from the original 1.1 must be buried somewhere in the registry. I'm at a loss.

Thanks,
rinkejas

[PepiMK]

Does this depend on the type of file you try to open? E.g. it crashed on .exe but loads on .txt?

Do you have the BSOD error message (not everything, just the text from the first two lines)?

We've fixed a number of mostly invisible bugs in the past weeks, and after adding a beta disassembler view, there'll be a new version :)

[rinkejas]

I will reinstall and capture the BSOD data. I know it crashed on .exe, I think it crashed on .avi/.mpg.

I will test tomorrow and let you know.

Tnx,
rinkejas

[rinkejas]

Hi PepiMK:
Reinstalled 1.4. Right-clicked on a small .txt file and selected analyze... BSOD

STOP: 0x0000008E (0xc0000005, 0xA9686703, 0xA9470c70, 0x00000000)

I can send you minidump if you want it.

TNX

[Rosenfeld]

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/DevTest_g/hh/DevTest_g/t05_bugs_60_299217d6-98d1-4d1d-8068-883e89933845.xml.asp

[PepiMK]

I'm sorry, I was delayed in finishing the disassembler by PivotPro which ran havoc on both machines I usually use. Will hopefully have a new version to test tomorrow.

A kernel mode exception is nothing that could/should come from FileAlyzer directly though; maybe it's some kind of bad driver? The new version may work better though since it handles memory for a few special system calls better.

[PepiMK]

Ok, please download this (http://www.safer-networking.org/files/filealyzer-152-beta.zip) and extract it over your existing installation, it should replace the main executable with a newer version (1.5.2 beta). The disassembler isn't completely finished yet (that's why it's beta), but I've tested with all supported file types and couldn't find any memory leaks or other irregularities (from the code standpoint, logical problems could always still exist of course ;) ) any more.

[rinkejas]

I unzipped over 1.4. I right-clicked over a txt file, it started to launch FileAlyzer (showed in the toolbar) then BSOD.

What do I need to do to completely remove any traces of Filealyzer? I'd like to reinstall 1.1f. That worked on my machine.

Thanks!

[PepiMK]

Since I'm inspired by the Apple Mac concepts a lot, I'm careful that our applications are similarly independent than Mac apps; users should be able to move them etc..

Therefore, FileAlyzer.exe and UnzDll.dll are the only files you need to replace with the 1.1 version. No system drivers etc. are in place. The only bad thing is that 22 years later, Microsoft still hasn't got a proper alias manager, so you'll have to use regedit. Well, or lets say that it can't harm. Open regedit, then navigate to HKEY_CLASSES_ROOT\*\shell\. There, delete the subkey named filealyzer.

There's another file you may remove, it's not related, but belongs to FileAlyzer as well; go to C:\Documents and Settings\Username\SendTo\ and delete the FileAlyzer link there as well.