WinBuilder Win7PE_SE Project HELP

Hi Chris,

**
yes I cheated on your post 11 
as usual to get things faster by proving copy-paste codes 

***

By cons in this case, in winbuilder this part of the log is not very nice but I believe it is better for SupportLog.

himmmm, I agree, with your tip I guess I figure out a universal expansion slot on SupportLog for such cases
Try/Test this:
http://www.mediafire.com/?lkf1r6ffgj4aayh

at script.project
SaveConditionAddFiles=1
(it is planned to be default 1)

at

Code: [Select]

[WimInfoMissing]
If,ExistFile,%TempDir%\WimUtil.log,Begin
If,Not,ExistDir,%ProjectTemp%\SupportLog_AddFiles,DirMake,%ProjectTemp%\SupportLog_AddFiles
FileCopy,%TempDir%\WimUtil.log,%ProjectTemp%\SupportLog_AddFiles
End
//----
Message,"Wim file information missing. A problem occurred to Get Image Information with %WimToolsInfo% !!!#$x#$xTips:#$x1) Try using official MS sources#$x(Check 'List of Official Windows 7 ISO' button at main screen) #$x#$xExiting...",Error
Halt,"Wim file information missing. A problem occurred to Get Image Information with %WimToolsInfo% . -- Tips:-1) Try using official MS sources-(Check 'List of Official Windows 7 ISO' button at main screen) Exiting..."

**
since projecttemp deleted at everybuild, %ProjectTemp%\SupportLog_AddFiles would reset,
so for all supportlog+add file conditions (where we ask additional files, mostly log, from end users), %ProjectTemp%\SupportLog_AddFiles folder can be used by relevant plugins easly without improving Support_Log.script
above %95 should be working (partially tested),
let me know improvments, also I am open to suggestions for new (unique) folder name %ProjectTemp%\SupportLog_AddFiles since it would be critial-shared name


 

Hi Lancelot,

Your universal expansion slot on SupportLog is very good
And the SupportLog_AddFiles name sounds good for me.

Also tested here without any problems.
This addition to Support_Log is very useful and easy to implement for other plugins, if needed.
Ready on my side to put it on server.

than update  ,
Galapo would follow you   

Done, with also NoRootDirCheck (reply #16)  

Have a nice day
 

Please Redownload latest complete package Win7PE_SE_20120216 http://theoven.org/index.php?topic=131.0

That is the exact package I am using, in the directions it says that I have to swap some files out from different folders...

For Win7 SP1 Source CD

Get these files from Win7 Waik KB3AIK (KB3AIK_EN.iso) , Win7 Waik Mandatory for SP1

VersionInfo of PreRequest Files:
bcdedit.exe v6.1.7600.16385
imagex.exe v6.1.7600.16385 (6.1)
wimgapi.dll v6.1.7600.16385 (6.1)
wimmount.inf
wimmount.sys v6.1.7600.16385
wimserv.exe v6.1.7600.16385

Where to put Files:
*Important*:
These files are for your Windows, you can build Win7PE SE x86 or Win7PE SE x64 on ANY Windows Architecture.

Put Following 6 files in relevant folders:

If your Windows is x86:
- <Tools>\x86\bcdedit.exe
- <Tools>\x86\imagex6.1.exe
- <Tools>\x86\wimgapi6.1.dll
- <Tools>\x86\wimmount.inf
- <Tools>\x86\wimmount.sys
- <Tools>\x64\wimserv.exe

If your Windows is x64:
- <Tools>\x64\bcdedit.exe
- <Tools>\x64\imagex6.1.exe
- <Tools>\x64\wimgapi6.1.dll
- <Tools>\x64\wimmount.inf
- <Tools>\x64\wimmount.sys
- <Tools>\x64\wimserv.exe

The machine I'm working on is Windows 7 SP1 64 bit. So I'm doing the x64 (6.1) steps.
Should I NOT be doing this?

Hey guys,

So I re-downloaded the Win7PE_SE_20120216, and made a WinBuilder2 folder.  I pointed the source to C:\Windows 7 Professional with SP1 32Bit folder. Pressed the Goooo button.  Ran the big blue play button.  It worked. Everything went better than expected.

Upon putting this USB Drive in a computer (and also in the VM that it auto loaded) It went to the Sunset background, where all the text was whited out for whatever reason, and when I selected WinPE it crashed.

0xc000000f was the error.

What now?

Hi Erock,

I feel suspect about source...
have you tried with digital river download you had planned to....
 

the List of Official Windows 7 ISO from Digital River is on the main script (Win7PE_SE), the button below the image.

I looked also to your log in detail, it's better, it'is more consistent with the last Win7PE_SE package, and no more incompatibility between script versions, as previously ?

The problem in your last building, is still in relation with the use of Imagex or wimutil  (more precisely MS wimgapi.dll exiting with error 2 "WIMGAPI failure")
and in your log the capture to create image boot.wim does not work, impossible to start without it.

ShellExecute: [Hide] using: [%BaseDir%\Projects\Tools\Win7PE_SE\X64\imagex.exe] with parameters: [/capture "%BaseDir%\Target\Win7PE_SE\boot.tmp" "%BaseDir%\Target\Win7PE_SE\sources\boot.wim" "Win7PE" /boot]
ImageX Packing boot.wim return : 2     (ps: a message box + halt would be well if the capture fails)

I do not really know how to help you to solve this problem, it works for most people.
Maybe, you can try a new building with wimutil and in case of failure, look at wimutil.log in %temp% folder, if more eloquent !!!

Otherwise try to play manually on cmdline with wimutil, imagex or even dism (log in C:\Windows\Logs\DISM\dism.log) to try to understand, google is your friend.
Try switch like /info, /capture, /mount, /unmount, the switch names are a little different for dism (/Cleanup-Wim, /Get-WimInfo, ...).

For help
...\Projects\Tools\Win7PE_SE\x64\Imagex /?
...\Projects\Tools\Win7PE_SE\x64\WimUtil without parameters
dism /?

You can also use GImageX (A graphical user interface for the ImageX tool) http://www.autoitscript.com/site/autoit-tools/gimagex/ (but the imagex error messages are not really explicit).

any ideas are welcome,
Happy testing 

Error 2 could have multiple reasons, it could be an aggressive AV software.

What Anti virus software are you using?

Done, with also NoRootDirCheck (reply #16)  

Hi Chris,

What was the code you used? No sense in my duplicating what you've already done. I'll add to Gena as well.

Thanks,
Galapo.

also don't forget that WimUtil will append to WimUtil.log so you may want to think about clearing the log at some point or it will become quite long and clutter the support log, especially if used for some weeks without the %temp% being cleared.

The file WimUtil.log is now fully copied in support log and compressed in log_xxxx_Win7PE_SE_Support.7z.
Also the size of log file is not really important (few Kb once packed).
But, indeed, the file WimUtil.log could be deleted in Main Configuration as other Temp files.

Also the size of log file is not really important (few Kb once packed).

its not the file size that concerns me, its the fact that depending on the number of images mounted, index contents, etc and the period of time since the log was created, it can be 1000's of lines long.
clearing it as a part of the Clean Files button sounds like the most reasonable option.

Ok added to the process of  the "Clean Temporary files" button, even if it is not difficult to go at the bottom of WimUtil.log for support.
Main config is on server  .
 

Sorry I haven't checked in on this project in a while.

I was on vacation.

Upon return, we have decided to put this on hold for now as I had invested quite a bit of time and we weren't getting the result we need.  We may be switching to our old Ghost Solution Suite and we might just do everything from their built in Console.

I'm thankful for all the help, and personally would like to keep at this to figure it out.  I'll be sure to check in from time to time and see if I can make some progress.

Thank you again for all your help, I'm sure I'll be back!