WA Installer 2.7- 3.0.6.0B - WA Cmd 0.1 (9-4)

[Guest]

You saw this, right?

yep and already added it to the new version

[Guest]

ok i found a bug

i was rereading the guide

when i got into this

if ! doesn't exist in the build it should be passed

if the Os Build is newer than the one being used

but the good thing is

there is an ignore button

i wanted to tell you guys

right now i'm just working on compressing the code

so a new version might be out in a couple of days

( but would only have this bug fix )and the some new commands

i'm trying also to make the progress more effective

as when copying files the progress moves ( but i'm still reading this part)

that all what i wanted to say any other bugs please report

[testesser1]

Hi,

thanks for your great tool. :thumbsup_anim:

I've translated the language-file to german. Maybe you can add it to your next release?

greets

testesser1

German_lang_WA_2.5.7z

[Guest]

Hi,

thanks for your great tool. :thumbsup_anim:

I've translated the language-file to german. Maybe you can add it to your next release?

greets

testesser1

thx for tranlating it

i just installed a new os

i will just finish some stuff and will see if i can finish the new version today

and i will put the new lang in it

just a wired notice

Edit:

didn't testesser1 translated to Dutch

and a dutch translation is already done by Rauol

what is the difference then ??

Edited October 6, 2009 by DaRk MaDnEsS

[testesser1]

didn't testesser1 translated to Dutch

and a dutch translation is already done by Rauol

what is the difference then ??

The difference is the speech and the country:

German (Deutsch) --> Germany (Deutschland)

Dutch --> Holland or Netherland (Niederlande)

They are only bordering countries, and have not the same speech.

[Guest]

The difference is the speech and the country:

German (Deutsch) --> Germany (Deutschland)

Dutch --> Holland or Netherland (Niederlande)

They are only bordering countries, and have not the same speech.

hmm ok nice to know that

then next version i will make

German Dutch

and Netherland Dutch

i hope the new version will be soon i just need to test some stuff

[testesser1]

no, you misunderstand me. i'll try to explain.

Country - - - - - - - -> speech

United Kingdom (UK) -> english

USA - - - - - - - - - -> english

Netherland (Holland) -> dutch

Germany - - - - - - -> german

the english word "german" translated to german language is called "Deutsch". it has nothing to do with "dutch".

I hope that's clear now.

[Guest]

no, you misunderstand me. i'll try to explain.

Country - - - - - - - -> speech

United Kingdom (UK) -> english

USA - - - - - - - - - -> english

Netherland (Holland) -> dutch

Germany - - - - - - -> german

the english word "german" translated to german language is called "Deutsch". it has nothing to do with "dutch".

I hope that's clear now.

oh my bad

i mis understood i get it now

for some reason i didn't want to understand that

[testesser1]

Hi,

i've added a new lang-file. I only changed the "LangInFo" to "German", so nobody can confuse with "Dutch".

Another Question. Is it possible that i can change the language of you tool, without editing "Option.ini"?

German_lang_WA_2.5_v2.7z

[Guest]

Hi,

i've added a new lang-file. I only changed the "LangInFo" to "German", so nobody can confuse with "Dutch".

Another Question. Is it possible that i can change the language of you tool, without editing "Option.ini"?

well the only way is using Option.ini

until i finish the current version i'm working on

[testesser1]

Hi *reaper*,

thank you for the addons. I installed the winrar-x64-addon with WA-installer on Win7 x64 on running system. Installation was working well, but the links from startmenu point to wrong install-dir. They point to "C:\Program Files (x86)".

Another Problem that i have. I tried to uninstall winrar x64 from control panel but it gave me this error.

So i was looking to winrar.inf.

[uninstall]
BeginPrompt =BeginUnInsPrompt
RunPreSetupCommands=Run.Uninstall
...
[Run.Uninstall]
%16422%\%PROG_NAME%\Uninstall.exe

For me it looks correctly. So i searched the registry and found a strange entry.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion]

"CommonFilesDir"="C:\\Program Files\\Common Files"

"CommonFilesDir (x86)"="C:\\Program Files (x86)\\Common Files"

"CommonW6432Dir"="C:\\Program Files\\Common Files"

"ProgramFilesDir"="C:\\Program Files"

"ProgramFilesDir (x86)"="C:\\Program Files (x86)"

"ProgramFilesPath"=%ProgramFiles%

"ProgramW6432Dir"="C:\\Program Files"

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion]

"CommonFilesDir"="C:\\Program Files (x86)\\Common Files"

"CommonFilesDir (x86)"="C:\\Program Files (x86)\\Common Files"

"CommonW6432Dir"="C:\\Program Files\\Common Files"

"ProgramFilesDir"="C:\\Program Files (x86)"

"ProgramFilesDir (x86)"="%ProgramFiles(x86)%

"ProgramW6432Dir"="C:\\Program Files"

Shouldn't be the two entries the same, without the red (x86)? After removing the two "(x86)" i could uninstall winrar without problems.

Did MS make a BIG mistake, or are the entries correctly?

Thanks for your help.

[Guest]

Hi *reaper*,

thank you for the addons. I installed the winrar-x64-addon with WA-installer on Win7 x64 on running system. Installation was working well, but the links from startmenu point to wrong install-dir. They point to "C:\Program Files (x86)".

Another Problem that i have. I tried to uninstall winrar x64 from control panel but it gave me this error.

So i was looking to winrar.inf.

[uninstall]
BeginPrompt =BeginUnInsPrompt
RunPreSetupCommands=Run.Uninstall
...
[Run.Uninstall]
%16422%\%PROG_NAME%\Uninstall.exe

For me it looks correctly. So i searched the registry and found a strange entry.

Shouldn't be the two entries the same, without the red (x86)? After removing the two "(x86)" i could uninstall winrar without problems.

Did MS make a BIG mistake, or are the entries correctly?

Thanks for your help.

the problem doesn't have anything to do with the addon

it's a serious bug i found in Wa Installer

it's fixed in a testing version i'm working on

the problem was connected to the 64 kernel as it changes the direction to the 32 bit dir (program files (x86) etc..)

i already made a workaround to fix that issue

and it seems it's installed fine now

the release would be on today in a couple of hours

[testesser1]

I got i working now. The Registry-Entry is correct!

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion]

"CommonFilesDir"="C:\\Program Files (x86)\\Common Files"

"CommonFilesDir (x86)"="C:\\Program Files (x86)\\Common Files"

"CommonW6432Dir"="C:\\Program Files\\Common Files"

"ProgramFilesDir"="C:\\Program Files (x86)"

"ProgramFilesDir (x86)"="%ProgramFiles(x86)%

"ProgramW6432Dir"="C:\\Program Files"

I installed a new clean Win7 x64 without addons or anything. I removed the (x86) in the registry. After that i installed original winrar-setup x86, but it installed it to "C:\Program Files\Winrar" - which is the false dir for a x86-application. That's why i think the Registry is correct.

I got managed it changing the target-path from link to "%ProgramFiles%\Winrar\Winrar.exe". and now it's working well.

EDIT: Now i installed winrar-addon (links were corrected) with WA-Installer (all links are correct) and tried to uninstall with control panel. But it gaves me the same error again.

So a think it's a MS bug. The DirID %16422% from winrar.inf isn't redirected correctly from Windows. Or the DirID isn't correct, i don't know.

Edited October 8, 2009 by testesser1

[Guest]

testesser1

you should have translated the one i attached in the topic it had some other strings not in the

one in the lang folder

so i need the translate in this two lines

[Installer]
UpperLabel=Install WA Installer on your Computer
SecondLabel=WA Installer Will be Installed On Your computer&If you want to Continue Press Install

[Guest]

I got i working now. The Registry-Entry is correct!

I installed a new clean Win7 x64 without addons or anything. I removed the (x86) in the registry. After that i installed original winrar-setup x86, but it installed it to "C:\Program Files\Winrar" - which is the false dir for a x86-application. That's why i think the Registry is correct.

I got managed it changing the target-path from link to "%ProgramFiles%\Winrar\Winrar.exe". and now it's working well.

EDIT: Now i installed winrar-addon (links were corrected) with WA-Installer (all links are correct) and tried to uninstall with control panel. But it gaves me the same error again.

So a think it's a MS bug. The DirID %16422% from winrar.inf isn't redirected correctly from Windows. Or the DirID isn't correct, i don't know.

i told you before the issue from this addon

is not reaper fault

it's my WA Installer issue

this version should already be installed to Program Files not Program Files (x86) << that my tool problem

[testesser1]

i told you before the issue from this addon

is not reaper fault

it's my WA Installer issue

this version should already be installed to Program Files not Program Files (x86) << that my tool problem

Ok, I think the WA installer installed the addon correctly (except the links). It was installed to "C:\Program Files\Winrar".

But if i want to uninstall through control panel, the "UninstallString" from registry

rundll32.exe advpack.dll,LaunchINFSection WinRAR.INF,Uninstall

calls the "Winrar.inf". There at section [Run.Uninstall] it calls "%16422%\%PROG_NAME%\Uninstall.exe". In this case it calls "%16422%\WinRAR\Uninstall.exe". But windows tries to execute

C:\Program Files (x86)\WinRAR\Uninstall.exe

So i think that the DirID %16422% isn't redirected correctly.

[Guest]

Ok, I think the WA installer installed the addon correctly (except the links). It was installed to "C:\Program Files\Winrar".

But if i want to uninstall through control panel, the "UninstallString" from registry

rundll32.exe advpack.dll,LaunchINFSection WinRAR.INF,Uninstall

calls the "Winrar.inf". There at section [Run.Uninstall] it calls "%16422%\%PROG_NAME%\Uninstall.exe". In this case it calls "%16422%\WinRAR\Uninstall.exe". But windows tries to execute

So i think that the DirID %16422% isn't redirected correctly.

%16422% is Program Files not Program Files (x86)

it's working fine in here (there is another issue that might happen )

seems it's not the one i'm fixing

but i don't know it's working fine in here any way

[testesser1]

Here it is

[installer]

UpperLabel=WA Installer auf deinem Computer installieren

SecondLabel=WA Installer wird auf deinem Computer installiert&Zum Fortsetzen auf "Installieren" dr

Edited October 8, 2009 by testesser1

[Guest]

Updated to 2.6.0.0

[Guest]

just if any one had any issue with V 2.6.0.0

and i think there is a lot of issue that may happen

i will try to fix it

and i will work on V 3 now

as i will write half the program from scratch

as well as Cab Maker 3.5

both this tool will need a lot of work on the upcoming version

so i'm sorry if i didn't give the full support to this versions

[XC*LUSiVE]

Turkish Translation:

http://www.mediafire.com/download.php?vdayyimhdj1

Edited October 10, 2009 by XC*LUSiVE

[Guest]

Turkish Translation:

http://www.mediafire.com/download.php?vdayyimhdj1

thx for the translation

ok guys since i'm rewriting the code

and now i'm using the windows copy system

to overcome the autoit problems with the windows

ok now what you would like to be in this version

the new idea i think i would support multi files installer

when you run the program from shortcut and in the command mode

right now i'm just writing the gui progress

on today almost all the old feature would be written

except (Uninstaller and Command)

[testesser1]

Hi,

i figured out, why i couldn't uninstall the Winrar-addon (from *reaper*). The problem is the WA installer. He imports the reg.reg inside the winrar-addon to the false subkey in the registry.

Normally the reg should be imported to "HKLM\Software\...", but your tool imports the reg to

"HKLM\Software\Wow6432Node\...". Maybe this is the problem with shortcuts too.

I don't know, which "regedit.exe" your tool is using, but if you start the "regedit.exe"

from "%systemroot%\SysWOW64" than ALL reg-entries are redirected to "HKLM\Software\Wow6432Node\..."

This subkey is for 32bit only. Maybe this article from MS helps.

I've also a problem with the new v2.6.0.0. I get this error on every Addon i try to install.

And no files were copied.

I found another cosmetic error. If i install an addon, which contains only a reg-file (for tweaks), then the statusbar isn't "green" at finish.

[Guest]

Hi,

i figured out, why i couldn't uninstall the Winrar-addon (from *reaper*). The problem is the WA installer. He imports the reg.reg inside the winrar-addon to the false subkey in the registry.

Normally the reg should be imported to "HKLM\Software\...", but your tool imports the reg to

"HKLM\Software\Wow6432Node\...". Maybe this is the problem with shortcuts too.

I don't know, which "regedit.exe" your tool is using, but if you start the "regedit.exe"

from "%systemroot%\SysWOW64" than ALL reg-entries are redirected to "HKLM\Software\Wow6432Node\..."

This subkey is for 32bit only. Maybe this article from MS helps.

I've also a problem with the new v2.6.0.0. I get this error on every Addon i try to install.

And no files were copied.

I found another cosmetic error. If i install an addon, which contains only a reg-file (for tweaks), then the statusbar isn't "green" at finish.

yeah i know about the registry error

i'm still trying to figure a work around

but i think i found a workaround already

second about the error

try to drop to ver 2.5.0.0

as i said before the error would stay in that version and it's fixed in v3

third

hmm well you got a point about the reg thing

it would be fixed

i woll over the V 2.7.0.0

will go directly to 3

it would take 2 other days to get it finished

just the way i add the registry needs to be checked and to be sure it's 100% right and would't do that error in some PC

Edit:

Just to report after 3 hours of testing

i manged to produce the error and make the successful work around

now the tool in the next version would be 0 error in 64 bit

(working on a 64 bit is better than making a workaround and make some test it)

so just couple of days and the version would be ready

Edited October 12, 2009 by DaRk MaDnEsS

[Guest]

well i would like to say some things

i got good news and bad news lets start with the bad one

after working on V3 and trying to keep the tool working on both 32 and 64 bit

it failed i couldn't overcome all the problems even if i did my best

so to make this tool 100% right i got to do this

make a separate file for 32 and 64

the good news since it would take me a longer time to re modify the

V3 i will make 2.7 that works that way

i already made it and it seems fine now

but i will need to make an installer

for each one

but i might make an inf installer