bug in autoLocalization

Hi psc!
Found some errors in processLocalization.script in the LiveXP project. Unfortunately i can't fix them, as they seem to originate in Localize.exe.
In processLocalization.script the variable DRIVELETTER% is used 3 times, insted of %DRIVELETTER%.

Another problem is the 'SendTo' folder, as it is created in 'Documents and Settings' instead of 'Dokumente und Einstellungen'.
Not sure if the fixing of the above will correct this error too or if it is related to the following error, from the WB Log, instead.

INIRead - Failed to read value from: [C:\BootBuilder\WinBuilder053Beta12\Projects\LiveXP\autoTweaks\autoLocalization\processLocalization.script] Section: [Main] Key: [Check] to variable: [%check%]

Happy bug hunting!

In processLocalization.script the variable DRIVELETTER% is used 3 times, insted of %DRIVELETTER%.

LiveXP has the version 19 of autoLocalize.Script.
The actual version 21 can be found here
(I'll try to update the server)

Another problem is the 'SendTo' folder, as it is created in 'Documents and Settings' instead of 'Dokumente und Einstellungen'.

That is hardcoded in shortcuts.Script and not an issue of autoLocalize.

INIRead - Failed to read value from: [C:\BootBuilder\WinBuilder053Beta12\Projects\LiveXP\autoTweaks\autoLocalization\processLocalization.script] Section: [Main] Key: [Check] to variable: [%check%]

This is a version check; the error occurs when processLocalization.Script is not yet generated.
Not nice, but does not disturbe correct project generation.

Peter

LiveXP has the version 19 of autoLocalize.Script.
The actual version 21 can be found

Never occured to me, that the file from the update-server might be out of date.

That is hardcoded in shortcuts.Script and not an issue of autoLocalize.

Thanks, will look into it.

This is a version check; the error occurs when processLocalization.Script is not yet generated.
Not nice, but does not disturbe correct project generation.

OK, thanks Peter

Where is my 'Dokumente und Einstellungen' and why do i have now a ProfilesDir?

Never occured to me, that the file from the update-server might be out of date.

There is samething with 'Beta' in the URL

Peter

Where is my 'Dokumente und Einstellungen' and why do i have now a ProfilesDir?

???
Please some words more!
Maybe a post of the log

Peter

???
Please some words more!
Maybe a post of the log

Peter

I take everything back and say the opposite!
I'm so used to updating without loosing my settings, that i keep forgetting, that i have to reenable settings in WB when updating.

I take everything back and say the opposite!
I'm so used to updating without loosing my settings, that i keep forgetting, that i have to reenable settings in WB when updating.

What about using myOptions?
Peter

LiveXP has the version 19 of autoLocalize.Script.
The actual version 21 can be found

Peter in the here posted version a path to the Archive folder is still present.
Had you fixed that before uploading to the downloadcenter?

Peter in the here posted version a path to the Archive folder is still present.
Had you fixed that before uploading to the downloadcenter?

The processLocalize script is build once and valid vor every project.
Maybe qith the new structure would be better for every project to have its own processLocalize.Script.

Peter

The processLocalize script is build once and valid vor every project.
Maybe qith the new structure would be better for every project to have its own processLocalize.Script.

Peter

You misunderstood, the Archive path is coded into the autoLocalize.Script, but we no longer have an archive folder.

You misunderstood, the Archive path is coded into the autoLocalize.Script, but we no longer have an archive folder.

I can rename it, but it has to be a folder under %basedir% and outside the different projects.

BTW: This version of localization is ice-age. Go to nativeEX.

Peter

I can rename it, but it has to be a folder under %basedir% and outside the different projects.

Why? I replaced your %basedir&\archive string with %projectdir% and it works like a charn.

BTW: This version of localization is ice-age. Go to nativeEX.

There is no autoLocalization.script in my nativeEX project and downloader does not show anything missing.

Why? I replaced your %basedir&\archive string with %projectdir% and it works like a charn.

That's ok, but it brings the same processLocalization script into every project.
Again a question of the new structures.

There is no autoLocalization.script in my nativeEX project and downloader does not show anything missing.

It is a part of the hivesFactory

Peter

It is a part of the hivesFactory

Peter

Ah, now i get it! Not, that's an old script, go to nativeEX and use the new one, but use nativeEx instead!

At the moment, i work on making the standart project work as flawless as possible without actually having to invent own scripts. Just a little bugfixing.
When everything works, i will try to merge it to LiveXP and nativeEX.

PS: nativeEx is a great idea, but unfortunately to many scripts seem not to work yet right with it.

PS: nativeEx is a great idea, but unfortunately to many scripts seem not to work yet right with it.

That's our job for the near future!

Peter

That's our job for the near future!

Peter

Yep, it is, but i think we should also have a stable product for our customers.

Yep, it is, but i think we should also have a stable product for our customers.

Just have a look at the blue lines at bottom
Peter

Just have a look at the blue lines at bottom
Peter

I'm more in favour of the M$ way. Always have an ok product to sell, while working on the superior one!

I'm more in favour of the M$ way. Always have an ok product to sell, ...

I saw a lot of products they sold, but I do not remember having ever seen a product ready to sell
And M$ has ??? thousand developers, and we ??

Peter

And M$ has ??? thousand developers, and we ??

You for the improved version and me for the outdated one.

So we should make faster progress than M$!

You for the improved version and me for the outdated one.

So we should make faster progress than M$!

I have a very serious question : Why do we keep two different projects that do almost the same thing? WE can merge them as MedEvil said. Let's create a barand new project with a different name wich will be compatible with the scripts of both projects.


John

I have a very serious question : Why do we keep two different projects that do almost the same thing? WE can merge them as MedEvil said. Let's create a barand new project with a different name wich will be compatible with the scripts of both projects.
John

I'm not yet so deep into the projects, but i don't think it can or should be done.
The way i see it:
- LiveXP is the 'easy' clone from BartPE. It's very compatible to BartPE, so plugins can be more easily transformed.
- nativeEX is the new kid on the block with lots of potential, but not as compatible to BARTPE. So, more trouble tranforming plugins.

I think we will eventually move to nativeEX as the main project, but for now it's nice to have LiveXP to see, if the transformation of the plugin to script worked, at least in general.