98 replies to this topic

[ludovici]

Hello Everybody
I come back after 4 month of standby
I need tester for 2 scripts
http://www.mediafire...vrf4w958ymf9w8f Net Framework V4
http://www.mediafire...4bnzf38q4tqf12p Printer Feature

Thanks for your help

[Aeolis]

Hello folks,

You have a tester here for the printer script.

Best regards,

Aeolis

[Aeolis]

Hello folks,

Dear ludovici, my first test with the Printer script ended unexpectedly due to a build error. Here is the log file:  log_20120502_182200_Win7PE_SE_Support.7z   171.71KB   6 downloads

I may be wrong, but after I have studied the log file and your script a little it seems that it is a simple error of the destination folder not being created before the source files be copied into it. Just add the extra checks or the create folder before the copy commands.

Keep the good job. A Printer script is a must have for PE's if you need any assistance just let me know. I would like to join you in your Printer script development.

Best regards,

Aeolis

[MedEvil]

Ran into the same error.

The script seems to be the old one from your project. If so, it's not working, i tested it back then.

[MedEvil]

PS: If i remeber correctly, the problem is that the foldernames are from a Win7SP0.
In the copy commands, some foldersnames, or best all foldernames, need to loose the long number at the end.

[MedEvil]

No it wasn't that kind of an error. Build fails also with Win7SP0.

[ludovici]

http://www.mediafire...9739f2boquok7xm
Print Feature V5

Thanks for your test Medevil and Aeolis

[Aeolis]

Hello folks,

I still have the build error problem with version 5 of the printer script:  log_20120503_180400_Win7PE_SE_Support.7z   172.09KB   3 downloads

Best regards,

Aeolis

[ludovici]

Thanks Aeolis

Can you test with this new version 6 http://www.mediafire...3vmj97wj9964cc1
But in winbuilder tools uncheck Stop build on error

[MedEvil]

Since i'm in an especially good mood today, i went over the print.script and fixed all errors and warnings.
Still doesn't work.
At least we know now, it's not because of a script error.

Error message, when one tries to start spooler service: Dependency group failed to start.

Print.script v7
 Print.script   200.52KB   16 downloads

[ludovici]

Thanks Medevil for your work
And for my script

I will check this night what are this dependancy (DCOM Server Process Launcher, Remote Procedure Call (RPC), DCOM Server Process Launcher
http://www.speedyvis...int_Spooler.php

Medevil have you the file "http.sys" in your System32Drivers directory of your WinPE ?

Can you explain Medevil, what are you doing on my script ?
I see this line "Unpack,Files,Spoolsv.7z,True,%TargetDir%Windows,System32"
The unpack command has been modified ?

[MedEvil]

I think i have isolated the problem.
The http driver entry is malformed.

Just running tests, which of 2 solutions gives the better result.

[ludovici]

Yes it's maybe HTTP service; i has add this service with speed delay; sorry i will check.

Maybe add also the "RootLEGACY_HTTP0000" registry key also

[MedEvil]

Yep eighter the ENUM entry has to be removed in the HTTP service or the "Root\\LEGACY_HTTP\\0000" registry key has to be added, both works.

I went in the end with the second, cause it's the cleaner solution and i had hoped that that would allow the spooler service to auto start.
It does not.

So for now, spooler service needs to be started by hand, then ... printing works!

Unfortunately the add printer dialog presents me with no ports to choose from, so i had to try with the XPS-Printer.




PS: New printer script v8  Print.script   201.54KB   20 downloads

[MedEvil]

Wow! Given the fact, how often i have heared that people want printing to work in PE, there's surely little interest in testing a working Printer script.

[Aeolis]

Hello folks,

Sorry, for the delay. I am using version 8 of the print script and I have disabled the "stop on build error" option as requested, here is the log:  Win7PE SE-Win7x86_2012-mai-05_10-37.7z   190.74KB   6 downloads

Still have the missing files errors.

Best regards,

Aeolis

[MedEvil]

You still have the error messages with v8?
That shouldn't be possible.

[Aeolis]

Hello folks,

Just check the log file.

Best regards,

Aeolis

[MedEvil]

Aeolis, i don't understand that error. There's no error in the script code and since the dll is found ok, there's no reason the mui file wouldn't be there.

Could you check in the install.wim if the files exist? Maybe boot.wim too?

[Aeolis]

Dear MedEvil,

After some research I've found out that "DevicePairingProxy.dll.mui" and "DeviceUxRes.dll.mui" are not present on my Install.win %DistLang% folder which is by the way pt-BR. Those files are only present in my Install.win folder under en-US, maybe you could copy them from en-US.

They can't be found at the Boot.win folder too. I hope it helps.

Best regards,

Aeolis

[MedEvil]

I could add a workaround, that if the files are not found in ones language, then it would default to english.
But before i do that, i would like to be sure, that this is not just a hickup with your source.

Could you compare the files installed on your regular Win7, with the ones found in the en-US folder on your DVD, to verify that M$ simply copies the en-US files to your pt-BR folder?

[MedEvil]

@Ludovici
Support for parallelport printer (LPT1) is definitly missing in the script. I tryed everwhichway to get the add printer dialog to show me LPT1 as an option, i didn't work.

[MedEvil]

Just checked on a regular Win7. The listing of all ports in PE is missing not just parallel port, but also serial ports and xps-port and file port.

[Aeolis]

Hello folks,

MedEvil, I have checked the files in my working environment (I run Windows 7 Ultimate 64-Bits in my working machine), so I have:

C:WindowsSystem32pt-BR: DeviceCenter.dll.mui, DevicePairing.dll.mui, DevicePairingFolder.dll.mui and DeviceProperties.exe.mui.
C:WindowsSystem32en-US: DevicePairingProxy.dll.mui and DeviceUxRes.dll.mui.

C:WindowsSysWOW64pt-BR: DeviceCenter.dll.mui, DevicePairing.dll.mui, DevicePairingFolder.dll.mui and DeviceProperties.exe.mui.
C:WindowsSysWOW64en-US: DevicePairingProxy.dll.mui and DeviceUxRes.dll.mui.

As we can see here, it seems that M$ uses DevicePairingProxy.dll.mui and DeviceUxRes.dll.mui as fallback files in the en-US folders. So, I think you should copy them from en-US and put them in the en-US PE folders too not in the PE pt-BR (%DistLang%). I hope it helps.

Best regards,

Aeolis

[MedEvil]

Oops, that's even weirder than i thought.
We could try it like that, but you would need to check, if it works like that in a PE too.

I have my doubts, sidebar proved to be rather picky about the mui folder in PE.




Print.script V8 Aeolis-Test-Version:  Print.script   202.27KB   15 downloads