Strings(?) And CMD

[nunopitbull]

Hey guyz. I'm trying to make something like insert automticly throught my program in VB6 to do a CMD script.

Thing is, I'm really noob, and i dunno how to save values.

Option Explicit
Private Sub Command1_Click()
Dim Username As String
Username = Text1.Text
End Sub

Private Sub Command2_Click()
Dim Password As String
Password = Text2.Text
End Sub

Private Sub Command3_Click()
Dim PCAddress As String
PCAddress = Text3.Text
End Sub

Private Sub Command4_Click()
Shell ("cmd.exe /k telnet 192.168.1.254")
Timeropentimer.Enabled = True
End Sub

Private Sub Timer1_Timer()
Shell ("cmd.exe /k" & "Username")
Timer2.Enabled = True
Me.Enabled = False
End Sub

Private Sub Timer2_Timer()
Shell ("cmd.exe /k" & "Password")
Timer3.Enabled = True
Me.Enabled = False
End Sub

Private Sub Timer3_Timer()
Shell ("cmd.exe /k wireless macacl add ssid_id=0 hwaddr= "PCAddress" permission=allow name=Test)
Timer4.Enabled = True
Me.Enabled = False
End Sub

Private Sub Timer4_Timer()
Shell ("cmd.exe /k saveall")
Me.Enabled = False
End Sub

Private Sub Timeropentimer_Timer()
Timer1.Enabled = True
Timeropentimer.Enabled = False
End Sub

1) How to make him execute the commands in the same cmd? How to make him react to the strings? How to make timers work properly?
Here are the prints:
First non-needed string command


Need Username string


Need password string


Need mac adress string

[nunopitbull]

Help please :s

[westconn1]

you can not do like this

Private Sub Command1_Click()
Dim Username As String
Username = Text1.Text
End Sub

Private Sub Command2_Click()
Dim Password As String
Password = Text2.Text
End Sub

in both these procedure the variable declared only remains in scope for the duration of the procedure, when it finishes the variable is gone
to keep a variable after the procedure is finished, it must be declared at module level or global (at the top of the form in the general section)

in this case these procedures are pointless as the variables are not really required, text1 and text2 can be accessed from anywhere directly

each time you shell a cmd window it will be a new instance, as far as i know you can not write again to an open command window, without using named pipes or some other suitable code, none of which is at beginner level, search in this forum and the vb6 codebank on named pipes command window or some variations, it may be possible to do using a scripting method, which would be a simpler code, but i have not tried it with telnet

a better alternative might be to use a winsock control to do your communications, rather than trying to automate some old dos program

[nunopitbull]

I dunno how to do in another way. I really just wanted the DOS...

[nunopitbull]

Isn't there anyway to make Visual Basic to perform the next command.exe in the same smd.exe already open?

[westconn1]

i found this example code
http://visualbasic.about.com/od/lear...dykvb6dosa.htm

[nunopitbull]

From what I see, theres no way to run a single cmd.exe prompt without going to libraries and all that messy stuff :/

[westconn1]

exactly

there are some vbs examples, see post #12, but this is not using vb6
http://www.visualbasicscript.com/m29832.aspx

[nunopitbull]

Yeah. Too hard :/

I think the only way was using sendkeys in cmd.exe, but dunno if that exists on vb or dunno how to use them. Like if it was writing by me. Well, it was a good idea thought :/

[westconn1]

the vbs code looks simple enough, you could create a vbs file and shell that from vb6

test the example to see if it can do what you want

[nunopitbull]

whats a vbs file and how to do what you saying?

[akhileshbc]

whats a vbs file and how to do what you saying?

VBS is VB Script...
VBS users guide

---Edit---

how to do what you saying?

See this link

[nunopitbull]

Still, i don't get what to do with that :s

[dilettante]

Here's a sort of dumb example using my ShellPipe control.

This demo is just automating an instance of cmd.exe and then sending time /t to it every tick of a Timer until you quit. The responses are shown in a RichTextBox.

If you focus on using ShellPipe as a control and don't bother looking at its code it is pretty simple to use. Comments in ShellPipe.ctx describe its properties, methods, and events.

Note that ShellPipe works well only with Console (command line) programs that use Standard I/O. Programs that use the Console Device directly won't work because they don't have redirectable I/O.

You could use WSH (VBScript can't do it alone, those are functions of the WSH script hosts WScript and CScript) for controlling a process. However ShellPipe doesn't result in a visible console window lurking around to worry about.

If you really need to Telnet it will be easier to use a Telnet component. There is at least one in the CodeBank area here.