51 replies to this topic

[m4dm4Xz]

Hi m4dm4Xz,

I found the issue, can you please test following packages:

This one has a general fix by adding files (which is available in LiveXP for a while), I hope it also have ability to fix the issue on your pc,
http://lancelot.winb..._sp6_mod_All.7z

This one has a trial to fix by adding 1 file for your case. (post only log of this one)
http://lancelot.winb...p6_mod_Test1.7z

This one has a general fix by not adding a reg key
http://lancelot.winb...od_candidate.7z

(ps: you can delete previous attachments in your posts to get some space )

Hi Lancelot,
I'm finished with the results and my system that i build on is Windows XP SP2 english, and all builded with source of Windows XP SP2 professional english version (not slipstreamed that Mr. Peter ask me and Lancelot), the results in order:
1. 201001262259_sp6_mod_All
- Success to open the shell and no errors.
2. 201001262259_sp6_mod_Test1
- Failed to open the shell and came with the same errors like the previous post's.
3. 201001262259_sp6_mod_candidate
- Success to open the shell and no errors.
I attached the log file of 201001262259_sp6_mod_Test1 builder(like Lancelot tell me)

Ps: I would to ask about the space of attached files too but now i know how to get the space back. Thank you



m4dm4Xz

[pscEx]

Ps: I would to ask about the space of attached files too but now i know how to get the space back. Thank you

(I hope that) You can edit YOUR old posts (full edit) and remove the attachements.
If you are not allowed, I'll do for you.

Thanks for your help!

Peter

[Lancelot]

Hi m4dm4Xz,

Thanks a looooot for the result,
I put a copy of your log here http://lancelot.winb...0128_204841.zip in case somebody needs in future (and you can delete previous one to get space for your future uploads)

my system that i build on is Windows XP SP2 english

Around boot-land, we call it hostos

and all builded with source of Windows XP SP2 professional english version

and around boot-land we call it sourceos

I hope it will be easier to write in future .

Your hostos is xpsp2english, but your localization info is not which caused all these issues with "autolocalization" script.

With your great support , now we know the exact reason of the issue, "Locale" value of "Control Panel\International" , in your case 0000041E (and my case (Turkish) 0000041F)

for 0000041F , I found the exact nls file (c_1254.nls) but for you (0000041E) I do not know the exact nls file (and c_1254.nls is not), but it is nice to see copying all nls fixes .


For now, we learn this value must be changed by none-auto scripts
autolocalization script on LiveXP already updated with this fix

We have some none-auto-scripts for localization purposes, at \Finish\1 Optimizations\ you will notice ChineseSupport , RussianSupport scripts written and provided by the boot-land members. Maybe one day we can have "ThailandSupport" with your contribution.

See you around

[m4dm4Xz]

(I hope that) You can edit YOUR old posts (full edit) and remove the attachements.
If you are not allowed, I'll do for you.

Thanks for your help!

Peter

Hi Mr. Peter,

Thank you for explaining and please nothing to thank's to me because all that's solution and beginning to help me it's from you and Lancelot, so I'M the one that have to thank you to you both. Don't be hesitate to ask me to test files or helping you, gladness for me.



m4dm4Xz

[pscEx]

Hi Mr. Peter,

Thank you for explaining and please nothing to thank's to me because all that's solution and beginning to help me it's from you and Lancelot, so I'M the one that have to thank you to you both. Don't be hesitate to ask me to test files or helping you, gladness for me.



m4dm4Xz

You can do me a favour:
We all are friends her (in most cases )
So, next time replace the "Mr." by ""

Peter

[m4dm4Xz]

Hi m4dm4Xz,

Thanks a looooot for the result,
I put a copy of your log here http://lancelot.winb...0128_204841.zip in case somebody needs in future (and you can delete previous one to get space for your future uploads)

No problem with gladness and thank you too.

Around boot-land, we call it hostos
and around boot-land we call it sourceos

I hope it will be easier to write in future .

Already write down to my memory brain (sometimes it works like an random access memory but hope this time not ),
thank you.

Your hostos is xpsp2english, but your localization info is not which caused all these issues with "autolocalization" script.

Did i understand it right, that the "autolocaliztion" script doesn't work in this case ?

With your great support , now we know the exact reason of the issue, "Locale" value of "Control Panel\International" , in your case 0000041E (and my case (Turkish) 0000041F)

for 0000041F , I found the exact nls file (c_1254.nls) but for you (0000041E) I do not know the exact nls file (and c_1254.nls is not), but it is nice to see copying all nls fixes .

For now, we learn this value must be changed by none-auto scripts
autolocalization script on LiveXP already updated with this fix

We have some none-auto-scripts for localization purposes, at \Finish\1 Optimizations\ you will notice ChineseSupport , RussianSupport scripts written and provided by the boot-land members. Maybe one day we can have "ThailandSupport" with your contribution.

See you around

Didn't understand much but try it.

m4dm4Xz

[Lancelot]

Did i understand it right, that the "autolocaliztion" script doesn't work in this case ?

no wrong,
lets say "OLD autolocalization" script does not work in this case
but
"Fixed autolocalization" script does work in this case .

Fixed autolocalization script test already made by you (and me) and confirmed by you (and me) ( 201001262259_sp6_mod_candidate ) , fixed version is available on LiveXP now and probably will be available on nativeex_barabone in a short time.

Didn't understand much but try it.

Begining is just an explanation to be referenced in future, rest is: When you learn more about script writing, since you are our boot-land member from Thailand , maybe you will write more advanced localization script in future for People of Thailand .

[m4dm4Xz]

no wrong,
lets say "OLD autolocalization" script does not work in this case
but
"Fixed autolocalization" script does work in this case .

Fixed autolocalization script test already made by you (and me) and confirmed by you (and me) ( 201001262259_sp6_mod_candidate ) , fixed version is available on LiveXP now and probably will be available on nativeex_barabone in a short time.

Begining is just an explanation to be referenced in future, rest is: When you learn more about script writing, since you are our boot-land member from Thailand , maybe you will write more advanced localization script in future for People of Thailand .

Ahh more clearly for me, thank you.


m4dm4Xz

[m4dm4Xz]

Your hostos is xpsp2english, but your localization info is not which caused all these issues with "autolocalization" script.

I have some question about this, my hostos is xpsp2english but if i installing my windows i set some regional and language settings.
1. If i change settings while installing xp or changing through "Control Panel > Regional and Language Option", make my localization info be changed ? ( it should be, right?)
2. And does nativeEX used some files from the hostos which is from my localization ?
3. And if it does in number 2. , did it get my localization of my installing CD or the changes that i do in "Regional and Language Option" from the hostOs?

Ps: I'm try... try to explain my confusing and i'm "eager to know"(get these 3 word from a dictionary never used it before but would to say want to know )

m4dm4Xz

[m4dm4Xz]

native means that every text, menu, etc. in your final WinBuilder created PE is taken from the CD (in your native language) which you have defined as source.

This is different from other PE creating software, which usually uses predefined hives, predefined ressources etc. As a result, your PE in the best case looks (usually) English. In worst cases, you also have an English keyboard, English time and date format, etc...

From http://native.boot-land.net/ page.
So i think all files are from the sourceOs or not? Confusing

[Lancelot]

1. yes
2. no, neither nativeEX nor LiveXP use any FILES from hostos, autolocalization script takes localization information from your registry and use them. That is why it is auto
3. ---2 is no--- (and I do not understand too)

ps: ( HKCU\Control Panel\International )

see you some hours later

[m4dm4Xz]

autolocalization script takes localization information from your registry and use them. That is why it is auto

see you some hours later

That means "autolocalization" script does nothing to do with the build, right?
It only a script that you put to check my localize on my hostOs?

Your hostos is xpsp2english, but your localization info is not which caused all these issues with "autolocalization" script.

And that makes you know that i use xpsp2 english but not really english because by checking with the "autolocalization" script.
And why does it makes issues with my localization from my hostOs?

See you,

m4dm4Xz

[Lancelot]

That means "autolocalization" script does nothing to do with the build, right?

wrong, it reads the registry values from your hostos and writes them to your build. (no FILE, only registry)

And that makes you know that i use xpsp2 english but not really english because by checking with the "autolocalization" script.

no, your log shows you have other localization setting then english.

And why does it makes issues with my localization from my hostOs?

simply because the script WAS not perfect, but now it is better.

btw, auto scripts normally are not selected as default, probably something went wrong on nativeex server and resulted with enabled autolocalization script, and ..... we are here .

Here is a test for you.
Download LiveXP minimum with winbuilder (choose minimum on download option) (prefer wb077rc2) ,
on your winbuilder settings, enable autolocalization,
make the build
and I hope now everything works.

Time to go forward.

[m4dm4Xz]

wrong, it reads the registry values from your hostos and writes them to your build. (no FILE, only registry)

no, your log shows you have other localization setting then english.

simply because the script WAS not perfect, but now it is better.

btw, auto scripts normally are not selected as default, probably something went wrong on nativeex server and resulted with enabled autolocalization script, and ..... we are here .

Here is a test for you.
Download LiveXP minimum with winbuilder (choose minimum on download option) (prefer wb077rc2) ,
on your winbuilder settings, enable autolocalization,
make the build
and I hope now everything works.

Time to go forward.

Wow, everything cleared !!
Thank's and i will test that. But for now i must do my critical homework before.

m4dm4Xz

[m4dm4Xz]

Here is a test for you.
Download LiveXP minimum with winbuilder (choose minimum on download option) (prefer wb077rc2) ,
on your winbuilder settings, enable autolocalization,
make the build
and I hope now everything works.

Time to go forward.

Where exactly can i set autolocalization again ?
I didn't find it.

m4dm4Xz

[Lancelot]

Sorry, you are right, I never include that on LiveXP Minimum

Since you already download LiveXP Minimum, follow this:
on winbuilder click download,
change download option to Recommended,
unselect all selected scripts (remove checkbox on 2 folders),
On the list browse through: LiveXP--Components--Tweaks
There you will find "autolocalization.script", put a checkbox on it,
click download (it will download only autolocalization.script)
ps: like a simple download manager.

Than back to winbuilder main interface,
at left, go to LiveXP--Components--Tweaks , enable autolocalization.script , make your build.

[m4dm4Xz]

Tested on hostOs XPSP2 (thai i think) and used sourceOs XPSP2 english.
It works without errors but normally LiveXP did work for me before that.
However, thank's

Hmm, i have screenshot's from my "Regional and Language Option" and from what tap exactly can i see and say that mine hostOs is Thai because i set the most settings to Thai.





m4dm4Xz
edit: also i know it is Thai but i want to know where exactly.

[Lancelot]

It works without errors but normally LiveXP did work for me before that.

Because LiveXP do not "accidently" enable autolocalization script on server. If you tested livexp with manually enableing autlocalization script at the times of this topic start, you would get the failure. Now as you see it is fixed.

Thanks for the pictures

Since issue solved, time to go forward

[m4dm4Xz]

Ah, okay ,thank's
also the localization == location that i set from the first tab of "Regional and Language option" or the another tab's too with the unicode settings?

m4dm4Xz

Ps: i can't sleep and go forward if i don't know about that, thank's

[Lancelot]

I do not understand the question of yours, do not play with your hostos reginonal settings.

The builded pe should be working fine on unicoded file,
Is this the case: you have some .txt files written in thai language, but when you open with notepad on livexp they do not work ?

!!!

[m4dm4Xz]

Try to say in the first i installed my windows with a XPSP2 english version CD but now it wasn't an english version. Why is it not?

m4dm4Xz

[Lancelot]

In his bones, it is still XP english .
only you set your local settings for Thai, which turned all "Regional and Language" options to Thai

I do the same here, I install XP english and use Turkish "Regional and Language" settings.

Further this is all about knowing & learning Windows, you should check other forums - topics about that. Google Kung-Fu time .

[m4dm4Xz]

Let's get some knowledge by googling.
Thank's
m4dm4Xz

[MaineCoon]

now we know the exact reason of the issue, "Locale" value of "Control Panel\International" , in your case 0000041E (and my case (Turkish) 0000041F)

for 0000041F , I found the exact nls file (c_1254.nls) but for you (0000041E) I do not know the exact nls file (and c_1254.nls is not), but it is nice to see copying all nls fixes .

Lancelot,

seems it is not necessary anymore, so JFYI:
- c_874 = Thai
- c_932 = Japan
- c_936 = Chinese simple
- c_949 = Korean
- c_950 = Chinese traditional
- c_1250 = Central European
- c_1251 = Cyrillic
- c_1252 = Western European
- c_1253 = Greek
- c_1254 = Turkish
- c_1255 = Hebrew
- c_1256 = Arab
- c_1257 = Baltic
- c_1258 = Vietnamese

MaineCoon

[Lancelot]

Thanks a looot MaineCoon, this makes it verrrry clear

May I be a bit lazy and ask Locale values to reference with these values

Edit: I found a perfect answer to my question, solution is on the way