Win10PXE - How get custom screen resolution - ?

Hi,
My screen is an ASUS VE47 - Native reso 1920x1080  16/9 ratio -
My problem: I can't easily read at full range (personal eyes problems) and use always 1600x900 (16/9) resolution under Windows. Graphic card is an Nvidia GTX 970.

I have made my first Win10PXE following nice tutorial here :), but I am facing to that screen problem when booting WinPE.
 - By default, I start at 80x600 and can choose between 1280x800 (4/3 ratio) or 1920x1080 where I got problem.

I have tried many times to use PECMD 2012, but cannot get it working - I must be not so good  for configuration -
Is there a simple way to get that 1600x900 custom resolution ? 
Any help would be appreciated

Not sure it's good without integrating your Nvidia driver
but you can try to edit pecmd.ini (Button in Build Core) and change the line
 

Code: [Select]

TEAM DISP W1024 H768 B32|DISP W1366 H768 B32
=>
TEAM DISP W1024 H768 B32|DISP W1366 H768 B32|DISP W1600 H900 B32

Did you try using 5he pecmd that's running in tray? There should also be a display settings on right click of desktop.

Thanks for quick response.
I will make a new one with your suggestion and let you know.
(I would not try to integrate 1 Gig of Nvidia drivers ... )

@ Bigbadmoshe
I did not see pecmd running in the tray (the blue square one ?)

 

It's a colorful icon that looks like a screen.

I just made a new ISO.
Unfortunately the screen resolution is still the same after editing pecmd.ini.
When using the Pecmd Icon in system tray I can see my reso 1600x900 with others, but clicking on it does nothing.
The only way to change is the right click on desktop ... But choice is 800x600 , 1280x800 (4/3/ and 1920x1080 the one I want to change to 1600x900.
I have checked pecmd.ini when in ram mode, and it is correct and reflect the editing changes.
In Pecmd tray there is an option to load drivers.. But not very useful, my ISO is 1GB large.

Quick question. Do you really need it that high?

It's most probably a driver thing. As well as cache size. What happens if you up it to 2048?

Yes, probably. But inserting Nvidia drivers should be a hard work and will dramatically increase the ISO.
About 2048, My Asus Ve47 is limited to 1920x1080 native, and if I need 1600x900 ... I explained above.
Maybe CHrisR will have a clue next time.
I need less than 15 Mn to make an ISO on SSD.
Edit: I can use less than 1600x900 but I want to keep the good ratio 16/9. There is no other resolutions offering that.

I mean the cache size.

What do you have it set to?

You can try to trim down the nvidia driver by commenting the files inside the inf.

This one work with my GTX 1060 https://mega.nz/#!xuJQyIrY!SwEKyyxkl4Y88pUsK8GC-Z1Barl5wUnOWvxyjX0XfcE

But if you mod the inf file you also will need to patch drvinst.exe.

Thanks JFX I have the same card. 

BTW that zippyshare link is trecherous    Here is a mega link for the same file(JFX GTX 1060 - 417.71.7z): https://mega.nz/#!xuJQyIrY!SwEKyyxkl4Y88pUsK8GC-Z1Barl5wUnOWvxyjX0XfcE

Oh, never visit this site without an adblocker before 

Thanks JFX, it's a really Big Reduction 
I'll try it a little later with my GTX 950 card
Does DrvInstPatch should be operational also for RS6 ?

As long MS does not change to much code in drvinst.exe, it should work with future version.
It's a generic patcher for x86, x64 and arm64 version.

Thanks 

In addition, here is a plugin to Set Max Resolution at startup using NirSoft MultiMonitorTool
MultiMonitorTool.exe /Setmax Primary

 SetMaxResolution_XPE.Script (19 kB - downloaded 82 times.)
 SetMaxResolution_XPE_File.Script (10.92 kB - downloaded 74 times.) Container File

Also, as an example of using XPEStartup.ini (in latest package)
To Launch WinXShell Display Settings at startup by adding:

Code: [Select]

EXEC %programfiles%\WinXShell\WinXShell.exe -ui -jcfg wxsUI\UI_Resolution\main.jcfg

 
Feature For Build Core Options

@JFX:
This looks rather interesting to me, and I wonder whether you might be able to address a few questions:

• How did you work out the minimal set of files required?
  I've so far only done such an exercise for rather simple cases (e.g. Ethernet NICs) where a bit of trial & error was (albeit not always) enough to succeed.
  But in these cases I could typically assume that only the *.sys file was the only one really required (apart from the "reduced" *.inf file of course).
• What is the purpose of patching 'drvinst.exe'? I mean, what is "wrong" with the un-patched 'drvinst.exe'?
  Or, is there a way to use the original 'drvinst.exe' via a maybe more manual "intervention"?
• Would one need a patched 'drvinst.exe' also for earlier versions of Windows (e.g. 7 or 8.1)?

Cross-replies, interesting question!

Feature For Build Core Options

Yep and probably good directly in the base without an apps plugin, just a checkbox in additional option.
Or even in automatic, without any option, I guess it's good feature for everyone, if it works well, what do you think?
For now, I only tested in VM

Also, it would be nice to have a plugin with JFX's reduced NVidia 417.71 driver + DrvinstPatch.

I tested from PE boot from Host Drive..
quick black screen after load then proper res...

I think good as default - but need more feedback results...

But most feedback will come if default and not work..

Or even in automatic, without any option, I guess it's good feature for everyone,

My vote:
Just add an option as we did on Gena ~8> years ago.
 ( you know same plugin available for SE some years since Win7PESE...)
Default enabled or not up to you.

History:
Like you did it was added to Gena default  (Max Res - Default enabled)
 later figured out Default to Highest support res was not good for everyone... (back to: Max Res - Default false) - Default windows driver was not always resulting good for all hardware.

After many years Today maybe it can be good with hardware changes !
 (Max Res - Default enabled)

In all cases, good with a noticeable option.