One huge zero padded text file!!! I would like to get rid of fidbox.dat, because it takes 4GB of space, and insists on becoming horribly fragmented. When trying to run this, a message saying AV is disabled appears. And fidbox soon fills my disk. http://apicsa.net/c-windows/c-windows-system32-drivers-pfc-sys.html
So fidbox.dat is used by that virus scanner. Learn More. I searched on Google and the only relevant info I can find is that it's used by Kaspersky Antivirus. Perhaps ESET, the publisher of NOD32, might have some way to fix the problem, as it does not occur with their back level version. 2.
So even though one of these functions is disabled, the other one forces the fidbox function to be present. Other than some occasional testing. Message Edited by Oldsod on 09-21-2008 11:07 PM jasimonSeptember 21st, 2008, 05:29 PMI believe I will do ahead and try your suggestions, along with the previous ones for removing the KAV I had divided my hard drive into a half-dozen partitions and installed Windows XP Pro in two of them, one for everyday use, the other to test new or beta programs.
I have stopped getting the annoying prompts thereafter. Best regards. Attached Files: PDBootLog.log File size: 3.6 KB Views: 1 On edge, Jan 31, 2009 #1 dlb MajorGeek How can I find out what program or process is behind these files?Click to oldsodSeptember 27th, 2008, 11:23 PMThe multiscan.exe is for the antivirus scanning in the ZAISS, whereas the ZA Pro uses the vsmon.exe for the antispywre scanning (along with the srescan sys and
Oldsod. In any case, some useful alternative approaches. Have "played" with the ZA pro versions and have made successful personal customizations. jazziSeptember 29th, 2008, 11:54 AM
jasimon wrote: I understand that fidbox.dat is used by the Kaspersky AV embedded with ZASS.
Oldsod. Revert NOD32 to a previous version. Machines that do not have the problem -- leave them alone. Maybe if it does not scan the file, then the file will stay the same.
I do not need to use this function, as I use NOD32 for AV. One way might be if ZASS allowed command line options to run an anti-spyware scan, but I have not found any yet. The same svchost.exe went to perform the same operations on fltmgr.sys, ftdisk.sys, hdaudio.sys, ... It was located in C:\WINDOWSSystem32\drivers and nearly 500mb in size.
More than likely it is listed in one or more of the .xml files of the ZA - use the notepad.exe and just delete the entire line with the fidbox.dat entry this content Join 91230 other members! So what else can I do now? 0 #4 Broni Posted 28 August 2009 - 10:15 PM Broni Kraków my love :) Member 12,300 posts What CD did you out in? C:\Program Files\Huawei technologies\Vodafone ... \Vodafone 3G Broadband Modem.exe Samsung Electronics.
Caution: During the testing of Video Adapter, a variety of patterns, shapes, colors and text are “flashed” onto the users monitor screen. The Details > Device Instance ID was ROOT\LEGACY_KLIF. And see what happens once in the normal mode. weblink Back to top #11 JEtkins JEtkins Occasional Forum Poster Members 51 posts Posted 26 September 2008 - 07:36 PM OK, I need to eat some humble pie - it failed appears
Back to top #6 Mickeyjoe Mickeyjoe New Member New Member 5 posts Posted 06 December 2007 - 08:27 AM You do not mention any system performance problems. Reboot. 5. The followingerror occurred: %%1223.Your computer will continue to try and obtain an address on its own fromthe network address (DHCP) server.Event Record #/Type17182 / WarningEvent Submitted/Written: 03/15/2008 10:52:25 AMEvent ID/Source: 1003
Back to top #4 don77 don77 Forum Regular Members 3,212 posts OFFLINE Gender:Male Location:Boston Mass Local time:01:20 PM Posted 15 March 2008 - 11:00 PM Nothing really showing here still
Note: it is critical to disable the scanning during the initial install of ZASS on a clean system or it is "too late." I don't know how this latter approach would Thanks. Yes it is a known problem and ideally it would not happen at all, but the point i made, is that to be in a situation where you need to use Also worth a note: I've had procmon on while typing this, and I just noticed that svchost had accessed fidbox.dat last at 3:03:09 PM (another FASTIO_NETWORK_QUERY_OPEN).
The command is multiscan.exe c:/ to scan the c drive, where multiscan.exe is in the ZoneAlarm program root directory. No, create an account now. Please advise as how to remove fidbox.dat. http://apicsa.net/c-windows/c-windows-system32-drivers-floppy-sys.html Run Kaspersky Anti-Virus 6.0 for Windows Servers Enterprise Edition either via the console or by running the following command in the command prompt: net start kavfs Warning Important: o no anti-virus
Oldsod. C:\WINDOWS\system32\PDesk\PDesk.exe Matrox BiosGuard Matrox Graphics Inc. Information Pay attention, this file has the hidden attribute. 4. WE'RE SURE THAT YOU'LL LOVE US!
I have also noticed that chdsk run about a reboot does take a very long time during phase 2 compared to what I would expect. Register now to gain access to all of our features, it's FREE and only takes one minute. On top of everything I caught a dose of laryngitis that put me out of action for a couple days. However ("just delete it") is a rather risky way to handle something that may not be causing difficulty now.
SVI is a protected folder which I cannot access. Rather it is ZASS scanning any file, which then causes fidbox to do something to store something about that file. Those terms pop-up within legitimate reg keys, but they also lead me to a number of leftover Kaspersky entries: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\KLIF and various LEGACY_is-[8 caharacter] entries across different ControlSets.