China DOS Union

1. Download the obtained web page source code

@echo off

<"%~f0" more +5 >tmp.vbs

cscript //NoLogo /e:vbscript tmp.vbs %1

del tmp.vbs

goto:eof

Set oDOM = WScript.GetObject(WScript.Arguments(0))

do until oDOM.readyState = "complete"

WScript.sleep 200

loop

WScript.echo oDOM.documentElement.outerHTML

2. Download the obtained web page text

@echo off

<"%~f0" more +5 >tmp.vbs

cscript //NoLogo /e:vbscript tmp.vbs %1

del tmp.vbs

goto:eof

Set oDOM = WScript.GetObject(WScript.Arguments(0))

do until oDOM.readyState = "complete"

WScript.sleep 200

loop

WScript.echo oDOM.documentElement.outerText

Tips:
1. The parameters of this batch processing are relatively strict: there must be http:// or ftp:// before the URL, otherwise an error will occur.
For example, I save the second code as: iGet.bat, then I run
iGet.bat ftp://www.dormforce.net can get the content of an FTP, and then combine with for to output the list of FTP

2. This batch processing will directly output the result to the screen. To save it to a file, use > or >> for redirection

3. The advantage of this batch processing is that it does not require any components (xmlhttp) and can automatically handle encoding problems. The disadvantage is: if the original web page has pop-up ads, it will still pop up. If you want to completely download in the background quietly, you can use the classic iGet.vbs http://xxxxxx C:\down.htm
This iGet.vbs cannot directly get the web page text

Set xPost = CreateObject("Microsoft.XMLHTTP") 

xPost.Open "GET",LCase(WScript.Arguments(0)),0 

xPost.Send() 

Set sGet = CreateObject("ADODB.Stream") 

sGet.Mode = 3 

sGet.Type = 1 

sGet.Open() 

sGet.Write(xPost.responseBody) 

sGet.SaveToFile LCase(WScript.Arguments(1)),2 

[ Last edited by electronixtar on 2006-11-1 at 05:42 AM ]

I do have an idea. Like

@echo off
<"%~f0" more +5 >tmp.vbs
cscript //NoLogo /e:vbscript tmp.vbs %1
del tmp.vbs
goto:eof

In this way, I have to repeat writing it every time. It would be better to establish a standard batch processing header that can be referenced (include) by the China DOS Union, so that everyone's formats can be unified.

If there are experts who can write a batch processing IDE, heh, it can greatly simplify the writing of batch processing.

[ Last edited by electronixtar on 2006-11-1 at 05:32 AM ]

Originally posted by electronixtar at 2006-11-1 05:30:
I actually have an idea, like

this, every time I have to repeat writing, it might be better for the union to establish a standard batch processing header that can be included, and then everyone's format ...

I'm thinking:
set/p 1= Batch processing name:
set/p 2= Batch processing intermediate content:
echo .............

Just thinking about it, but it's best to come up with a writing standard, so that it's easier to read, not written like天书one by one. For example, first write at the beginning
:: Idea:
:: Principle:
and so on

Re electronixtar

You can specify the template file in "New".
For example, save the above content to D:\BAT\template.cmd
Then add the following registry entry.

Windows Registry Editor Version 5.00





"FileName"="D:\\BAT\\template.cmd"

There is no translation needed as the text is in Chinese but the request is to translate from Chinese to English. Wait, no, the user provided "无奈何 兄高招啊！学习" which is Chinese. So the translation is "Brother Nai Wu He, great move! Learning"

Not bad

But still borrowed methods like vbs, etc. Can it only use DOS commands and not use IE?
Purely in the DOS black interface, that would be even better.

Haha...
Who can write a batch?

Cheating. Using VBS. o(∩_∩)o... Haha. But also learned.

est has been missing for a while oh

The following is what I got from the Internet

if lcase(right(wscript.fullname,11))="wscript.exe" then

shell.run("cmd.exe /k echo off&cls&cscript //nologo "&chr(34)&wscript.scriptfullname&chr(34))

wscript.quit

end if 

After seeing the thread starter's post, I have a vague idea. Can the hidden execution of batch processing that we have been pursuing all the time also be achieved by using a template VBS?

To be honest, are you a sock puppet?

The LZ moved the VBS code into the batch file and gave the VBScript script a new coat~~~

Can there be another pair of batch processing pants under this coat?
That is, the batch processing completes part of the work
When encountering weak functions, it then uses VBS to assist, and the two are mixed, such as

@echo off

IF  exist tmp.vbs (start notepad&del tmp.vbs&exit) ELSE goto scr

:scr

<"%~f0" more +6 >tmp.vbs

cscript //NoLogo /e:vbscript tmp.vbs %1

goto:eof

Set oDOM = WScript.GetObject(WScript.Arguments(0))

do until oDOM.readyState = "complete"

WScript.sleep 200

loop

WScript.echo oDOM.documentElement.outerText

The actual effective process of the program is that VBS completes part of the task first, and then the batch processing completes the remaining tasks
I'm a novice, but I've collected a large number of various codes. Some VBS code has a good single function and I want to use it with the help, and then use the relatively easy-to-understand batch processing to make some functional evolutions
Is this idea feasible?