• Gradual out of disk space - fidbox.dat

    From rhhardin@mindspring.com@1:124/5013 to All on Thu Jan 3 09:08:36 2019
    Path: eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!f eeder.erje.net!2.eu.feeder.erje.net!newspeer1.nac.net!border2.nntp.dca1.giganew s.com!nntp.giganews.com!buffer2.nntp.dca1.giganews.com!nntp.earthlink.com!news. earthlink.com.POSTED!not-for-mail
    NNTP-Posting-Date: Tue, 03 Jan 2017 09:08:25 -0600
    Message-ID: <586BBE74.4BF3@mindspring.com>
    Date: Tue, 03 Jan 2017 10:08:36 -0500
    From: Ron Hardin <rhhardin@mindspring.com>
    X-Mailer: Mozilla 2.02 (WinNT; I)
    MIME-Version: 1.0
    Newsgroups: microsoft.public.windowsxp.help_and_support
    Subject: Gradual out of disk space - fidbox.dat
    Content-Type: text/plain; charset=us-ascii
    Content-Transfer-Encoding: 7bit
    Lines: 25
    X-Usenet-Provider: http://www.giganews.com
    NNTP-Posting-Host: 71.54.70.210
    X-Trace: sv3-pgEwfdiKI3AP/HPBw14YAJL7nqZ78uaGSiyxuyNg5/JAiy6MM4fER3pKF8JCeATNYDEMGbY/SLb JWWl!TaXy7frGjOWlSMOfQ0rwI0ZSnEFs1ynobKwsyB7Jmbj92Z2O478wyJ+CsTktGU20hkWZcXGaco dH!uRUmWFJjaA==
    X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
    X-Postfilter: 1.3.40
    X-Original-Bytes: 1570
    Xref: news.eternal-september.org microsoft.public.windowsxp.help_and_support:31880

    In case anybody didn't know about it, there's a
    remnant from some popular virus scanner that gives
    you a growing file that eventually gets big enough
    to matter.

    c:WINDOWS/system32/drivers/fidbox.dat

    It's harmless to delete (and will grow again over
    a period of months) but you have to be in safe
    mode.

    A smaller one

    c:WINDOWS/system32/drivers/fidbox.idx

    can be deleted at the same time.

    The feature stays there long after the virus
    scanner has gone.

    It's worthwhile to check if you have them.
    --
    rhhardin@mindspring.com

    On the internet, nobody knows you're a jerk.
    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From V@nguard.LH@1:124/5013 to All on Thu Jan 3 13:44:32 2019
    Path: eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!n ews.unit0.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
    From: VanguardLH <V@nguard.LH>
    Newsgroups: microsoft.public.windowsxp.help_and_support
    Subject: Re: Gradual out of disk space - fidbox.dat
    Date: Tue, 3 Jan 2017 13:44:32 -0600
    Organization: Usenet Elder
    Lines: 36
    Sender: VanguardLH <>
    Message-ID: <ed2d90Fa2poU1@mid.individual.net>
    References: <586BBE74.4BF3@mindspring.com>
    Mime-Version: 1.0
    Content-Type: text/plain; charset="us-ascii"
    Content-Transfer-Encoding: 7bit
    X-Trace: individual.net 6xwmeiAeA/RqwcNPNSk6MgoaHFF+ZEkE7Tfc8orNpcRITuAhzr Keywords: VanguardLH VLH811
    Cancel-Lock: sha1:xDMRsM+/Losl9GuD/C/rF/sL/LY=
    User-Agent: 40tude_Dialog/2.0.15.41
    Xref: news.eternal-september.org microsoft.public.windowsxp.help_and_support:31881

    Ron Hardin <rhhardin@mindspring.com> wrote:

    In case anybody didn't know about it, there's a remnant from some
    popular virus scanner that gives you a growing file that eventually
    gets big enough to matter.

    c:WINDOWS/system32/drivers/fidbox.dat

    It's harmless to delete (and will grow again over a period of months)
    but you have to be in safe mode. A smaller one

    c:WINDOWS/system32/drivers/fidbox.idx

    can be deleted at the same time.

    The feature stays there long after the virus scanner has gone. It's worthwhile to check if you have them.

    How is that info going to help anyone since you deliberately chose to
    omit WHICH anti-virus program is modifying that file? There a tons of anti-virus programs available. Your post is like saying "A certain
    program to remain unnamed will crash the OS when you use its File ->
    Save dialog". Uh huh, yeah, like who would know what to look out for.

    If the "feature stays there long after the virus scanner is gone", where
    "gone" is assumed to mean uninstalled, then the program wasn't really uninstalled, was it? It's still there updating that file. Perhaps the
    partial uninstall is why the remnant process doesn't properly manage
    that file. Some anti-virus software has an incomplete uninstall which
    not only leaves behind remnant registry entries and files but also
    leaves behind remnant active processes; however, you won't name the
    crappy software. Thanks for nothing.

    Is it a secrete anti-virus program that you created for only your own
    use or software that only you are supposed to know about? Without
    identifying specifics, you're just spreading FUD.
    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From rhhardin@mindspring.com@1:124/5013 to All on Thu Jan 3 16:10:48 2019
    Path: eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!n ews.glorb.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!b order1.nntp.dca1.giganews.com!nntp.giganews.com!buffer1.nntp.dca1.giganews.com! buffer2.nntp.dca1.giganews.com!nntp.earthlink.com!news.earthlink.com.POSTED!not -for-mail
    NNTP-Posting-Date: Tue, 03 Jan 2017 16:10:35 -0600
    Message-ID: <586C2167.1114@mindspring.com>
    Date: Tue, 03 Jan 2017 17:10:47 -0500
    From: Ron Hardin <rhhardin@mindspring.com>
    X-Mailer: Mozilla 2.02 (WinNT; I)
    MIME-Version: 1.0
    Newsgroups: microsoft.public.windowsxp.help_and_support
    Subject: Re: Gradual out of disk space - fidbox.dat
    References: <586BBE74.4BF3@mindspring.com> <ed2d90Fa2poU1@mid.individual.net> Content-Type: text/plain; charset=us-ascii
    Content-Transfer-Encoding: 7bit
    Lines: 50
    X-Usenet-Provider: http://www.giganews.com
    NNTP-Posting-Host: 71.54.70.210
    X-Trace: sv3-4PPreWUS9kiMyFySgYXG4F63/BN/Ft9esmEfI2NQcJvOfDUU6be/qpDrn/4sjUbWAzZzNlI+c3N Ek84!iN4+cnzVWr6U7EQTgQpKX7ioASsDR5nlifCmGlDlJwbwiUaeoMnQx7UBdFI8mjWHFfnjw2eElY B3!bCXHDrQTrA==
    X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
    X-Postfilter: 1.3.40
    X-Original-Bytes: 3223
    X-Received-Bytes: 3345
    X-Received-Body-CRC: 3044390240
    Xref: news.eternal-september.org microsoft.public.windowsxp.help_and_support:31882

    VanguardLH wrote:

    Ron Hardin <rhhardin@mindspring.com> wrote:

    In case anybody didn't know about it, there's a remnant from some
    popular virus scanner that gives you a growing file that eventually
    gets big enough to matter.

    c:WINDOWS/system32/drivers/fidbox.dat

    It's harmless to delete (and will grow again over a period of months)
    but you have to be in safe mode. A smaller one

    c:WINDOWS/system32/drivers/fidbox.idx

    can be deleted at the same time.

    The feature stays there long after the virus scanner has gone. It's worthwhile to check if you have them.

    How is that info going to help anyone since you deliberately chose to
    omit WHICH anti-virus program is modifying that file? There a tons of anti-virus programs available. Your post is like saying "A certain
    program to remain unnamed will crash the OS when you use its File ->
    Save dialog". Uh huh, yeah, like who would know what to look out for.

    If the "feature stays there long after the virus scanner is gone", where "gone" is assumed to mean uninstalled, then the program wasn't really uninstalled, was it? It's still there updating that file. Perhaps the partial uninstall is why the remnant process doesn't properly manage
    that file. Some anti-virus software has an incomplete uninstall which
    not only leaves behind remnant registry entries and files but also
    leaves behind remnant active processes; however, you won't name the
    crappy software. Thanks for nothing.

    Is it a secrete anti-virus program that you created for only your own
    use or software that only you are supposed to know about? Without identifying specifics, you're just spreading FUD.

    I think it's a common module from Kapersky code. Just check if you have the file.

    It's a roach motel kind of thing. It stays behind no matter what.

    I think for instance Zone Alarm installs it, and maybe AVG, in old versions at least.

    Harmless to delete but it will grow again and you delete again after a few months.
    --
    rhhardin@mindspring.com

    On the internet, nobody knows you're a jerk.
    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From V@nguard.LH@1:124/5013 to All on Thu Jan 3 17:30:30 2019
    Path: eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!n ews.unit0.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
    From: VanguardLH <V@nguard.LH>
    Newsgroups: microsoft.public.windowsxp.help_and_support
    Subject: Re: Gradual out of disk space - fidbox.dat
    Date: Tue, 3 Jan 2017 17:30:30 -0600
    Organization: Usenet Elder
    Lines: 76
    Sender: VanguardLH <>
    Message-ID: <ed2qgmFdckfU1@mid.individual.net>
    References: <586BBE74.4BF3@mindspring.com> <ed2d90Fa2poU1@mid.individual.net> <586C2167.1114@mindspring.com>
    Mime-Version: 1.0
    Content-Type: text/plain; charset="us-ascii"
    Content-Transfer-Encoding: 7bit
    X-Trace: individual.net hOmbmHcDwECCX9xccm8jbgj6vQFPoAWzxqWTpqKP0zve/xpUxM Keywords: VanguardLH VLH811
    Cancel-Lock: sha1:2AratJb0s9LvmrLUmVihAVdiwZo=
    User-Agent: 40tude_Dialog/2.0.15.41
    Xref: news.eternal-september.org microsoft.public.windowsxp.help_and_support:31883

    Ron Hardin <rhhardin@mindspring.com> wrote:

    VanguardLH wrote:

    Ron Hardin <rhhardin@mindspring.com> wrote:

    In case anybody didn't know about it, there's a remnant from some
    popular virus scanner that gives you a growing file that eventually
    gets big enough to matter.

    c:WINDOWS/system32/drivers/fidbox.dat

    It's harmless to delete (and will grow again over a period of months)
    but you have to be in safe mode. A smaller one

    c:WINDOWS/system32/drivers/fidbox.idx

    can be deleted at the same time.

    The feature stays there long after the virus scanner has gone. It's
    worthwhile to check if you have them.

    How is that info going to help anyone since you deliberately chose to
    omit WHICH anti-virus program is modifying that file? There a tons of
    anti-virus programs available. Your post is like saying "A certain
    program to remain unnamed will crash the OS when you use its File ->
    Save dialog". Uh huh, yeah, like who would know what to look out for.

    If the "feature stays there long after the virus scanner is gone", where
    "gone" is assumed to mean uninstalled, then the program wasn't really
    uninstalled, was it? It's still there updating that file. Perhaps the
    partial uninstall is why the remnant process doesn't properly manage
    that file. Some anti-virus software has an incomplete uninstall which
    not only leaves behind remnant registry entries and files but also
    leaves behind remnant active processes; however, you won't name the
    crappy software. Thanks for nothing.

    Is it a secrete anti-virus program that you created for only your own
    use or software that only you are supposed to know about? Without
    identifying specifics, you're just spreading FUD.

    I think it's a common module from Kapersky code. Just check if you have the
    file.

    It's a roach motel kind of thing. It stays behind no matter what.

    I think for instance Zone Alarm installs it, and maybe AVG, in old versions
    at least.

    Harmless to delete but it will grow again and you delete again after a few
    months.

    Here's what I found for Kaspersky:

    https://support.kaspersky.com/1700

    While that article discusses the Enterprise edition, the feature may be available in other editions.

    My recollection of Kaspersky (but it might've been a different
    anti-virus program) was that it use alternate data streams of files to
    record whether or not a file had already been tested. A hash and flag
    got recorded in a file's alternate stream to identify the file (the hash
    would check if the file had been changed since the last time it got
    recorded) and the flag said whether that file already got tested or not.
    That way, the AV scanner did not have to spend time retesting the same unchanged files over and over. Alternate data streams are a property of
    NTFS so you must be using that file system to make use of ADS

    https://en.wikipedia.org/wiki/NTFS#Alternate_data_streams_.28ADS.29

    Apparently either Kaspersky abandoned using ADS or it was something else
    that used ADS to track scanned files. Instead of using ADS, Kaspersky
    is [now] using its own database.

    However, if you uninstalled Kaspersky per your "The feature stays there
    long after the virus scanner has gone" then having any of its process
    lingering around to continue building the database sure makes it look
    like you did not [completely] uninstall Kaspersky.
    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From jj4public@vfemail.net@1:124/5013 to All on Fri Jan 4 01:56:14 2019
    Path: eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!n ews.albasani.net!.POSTED!not-for-mail
    From: JJ <jj4public@vfemail.net>
    Newsgroups: microsoft.public.windowsxp.help_and_support
    Subject: Re: Gradual out of disk space - fidbox.dat
    Date: Wed, 4 Jan 2017 14:56:14 +0700
    Organization: ?
    Lines: 18
    Message-ID: <divrdots4eqw$.1hvv08obkia5u.dlg@40tude.net>
    References: <586BBE74.4BF3@mindspring.com> <ed2d90Fa2poU1@mid.individual.net> <586C2167.1114@mindspring.com>
    Mime-Version: 1.0
    Content-Type: text/plain; charset="us-ascii"
    Content-Transfer-Encoding: 7bit
    X-Trace: news.albasani.net v6eSZ96V2vji3wvb8sjnhXbAQub9skqmN/YZVjFw/Bt1leF18jaYFsgVE79GEYVnEeU5VWvB0RZDj5X tg//Cpw==
    NNTP-Posting-Date: Wed, 4 Jan 2017 07:56:14 +0000 (UTC)
    Injection-Info: news.albasani.net; logging-data="lAP6x4oEJUOaCvLs7LbH3tLs9MQK3JavIzK+NylCr5myAmzYLlg4tvkxGjkppIhpV T6QgTMVSJmpr/iaE0YON7v8Md7Eog09cmzoV4NPs6FLB+GD3B88LmZZg3iFXQcH"; mail-complaints-to="abuse@albasani.net"
    User-Agent: 40tude_Dialog/2.0.15.84
    X-Face: \*\`0(1j~VfYC>ebz[&O.]=,Nm\oRM{of,liRO#7Eqi4|!]!(Gs=Akgh{J)605>C9Air?pa d{sSZ09u+A7f<^paR"/NH_#<mE1S"hde\c6PZLUB[t/s5-+Iu5DSc?P0+4%,Hl
    Cancel-Lock: sha1:1rdOvlNaZmTB2h533NYHndYciBc=
    Xref: news.eternal-september.org microsoft.public.windowsxp.help_and_support:31884

    On Tue, 03 Jan 2017 17:10:47 -0500, Ron Hardin wrote:

    I think it's a common module from Kapersky code. Just check if you have the
    file.

    It's a roach motel kind of thing. It stays behind no matter what.

    I think for instance Zone Alarm installs it, and maybe AVG, in old versions
    at least.

    Harmless to delete but it will grow again and you delete again after a few
    months.

    Try going into safe mode, delete that file, then create a subfolder using
    the exact name. i.e.

    c:\WINDOWS\system32\drivers\fidbox.dat

    If whichever software is creating that file doesn't complain and doesn't
    delete that subfolder and replace it with a file, it'll never eat the disk space again.
    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From michaeljohnnovilla@gmail.com@1:124/5013 to All on Thu Jan 31 19:14:23 2019
    X-Received: by 10.129.101.133 with SMTP id z127mr7331885ywb.148.1491227198954;
    Mon, 03 Apr 2017 06:46:38 -0700 (PDT)
    X-Received: by 10.157.47.183 with SMTP id r52mr438818otb.12.1491227198916;
    Mon, 03 Apr 2017 06:46:38 -0700 (PDT)
    Path: eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!1 .eu.feeder.erje.net!feeder.erje.net!2.us.feeder.erje.net!weretis.net!feeder6.ne ws.weretis.net!feeder.usenetexpress.com!feeder1.iad1.usenetexpress.com!border1. nntp.dca1.giganews.com!nntp.giganews.com!n37no4837449qtb.0!news-out.google.com! m191ni19057itc.0!nntp.google.com!y18no3631595itc.0!postnews.google.com!glegroup sg2000goo.googlegroups.com!not-for-mail
    Newsgroups: microsoft.public.windowsxp.help_and_support
    Date: Mon, 3 Apr 2017 06:46:38 -0700 (PDT)
    In-Reply-To: <586BBE74.4BF3@mindspring.com>
    Complaints-To: groups-abuse@google.com
    Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=112.198.243.222;
    posting-account=d4G_9woAAACGVEJVI8HWTPVReXSj5iF9
    NNTP-Posting-Host: 112.198.243.222
    References: <586BBE74.4BF3@mindspring.com>
    User-Agent: G2/1.0
    MIME-Version: 1.0
    Message-ID: <5ee94f73-55c0-4d2e-ad66-3ef743cbae25@googlegroups.com>
    Subject: Re: Gradual out of disk space - fidbox.dat
    From: "Microsoft.public.Windowsxp.help_and_support" <michaeljohnnovilla@gmail.com>
    Injection-Date: Mon, 03 Apr 2017 13:46:38 +0000
    Content-Type: text/plain; charset=UTF-8
    Lines: 26
    Xref: news.eternal-september.org microsoft.public.windowsxp.help_and_support:31900

    On Tuesday, 3 January 2017 23:08:32 UTC+8, Ron Hardin wrote:
    In case anybody didn't know about it, there's a
    remnant from some popular virus scanner that gives
    you a growing file that eventually gets big enough
    to matter.

    c:WINDOWS/system32/drivers/fidbox.dat

    It's harmless to delete (and will grow again over
    a period of months) but you have to be in safe
    mode.

    A smaller one

    c:WINDOWS/system32/drivers/fidbox.idx

    can be deleted at the same time.

    The feature stays there long after the virus
    scanner has gone.

    It's worthwhile to check if you have them.
    --
    rhhardin@mindspring.com

    On the internet, nobody knows you're a jerk.
    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)