Loading...

Alright, sorry for the delay. I just had to queue up the connection command for Michigan. Yeah, like you say Gray, once you get used to the commands and stuff, it's easy peasy man. It really is. The only one you need to keep close by is the password. And never forget the dot in front of any admin commands. That's really important. Because if you don't put in the dot, your command will not execute. And it will just become visible to the entire group in the text box without the dot. So, it's a very important part. But other than that, once you get used to it, it is easy. .disk for disconnect, .mute, .unmute, .con for connect. Or you can type out the whole word, but there's no sense. .disk and .con and .mute and .unmute, they work just fine. They also require the dot in front of them to identify them as the system command, as opposed to a text box entry. Now, we do have another means of doing this as well. But it needs a dynamic DNS forwarding address to be set up and whatnot. But, yeah, that's another way to do it. I just haven't gotten to doing that yet. It's like so many little things that I need to do that I just haven't gotten to doing yet. But eventually we'll get it and that will work out. And then it's like a little website you can have open on your screen on a computer. And instead of having to type things, you just click things. And then those commands then issue to the conference server. So, yeah, that's another way of doing it. But right now the text command typing them is the way to go. Or you can cut and paste. I'm not sure if you can cut and paste the admin password command. I think that one has to be actually typed. And then the rest of them, the .con and .disconnect and all that, you can cut and paste those. So, let me reset.