Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - noelBlanc

Pages: [1] 2 3 ... 5
Win10PE SE HomePage / Re: Difference between WinBuilder an Win10PE SE?
« on: February 12, 2017, 12:43:49 AM »
For me, and it's just me (a beginner in the field):

-winbuilder is a shell evolved command contained in scripts located in the directory... \projects\win10PeSE.
Scripts describe the content of each screen. See section "[Interface]" in a script.  Entries of the operator are stored in variables.
The scripts also describe the actions that will be undertaken after the action on the "go" button. So, scripts traite entries of the operator. See section [Process] in a script.
- WinpeSE is therefore intelligence filed in scripts and therefore is also the name of the product that represents the final ISO .
In french, we say: i drink a glass. Glass, this is the way (winbuilder), we drink the content (using the scripts developed by a competent team), feels the pleasure of drinking or drunkenness (it has an advanced winpe).

Of course, I'll let product managers explain better.

I continue to play with IE11-64bits in the ADM session. I wanted to use the debugger F12. At first, it miss some files.
Now, i can get the network trace. it use the service "diagnosticshub.standardcollector.service".
I tryed also "fiddler". In my first test, fiddler ask to install its certificat for https. I install it with certutil.exe.
Not a revolution.

Win10PE SE HomePage / Re: In the boot Said: loading files...
« on: February 07, 2017, 01:15:47 AM »
Sorry, i miss UEFI.
For UEFI, the BCD is here : yourRoot\EFI\Microsoft\boot\bcd.
It's this file you can try to edit and verify the parameter "locale = Es-ES".
Perhaps the best way is the tool BCDBOOT.exe. It manage correctly  UEFI.
Hope this help.

Win10PE SE HomePage / Re: In the boot Said: loading files...
« on: February 06, 2017, 07:33:17 AM »
not a good news.
You modify boot.wim and only boot.wim (pecmd.ini only ) on the media usb. Can you describe how you do? witch tool?
Can you verify in boot.wim the presence of the file yourRoot\windows\system32\boot\winload.efi.
And the presence of yourRoot\windows\system32\boot\es-ES\winload.efi.mui
can you more describe the text error?

i find this :
So perhaps you can redo from scratch your Usb key ( FAT system File it seem ), format, initialize, active the partition, copy all files and boot
see you soon

Win10PE SE HomePage / Re: In the boot Said: loading files...
« on: February 06, 2017, 03:43:54 AM »
my pc is not uefi and i use vm in bios mode. I hope our masters and big chefs can bring a reply. I think i can test with hyperv and uefi, but later in the day.
I speek effectively about this bar : is it at this time that comes the text ?

For the line in pecmd.ini "TEXT System configuration, Please Wait...#0xFFFFFF L59 T39 $20* ", it's easy and at least two ways.
- one shot method : modify your boot.wim in the usb key ( not good for a disk DVD/CD ):
     - assume your usb disk/key is writable ( you can copy yourRoot\sources\boot.wim in a directory c:\mytest\ but not mandatory
     - mount the file boot.wim with DISM or mount-diskimage in PowerShell, as you like, in a new directory c:\mytest\mount
     - modify the file pecmd.ini in this directory c:\mytest\mount\windows\system32\pecmd.ini
     - unmount this directory with "DISM ... /commit" or "Dismount-DiskImage ... -save" in PowerShell, as you like
     -  copy back to usb key if need
With this method, you need to make each time this modification if you create a another instance of winpese

- second way : modify a script used by winpebuilder but too complex for me, i'm newbie in winpese

A bientôt

PS : many people in the street in catalogne. Good thing, romania also, good thing. But in french : nothing. No politic, yes, it's not the good site.

Win10PE SE HomePage / Re: In the boot Said: loading files...
« on: February 06, 2017, 01:47:02 AM »
i forget, you boot on a computer : uefi or bios ?

Win10PE SE HomePage / Re: In the boot Said: loading files...
« on: February 05, 2017, 11:37:05 PM »
hello teik,
Sorry for my bad english... i'm newbie with winpeduilder. I play to dicover winpe with it and play with microwinpebuilder and PS. So ....

Can you put the result of this command : bcdedit /store y:\boot\bcd where y: is the root of your key usb?
( command line is often better because it give more/full informations for the remote people, not only a piece of bcd ... )
I modify my bcd with bcdedit /store myRoot:\boot\bcd /set {bootmgr} locale en-US and i receive the text "Loading files...." at the begining of boot, when a big white progress bar comes. And come back to fr-FR with "Chargement des fichiers".
Does "yourRoot:\boot\es-ES\" directory not empty and contain bootmgr.exe.mui ?

For "please wait...", i found in my X:\windows\system32\pecmd.ini ( i product a winpese with session ADM ):
TEXT System configuration, Please Wait...#0xFFFFFF L59 T39 $20* <<<-------- is it "your" text ?
Can you say when and, better, where it appear on the screen, color, size, etc?
Do you know to read/modify the sequence to track it? (read/modify the system hive, setup\cmdline ? )
Are you sure it's not a third program that display it? if you select one or other feature/addon, scripts played in directories build/target are différents. Too many combinaisons. Can you product a basic winpese?
Many questions but you can forget it if you think it's not in the scope.

Hope this help.

Win10PE SE HomePage / Re: Remaining watermark
« on: February 05, 2017, 12:59:41 PM »
i think the text is "test mode" in English.
In your file BCD, there is a parameter "TESTSIGNING". Delete it with bcdedit. See documentation in ADK from ms site.
rem to see your bcd
bcdedit /store "your root\boot\bcd"
rem if {default} is good for you
bcdedit /store "your root\boot\bcd" /delete {default} TESTSIGNING
I think you use a checkbox "mode test for drivers" ( i don't remember the good text ) in winbuilder.
Hope this help

Win10PE SE HomePage / Re: In the boot Said: loading files...
« on: February 05, 2017, 11:59:34 AM »
Sorry for my English....

"Loading files" is displaying during the boot phase. The language is found in the file "root of your usb key\boot\BCD" on the active partition.
See the  presence of the directory"root of your usb key\boot\es-ES for spanish.

Winbuilder create the good directory fr-fr and the good bcd for me in the directory "target". Winbuilder make also my .ISO good. I see with 7Z.
After that, i copy all files in my key. Perhaps you create your bootable usb key with a tool that create a bcd in English.
How do you make your booting usb key ?

But you can easely modify your "bcd" with bcdedit. You can do that from winpe or from an active windows 10.
Assume you want to do from winpe.
Assume you boots on your key usb with only one partition. Winpe is active.
I don't remember that letter is affected by winpe to the "boot key usb". Assume it's Y:
Assume your usb key ( or usb disk) in not write protected
From a console in winpe  :
Code: [Select]
rem display actual parameters
bcdedit /store y:\boot\bcd
rem modify bootmgr
bcdedit /store y:\boot\bcd /set {bootmgr} local es-ES
rem modify the menu default if it the good for you
bcdedit /store y:\boot\bcd /set  {default} local es-ES
rem display the modifications
bcdedit /store y:\boot\bcd
rem And don't forget : copy the directory "your reference\boot\es-ES\*.*" in your usb key

I don't remember in which phase is displaying the message "Please, waiting...", perhaps in pecmd.ini or other .ini

In my memory ( i don't have winbuilder at this time ), there is a checkbox for catch regional parameters in the reference or in the host computer.
Did you see this checkbox?

Hope this help.

Ps : the winpe documentation in ADK from MS is good to read, command line tools ....

From Session System : files are downloaded well but not display
I find them ( many try before i see in directory) in directory.
See picture...

I reply from session System. But download doesn't work.
I try to investigate ..... But security for system is an enfer/evil

Chris find the solution for "session ADM".
And during this reseach, i find why ie64 doesn't work well. A file missing in microWinpeBuilder : ieframe.dll.mui
So, i'm glad to write this reply from IE64 in MicroWinpeBuilder in a VHD mode flat.  :smile:
I test to download a file = OK
I put a picture ...
I am preparing a new version of my PDF(verson 3) to explain for ie64. i'll post as soon as possible.

PS : with ie64 in winpe, i meet difficulties for sign in this site : i receive many times the page "verify cookies..."
        manage password seem not working
        download and historique dowload = OK

Forum Support / Re: this site and EDGE
« on: January 28, 2017, 01:17:00 PM »
Don't let me in the dark ! i'm a stupid boy and i want to progress. ( bold is ok , italicised is ok)
With IE, i have no problem with the drag and drop of a smiley.
I'm not only stupid, i'm very stupid. I need only to clic on the smiley and not drag and drop the smiley
thank you, galapo, you open my eyes  :w00t:

Forum Support / Re: this site and EDGE
« on: January 28, 2017, 01:09:22 PM »
i'm trying to put a smeley, drag and drop in the edit box :
I use "preview" to see before sending : only the url of the file is displaying.
I use "Post" and i'll see in a few secondes

Forum Support / this site and EDGE
« on: January 22, 2017, 11:06:42 AM »
With Edge in Windows 10, i can't use "insert codebox" (or use smiley) to write a message in this site.
A parameter somewhere perhaps ...
(you don't have to tell me that I can use another browser i know that)

I'm trying to understand why the button in the task bar at the bottom right does not show the desktop.
I have no ambition to find but I want a look and implement some tools like spy ++ and windbg.
1 - address of the WndProc of the button whose class is "TrayShowDesktopButtonWClass".
It is easily found with spy ++. But I can not find it with the API GetWindowLongPtr.
The following code snippet returns 0 and GetLastError returns 50 (decimal): The request is not supported.
While I get all other indexes (hinstall, type).
I don't understand why I get "GWL_HINSTANCE" but not "GWL_WNDPROC".
If someone can explain to me...
Code: [Select]
using System;
using System.Runtime.InteropServices; 
namespace Win32_API
public enum GWL
     GWL_WNDPROC =    (-4),
     GWL_HINSTANCE =  (-6),
     GWL_HWNDPARENT = (-8),
     GWL_STYLE =      (-16),
     GWL_EXSTYLE =    (-20),
     GWL_USERDATA =   (-21),
     GWL_ID =     (-12)
public class Win32_API_Class
[DllImport("user32.dll", EntryPoint="GetWindowLongPtr", SetLastError = true )]
public static extern IntPtr GetWindowLongPtr(IntPtr hWnd, int nIndex);

public static extern uint GetLastError();
[DllImport("user32.dll", SetLastError = true)]
public static extern IntPtr FindWindow(string lpClassName, string lpWindowName);
[DllImport("user32.dll", SetLastError = true)]
public static extern IntPtr FindWindowEx(IntPtr parentHandle, IntPtr childAfter, string className,  string windowTitle);
        static public IntPtr GetWindowLongPtr_(IntPtr hWnd, int nIndex)
  IntPtr ret = GetWindowLongPtr( hWnd, nIndex);
  if (ret == IntPtr.Zero){
  Console.Write("GetLastError : {0}", GetLastError());
  return ret;
add-type -TypeDefinition $code
$h1 = [Win32_API.Win32_API_Class]::FindWindow("Shell_TrayWnd", "");
$h2 = [Win32_API.Win32_API_Class]::FindWindowEx($h1, 0, "TrayNotifyWnd", "");
$handle  = [Win32_API.Win32_API_Class]::FindWindowEx($h2, 0, "TrayShowDesktopButtonWClass", "");
"Handle de TrayShowDesktopButtonWClass : {0:x}" -f [int]$handle
$hinst=[Win32_API.Win32_API_Class]::GetWindowLongPtr( $handle, [int][Win32_API.GWL]::GWL_HINSTANCE)
"hinst : {0:x}" -f [int64]$hinst

[Win32_API.Win32_API_Class]::GetWindowLongPtr_( $handle, [int][Win32_API.GWL]::GWL_WNDPROC)
#WindowProc fournie par Spy++ : c68D1FB0 mais il n'y a pas de segment, juste l'offset

2 - Trace the WndProc of "TrayShowDesktopButtonWClass" with WinDbg code in a normal 10 windows
As Spy ++ provides the WndProc and PID, I can use WinDbg with the "segment" Hinstance. Otherwise, I do not know what use segment.
The WndProc addresses different "WM_message", as 0x81 (WM_NCCREATE), and 0x82 (WM_NCDESTROY).
Messages that activate the display seems to be: WM_LBUTTONDOWN = 0x201 and WM_LBUTTONUP = 0x202.
These messages are identified by spy ++
The passage of the parameters with X 64 is a little disturbing.
Explore! CWRLImpWndProc <CShowDesktopButton>: s_WndProcBase:--->>> param: handle = RCX, Msg = RDX, wParam = R8, and lParam = R9.

The WM_LBUTTONUP code is currently analysing. There's a piece of interesting code:
00007ff6`c69addd3 e8f85affff         call    Explorer!CShowDesktopButton::_ActivateLivePreview (00007ff6`c69a38d0)
00007ff6`c69addd8 e8df020000      call    Explorer!CShowDesktopButton::_ToggleDesktop (00007ff6`c69ae0bc)

This last function sends a WM_message = 0x579 at the window "Shell_TrayWnd".
And if launches a SendMesssage (need test with postMessage!), then the desktop is displayed in Windows10 normal .
But he does not appear in Winpe.
I conclude that must also trace "Shell_TrayWnd", which will be much longer!
Code: [Select]
$signature = @"
[DllImport("user32.dll", SetLastError = true)]
public static extern IntPtr FindWindow(string lpClassName, string lpWindowName);
public static extern int SendMessage(int hWnd, int hMsg, int wParam, int lParam);
#Add the SendMessage function as a static method of a class
$Win32_API = Add-Type -MemberDefinition $signature -Name "C_Win32_API" -Namespace Win32Functions -PassThru
$h1 = $Win32_API::FindWindow("Shell_TrayWnd", "");
"{0:x}" -f [int]$h1


Hello JFX,
Thank you very much. Merci beaucoup.
My ask was about the tools you use for find it
And i understand that it's only your experience of programmer  that puts you on the track of the solution.
I also understand that this only sendmessage is not enough for you, because you are in front of many différents contexts.
Once again, thank you for taking the time to answer me

In microWinpeBuilder context, I use this PS attached script with a GUI to change screen resolution with your tips. It's OK for me.

Hello JFX,
Thank you very much to share your code .
I hope you understand my poor English, i am trying without translator.

May i ask you an other question? How do you find the need of the "sendmessage WM_SETTINGCHANGE" ?

I think i don't use the good tool or good method to investigate. I try spy++ in winpe without result. On internet, i founded only reference to "WM_ChangeDisplay".
Thanks again

Note : i'll test more but i think that WM_SETTINGCHANGE is the only one msg  needed in "my winpe" when changing screen resolution.

Bonsoir ChrisR,

Mais comment JFX a t-il bien pu trouver qu'il fallait envoyer un WM_DISPLAYCHANGE lors de la réception d'un WM_SETTINGCHANGE  ?
Ca marche !

How does JFX find that to adapt task bar on the desktop (explorer), it needs to send WM_DISPLAYCHANGE  after system sends WM_SETTINGCHANGE ?
And why winpe doesn't do that?
Many questions without response, i suppose.

I'll put scripts Ps for anyone can see by itself how to change the screen resolution from winpe, dynamically and manually.


I play with "ChangeResolution" to modify width and height of the screen in PS for Winpe.

Msdn says that the WM_DISPLAYCHANGE  is sent to all windows when the display resolution has changed.
And here, Msdn says "When the display mode is changed dynamically, the WM_DISPLAYCHANGE message is sent to all running applications with the following message parameters." But with my PS script, the desktop don't adapte itself. I must kill the task explorer.exe and launch again for a good desktop.

If someone knows the solution, please, says to me.

Pages: [1] 2 3 ... 5
Powered by EzPortal