lowray1975

The best way, in my opinion, would be to capture the link and redirect. You could insert the following javascript using _IEHeadInsertEventScript <script type="text/javascript"> ​window.onclick = function (e) { if (e.target.localName == 'a') { console.log('a tag clicked!'); } }​ </script> From there you can rewrite the javascript to navigate to the same tab. Actually: Look at the first example for the _IEHeadInsertEventScript function.

Take a look at the _IEHeadInsertEventScript documentation in the help file. The second example demonstrates exactly how to do this.

Sorry for the delay, my lovely wife took me and the kids away unexpectedly for a few days. Before getting into the code I might be a good idea if I explain the situation I was in when I created the VB code. Back in the days of Outlook 2000, XP, and 2003 I worked for a company that outsourced office's for single employee or very small companies. My boss, the owner of the company, didn't believe in complication - meaning everything was simplified. Because he also believed he understood IT he made the decision that Active Directory would not be used (this occurred years before I became employed . Each of the seven locations would be configured as a workgroup and, instead of logging into workstations as an individual, an employee logged in as a function (e.g. the front desk receptionist logged in as the "frontdesk" account). Even though employees traveled between all of the location this typically didn't cause any issues because the main application that was used has an internal user management system. However it made configuring Outlook for Exchange a huge issue when a] people couldn't follow simple directions and b] the user using the workstation that day could have never used the workstation in the past. This prompted me to find a way to automate the initial configuration of Outlook. The VB program that I wrote did nothing more than displays a list of employee names in a dropdown box, allowing the user to select his or her name and click the “Create Outlook Profile” to automagically create their Outlook profile. When the button was clicked it did nothing more than replace a couple of variables within the PRF template and then use Outlook to import the PRF file using the syntax: outlook.exe /importPrf "*prf*" (where *prf* was replaced with the full path to the newly created PRF file) If I needed to do this all over again I would absolutely do it using AutoIT (honestly I didn’t even know about AutoIT until 2007 – I haven’t used VB since). However before recreating this program I would have tried to sway the owner of the company to allow me to configure the environment correctly… I’ve attached the VB code; although please keep in mind it was created almost 10 years ago. I doubt a lot of people will need to use it since Outlook 2010/2013 auto configure if Windows authentication is used correctly. It’s also possible that the complete PRF format has changed (highly doubted). If there is enough need/demand/requests I’ll be glad to recreate using AutoIT. - Josh PS: I didn't proof this, Valik would be pissed. OutlookConfigToolSource.7z

Sorry to throw you off track, however there might be a better way to do this. A long time ago I wrote something in VB that created Outlook profiles by using PRF files. http://technet.microsoft.com/en-us/library/cc179062(v=office.14).aspx Let me know if you're interested and I'll try to find the source code. It would be great to see it translated to Autoit. Hopefully you find this useful.

I believe I've found a bug. For the key named "DownloadURL32" the UDF will match the "DownloadURL32", "URL32" and "32" (well, the UDF will match string of characters right to left). I'll post the fix if I'm successful [RemoteSupport] DownloadURL32=1234 $INI_RemoteSupport_DownloadURL32 = _IniString_Read($tmpGuardianINI, "RemoteSupport", "DownloadURL32", "") $INI_RemoteSupport_DownloadURL32 = _IniString_Read($tmpGuardianINI, "RemoteSupport", "URL32", "") $INI_RemoteSupport_DownloadURL32 = _IniString_Read($tmpGuardianINI, "RemoteSupport", "32", "") All return the value "1234"

I believe this will be supported in the next release (it's in beta now).

@stg68 - Excellent, glad I could help! @BrewManNH - Crap, I didn't pick up on that - good catch and thank you!

Which OS are you testing this on? I just tried you code (without modification) on Windows XP and it worked perfectly. If it's Vista or 7 try adding #RequireAdmin.

Mind you, I have no idea was it was removed in v3.3.1.0: Func _WinAPI_MakeDWord($HiWord, $LoWord) Return BitOR($LoWord * 0x10000, BitAND($HiWord, 0xFFFF)) EndFunc

It looks like _WinAPI_MakeDWord() was removed several versions ago.

I just tested the help example for the StdoutRead function and it appears that certain outputted data is "groups". I just confused myself. #include <Constants.au3> $net = Run(@ComSpec & " /c dir c:temp", @SystemDir, @SW_HIDE, $STDERR_CHILD + $STDOUT_CHILD) While 1 $line = StdoutRead($net) If @error Then ExitLoop If $line <> "" Then ConsoleWrite("STDOUT read:" & $line & " -- " & @Sec & "." & @MSEC & @CRLF) Wend Exit I then changed the directory to c:windows and there were many more "groups" of outputted data.

@water What I found is that the standard method of retrieving STDOUT within AutoIt didn't work unless the -v was present. According to the ncftpput documentation it does write to TTY, which I thought was STDOUT.in the Windows world.

XP SP3 x32 here!

Very strange. Here's the code I'm using: $tcrtout = "" $iPID = Run("ncftpput.exe -v -p " & $Password & " -u " & $Username & " -C " & $SiteName & " """ & @ScriptDir & "ncftpput.rar"" /subdomains/photos/httpdocs/ncftpput.rar", @TempDir, @SW_SHOW, 0x2) While 1 GUIGetMsg() $tcrtout &= StdoutRead($iPID, True) If @error Then ExitLoop If $tcrtout <> "" Then ;$tcrcatch Then ConsoleWrite($tcrtout & @LF) EndIf WEnd Exit Here's the output: >Running:(3.3.8.0):C:Program FilesAutoIt3autoit3.exe "hnc-officeusersjcookMy Documents_ProgrammingAutoITTestingftp shitftpdownload.au3" ...usersjcookMy Documents_ProgrammingAutoITTestingftp shitncftpput.rar: ...estingftp shitncftpput.rar: ETA: 0:00 32.00/ 95.79 kB 0.00 B/s ...estingftp shitncftpput.rar: ETA: 0:00 95.79/ 95.79 kB 437.89 kB/s ...estingftp shitncftpput.rar: ETA: 0:00 95.79/ 95.79 kB 266.54 kB/s ..._ProgrammingAutoITTestingftp shitncftpput.rar: 95.79 kB 266.54 kB/s ..._ProgrammingAutoITTestingftp shitncftpput.rar: 95.79 kB 266.54 kB/s +>11:14:08 AutoIT3.exe ended.rc:0 >Exit code: 0 Time: 3.320 It's the -v that made the difference.

I believe this is what you're looking for: $iPID = Run('ncftpput.exe -v -p password -u greg -C newlap "C:Program FilesJDASTUPtestfile.bin" test/test.upt', @TempDir, @SW_SHOW, 0x2)