Three disabled FSO components of the virtual machine

http://www.cprogramdevelop.com/1100335/

Tag: Session, C, domain, server, asp, Virtual machine Category: C Author: liu2000yx Date: 2010-07-21

Introduction: 
Well-known, the FileSystemObject component powerful and destructive is often free home providers (those who support ASP) disabled reason, I order a bit, had found only two methods, and later someone stimulus, he just imagined three not known, I do not know is not the case. 

The first is: RegSrv32 / u C :/ WINDOWS / SYSTEM / scrrun.dll (win98 path) to unregister the component. This method is too vicious, the methods are to die together, we did not use statistics, the next trick second: modify the Progid the value, usually called in the ASP components Set object name = Server. 
CreateObject (the PROGID "), this time we can by modify the registry Progid value from disable the component approach. In the Start - Run, typing regedit, and then find HKEY_CLASSES_ROO 
T / Scripting.FileSystemObject, this time we can change the value of the ProgID, such as changedScripting.FileSystemObject8. So that such a call in the ASP page: 
<% @ Language = Vbscript%> 
<% 

Set fs = Server.CreateObject ("Scripting.FileSystemObject8) 

BBS.bitsCN.com Webmaster Forum 

%> Set Fs = Server.CreateObject ("Scripting.FileSystemObject8") 

BBS.bitsCN.com Webmaster Forum 

%> 
(If you do not call in front of the component, without rebooting, you can see the effect, or restart to see the effect.) 
This time we look or the results of the original call: 
<% @ Language = Vbscript%> 
<% 

Set Fs = Server.CreateObject ("Scripting.FileSystemObject") 

%> Set Fs = Server.CreateObject ("Scripting.FileSystemObject") 

%> 
At this time the result is: 
Server object error 'ASP 0177: 800401f3' 
Server.CreateObject failure / aspimage/testfile2.asp in line 3 
800401f3 
(OK, to meet our requirements) 
I was late two-step, the result of rushing to let others answered so greatly stimulated my result was the third method. 

Third: a careful master would think, since by amending the existing the ProgID value to disable the component, Clsid whether to modify it? (OK, you want to be like me) we know that, in addition to the CreateObject method, you can use the generalMarked the establishment of a component, we can use the HTM in ASP 
L Note that a component in order to add the page. The method is: bitsCN to com 

the ect? progID = Scripting.FileSystemObj 
ect "scope =" page "runat =" server "> 
</ Object> 
Runat on the service side, Scope is the life cycle of the component can be selected Session, Appl 

ication or (the current page, can also be the default) 
The wording is useless to us, there is a written: 

& Ltobject runat = server id = the fs1 scope = page classid = "clsid: clsid value> 
ect> 
We can also modify the value of the Clsid disable the component, such as the registry HKEY_CLASSES_RO 

OT / Scripting.FileSystemObject / CLSID value 0D43FE01-F093-11CF-8940-00A0C90 

54228 into 0D43FE01-F093-11CF-8940-00A0C9054229 (change the end of one), this time the wording: 


CF-8940-00A0C9054229? Scope = "page" runat = "server"> 
</ Object> 
See the results, no problem, OK. At this time, we then 
CF-8940-00A0C9054228? Scope = "page" runat = "server"> 
</ Object> 
This time on the error. 
New user: iusr_domain with 

The anonymous user IUSR_DOMAIN set the corresponding sites in IIS 
CACLS: set directory permissions FSO available, but it will not affect others 

Tag: Session, C, domain, server, asp, Virtual machine Category: C Author: liu2000yx Date: 2010-07-21

Introduction: 
Well-known, the FileSystemObject component powerful and destructive is often free home providers (those who support ASP) disabled reason, I order a bit, had found only two methods, and later someone stimulus, he just imagined three not known, I do not know is not the case. 

The first is: RegSrv32 / u C :/ WINDOWS / SYSTEM / scrrun.dll (win98 path) to unregister the component. This method is too vicious, the methods are to die together, we did not use statistics, the next trick second: modify the Progid the value, usually called in the ASP components Set object name = Server. 
CreateObject (the PROGID "), this time we can by modify the registry Progid value from disable the component approach. In the Start - Run, typing regedit, and then find HKEY_CLASSES_ROO 
T / Scripting.FileSystemObject, this time we can change the value of the ProgID, such as changedScripting.FileSystemObject8. So that such a call in the ASP page: 
<% @ Language = Vbscript%> 
<% 

Set fs = Server.CreateObject ("Scripting.FileSystemObject8) 

BBS.bitsCN.com Webmaster Forum 

%> Set Fs = Server.CreateObject ("Scripting.FileSystemObject8") 

BBS.bitsCN.com Webmaster Forum 

%> 
(If you do not call in front of the component, without rebooting, you can see the effect, or restart to see the effect.) 
This time we look or the results of the original call: 
<% @ Language = Vbscript%> 
<% 

Set Fs = Server.CreateObject ("Scripting.FileSystemObject") 

%> Set Fs = Server.CreateObject ("Scripting.FileSystemObject") 

%> 
At this time the result is: 
Server object error 'ASP 0177: 800401f3' 
Server.CreateObject failure / aspimage/testfile2.asp in line 3 
800401f3 
(OK, to meet our requirements) 
I was late two-step, the result of rushing to let others answered so greatly stimulated my result was the third method. 

Third: a careful master would think, since by amending the existing the ProgID value to disable the component, Clsid whether to modify it? (OK, you want to be like me) we know that, in addition to the CreateObject method, you can use the generalMarked the establishment of a component, we can use the HTM in ASP 
L Note that a component in order to add the page. The method is: bitsCN to com 

the ect? progID = Scripting.FileSystemObj 
ect "scope =" page "runat =" server "> 
</ Object> 
Runat on the service side, Scope is the life cycle of the component can be selected Session, Appl 

ication or (the current page, can also be the default) 
The wording is useless to us, there is a written: 

& Ltobject runat = server id = the fs1 scope = page classid = "clsid: clsid value> 
ect> 
We can also modify the value of the Clsid disable the component, such as the registry HKEY_CLASSES_RO 

OT / Scripting.FileSystemObject / CLSID value 0D43FE01-F093-11CF-8940-00A0C90 

54228 into 0D43FE01-F093-11CF-8940-00A0C9054229 (change the end of one), this time the wording: 


CF-8940-00A0C9054229? Scope = "page" runat = "server"> 
</ Object> 
See the results, no problem, OK. At this time, we then 
CF-8940-00A0C9054228? Scope = "page" runat = "server"> 
</ Object> 
This time on the error. 
New user: iusr_domain with 

The anonymous user IUSR_DOMAIN set the corresponding sites in IIS 
CACLS: set directory permissions FSO available, but it will not affect others