Leaderboard

Easy_Dism Primary goal is an easy to use, user friendly interface! For amateur and expert alike. Download Page Windows 8.1 and 10 you can now run Easy_DISM from anywhere. No need to add dism files to Easy_DISM folder. Requirement: For Windows 7 only, Dism files Must be located in Easy_DISM folder. Reason for this gives the ability to use Easy_DISM from any version Windows OS or PE Recommend DISM 10 and can be used on any Windows Image from 7 to 10 (Probably add Vista also). Use Get Waik Tools "Thanks to JFX" and download Dism for 10. Download GetWaik Restrictions: Easy_DISM Program folder must not contain any blank spaces in path! If running from PE just use the plugin and everything will be done automatically. http://theoven.org/index.php?topic=955.msg11799#msg11799 Easy_DISM v2.5 Added AppPkg Tab. This was all for Subz and created by Subz. Primary focus on removing Apps and the process he came up with is really simple to use. Add AppPkgs Untested and I won't pursue unless requested. Program Update: In Windows 8.1 and 10 No longer necessary to run from same folder as DISM files. Removed Edit tab and need for Imagex. Easy_DISM v2.4.1 Thanks to Subz new process sorting exported drivers New folder structure will be SaveFolder\ClassName\ProviderName\blahblahblah\driverfiles Easy_DISM v2.4 New Progress Bar! Driver Export\Import Now uses PnPutil as default installer available in all Windows and PE SE projects DPinst option still available Easy_DISM v2.3 Added a Progress Bar and eliminated Cmd Window all tabs except pkgs and features. As I added Progress Bar and testing fixed a few bugs already present and fixed any new bugs caused by the new addition (I Hope). Biggest source of problems has always been spaces in file path so if you find any let me know.

Try this.. ; - Replace this Local $Text = GUICtrlCreateLabel('HKEY_CLASSES_ROOT\Directory\Background\shell\07 Sync\command', 10, 10, 200, 45, $SS_LEFT, $WS_EX_CLIENTEDGE) ; - With Local $trimamount = 31 Local $Text = 'HKEY_CLASSES_ROOT\Directory\Background\shell\07 Sync\command' Local $Text_len = StringLen($Text) Local $Text_P1 = StringTrimRight($Text, $Text_len - $trimamount) Local $Text_P2 = StringTrimLeft($Text, $trimamount) Local $Output = $Text_P1 & @CRLF & $Text_P2 GUICtrlCreateLabel($Output, 10, 10, 200, 45, $SS_LEFT, $WS_EX_CLIENTEDGE)

Why would it be 4? 100-100 = 0, so your parameter is 0. You would need to use example("100-100") to return a string.

In my book, 100 - 100 = 0 You probably mean "100-100"

Something like this maybe? #include <Array.au3> $query_logo_niveau = "SELECT logo.niveau FROM logo where logo.num_col = '" & Guictrlread($numcol) & "';" $AdoCon2 = ObjCreate("ADODB.Recordset") $AdoCon2.ActiveConnection = $AdoCon $AdoCon2.Open($query_logo_niveau) $RS2 = $AdoCon2.getstring() $aRS2 = StringSplit($RS2, @CR) _ArrayDisplay($aRS2)

That is because cmd.exe (command prompt) returned 1 (That means the call actually succeeded). Failure only occurs if the process/command was not able to execute, in this case, the command did execute. _RunDos is just a wrapper for cmd.exe (look at the code yourself). That means cmd.exe was successfully executed and therefore there is no failure here, hope I have cleared your doubt

aa2zz6, subz, F.Y.I, SetSel is Not required. The third parm of GuiCtrlSetData ensures that the caret (insertion point) is always at the end... #include <StaticConstants.au3> #include <GUIConstantsEx.au3> #include <GuiEdit.au3> #include <ScrollBarsConstants.au3> #include <date.au3> #AutoIt3Wrapper_Add_Constants=n Local $gui010 = GUICreate('Edit Example') $log1 = GUICtrlCreateEdit("", 20, 40, 170, 300) $log2 = GUICtrlCreateEdit("", 210, 40, 170, 300) Local $btn010 = GUICtrlCreateButton('Clear', 20, 360, 360, 20) GUISetState() AdlibRegister('Write_Log', 100) While 1 Switch GUIGetMsg() Case $GUI_EVENT_CLOSE Exit Case $btn010 GUICtrlSetData($log1, '') ; <----- clear the logs GUICtrlSetData($log2, '') ; <----- clear the logs EndSwitch WEnd ; fill the log up to show scrolling Func Write_Log() GUICtrlSetData($log1, _NowCalc() & @CRLF, 1) GUICtrlSetData($log2, _NowCalc() & @CRLF, 1) ;$iEnd = StringLen(GUICtrlRead($gui010)) ;_GUICtrlEdit_SetSel($gui010, $iEnd, $iEnd) ;_GUICtrlEdit_Scroll($log1, $SB_SCROLLCARET) EndFunc ;==>Write_Log kylomas edit: None of the scrolling is required.

Just for grins you may want to try my compiled UpdateEnv program. It uses a variation of Melba's Toast with 3 calls to EnvUpdate() and sleep while the toast is showing. Just makes it obvious to the user that something is happening. Mainly I use it to flush the Registry to disk without having to log out and back in. That is why I make 3 calls. Just to try to drive in the nail. The file is UpdateEnv.zip on the page below http://milesaheadsoftware.org/ btw I have noticed on Windows 7 and Windows 8.0 that EnvUpdate() can have long delays and hang at times. I think that is one reason I wrapped it in Toast. To make it obvious where the program was pausing. It seems to require killing via Task Manager much less often the way I have it now. Three calls interspersed with calls to Sleep(). If I just let it sit it will usually complete on its own accord. Most times it runs as expected though. I have no idea why unless the Registry has lots of changes to save to disk? I don't know.

Hey folks, I just explored the new helpfile and found a new Keyword (dunno if its that new, but i never saw it before) called Volatile. It was made especally for CallBack and Com event functions, so I wanted to try that out. the advantage of this Keyword is, that you can run the Dll while you can do other things in autoit (AutoIt wont freeze/pause anymore while the dllcall is executed!) I made up a little example i want to share with you, the c source is compiled in MinGW, you need at least AutoIt 3.3.10.2. Hope you like it, would be interested in some comments Greetz, Spider testLibCallback.zip