Jump to content

XPect

Member
 View Profile  See their activity

  • Posts

    80

  • Joined

  • Last visited

  • Donations

    0.00 USD 

  • Country

    France

 Content Type 

Posts posted by XPect

    Toggle between 2 versions ..

    in WIHU

    Posted

    This one is quite easy, it's show in the install.ini that come with wihu

    description.0.1.2=Group test

    command.0.1.2=cmd.exe /c @echo command.0.1.2

    group.0.1.2=1

    description.0.1.2.0=Option 1

    command.0.1.2.0=cmd.exe /c @echo Option 1

    description.0.1.2.1=Option 2

    command.0.1.2.1=cmd.exe /c @echo Option 2

    description.0.1.2.2=Option 3

    command.0.1.2.2=cmd.exe /c @echo Option 3

    selected.0.1.2.1 = 1

    group.0.1.2.0=1

    The command to use is goup.x = 1

    This signify that the lower levels are options and that you can only select one of them.

    Hope this help.

    0

    can't understand test.eval

    in WIHU

    Posted

    Hello,

    Test.eval is designed to test a file (existence or version) or a registry key (existence or value), not to test another item in wihu.

    If you want to chek 7 if 6 is checked, use subitems like this:

    description.6 = XnView v1.74

    command.6 = %SRCDRIVE%\$MistoMare$\XnView-win-full_v1.74.exe /VERYSILENT /SP-

    selected.6 = 1, inherit

    description.6.0 = XnView v1.74 - registry settings

    command.6.0 = regedit /S %SRCDRIVE%\$MistoMare$\XnView_config.reg

    I think this will do what you need ;)

    Another tip, you can do this also without showing the second command to the user, to be shure that the second one is not accidentaly uncheked by hidding the second command, just had this line:

    hidden.6.0=1
    0

    WMI Unattended (Auto detect and install driver)

    in Device Drivers

    Posted

    Hello, 1st of all I'm not shure this is the right place to post, on my understanding must be in the main Unattended Windows section while it's not directly related to wihu.

    Anyway your project seem interresting on the hardware detection part. How did you do it ?

    This could be a complement to wihu, to automaticaly install drivers with criterion not only based on reg key or files test.

    Regards

    0

    Still don't understand its functions.

    in WIHU

    Posted

    My modest contribution

    Wihu should be consider in 2 ways:

    - 1st like any cmd file to be abble to automaticaly add software in your unattended install but with testing capabilities and possibility to easilly add/change users

    - 2nd like a post install wizard to be abble to select additional soft to install to a specific machine.

    I use it in both way, a 1st pack of soft are installed thru unattended setup and I re run wihu on windows 1st run to select other softs to install... :yes:

    0

    problems with office xp

    in WIHU

    Posted

    Could be just that wihu doesn't find the Custom.mst.

    Try to had the path of the file in the command line, something like

    command.0 = %SRCDRIVE%\soft\officexp\setup.exe TRANSFORMS=%SRCDRIVE%\soft\officexp\Custom.mst /qb-

    let us know the result

    XPect

    0

    Check OS and install hotfixes

    in WIHU

    Posted

    I agree, if a sub item doesn't respect the same selection rules than the orignal item, inherit sould not be used, it's just logic.

    I got the same problem to differentiate a program installation than the icon removal and the registering. At the end it's more logic to just add a different test per sub item, even is the test is the same for several sub items...

    0

    Inf-File misbehaving

    in WIHU

    Posted

    Why don't you code the install directly in wihu rather than using inf file ?

    For me or you use wihu or you use xplode, but I don't see the interest of having a mix of the 2, but maybe I'm missing something.

    What is your purpose ?

    0

    New testing system and files existence

    in WIHU

    Posted

    I will send them a mail, but I'm not shure they will be as reactive as you ;)

    Thanks for the mofification anyway.

    PS: Do you have somewhere a list of all command available now ? (I've tried your doc but German is to difficult for me)

    Just a list should be ok, I should be abble to understand the purpose now :D

    Regards

    XPect

    0

    New testing system and files existence

    in WIHU

    Posted

    I've tested the exe, I wil try to find another file.

    Anyway (I'm not very aware on how files handle version) what sound stange to me is that when I open properties on the exe, the dialog box show version information.

    That's why have asked.

    Thanks

    XPect

    0

    A little help on how command.x work please

    in WIHU

    Posted

    Hello Benjamin,

    Can you give me a little help on how command.x work please.

    This doesn't work

    command.0 = cmd.exe /c del /F "%UserProfile%\Bureau\Directory Lister.lnk"
    This work
    command.0  = cmd.exe /c %apps%\02-Utils\DirectoryLister\_RemoveIcon.cmd

    Batch File _RemoveIcon.cmd:

    @Echo off

    del /F "%UserProfile%\Bureau\Directory Lister.lnk"

    I don't understand why the 1st one doesn't work. Can you give me the clue :rolleyes:

    0

    New testing system and files existence

    in WIHU

    Posted

    Hello Benjamin,

    I use this to check if prog version is lower than the one to be installed (please note the use of the %PowerArc.ver% to display the version installed ;) )

    description.4 = PowerArchiver 9.02 [Version Installed : %PowerArc.ver%]command.4 = %apps%\02-Utils\PowerArchiver.exe /sp- /verysilent /norestart

    test.4.0 = %ProgramFiles%\PowerArchiver\POWERARC.EXE?<9.02

    test.eval.4 = 0

    Disabled.4 = if.false

    Selected.4 = if.true

    flags.4  = italic:if.false

    Work fine is the file exist, but if the file don't exit the test return false.

    This was not the case with the previous testing method (If I do remember the version was set to 0 if the file don't exist)

    So I'm obliged to double the test like this

    description.4 = PowerArchiver 9.02 [Version Installed : %PowerArc.ver%]command.4 = %apps%\02-Utils\PowerArchiver.exe /sp- /verysilent /norestart

    test.4.0 = %ProgramFiles%\PowerArchiver\POWERARC.EXE?<9.02

    test.4.1 = !%ProgramFiles%\PowerArchiver\POWERARC.EXE

    test.eval.4 = 0 | 1

    Disabled.4 = if.false

    Selected.4 = if.true

    flags.4  = italic:if.false

    Not a real problem but I would like to know if this is voluntary or a bug

    Regards

    XPect

    0

    Req : Windows size & position in % of screen

    in WIHU

    Posted

    Hello Benjamin,

    Devinitively can't post images there so I've join a small fil with 2 samples of splitterpos problem.

    [Edit]

    Found the problem, it come from the command line.

    If I use

    wihu /usecurrent /skiprestart /skipsettings /INI=registry.ini
    The splitterpos is ignored (but dimension.width and dimension.height works)

    If I use

    wihu /usecurrent /skiprestart /INI=registry.ini
    everything work

    Seem to be a little bug anyway :whistle:;)

    Regards

    XPect

    Sample.zip

    0

    Req : Enhancement to environment vars

    in WIHU

    Posted

    Scripting could be good definitely, but as you mention need a big rewriting ;)

    I was thinking more to something like your 1st example or like you do for the testings in the test.x

    I don't see what other uses users can do with such vars, so this could be a good starting point

    Regards

    XPect

    0

    Req : Enhancement to environment vars

    in WIHU

    Posted

    Benjamin,

    Please take a look at this ini

    [Environment]Test = HKCU:Control Panel\Desktop\MenuShowDelay

    [Var Test]

    description.0 = Faster menu display (0.1 second) [Actual value : %Test%]

    command.0  = regedit /s %reg%\UI-StartMenu-Gobal-MenuShowDelay.reg

    test.0.0  = HKCU:Control Panel\Desktop\MenuShowDelay?=100

    test.eval.0  = 0

    disabled.0  = if.true

    selected.0  = if.false

    As you can see I initialise a var Test that will contain the registry key value (here menushowdelay) and use this var to display actual value in the item description.

    Is it possible to do the same thing with program version, I've tried but it's not working.

    The idea beyong is to display actual prog/DLL version in the description, as an help for users to evaluate if they should really upgrade or not.

    Hope I'm enougth clear :D

    0
×
×
  • Create New...