IFSMGR(04) + 000129D0 etc

Hi all. One to store in the memory banks for future reference.

Recently had a problem with this message...
IFSMGR(04) + 000129D0 : OE :0028 : C02B2CDC

IFSMGR = Microsoft Installable File System Manager

I was unable to find any reference to this exact code anywhere (MS,
google etc).

This only started after a recent upgrade from Win98 to Win ME.

Eventually I realised that it would occur only when a program was trying
to read a dir (folder) for a file listing. Didn't matter if it was my
database program (DOS based Paradox 4.5 reading a directory to present a
picklist of files, which was my initial thought), WinZip after starting
when I clicked open and it was to present a file pick list or Power Desk
Pro when trying to list a folder ... etc. Seemed like any program that
tried to read a directory off of a drive brought up this message. Exiting
from the error caused windows to crash, requiring a reboot with a
consequent sacndisk.

I tried all sorts of cures and was ready to revert to Win98 when I
remembered something on my PC. And it cured the problem too.

A year or so ago, while still using Win98, I used a program called "Hide
Folders" to hide a couple of folders from a flatmate who would use my PC
to check his emails. It ran at boot time and effectively hid the folders
from him. When he left I disabled the program from running at boot-time,
the hidden folders were restored to any directory listing etc. However I
never "uninstalled" the program. I had its own directory with its files
..... but also had one file (a .dll) in win\system dir.

An uninstall of this program has cured my IFSMGR error. And I am a happy
chappy again

--
aardvark (ard'-vark) a controversial animal with a long probing nose used
for sniffing out the facts and stimulating thought and discussion.

Doc ] wrote in
:


A year or so ago, while still using Win98, I used a program called
"Hide Folders" to hide a couple of folders from a flatmate who would
use my PC to check his emails. It ran at boot time and effectively hid
the folders from him. When he left I disabled the program from running
at boot-time, the hidden folders were restored to any directory
listing etc. However I never "uninstalled" the program. I had its own
directory with its files .... but also had one file (a .dll) in
win\system dir.

Forgot to mention ...... it wasn't only the folders that were previously
'hidden' that caused the error, it was ANY folder that a program tried to
read for a file LISTING. Emphasis on "LISTING" ..... the crash only ever
occured when a file list was required ..... file access by running
programs was normal.

The 'rogue' program "Hide Folders" would also allow program access to
'hidden' files, it just prevented 'viewing' and 'navigation' to the
folders.

I still wonder HOW a programs DLL ( a program NOT activated at run time )
could have had this effect.

--
aardvark (ard'-vark) a controversial animal with a long probing nose used
for sniffing out the facts and stimulating thought and discussion.

The program added a shell extension and it appears that the DLL involved
is/was incompatible with Win Me. Such shell extensions are loaded each time
the system is booted. Many programs install shell extension whether it be to
add additional columns to Windows Explorer detailed view or to add right click
functionality.

A useful tool that shows which shell extensions you have installed and also
allows them to be temporarily disabled is ShellExView
(http://freehost14.websamba.com/nirso.../shexview.html).

--
Mike Maltby MS-MVP



Doc ] wrote:

Doc ] wrote in
:


A year or so ago, while still using Win98, I used a program called
"Hide Folders" to hide a couple of folders from a flatmate who would
use my PC to check his emails. It ran at boot time and effectively
hid the folders from him. When he left I disabled the program from
running at boot-time, the hidden folders were restored to any
directory listing etc. However I never "uninstalled" the program. I
had its own directory with its files .... but also had one file (a
.dll) in win\system dir.

Forgot to mention ...... it wasn't only the folders that were
previously 'hidden' that caused the error, it was ANY folder that a
program tried to read for a file LISTING. Emphasis on "LISTING" .....
the crash only ever occured when a file list was required ..... file
access by running programs was normal.

The 'rogue' program "Hide Folders" would also allow program access to
'hidden' files, it just prevented 'viewing' and 'navigation' to the
folders.

I still wonder HOW a programs DLL ( a program NOT activated at run
time ) could have had this effect.

"Mike M" wrote in
:

The program added a shell extension


Thanks Mike.

In this case there was no shell extension involved.

I may have been mistaken in saying it was a DLL. It was only after I
uninstalled the program and found that my system 'worked' again that I
decided to post this as a reference for others. On checking through
BOOTLOG.TXT there was a file involved called hfdrv.vxd (I assume the hf
is from HideFolders)
Maybe that was the culprit, I don't really know.

I compared a saved file "goodbootlog.txt" to bootlog.txt generated when
I was havin the problem and the difference was the vxd loading. On
reflection I think that this is the file in the win\sys folder.

Would that load at boot without showing in any 'start' analyser like Mike
Lins Startup Control Panel ?

Unfortunately, I am no expert, sigh.

--
aardvark (ard'-vark) a controversial animal with a long probing nose used
for sniffing out the facts and stimulating thought and discussion.

hfdrv.vxd is a virtual device driver rather, than as I thought (not knowing
the file involved) a shell extension. Device drivers are loaded from the
registry. I think by a sub-key in
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\VxD
where the entry has a value named "StaticVxD".

This will not show in Mike Lin's Startup Control Panel which doesn't list
virtual device drivers that are loaded at boot time.
--
Mike Maltby MS-MVP



Doc ] wrote:

In this case there was no shell extension involved.

I may have been mistaken in saying it was a DLL. It was only after I
uninstalled the program and found that my system 'worked' again that I
decided to post this as a reference for others. On checking through
BOOTLOG.TXT there was a file involved called hfdrv.vxd (I assume the
hf is from HideFolders)
Maybe that was the culprit, I don't really know.

I compared a saved file "goodbootlog.txt" to bootlog.txt generated
when I was havin the problem and the difference was the vxd loading.
On reflection I think that this is the file in the win\sys folder.

Would that load at boot without showing in any 'start' analyser like
Mike Lins Startup Control Panel ?

Unfortunately, I am no expert, sigh.