It cycles between all lowercase, all uppercase and capitalized all words in the surrounded text.
If you choose all lower-case, you will lose the capitalization of the first word in the sentence.
Remember to do a Cntl-Z (undo) for as many times as you need, if you want to revert back to your original selection
I had done a google search for:
ms word change all uppercase to mixed case
The second search result for me answered my question:
FYI - the Shift-F3 shortcut did not work in Notepad or Wordpad (Write.exe)
But first, you have to plug it into your computer's USB port to set it up.
This worked fine, though there were quite a few steps to set it up.
When it was done being set up, I was able to make a call with a wired phone connected to the MagicJack plugged into my computer. The Ethernet plug remained unconnected at this time.
I was wondering if I had to change any settings through the control panel to be able to unplug it from the computer, and plug it directly into the router. I found a setting in the menu that let we switch from using the wired phone to using my computers speakers and microphone. This worked fine too.
I switched it back to wired phone, then disconnected it from the USB port.
I plugged in the AC adapter and plugged the USB port (power-only, no data) into the adapter. I plugged in the included Ethernet wire into the router. It lit up, and I saw data lights flashing on the MagicJack.
I picked up the wired phone connected to the MagicJack, and heard a dial tone. I dialed a number, but it didn't work. I searched the MagicJack site for answers to what happens when it works on a PC, but not when plugged directly into the router. I tried many articles on their FAQ/knowledge-base without luck.
Then I tried Google. Eventually, I found a post on a site called http://www.magicjacksupport.com, but it does not seem to be directly linked with the main MagicJack site. The article spoke about the same trouble I was having, and the user had pasted the IM help chat they had with MagicJack. The said the user should open up port 5060 & 5070 for UDP on their router. This user said it did not work for them.
I tried added 5060-5070 UDP for the device and during the process, the router rebooted. So I don't know for sure if adding the port forwarding solved it or the reboot, but after that it was able to make and receive calls.
Out of curiosity, I started the MagicJack application on my PC with the device not plugged into the UDB, but plugged into the network. The application looked like it was going to do something, but then just said plug in the device to the USB, or click if you don't have a device. Clicking brings up the IE web browser to their site, to try to sell you a device.
The web control system has a place for setting up voice mail pin and email address to send a wav file copy of of the voice mail. It does not tell you how to retrieve voice mail from a wired phone. I searched the FAQ and found that you have to dial the 10-digit phone number to get to the voice mail.
They talk about an downloadable app, but it appears the currently only support iPhone.
I am surprised that MagicJack device will give a dial tone, even when it does not have the ability to connect the call.
When the device can not complete the call, I would expect it to give some sort of voice response with an error code that would let you understand why it did not complete the call.
I would have expected a better answer to router issues on the main MagicJack site, where you have to log in.
I tried to listen to a test voice mail on my Android phone, sent to my Gmail account, but the 2 audio players that came up would not play the WAV file from MagicJack. I tried downloading a couple more from the market, but none of those worked. Doing a search on the problem, I found that the application "Remote Wave" http://www.appstorehq.com/remotewave-android-162249/app worked!
The MagicJack device/service could have a who lot more functionality:
1) Voice mail should be reachable by a shortcut - such as *86 [* V M]
2) Provide the ability to set up control codes, such as quick-dial to *nn combinations.
3) Provide a way for the MagicJack PC application to talk to the device on the LAN
allow a local computer to make calls using the MagicJack connected to the LAN.
4) Provide a way to access the MagicJack device over the LAN via a web [server] interface.
5) Provide for the ability for phone number filtering (custom ring) or blocking.
6) Provide the ability to turn on telemarketer message to any phone number not on the caller list
7) Provide a call routing menu option, for custom ring tones, and route-able voice mails to a few different emails.
7) Provide an Android App
8) Provide the ability to do 7 digit dialing for a non-overlay zone
9) Let people know about options for porting (having home number switched to MagicJack) a number later instead of sounding like you only can do it during initial set up (especially considering many people will not want to port the number until they have a chance to try MagicJack for the trial period)
10) Provide a longer USB extension plug
11) Provide a shortcut test callback number
12) Provide voice dialing
Most of the ideas above should be doable pretty much with the same hardware.
If they wanted to come out with an even more advanced hardware, I'd suggest:
1) adding Wifi,
2) adding Bluetooth
3) add an option to order with built-in in home wireless phone (option to partner with a company like vtech)
4) add a speakerphone option to the jack
Now I had done some simple email programs in the past, from unix and PC, using telnet, sendmail and sockets. But I had never tried it from the mainframe. There were ways to send email from the mainframe, but it could take up to 15 minutes.
So I looked around trying to get sockets working via Cobol. But I could only find examples for CICS, and that would not work for what I needed.
After some more searching, I found an example of using sockets in Rexx. It was not set for email the way I wanted, and the example was not all that straightforward. So I recoded it and got it to work!
The challenge may be finding a server in your shop that will allow you to connect and send mail. Many servers will be limited to having internal emails. You may be able to connect to your internal Exchange server.
One of the things that was interesting is that when I connected to a unix server, the first version of the code worked fine, but didn't work to the Exchange server until I added Carriage-return to the linefeed. Note the use of 'So_ASCII' on the 'SetSockOpt' command.
The code could also be updated to handle attachments (with some real work) or use other text-based socket connections, including http and XML/soap requests.
/* rexx */ lf = '25'x cr = '0d'x smtp_server = 'msx' from_server = 'mvs' from_email = 'firstname.lastname@example.org' to_email = 'email@example.com' subject = 'Test Email' body_line_1 = 'This is a test email.' body_line_2 = 'The end.' src = socket('socketsetlist') src = Socket('initialize', 'TCP3') src = socket('socket',af_inet,'SOCK_STREAM','TCP') parse value src with lcc sock rest src = Socket('SetSockOpt',sock,'Sol_Socket','So_ASCII','On') src = socket('gethostbyname',smtp_server) parse value src with lcc hip src = socket('connect',sock,af_inet 25 hip) src = socket('read',sock,500) src = socket('send',sock,'HELO '||from_server||cr||lf) src = socket('read',sock,500) src = socket('send',sock,'MAIL FROM: '||from_email||cr||lf) src = socket('read',sock,500) src = socket('send',sock,'RCPT TO: '||to_email||cr||lf) src = socket('read',sock,500) src = socket('send',sock,'DATA'||cr||lf) src = socket('read',sock,500) src = socket('send',sock,'From: '||from_email||cr||lf) src = socket('send',sock,'To: '||to_email||cr||lf) src = socket('send',sock,'Subject: '||subject||cr||lf) src = socket('send',sock,''||cr||lf) src = socket('send',sock,body_line_1||cr||lf) src = socket('send',sock,body_line_2||cr||lf) src = socket('send',sock,'.'||cr||lf) src = socket('send',sock,''||cr||lf) src = socket('send',sock,'quit'||cr||lf) src = socket('read',sock,500) src = socket('close',sock) src = socket('terminate',from_server)
On a couple of the lines, you see 'parse src' - that is used to split out the needed return values.
If you were sending a variable body for the email, you can replace the 2 lines sending the body_line_1 & 2 with a loop based on reading a file or other data.
I was able to get Citrix to work on my Droid 2 yesterday.
I found the Citrix receiver application in the market and installed it. When I tried to get it to connect, it never connected.
I tried logging in with the browser, and it got past the double-password authentication, but then the site said I did not have the software installed. I clicked download and it started to save a linux version of the server. That doesn't sound right.
So I did a search, and found that using the Firefox browser should solve the problem. The reason is that Firefox is supposed to pass the .ica file as a download.
So I downloaded Firefox and did thr double-password login again. Came up to the download software screen again. But there was another option on the screen I didn't try before: the link told it I already have the software, and skip to the next step. I tried that, and it took me to my list of applications!
So I clicked on the remote desktop, and it did a download of the .ica file, and then it let me connect to the remote machine to log on.
However, I kept getting bad password :( At one point, I had to reenter my userid, and that is when I saw that the interface was not respecting the blue-alt to type in numbers from the hard keyboard! It came out as letters even when I thought I was typing numbers.
Eventually I was able to enter my password via the soft-screen keyboard. I don't know if it was Firefox or Citrix that was not respecting the slider shift for numbers, but at least the soft keyboard worked.
I could only see just a small amount of the screen, about 1/12th, but it did give me a way to get on if I had to, and allowed me to confirm access that I use from a regular computer.
Android 2.1 - Droid2- Verizon- Citrix Receiver- Firefox
When I got home, the DSL light on the DSL modem was off. It is an Actiontec PK5000. I tried a power-cycle. No go. So I looked up the service number with my smart phone. I got the recording that they were already aware of a problem in my area and were working on fixing it.
Dinner goes by, and still no DSL. I try rebooting it again. Still no DSL. I try the number again, same recording. It would be nice to know an estimate of the time when service is expected to be restored.
Another hour or so goes by and at the same time as another roofing salesperson comes to the door, the DSL light comes back on! I was able to connect with my wired computer. But oddly, the laptop doesn't connect.
I log onto the DSL modem with the wired computer. It looks fine. But then I notice that the wireless light is off. I try cycling the wireless wifi off, then back on through the web control page. But the light does not come on. And there is no sign of the SSID (wireless name) with my smart phone.
I try some more settings. I look for troubleshooting options online. I try doing a reset-to-factory from the setting page for the modem. Nothing makes the light turn on.
I check and see that the modem firmware is a few minor versions back, so I read about how to update the firmware. Well, if I get it wrong, the device could well brick (be non-functional), so let me see what other options I have.
I pull up the online chat help with Qwest. First thing they need to tell me is that they are getting a new name. Good for them. What does that mean for me? Worse service? I hope not. I wait about 5 minutes, then start chatting with a nice enough gentleman from Salt Lake.
He said he was going to check the warranty. We didn't spend too much time on twenty questions, as I must have given him enough details to skip most of the annoying and worthless (in this case) troubleshooting steps on his script. Other than asking how I did the factory-reset, he didn't seem to have any useful troubleshooting steps he could have me try.
But what it came down to is that he didn't really have any active solutions for me. He said the modem was out of warranty. I checked, and it was 14 months ago that I bought this one. And it seems manufacturer's warranty is only one year. He said I could buy a new one at Wal-Mart or Best-Buy. He also suggested that I could rent one from them.
Now, there is something interesting about getting a new DSL modem 14 months ago. The old modem was just a few months out of warranty. And that old modem also didn't have a true hardware failure. It was able to talk perfectly well to Qwest's DSL equipment. But it would not authenticate to get onto the internet, and it would net let me update any of the configuration items. As if the modem was hacked or had an incomplete firmware update or perhaps had some sort of command to tell it to misbehave.
Now, here it is, 14 months later, totally different brand of DSL, yet a problem that looks to me to be more configuration than hardware again. And both purchased from Qwest. And both times Qwest is trying to push on me their rental plan instead of standing behind what they sell.
The tech suggested it must be related to the power in my area. Hm, really? Last time I was told that it was because I didn't unplug my DSL when I didn't need it. REALLY?? And when exactly is that? Is that like unplugging you phone when you don't expect a phone call??
I let them know I was very disappointed, and I would be investigating other internet options with other companies. That didn't seem to bother the representative. He thanked me and signed off.
Well, I had a few choices. I could find/buy a cheap wireless hub to add to the router by wire, as the wired part was still working fine. I could buy a new modem from a store or their Kiosk or even from them directly. Or I could agree to pay them every month for the piece of mind that it might just cost me more in the long run, but at least I know it would be their headache for future glitches. Well, more of a shared headache.
But I had one other option first. Unlike the previous modem, where I could not get to the configuration screen, this one was fully operational and cooperative except for the wireless not turning on. As it seemed likely that I would need to buy or rent a new modem, it was worth a shot against bricking the unit to try the firmware upgrade.
I followed the directions for the firmware update. Downloaded the software and directions from the net. I made sure that my wire was plugged in firmly. I hoped and prayed that the power stayed on while I did the update.
I started the update program. First time, my firewall blocked the update. Well, I told it the program was allowed to access the modem through the Ethernet. Then I retried. It told me it could take 4-10 minutes. I watched as the progress bar went across the screen in about 30 seconds. They went across again. And again. And again.
I started to get nervous that it would just do that for hours, and when I gave up, the unit would be a brick. I took a walk to the garage for a soda. I came back, and waited a few more seconds. The screen changed and said the next step as shown in the instructions. A power cycle.
So, I unplugged everything, just to be sure there was no confusing it as it woke up with the new version. The wireless light turned on right away, just like every other power cycle – just to prove that the light was still good – in the same fashion as a check-engine light comes on when you first turn the key in a car.
The wireless light went out as the modem went through the boot process. Lots of flashing lights. Then the DSL light was flashing – of course, as I had that disconnected too.
Then, it happened! The wireless light came back on! Something I had not seen since before dinner. I checked on my smart phone – it could see the wireless default SSID!! I plugged it back in, and worked on reconfiguring the settings back to what I'd had before the reset and firmware update. That took another 20-30 minutes, but then I was back to normal operations!
I am disappointed that the firmware upgrade was not an option that was suggested by the technician.
I am disappointed that Qwest did not stand behind their equipment, and seem to only be interested in how they can squeeze some dollars from my distress and dissatisfaction.
I am concerned that the modem will 'mysteriously' decide to have other configuration errors in the near future. Hopefully it will be at least another 2 months, so I can at least feel I made it to the break-even point on this modem as compared to their 'rental' plan.
I am happy that I was able to solve the situation, especially when the support service was not able to help.
Hopefully this helps other people solve the same issue without having to immediately give into the company's attempt to surcharge for a solvable soft issue. Good luck!
So, a firmware reload solved the issue. That suggests, for whatever reason, there was just a hidden configuration error or bad data in memory.
Settings -> Data Manager -> Data Delivery -> Data Enabled