Three ways to disable FileSystemObject components

As is well known, the powerful function and destructiveness of the FileSystemObject component is the reason why it is frequently banned by the free homepage (those supporting ASP). I have finished it. I originally found two methods, and later was stimulated by someone, hard thinking Three ways to know the method, huh, huh, I don't know if it is.

The first: uses REGSRV32 / U C: /WINDOWS/SYSTEM/SCRRUN.DLL (Win98 path) to log out of this component. This method is too vicious, belonging to the same way, everyone is not available, it is

The second: Modify the value of ProgID, the way to call the component in the ASP is usually the SET object name = server. CreateObject ("progid"), then we can disable the component by modifying the Progid value in the registry method. In the start - run, type regedit, then find hkey_classes_roo t / scripting.filesystemObject, then we can change the value of the Progid, such as change to scripting.filesystemObject8. This is called in the ASP page: <% @ language = VBScript%> <% set fs = server.createObject ("scripting.filesystemObject8)%> (If you have no call to the component in front, there is no need to restart, You can see the effect, otherwise, please restart.) When we look at the results of the original call method: <% @ language = VBScript%> <% set fs = server.createObject ("scripting.filesystemObject) ")%> This time the results are: server object errors 'ASP 0177: 800401F3'

Server.createObject failed

/ASPIMAGE/TestFile2.asp, line 3

800401F3 (OK, reaching our request) This method is due to the two steps later, the result will let others have acknowledge, so that I have stimulated me, the result produces the third method.

The third type: The careful master will think that since the component can be disabled by modifying the progid value, can the CLSID can be modified? (OK, you think of me) We know that in addition to the createObject method, you can use a general