Leaderboard

Several years ago Microsoft published Office 2010 Starter. Office 2010 Starter was a free Office 2010, however some functions were disabled. It installed only Microsoft Word and Excel and showed Microsoft advertisments during use. Microsoft Starter 2010 works with a virtualization technology like V-App. It does not really install Office on your computer, but a virtualized office (like Office in a virtual machine). To do this it creates a drive Q: which is not user accessable . If you are using drive Q: already, Office 2010 Starter won't work. Office 2010 Starter could be installed using a setup (SetupConsumerC2ROLW.exe) which downloaded the installation files from internet. Sometime around 2012, Microsoft pulled the plug, so the installation files couldn't be downloaded anymore. A few days ago, I found the old executable and behold, I got it working again on my old computer with Windows 10 installed. So Microsoft quietly activated the Office 2010 Starter files again, but will they pull the plug again in the near future ? I found out that if the installation files are available locally, the setup won't need internet during the installation. However the setup does not keep the files after installation, so I had to figure out how to get the installation files together locally. Monitoring the installation I got some partial information how to download all the installation files needed. This information was used to create the Office 2010 Starter downloader v1.0. Be ware, this script works as is. Not a lot of error checking has been put in place. E.g. I do not check for downlad errors, but every language folder should be about 700 - 900 MB. You are allowed to use this script in anyway execept asking money for it. In return, I ask you to donate at least € 1 or $1 to an organization against cancer in your country. E.g https://www.kwf.nl/donatie/donation Office2010S_Download_1E.zip Office2010S_Download_1F.zip

It has been over a year since the last update of the full SciTE4AutoIt3 installer which mainly had to do with the fact that Neil was moving toward v5 of SciTE and there weren't many functional changes in SciTE v4 other than to support the different setup of the Lexers to be used in V5. This is likely the final version with support for WinXP as the upcoming V5 version of SciTE will likely drop WinXP altogether. 22-3-2021: Updated Tidy.exe, which caused a hardcrash reading the new au3.api definition, in the installed/portable zip and direct download. 23-3-2021: Updated AutoIt3Wrapper.au3, which was running the "#autoIt3Wrapper_run_after" defined programs twice in some occasions. ==> SciTE4AutoIt3 v21.316.1639.2 Change log: -------------------------------------------------------------------------------------------------- 16-03-2021 *** Merged the SciTE v 4.4.6 by Neil Hodgson with our own version of SciTE. (Jos) - Change the workdir to the programdir to avoid locking up the last opened scriptfile directory. - Fixed Bom checking bug resulting to garbage characters in the editor for UTF encoded file other than UTF8 - Dropped support for WinXP (Compiled with vc15, Win sdk 8.1, Toolset v141) - Compiled with vc15 and changed SSE instruction set to ia86 compatible. *** Updated AutoIt3Wrapper v21.316.1639.0 (Jos) - 19.1127.1402.1 added clear errors when Tidy is ran with Ctrl+T. - 19.1127.1402.2 Avoid running Tidy for a second time when script needs to be run with #RequireAdmin in elevated mode. - 19.1127.1402.5 Added work-around to support Unicode characters in filenames for: - au3check - Tidy - au3stripper - 19.1127.1402.6 Added Win10 build to info lines. (tnx argumentum) - 19.1127.1402.7 Fix for support of filenames containing special ascii characters too. - 19.1127.1402.8 Restored some DIrectives still used for versioning and fileversion. - 19.1127.1402.8 Fix for support of filenames containing special ascii characters too. - 19.1127.1402.9 Fix checking for "#AutoIt3Wrapper_Version"check till after the GUI is done. - 19.1127.1402.10 Fixed Versionupdate with /RunAfter option I use for AutoIt3Wrapper updates. - 19.1127.1402.11 Fixed issue with #include statements where the filename is enclosed in single quotes. - 19.1127.1402.13 Updated File prompt. - 19.1127.1402.18 added include filelist and their encoding when /debug is supplied - 19.1127.1402.19 Cosmetic update showing the ">Setting Program ExecutionLevel Manifest information to...." only when the directive is provided - 19.1127.1402.20 Fix for elevated scripts running from mapped drive - 19.1127.1402.21 again Fix for support of filenames containing special ascii characters. - 19.1127.1402.22 Fix invalid FileExist statement on line 550. - 19.1127.1402.26 Added #AutoIt3Wrapper_Res_Fileversion_Use_Template - 19.1127.1402.27 Changed Func ShowStdOutErr to only capture total STDOUT/ERR when required, Avoiding unnecessary memory consumption - 19.1127.1402.28 Fixed regression creating duplicate resource entries. *** Updated Au3Stripper v21.316.1639.0 (Jos) - 19.1127.1402.1 Option /rsln: Added replace for @ScriptLinenumber for #includes to contain source files and original linenumber. - Changed replace for @ScriptLinenumber to only replace none literal string occurrences. - 19.1127.1402.3 Changed replace for @ScriptLinenumber to only replace when not on FUNC line. - 19.1127.1402.5 Added directive "#Au3Stripper_Ignore_Errors_in_Func=", which will suppress any errors triggered within the defined Functions. - 19.1127.1402.7 Fix for Func names in FUNC parameters to avoid stripping the target function. *** Updated SciTEConfig v21.316.1639.0 (Jos) - 19.1127.1402.1 - Fix bug in AbbrevMan.au3 when pipe symbol is used to set cursor position. (Melba23 *** Updated Tidy v21.316.1639.0 (Jos) - v19.1127.1402.2 fixed some issues in the /gendoc option: - func reference lines weren't listed - only show variables starting with $ or @ - v19.1127.1402.5 Default Tabsize to SciTE-TabSize when not provided. - v19.1127.1402.6 Made the backp sequencenumber 2 digits. old filenames will be converted. - v19.1127.1402.10 Reversed the 2 digit sequencenumber as this will fail when there are more than 99 backup versions. *** Updated Abbreviations (mLipok) - Updated au3abbrev.properties and helpfile page. Enjoy, Jos

Yes you can, as I did it in my player : GUICtrlSetTip($idRepeat, ($bRepeat ? "Désactiver" : "Activer") & " la lecture répétée")

Invicore, Great. But when you reply in future, please use the "Reply to this topic" button at the top of the thread or the "Reply to this topic" editor at the bottom rather than the "Quote" button - I know what I wrote and it just pads the thread unnecessarily. Thanks in advance for your cooperation. M23

Invicore, You can change the colour of the bar itself like this: #include <GUIConstantsEx.au3> #include <ProgressConstants.au3> #include <SendMessage.au3> $hGUI = GUICreate("Test", 300, 380) GUIStartGroup() $cRadio_1 = GUICtrlCreateRadio("Green", 60, 95, 60, 20) GUICtrlSetState(-1, $GUI_CHECKED) $cRadio_2 = GUICtrlCreateRadio("Red", 120, 95, 60, 20) $cRadio_3 = GUICtrlCreateRadio("Yellow", 180, 95, 60, 20) $cProgress = GUICtrlCreateProgress(25, 130, 250, 15) GUICtrlSetData(-1, 50) GUISetState() While 1 Switch GUIGetMsg() Case $GUI_EVENT_CLOSE Exit Case $cRadio_1 _SendMessage(GUICtrlGetHandle($cProgress), $PBM_SETSTATE, 1) Case $cRadio_2 _SendMessage(GUICtrlGetHandle($cProgress), $PBM_SETSTATE, 2) Case $cRadio_3 _SendMessage(GUICtrlGetHandle($cProgress), $PBM_SETSTATE, 3) EndSwitch WEnd No idea about how to change the background. M23

Probably YES. Possibly YES Check e.g. are-my-autoit-exes-really-infected EDIT : Damn, @seadoggie01 was a little faster

You have made a few statements and have not asked a single question or provided any details other than an HTTP status code. I try not to make assumptions. However, one thing is almost certain, if it was working before and now it isn't, then your issue is most likely not related to the AutoIt script. Unless, of course, you modified it in such a away that would cause the error. But I have no way of knowing because you didn't provide the script that you're running. So if you want assistance, you need to provide much more information, starting with the script that you are running -- not a few lines without context but a script that reproduces the issue. If I were to give a wild guess, which I really hate doing, then I would guess that the site has anti-hammering and other protections that try to keep people from doing whatever it is you're trying to do. So my guess is that you are trying to test your script over and over and have tripped one of their mitigation routines.

Match everything except the delimiter char. In RegEx (PCRE) you can define negative char groups with [^...] Edit: Ah I have now understood what you actually want. In principle you could put this into a single pattern but whether it actually works as desired still depends on the pattern in $RegExpPat. You can't treat this pattern as you might think. For example, in your example you would have to make sure that the quantifier is lazy, otherwise everything up to the end of the string would be matched: #include <Array.au3> $s = "" For $i = 1 To 1000 $s &= "|" & Round(Random(0, 15), 2) Next _ArrayDisplay(ArrRegExp($s, "|", ".*?")) Func ArrRegExp(ByRef $sString, $delim = ",", $RegExpPat = ".*") Return StringRegExp($sString, '(?<=\Q' & $delim & '\E)' & $RegExpPat & '(?=\Q' & $delim & '\E|\Z)', 3) EndFunc Therefore it should be the cleanest variant to first separate everything and then use the second Pattern to filter the results: #include <Array.au3> $s = "" For $i = 1 To 1000 $s &= "|" & Round(Random(0, 15), 2) Next _ArrayDisplay(ArrRegExp($s, "|", ".{5}"), Example) Func ArrRegExp(ByRef $sString, $delim = ",", $RegExpPat = ".*") Local $aVals = StringRegExp($sString, '[^\Q' & $delim & '\E]+|(?<=\Q' & $delim & '\E|\A).{0}', 3) Local $aRet[UBound($aVals)], $cCount = 0 For $sVal In $aVals If StringRegExp($sVal, $RegExpPat) Then $aRet[$cCount] = $sVal $cCount += 1 EndIf Next Redim $aRet[$cCount] Return $aRet EndFunc

Updated Tidy.exe, which caused a hardcrash when reading the new au3.api definition, in the installer/portable zip and direct download.

What you get is a recipient object (according to the MS docu I linked to in my last post). Use $oOutlook.GetNameSpace("MAPI" ).CurrentUser.Name to get the display name.

I suggest that you find different code to learn from. My crystal ball says there won't be much in the way of help with that one.