Main Forum > Feedback & Suggestions

Repair of WMI Issue (SOLVED)

<< < (2/2)

Shane:
The repairs are ran in bat files. I only have so much control over the commands I am able to run. So in the bat file the cmd to search the drive for the mof files is ran, not a lot of options with it.

Perhaps I need to see about changing the repair to where the program itself first goes and searches for the files, that way I can have it skip symbolic links and then some. Then it can output the files to be add back the wmi in the bat file and not have the bat file do the file search.

One way I could tell that this works is if any of the file scanners in the program itself dont have any problem with searching the drives (They are set to skip junctions and symbolic links) the unhide hidden files repairs is one, the check rephrase points is another.

Shane

bigaluk:
Thanks for looking into this.

I agree with the direction of your solution:  it needs something to limit the MOF search, then all will be ok and no damage will be caused.  It might even be worth putting up a warning to users in the pre-test checks you provide that such mount points are potentially hazardous to tools that use "indiscriminate" searching to do automated repair work  :smiley:.  Your tool won't be the only one in the world to fall foul of this.  Indeed if the mount point is recursive (one of mine was at one point: the mount point was to the drive on which the mount point resided) then a tool may never even complete - until it eventually crashes due to ridiculously long recursive path names.

You can test the problem scenario by using C:\Windows\System32\diskmgmt.msc to set up NTFS Path mount points to drives such that these paths are then folders on the C: drive.   I actually have to do this on my system because I sometimes have too many drives (many of them are USB) to provide drive letters for, and this is sometimes the only way I can mount such drives consistently to fixed locations. 

Since encountering this problem I have decided that 'C' is perhaps not the best drive to use for such mount-point folders. :)   Indeed, doing so is probably asking for trouble.  Hence my suggestion that detection and warning users in your "Pre-Scan" checking suite might be a useful addition to the tool:  Perhaps with a suggestion that the user only ever uses a non-OS drive for such folder-based mount points.

Shane:
I put it at the top of my to do list, not sure when I will have it done as I will have to build a new tool for it, but I have it at the top of the list :-)

Most users dont ever set mount points, it is the power users like yourself that do and who need more control over the automation of the repair. I will come up with some ideas when I make the new repair for it. I just dont have a time frame yet.

My computer repair business has been insanely busy and I am struggling to get caught up on all the programming :wink:

Shane

Navigation

[0] Message Index

[*] Previous page