Three ways to disable FSO

As we all know, the powerful function and destructiveness of the FileSystemObject component is its repeatedly free

Home Provider (Those Support ASP) Disabled Reasons, I have finished, I originally found two methods.

Later, I was stimulated by someone, hard thinking about the third kind of method, huh, huh, I don't know if it is.

Such.

The first one: use regsrv32 / u c: /windows/system/scribn.dll

(WIN98 path) to log out of the component. This method is too vicious, belongs to the same way, everyone is not available,

It is the next move;

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 modify the procid value in the registry

Thus the method of disabling the assembly is achieved. In the start - run, type regedit, then find

HKEY_CLASS_ROOT / SCRIPTING.FILESYSTEMOBJECT, when we can change this Progid

The value is changed to scripting.filesystemObject8. This is called in the ASP page:

<% @ Language = VBScript%>

<%

SET FS = Server.createObject ("scripting.filesystemObject8)

%>

(If you don't call the component in front, you can see the effect without restarting, otherwise you will be

Enhance the effect)

At this time, let's look at the results of the original call method:

<% @ Language = VBScript%>

<%

SET FS = Server.createObject ("scripting.filesystemobject")

%>

At this time, the results are:

Server object error 'ASP 0177: 800401F3'

Server.createObject failed

/ASPIMAGE/TestFile2.asp, line 3

800401F3

(OK, achieve our requirements)

This method is due to the later steps, and the result will let others have acknowledge, so greatly stimulate me, knot

There is a third method.

The third type: careful master will think, since it can disable the component by modifying the progID value, then

Can the CLSID can also be modified? (OK, you think about me) We know that except for CreateObject

Outside the method, you can also use a general