extension .prn with PDF printer

HI noelBlanc

Code: [Select]

... I notice the absence of a real installation

you need to add this to work ...

Code: [Select]

Question: But where does this data come from?

i think James have a better answer than me ...

Edit Lancelot:
Post moved here following noelBlanc request.
 http://theoven.org/index.php?topic=1639.msg36103#msg36103

Hi cretino, thanks for your reply.
Yes, i understand i need these keys to get "*.pdf" in the extension ;)
2 ways to put these keys in registry, a .reg file or all the drivers hive.
I thing my "cosmetic" issue was also in my first usage of PDF/XPS printers in Winpe, in 2016 (i do not verify because i don't keep old builds)
It's difficult for me to explain, my English is too poor.
With my precedent post, I wanted to show the link between the displaying of a wrong extension (*.prn) and the driversDataBase for X86 environment in a AMD64 OS.
On one side, a simple "cosmetic" error, on the other side, the complex imbrication of WOW and the impossibilty to install "ntprint_x86..." with dism on a ADM4 OS.

hi noelBlanc

Code: [Select]

It's difficult for me to explain, my English is too poor.

me too very very poor 

i see James has updated the scipt " http://theoven.org/index.php?topic=2607.msg28500#msg28500 "
now im at work i cant testit but i guess now is ok ...

hi cretino
i see in description of the plugin "print support" :
Print To PDF - defaults to .PRN File Extension - Which is Readable with a PDF Reader..
Is it a warning that "*.Prn" is displaying and not "*.Pdf" ?
I'm curious. Is this (below) key present on win10XPE ?

Code: [Select]

...\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows NT x86-Drivers\Version-3\Microsoft enhanced Point and Print compatibility driver

Please, would you send me the result when you'll test. Or A trace of procmon (net stop spooler, launch procmon, net start spooler)

hi noelBlanc
wwait im testing now ( Pause-café  )

edit

Is it a warning that "*.Prn" is displaying and not "*.Pdf" ?

i think description not updated 




edit
this test with MediaTransferProtocol_XPE.Script

Hi
@noelBlanc
 

Is this (below) key present on win10XPE ?

I cant find that key on my PE

@cretino
I thought I was using James latest printer plugin + MTP but I'm still getting .prn only
but I'll re-download that scriptfile and check

Cretino,
Thanks for taking the time to test printer support...
I see you added driverfiles to your reg.txt... (Easy Enough to do)
We have been there and done that - to fix MTP...


Test without Using MTP... (As we try to fix independently)

I use Base Build without Features - sometimes loads Fax, pdf printer, xml printer (sometimes not)
Tests usually better with Full Software Hive....

Need to find what works - then remove things until it breaks - then find why it broke > To Fix..
Being consistent with tests is vital - So when posting test results - post features or additions...

hi James
already done, without MediaTransferProtocol_XPE.Script not work properly

I thought so...
When you say not working - Printer not loading ?? or explain
seems there is an overlapping process required....

When you say not working - Printer not loading ??

loading but i cant print " .pdf " , only " .prn "

so we are missing a driver(s) from Printer Support [Driver_Registry] that is included in MTP Support [Driver_Registry]

try adding > RegAddDriver,winusb.inf < to printer support - files exist in basic build

@ Noel,
Do you want us to continue with Printer Support Testing here on this topic ? (as we testing with XPE) Or would you like us to Open a topic in XPE Homepage ??

@ Cretino,
are you testing with your Driver.reg.txt ???

Cretino,
Or use MTP as your test victim.... Since PRS works with MTP
Kill things inside MTP [Process] to see what breaks PRS (Registry or Files)

hi Jamesw box

naw with your scipt i can save as pdf, was missing this key from scipt in both arc (x86 & 64°

Code: [Select]

[HKEY_LOCAL_MACHINE\Tmp_Drivers\DriverDatabase]

[HKEY_LOCAL_MACHINE\Tmp_Drivers\DriverDatabase\DeviceIds]

[HKEY_LOCAL_MACHINE\Tmp_Drivers\DriverDatabase\DeviceIds\MicrosoftMicrosoft_MUSD]
"prnms003.inf"=hex:01,ff,00,00

[HKEY_LOCAL_MACHINE\Tmp_Drivers\DriverDatabase\DeviceIds\{4d36e979-e325-11ce-bfc1-08002be10318}]
"ntprint.inf"=hex(0):
"prnms003.inf"=hex(0):

[HKEY_LOCAL_MACHINE\Tmp_Drivers\DriverDatabase\DeviceIds\{D20EA372-DD35-4950-9ED8-A6335AFE79F0}]
"ntprint.inf"=hex:01,ff,00,00

[HKEY_LOCAL_MACHINE\Tmp_Drivers\DriverDatabase\DeviceIds\{D20EA372-DD35-4950-9ED8-A6335AFE79F1}]
"ntprint.inf"=hex:01,ff,00,00

[HKEY_LOCAL_MACHINE\Tmp_Drivers\DriverDatabase\DeviceIds\{D20EA372-DD35-4950-9ED8-A6335AFE79F2}]
"ntprint.inf"=hex:01,ff,00,00

[HKEY_LOCAL_MACHINE\Tmp_Drivers\DriverDatabase\DeviceIds\{D20EA372-DD35-4950-9ED8-A6335AFE79F3}]
"ntprint.inf"=hex:01,ff,00,00

[HKEY_LOCAL_MACHINE\Tmp_Drivers\DriverDatabase\DeviceIds\{D20EA372-DD35-4950-9ED8-A6335AFE79F5}]
"ntprint.inf"=hex:01,ff,00,00

[HKEY_LOCAL_MACHINE\Tmp_Drivers\DriverDatabase\DriverFiles]

[HKEY_LOCAL_MACHINE\Tmp_Drivers\DriverDatabase\DriverFiles\LOCALE.GPD]
@="ntprint.inf"
"SubDir"="I386"

[HKEY_LOCAL_MACHINE\Tmp_Drivers\DriverDatabase\DriverFiles\MSXPSINC.GPD]
@="ntprint.inf"
"SubDir"="I386"

[HKEY_LOCAL_MACHINE\Tmp_Drivers\DriverDatabase\DriverFiles\MSXPSINC.PPD]
@="ntprint.inf"
"SubDir"="I386"

[HKEY_LOCAL_MACHINE\Tmp_Drivers\DriverDatabase\DriverFiles\MXDWDRV.DLL]
@="ntprint.inf"
"SubDir"="I386"

[HKEY_LOCAL_MACHINE\Tmp_Drivers\DriverDatabase\DriverFiles\P6DISP.GPD]
@="ntprint.inf"
"SubDir"="I386"

[HKEY_LOCAL_MACHINE\Tmp_Drivers\DriverDatabase\DriverFiles\P6FONT.GPD]
@="ntprint.inf"
"SubDir"="I386"

[HKEY_LOCAL_MACHINE\Tmp_Drivers\DriverDatabase\DriverFiles\PCL4RES.DLL]
@="ntprint.inf"
"SubDir"="I386"

[HKEY_LOCAL_MACHINE\Tmp_Drivers\DriverDatabase\DriverFiles\PCL5ERES.DLL]
@="ntprint.inf"
"SubDir"="I386"

[HKEY_LOCAL_MACHINE\Tmp_Drivers\DriverDatabase\DriverFiles\PCL5URES.DLL]
@="ntprint.inf"
"SubDir"="I386"

[HKEY_LOCAL_MACHINE\Tmp_Drivers\DriverDatabase\DriverFiles\PCLXL.DLL]
@="ntprint.inf"
"SubDir"="I386"

[HKEY_LOCAL_MACHINE\Tmp_Drivers\DriverDatabase\DriverFiles\PCLXL.GPD]
@="ntprint.inf"
"SubDir"="I386"

[HKEY_LOCAL_MACHINE\Tmp_Drivers\DriverDatabase\DriverFiles\PJL.GPD]
@="ntprint.inf"
"SubDir"="I386"

[HKEY_LOCAL_MACHINE\Tmp_Drivers\DriverDatabase\DriverFiles\PJLMON.DLL]
@="ntprint.inf"
"SubDir"="I386"

[HKEY_LOCAL_MACHINE\Tmp_Drivers\DriverDatabase\DriverFiles\PrintConfig.dll]
@="prnms003.inf"
"SubDir"="I386"

[HKEY_LOCAL_MACHINE\Tmp_Drivers\DriverDatabase\DriverFiles\PS5UI.DLL]
@="ntprint.inf"
"SubDir"="I386"

[HKEY_LOCAL_MACHINE\Tmp_Drivers\DriverDatabase\DriverFiles\PSCRIPT.HLP]
@="ntprint.inf"
"SubDir"="I386"

[HKEY_LOCAL_MACHINE\Tmp_Drivers\DriverDatabase\DriverFiles\PSCRIPT.NTF]
@="ntprint.inf"
"SubDir"="I386"

[HKEY_LOCAL_MACHINE\Tmp_Drivers\DriverDatabase\DriverFiles\PSCRIPT5.DLL]
@="ntprint.inf"
"SubDir"="I386"

[HKEY_LOCAL_MACHINE\Tmp_Drivers\DriverDatabase\DriverFiles\PSCRPTFE.NTF]
@="ntprint.inf"
"SubDir"="I386"

[HKEY_LOCAL_MACHINE\Tmp_Drivers\DriverDatabase\DriverFiles\PS_SCHM.GDL]
@="ntprint.inf"
"SubDir"="I386"

[HKEY_LOCAL_MACHINE\Tmp_Drivers\DriverDatabase\DriverFiles\STDDTYPE.GDL]
@="ntprint.inf"
"SubDir"="I386"

[HKEY_LOCAL_MACHINE\Tmp_Drivers\DriverDatabase\DriverFiles\STDNAMES.GPD]
@="ntprint.inf"
"SubDir"="I386"

[HKEY_LOCAL_MACHINE\Tmp_Drivers\DriverDatabase\DriverFiles\STDSCHEM.GDL]
@="ntprint.inf"
"SubDir"="I386"

[HKEY_LOCAL_MACHINE\Tmp_Drivers\DriverDatabase\DriverFiles\STDSCHMX.GDL]
@="ntprint.inf"
"SubDir"="I386"

[HKEY_LOCAL_MACHINE\Tmp_Drivers\DriverDatabase\DriverFiles\TTFSUB.GPD]
@="ntprint.inf"
"SubDir"="I386"

[HKEY_LOCAL_MACHINE\Tmp_Drivers\DriverDatabase\DriverFiles\UNIDRV.DLL]
@="ntprint.inf"
"SubDir"="I386"

[HKEY_LOCAL_MACHINE\Tmp_Drivers\DriverDatabase\DriverFiles\UNIDRV.HLP]
@="ntprint.inf"
"SubDir"="I386"

[HKEY_LOCAL_MACHINE\Tmp_Drivers\DriverDatabase\DriverFiles\UNIDRVUI.DLL]
@="ntprint.inf"
"SubDir"="I386"

[HKEY_LOCAL_MACHINE\Tmp_Drivers\DriverDatabase\DriverFiles\UNIRES.DLL]
@="ntprint.inf"
"SubDir"="I386"

[HKEY_LOCAL_MACHINE\Tmp_Drivers\DriverDatabase\DriverFiles\unishare-pipelineconfig.xml]
@="prnms003.inf"
"SubDir"="I386"

[HKEY_LOCAL_MACHINE\Tmp_Drivers\DriverDatabase\DriverFiles\unishare.gpd]
@="prnms003.inf"
"SubDir"="I386"

i send it to you

the MediaTransferProtocol_XPE.Script  needed to show the fax in the window
will see witch one needed to add ...

Code: [Select]

are you testing with your Driver.reg.txt ???

sorry , i forghet it in customise script 

Noel,
Here are the PE registry hives after processing just printer support...

Chris & Slore > both use a batch file or cmd to copy Install.wim registry keys by name search.inf

Code: [Select]

Reg Copy Key,HKLM,Tmp_Drivers\DriverDatabase\DeviceIds,"#1"
Reg Copy Key,HKLM,Tmp_Drivers\DriverDatabase\DriverFiles,"#1"
Reg Copy Key,HKLM,Tmp_Drivers\DriverDatabase\DriverInfFiles,"#1"
Reg Copy Key,HKLM,Tmp_Drivers\DriverDatabase\DriverPackages,"#1*"

I see in your post > default as _86_
but think the important is > Active as _amd64_

Hi
@cretino : you can use my email noelblanc.winpe(at)free and write in french. So i'll understand more easier
@james : You are right. It would be better if the discussion continued in a new post win10XPE. A lot of people could participate.

as I said earlier, I have no problem with my winpeBuilder tool. And this is because I made the structuring choices to copy the soft hive in its entirety.

In order that the extension "". PDF" appears with the PDF printer I made the choice to copy the entire hive drivers.
I made a trade-off between size and detail (I look for details to please me and when it brings me satisfaction).

For more than 8 days I've been looking for how to display ''.pdf' in the context of my PS winpebuider tool (PS script). It was a great pleasure to play with Windbg.

About win10XPE and PRS plugin, The beginning of my interest was simply curiosity. Because it was my last activity.
I asked for a procmon trace because i wanted to compare with my trace (i really can't use the application winbuilder.exe. Sorry. To complex for my poor English).

I see this in my trace when starting the 64-bit spooler: setting up the context spooler_X86 (keys and files)
The installation of this context Spooler_X86 requires driversdatabase and driverstore items.  With a procmon track of the spooler start, I could have quickly seen if this X86 context was correct. The presence of the key is also a point showing a good installation.

Code: [Select]

...\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows NT [color=blue]x86-Drivers\Version-3[/color]\Microsoft enhanced Point and Print compatibility driver

Perhaps i can help.

Ps : since 2016, i use printers PDF in winpe. The delay of 2 minutes is hardcoding in spoolsv.exe. I never try to reduce. But it's possible. Is there a gain for
final user ?

WimBuilder2 has AddDrivers macro to copy both driver files and registry items.
But the ALL drivers registry items is small,  so WimBuilder2 has an option to RegCopy all the DRIVERS registry items(ON by default).

AddDrivers macro just copy files if it knows you already copied all system DRIVERS registry items.

It be simpler and faster, but gain 600kb size.


So with WimBuilder2,  I can see *. pdf type,  I can't reproduce the issue.
Good to know WHAT'S Key causes this issue.
Noel 

Hi noelBlanc,

you (and cretino and ..) can post French here 
It is nicer to have info available public. 


*
@noelBlanc
I feel you will have good times reading WimBuilder Log
http://lancelot.theoven.org/TheOvenAttach/20191227_WimBuilder_Build_Step_by_Step.zip

On last picture, notice "Open Last Build Log"

Syntax is cmd syntax so you will have no trouble when reading. 

*

Thanks Galapo,

We can continue cooking
 

Cooked burgers getting better. 

hi Lancelot,
it's always a pleasure to read you.

I have found that on the one hand I misunderstand what is written and on the other hand that I am misunderstood. My idea is not to hide something. But not to pollute the offers of others.

And in the case of the extension '*.prn' I just wanted a file of a procmon trace. This would have allowed me to check what I had written in a previous post about it.

About WIMBUILDER, i like it. And  I use it. And in a precedent post , i say that WimBuilder speak in French.

But when i want to investigate in winpe ( OOBE in spoolsv, ALP port in termservice…. BSOD...) i need to use my building scripts and vhd (flat, fullflat) because it is with my own tools that I am most effective.
I hope you understand me.
 

it is with my own tools that I am most effective.
I hope you understand me.

I fully understand you. 

I also do similar like you on other cases 

Generally, I also look dependencies and document as deep as I can like you do but different areas. 

See You 

hi

Code: [Select]

The presence of the key is also a point showing a good installation.

under pe this are present ( with lastes printer suppert scrip )

Code: [Select]

...\Control\Print\Environments\Windows NT x86\Drivers\Version-3\Microsoft enhanced Point and Print compatibility driver
...\Control\Print\Environments\Windows NT x86\Drivers\Version-3\Microsoft Shared Fax Driver
...\Control\Print\Environments\Windows NT x86\Drivers\Version-4\Microsoft Print To PDF
...\Control\Print\Environments\Windows NT x86\Drivers\Version-4\Microsoft XPS Document Writer v4

adding printer driver + WinUsb Driver + Still Image Setup File



printer device not recognized in "peripherals and printers" & not showing in printer window ...
still missed key ...
(tested without mpt script)
 " ça devient une folie , je me suis à peine réveillé et je me retrouve devant le pc ... "

edit

there was another hp driver that i forgot, now it's recognized by the system .. almost,
when i click on the print button, nothing happens, the printer does not print, it looks like a service is missing ... 

"( il y avait un autre identifiant hp que j'ai oublié,maintenant elle est reconnue par le systeme .. presque,
lorsque je clique sur le bouton imprimer, rien ne se passe, l'imprimante n'imprime pas ,on dirait qu'il manque un service ... )"