Hi,
Is there any way that a file system filter driver can corrupt hal.dll such
that system can not be rebooted again and OS had to be reinstalled.
When testing my file system filter driver we once encountered this issue and
we had to reinstall OS. When system is rebooted I get following message
“On boot computer displayed missing HAL.dll - unbootable”
Any information is helpful.
Thanks,
Kedar.
kedar ha scritto:
Hi,
Is there any way that a file system filter driver can corrupt hal.dll such
that system can not be rebooted again and OS had to be reinstalled.When testing my file system filter driver we once encountered this issue and
we had to reinstall OS. When system is rebooted I get following message“On boot computer displayed missing HAL.dll - unbootable”
Any information is helpful.
Thanks,
Kedar.
Probably your minifilter intercepted a read or write of the hal.dll and
modified some data while it was working, and so it did corrupt the
hal.dll file, which is not bootable anymore now.
Think about how a file is stored on the media. There are three places
involved in FAT. The first is the root directory entry and the subdirectory
entries. The second are the actual disk sectors where the file is located.
The third is the FAT where the next cluster(s) is(are) located. On NTFS
there is something similar, but no FAT, just a MFT. If you trash any piece
of this chain you can loose a file either by destroying the data or the
normal means to access it (most likely). Write garbage to the wrong place
and it can happen, IOW.
“kedar” wrote in message news:xxxxx@ntfsd…
> Hi,
>
> Is there any way that a file system filter driver can corrupt hal.dll such
> that system can not be rebooted again and OS had to be reinstalled.
>
> When testing my file system filter driver we once encountered this issue
> and we had to reinstall OS. When system is rebooted I get following
> message
>
> “On boot computer displayed missing HAL.dll - unbootable”
>
> Any information is helpful.
>
> Thanks,
> Kedar.
>
>