Win7 x64 build problem

Hi everyone,

I am new here and I tried winbuild but can't make an iso, because the followed error appearing:

FileCopy - Failed to copy [%BaseDir%\win7ins84bit\sources\install_wim\4\Windows\SysWow64\en-US\adsldp.dll.mui] to: [%BaseDir%\Target\Win7PESE\Windows\SysWow64\en-US\adsldp.dll.mui]: Invalid directory name.

My system:
windows7 enterprise sp1
My image: windows7 professional sp1 x64.

Any ideas?
Thank you very much for your help.

Hi kissd,

What is the Windows 7 source language and is it an orginal Windows ?
Anyway,  In WoW64 Basic, I Create the Target folder SysWOW64\en-US fallback now if not previously created (in copy files).

I heard same thing happens in Korean source.
Someone reported in Korean Community, too, in January 14 (So I thought he used 2013-11-30 version)
However, my Laptop was making a problem, so I couldn't tested it.

Part of his Log

[Failed] FileCopy - Failed to copy [%BaseDir%\Workbench\Common\Extract64\InstallWimSrc\Windows\SysWow64\en-US\adsldp.dll.mui] to: [%BaseDir%\Target\Win7PESE\Windows\SysWow64\en-US\adsldp.dll.mui]: 디렉터리 이름이 올바르지 않습니다 (= Invalid Directory Name).

So I suggested him making SysWOW64\en-US folder while building (not before building).
But he reported again, that he faced "0x0000006F ERROR_BUFFER_OVERFLOW 파일 이름이 너무 깁니다 (=File name is too long)." error while booting.

Now I'm testing it myself using 2014-01-16 version of Win7PESE. I hope this version works.

WoW64 Basic version 18 is on server but it is not included in the Win7PE_SE_2014-01-16 package. The addition was made after.

I tested Win7PESE x64 Build by myself.
Project version is 2014-01-16 with 01-24 Updated, and source is Windows 7 Ultimate SP1 x64 Korean.
Built with Wow64 script version 18.

Result : BSOD Again!? Whew.... 

Code: [Select]

SESSION3_INITIALIZATION_FAILED

(And so on.......)

Technical information:

*** STOP: 0x0000006F (0xFFFFFFFFC000007B,0x0000000000000000,0x0000000000000000,0x0000000000000000)

Bluescreen appears in VMware, and in real machine, too.
I failed to figure out what is a cause; Need more testing, I guess  .

Not happening in Win8PESE x64 and Win8.1SE x64.

Here I attach a Support Log of this Build :

Can you try by selecting "Other Language files (All Nls)" in "Build\1 Copy files"
It is enabled by default in Win8(8.1) but not in Win7PESE, an error. but I'm not sure this is the cause.
 

OK, I will try it 

Still BSOD.

I googled 0xFFFFFFFFC000007B, which means The NT status code according to Microsoft :
http://msdn.microsoft.com/en-us/library/windows/hardware/ff559156%28v=vs.85%29.aspx

But there is only 4 useless result, including this page.

So I googled 0xC000007B only since there is 8 'F's and maybe there are meaningless number to fit in 64bit memory address.
Some people experienced 0xC000007B because there were no required dll in System32 (and SysWOW64), but while excuting applications, not BSOD.

Well, maybe some SysWOW64 dll required for Eastern Asian Language is not included.

Hi ied206,

I downloaded last night Win7SP1_x64 korean X17-59300.iso
On my Win7 x64 Fr host, the building works well and the ISO starts successfully 

I have installed Win7SP1_x64 korean in a VM and I made a new building from it.
I had no worries when building but but I reproduced the same 0x6F BSOD  reproduce the concern is already a good step 

The problem is related to the host system with the Korean extended language.
I am, We're on the right track to find a solution. It is more a matter of timeeee.

Maybe related or not,

We had troubles in past with host zh-tw with autoit " buffer overrun "
http://theoven.org/index.php?topic=477.msg7245#msg7245

Maybe related or not...

More or less, but you put me on the right way 

It seems well linked to Autoit and the size of a variable that with Unicode exceeded the size limit with 95737 characters.
In Autoit, to prevent buffer overflow, each "variable" is limited to 65535 characters.
I have not much time this afternoon...

I really appreciate for your test, Chris.
It must have consumed lots of time! (And your wife's patience  )

May I ask a 'Support Log' of Win7SP1 K x64 Build in FR Host?
I am willing to compare them 'byte by byte'   

Don't know what's the worst Autoit  bugs or the terrible code I wrote 5 years ago.

ied206, please try this new Wow64 script: http://www.mediafire.com/download/5yx3bhbw6xybr02/5-Wow64.7z

Thanks, JFX, it works! 
So this bug's cause was invalid registry keys!

Can I ask more : How did you fix this?

No registry was ok. But the patching of smss.exe went wrong.

Also tested with success here in Virtual machine

Thanks JFX, you are the One   

The new Wow64 script is on SE server now, with support on korean host OS and I guess Chinese, Japanese

On building, I noticed that Super Finder could not be properly installed on Korean HostOS.
Not an autoit or other problem but Superfinder itself unable to create Language folder due to some character: Français.
Perhaps it is good to disable the plugin by default.

Thank you for all, everyone!!! 

It's a pity for WinBuilder (which Nuno calls 'legacy' now) can't support Unicode, which gives Koreans a lot of frustration.
For example, when building LiveXP in past, I had to use special and unofficial patch and never use hangeul (Korean characters) in folder names.
(The point is NT5's start menu's folder names were 'natviely' hangeul by default, which caused WinBuilder just freeze) 



By the way, I'm wondering, since Nuno and his team in reboot.pro discontinues upgrading WinBuilder 'legacy', what happens if WinBuilder 082 can't run in newer Windows in future?
Can LiveSystemPro be alternative to WinBuilder 082? (I heard from reboot.pro that only few syntax are different from WinBuilder 082)
http://reboot.pro/topic/16912-livesystempro-is-a-copy-of-winbuilder/
Nuno seemed to be upset thinking Kare copied WinBuilder..... which I think not, it shows improvement of WinBuilder to me.

And I have one more question, if you excuse me 
At least before January 2013, reboot.pro had a dedicated forum for Win7PESE, which is not in today.
Can anyone explain why theoven.org was made instead of reboot.pro?
I found a old thread : http://reboot.pro/topic/12427-win7pe-se-release/ and I guessed Win7PESE has started from reboot.pro.

Well the monopoly games which Nuno Brito trying to play unsuccessfully is quite out of current subject / topic / section 

Win7PESE had started at reboot by ChrisR , since Nuno Brito play monopoly games with Peter Schang against Win7PESE , at a point it ChrisR left ..
 Yep the old announcement link , with a little dignity should have been removed 
   In history, all project developers left after Nuno Brito , Peter Schang monopoly games  , winbuilder (legacy or not) toxic (or very toxic), nobody touch it to create any other project anymore, we only continue our work 


If you like, better open a section here http://theoven.org/index.php?board=15.0
better not to go out of subject 


Future of livesystempro , time will show
We gave them a section already http://theoven.org/index.php?board=23.0
well, I had encourage Kare to create such builder at very old times 


livexp, death for 4 years now, since Galapo and I (Lancelot) left it behind    (Thanks to Nuno Brito , Peter Schang )
We continued with creating Gena   
(it has unicode core by Saydin77 inside with the folder things workaround (because of wb) we are very aware  )
Check here
http://gena.cwcodes.net/
http://gena.cwcodes.net/Compressed/index.php
Things will work smoothly with Korean source / host 
Further Gena related things, go here
http://theoven.org/index.php?board=7.0
and open a topic 

Thanks JFX, you are the One   

 
 
As stated elsewehere by ChrisR to JFX

Continue with the things which interress you the more. to know you behind, is already much.