• Announcements

    • xper

      MSFN Sponsorship and AdBlockers!   07/10/2016

      Dear members, MSFN is made available via subscriptions, donations and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, become a site sponsor and ads will be disabled automatically and by subscribing you get other sponsor benefits.
kenedy

kTool (just another software selector)

146 posts in this topic

Removed

Link to beta version is moved to first post.

Edited by kenedy
0

Share this post


Link to post
Share on other sites

Hi Kenedy

Thanks for updating your simple yet powerful tool. I like the fact that it has the functions I need and nothing more (I love the clear .ini file format).

I have one simple request though. I like the fact that Ktool selects an .ini file depending on the OS, but I would also like to specify a .ini file, WITHOUT Ktool going in to unattended mode.

Here's why I need it: During first logon, I call ktool with a .ini file that installs the default applications unattended, then I run a .vbs scripts, that detects the computer model, and either runs Ktool again with a specific .ini file for that computer (e.g. if its a notebook I would need to install notebook related software), or tells the user that it doesn’t know the computer model, and asks the user to select any extra applications by them self. This list shouldn't contain all the default programs I already installed, but only the extra programs for that OS.

- Best regards, Egil.

0

Share this post


Link to post
Share on other sites

egil

Sounds good.

And it fits well it new code. Will add it.

Two possible ways to to it:

1. Add key to .ini file

[Config]

Silent = 1/0

2. Add command line parameter

ktool.exe inifile.ini /silent=1

Which one would be better?

0

Share this post


Link to post
Share on other sites

I'd would say that the second option is better, to use a /silent switch. This way the the .ini file can be used in a non-unattended situation, thus keeping the number of .ini files down, which leads to less maintenance.

With that in mind, you should generally keep things like "silent mode", "reboot after xx seconds" - basically options that is only valid for a specific run of Ktool, and options that apply to all programs, out of the ini files, so that a .ini file can be used in as many situations as possible.

0

Share this post


Link to post
Share on other sites
egil

Ok, I uploaded new version of 1.0beta and added comments.

Great, Ill just download it from the post above, here on page 3 right?

0

Share this post


Link to post
Share on other sites
egil

Ok, I uploaded new version of 1.0beta and added comments.

Great, Ill just download it from the post above, here on page 3 right?

Right.

0

Share this post


Link to post
Share on other sites

Hmm when I type "ktool-1.0b inifile.ini", it starts runing a silent install. Tried "ktool-1.0b inifile.ini /silent=0" as well.

What am I doing wrong?

0

Share this post


Link to post
Share on other sites

From page 3:

Addition:

-New command line switch "/GUI". Forces GUI mode for specified .ini file. Default action is still silent install.

"ktool.exe someinifile.ini /gui"

-Order of command line switches is not important any more

0

Share this post


Link to post
Share on other sites

bah didnt see that, did you edit your post?

btw shoudn't "Aviable" be "Available"? :)

0

Share this post


Link to post
Share on other sites

>>bah didnt see that, did you edit your post?

Yes :whistle:

>>btw shoudn't "Aviable" be "Available"? :)

Heh, can't get it right. It's the second time i misspelled it. :)

0

Share this post


Link to post
Share on other sites

I'm having some trouble with Ktool. The config/inis have the correct syntax, but when I try to install something, I get this error:

post-70-1097237305_thumb.png

0

Share this post


Link to post
Share on other sites

There is no error checking (currently).

Error is "can't find file specified". See at which item it happened (kTool is still running, just move error message) and check if all commands for that item are correct.

0

Share this post


Link to post
Share on other sites

:P First of all, i like this usefull tool very much :P

When i m making constant changes to the ini files to devellop en test my own cd i have te delete manually the ini files in the docu..............\temp directory. why are they not automickly removed?

(sorry for my english)

0

Share this post


Link to post
Share on other sites

AntonP

why are they not automickly removed?

I suggest you to try new beta version (link is in first post).

It works without making temp file.

0

Share this post


Link to post
Share on other sites

I have a problem launchining *.MSI files from CD,

They either put ktool into a "paused" mode or skips that software install alltpgether and continues to the next selection.

Any ideas ?

0

Share this post


Link to post
Share on other sites
Any ideas ?

Launch file without /qb switch, see if it gives any error message.

0

Share this post


Link to post
Share on other sites
Any ideas ?

Launch file without /qb switch, see if it gives any error message.

Thanks for the reply Kennedy

Removed /qb switches as you said,

But still the same, Goes into a paused state or skips it altogether with no error messages displayed.

Any more ideas on this ?

Thanks

0

Share this post


Link to post
Share on other sites

i made a new way to use this tool, i already had good sfx files to install.

i now use these files to install the problem cases as powerdvd5 etc.

i use sleep.exe as a timer to give the sfx enough time to setup. :wacko:

0

Share this post


Link to post
Share on other sites

AntonP

i use sleep.exe as a timer to give the sfx enough time to setup.

:blink:

Why? RunWait and WaitProcess are not working for sfx?

ironside

That seems to have fixed my problem.

There was bug in program. :rolleyes:

0

Share this post


Link to post
Share on other sites

I now now why Ktool RunWait launched to early when i used my sfx files.

In the sfx file i made a setup.cmd file. as soon as that was launched Ktool assumed that the sfx is ready.

I now launch that same setup.cmd from Ktool en now i dont need sleep.exe any more.

i also walked against a few msi files that would not install, i make a cmd file whit the following en than i have no problems

msiexec.exe /i daemon.msi /qn /norestart

:hello: thanks for the help here, the above is whit version 1b

0

Share this post


Link to post
Share on other sites

This is an excellent program! Much better (and easier) than the others I have seen out there. This is simple (in looks not functions) and it accomplishes the job which is exactly what i wanted out of a post-install progam.

A+ job!

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.