Help - Search - Members - Calendar
Full Version: kaspersky AV 7.0 : BSOD
UBCD4Win Forums > Other Support > Plugin Repository & Commercial software support
legolaz
Hello all,

I'm using the great plugins KAV6 and now KAV7 made by Hilander999 (Thank you for your great work by the way!)

But since I've downloaded UBCD4WIN 3.0.10 and using the KAV7 Plugin, I've got some troubles :

When I launch the plugin, I've got a BSOD regarding FLTMGR.SYS.

I've noticed that If I activate my old KAV6 plugin (another than Hilander's plugin), the KAV7 plugin is launching without any trouble.

Any help will be greatly appreciated
legolaz
QUOTE (legolaz @ Jan 28 2008, 07:55 AM) *
Hello all,

I'm using the great plugins KAV6 and now KAV7 made by Hilander999 (Thank you for your great work by the way!)

But since I've downloaded UBCD4WIN 3.0.10 and using the KAV7 Plugin, I've got some troubles :

When I launch the plugin, I've got a BSOD regarding FLTMGR.SYS.

I've noticed that If I activate my old KAV6 plugin (another than Hilander's plugin), the KAV7 plugin is launching without any trouble.

Any help will be greatly appreciated



MMMMM I think I know what is going wrong... I've used the static plugin from Vista and my PE is ... XP Based...

Kaspersky Drivers are not the same. I will try using the dll and sys files of my old plugins smile.gif

SteelTrepid
Actually, are you using 32bit or 64bit Vista?
All current versions of Kaspersky are 32bit, so that is not the problem.
Any MS 64 bit OS (XP 64 & Vista 64) that we have seen has a different registry structure and cause hell with our current plugins.
legolaz
QUOTE (SteelTrepid @ Jan 28 2008, 09:39 PM) *
Actually, are you using 32bit or 64bit Vista?
All current versions of Kaspersky are 32bit, so that is not the problem.
Any MS 64 bit OS (XP 64 & Vista 64) that we have seen has a different registry structure and cause hell with our current plugins.


It's a 32bit Os.

I don't get it... Have you another explanation ? I will try today to use klif.sys from my old XP plugin.

Thanks for the reply
legolaz
It seems that FLTMGR.sys (located in I386 Directory) crashes with my VISTA plugin. (I don't have XP with Kav7 installed to build a static plugin... sad.gif)

Do you know if this system file is depending on plugins in PEbuilder ?

Seems that kaspersky 7 is depending on this file, I don't know why... Also, I don't understand why it works when I activate my old KAV6 Plugin
legolaz
It works !!! I've replaced FLTMGR.sys from my vista to FLTMGR.SY_ in my input system folder (I386).

Dunno why it was crashing with this old system file...

Any ideas are welcome
hilander999
Help me understand:

Your building ubcd4win on a vista32 system.
your using XP SP2 as the source with NO OTHER PATCHES OR DRIVERS ADDED. (Only a slipstreamed SP2)
When you run kaspersky 7 from the booted ubcd4win it BSOD's.

You then replaced the file "FLTMGR.sys" that is included in XP SP2 with the same file from your vista32 dvd? (Or directly from the \windows\drivers folder?)

What other plugins are you using?
Search all added plugins for "FLTMGR.sys" and see if you have a strange file being added to the output directory.
Some Acronnis programs replace this file with a modified version.

I can easily modify the plugin to replace the file from either the xp source or the installed OS that you are building on but I need some more details because I cannot reproduce your error.


NOTE: KLIF.SYS is a protection routine for kaspersky and may not be needed at all.
I tried to work with the inf files provided by kaspersky because I figured the programer that wrote that software would know what was needed to make it work in a pe build, however I have found quite a few major errors in thier logic so the changes being made will reflect that also. I have a working beta plugin the is compatable with vista64 and need your feedback before I can get it out for testing.

BTW:
QUOTE
I'm using the great plugins KAV6 and now KAV7 made by Hilander999 (Thank you for your great work by the way!)

This is something I get very little of, honestly I do appreciate it when someone says THANK YOU. This is a mostly thankless use of what little free time I get these days meaning that most of the time we only get feedback from our userbase when I mess something up and there is a problem with one of my plugins. You are very welcome and thinks again (in advance) for taking the time to answer my questions about your BSOD.

I'm really guessing that you have an acronis plugin in your build and if that is true, does that program also work with the replaced filtmgr.sys file?
legolaz
Thank you, Hilander, for taking time to read this topic and try to understand (and reproduce) my BSOD.

QUOTE
Your building ubcd4win on a vista32 system.
your using XP SP2 as the source with NO OTHER PATCHES OR DRIVERS ADDED. (Only a slipstreamed SP2)
When you run kaspersky 7 from the booted ubcd4win it BSOD's.


Exactly.

QUOTE
You then replaced the file "FLTMGR.sys" that is included in XP SP2 with the same file from your vista32 dvd? (Or directly from the \windows\drivers folder?)


From my \windows\system32\drivers path

QUOTE
What other plugins are you using?
Search all added plugins for "FLTMGR.sys" and see if you have a strange file being added to the output directory.
Some Acronnis programs replace this file with a modified version.


I'm using a lot of plugins under XPE 1.0.7. Actually, I was trying to adapt your plugin on my XPE boot CD.

[Off Topic]
BTW, under my XPE build, your plugin I've modified is updating without any trouble. That rocks. I don't know if it is the same under UBCD4win because I don't have tried since I found the workaround. The old KAV6 plugins was not updating without FBWF plugin.
(I can post my modifications if you need/want).
[/Off Topic]

When I realize that your plugin was crashing my XPE, I've tried UBCD4win WITHOUT ANY PLUGINS except those embedded.

QUOTE
I'm really guessing that you have an acronis plugin in your build and if that is true, does that program also work with the replaced filtmgr.sys file?


You are guessing really well : I use Acronis True Image Server 9.1 with upperfilters active, but only under my XPE build.

For now, I've got nothing to report as problems with Acronis, and with any other plugins.

As I said, under UBCD4WIN, I don't have added any plugins : I've downloaded the .exe, launching the pebuilder ubcd, go to the plugins window, configure the plugin with your nice script (static mode) and build.

I use virtual box for all my tests but I've also try to burn the build.

QUOTE
This is something I get very little of, honestly I do appreciate it when someone says THANK YOU. This is a mostly thankless use of what little free time I get these days meaning that most of the time we only get feedback from our userbase when I mess something up and there is a problem with one of my plugins. You are very welcome and thinks again (in advance) for taking the time to answer my questions about your BSOD.


That's normal dude, you do an excellent job as all the people who works on releases/plugins and who shares their work and time with us ! !

Hope that my english is not so nasty smile.gifand don't hesitate to correct / add / ask anything you need / want smile.gif
hilander999
Updating does work in ubcd4win, the environment may have additional values then XPE.

Boot your XPE and from a CMD prompt, type SET and post the entire screen output. You can use "SET >B:\ENV_LIST.TXT" to create a file on the ramdrive.

Also post your modifications which are probbly adjustments to the environment settings.
legolaz
QUOTE (hilander999 @ Jan 31 2008, 10:27 AM) *
Updating does work in ubcd4win, the environment may have additional values then XPE.

Boot your XPE and from a CMD prompt, type SET and post the entire screen output. You can use "SET >B:\ENV_LIST.TXT" to create a file on the ramdrive.

Also post your modifications which are probbly adjustments to the environment settings.


indeed... I've just modified temp=%tmp% environment variables to temp=%b:% which is my ramdrive of course.

This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2008 Invision Power Services, Inc.