PENetwork Script

Hi,

I have noted that PENetwork sets the default action for driver installation to ignore. When I run a build without PENetwork and use the Universal Video Driver I get a Unsigned Driver Installation message.
Should Driver Installation Behaviour not be configured in a more core part of the nativeEx build?

Regards,
niche99

Hi,

I have noted that PENetwork sets the default action for driver installation to ignore. When I run a build without PENetwork and use the Universal Video Driver I get a Unsigned Driver Installation message.
Should Driver Installation Behaviour not be configured in a more core part of the nativeEx build?

Regards,
niche99

Thanks for the hint
On my ToDo list now!

Peter

Hi Peter,

Another observation. If I don't include PENetwork in my build, the task bar and desktop icons take a long time to appear. Includ e PENetwork and it's almost instantaneous.

Do you know why this is? If it's something particular to PENetwork should this feature not be part of the core nativeEx?

Regards,
niche99

Another observation. If I don't include PENetwork in my build, the task bar and desktop icons take a long time to appear. Includ e PENetwork and it's almost instantaneous.

@niche99: This post is a perfect addon to your first one!
If I add two registry entries (stolen from PENetwork) to the core

RegHiveLoad,"WB-Software","%TargetDir%\I386\system32\config\Software"
RegWrite,"HKLM",0x3,"%HiveKey%\Microsoft\Driver Signing","Policy","00"
RegWrite,"HKLM",0x3,"%HiveKey%\Microsoft\Non-Driver Signing","Policy","00"
RegHiveUnLoad,"WB-Software"

the PENetwork - free ISO comes up as fast as that one with PENetwork, and no 'uncertified driver' is mentioned.

Thanks again

Peter

BTW: I'm thinking about a CoreTweaks.Script which contains this and some other tweaks like the 'Fonts - Icon / main.cpl' issue.

Nice idea!

I've added a similar one for liveXP to add a shortcut on the desktop - small tweak but very handy for any admin..

tweaks.script:

[main]
Title=Other tweaks
Description=Add a small set of extra customizations
Selected=True
Level=2
Version=1
Date=2007-JUL-18

[Interface]
pCheckBox1="Add shortcut of CMD.exe on desktop",1,3,45,61,200,18,True

[process]
If,%pCheckBox1%,Equal,True,Run,%BuildModelScript%,Add-Shortcut,"DE","cmd.exe","Command prompt","/SW:#$psystemdrive#$p"

Please add this option as well to avoid double scripts with similar tasks..

Nice idea!

I've added a similar one for liveXP to add a shortcut on the desktop - small tweak but very handy for any admin..

tweaks.script:


Please add this option as well to avoid double scripts with similar tasks..

I'm not sure whether this shortcut is the same 'category'.

Desktop is depending on the (usually Explorer) shell.
Therefore it should be an option in MiskSettings.Script
@Holger ???

Peter

I just needed a simple script because miscsettings is most times too far away from common people's attention - look how even edborg wasn't aware of the option to disable numlock at startup..

These are just tweaks that are not as vital as choosing PEloader or shell start parameters - something that everyone can "play" with.

Had forgot the need to support other shells - nice one!

I still have the same unsigned messages when running the project - tried a few modifications but no good - still shows up the dialog box and takes a really long time to start compared to previously.


Been reading more and it seems that PE network script do disables the unsigned warning but there are other things that were not mentioned, including some aditional registry keys that could be added.

Look here: http://www.msfn.org/...p...st&p=247232

HKCU,"SOFTWARE\Microsoft\Driver Signing",,0x00000000
HKCU,"SOFTWARE\Microsoft\Non-Driver Signing",,0x00000000
HKU,".DEFAULT\SOFTWARE\Microsoft\Driver Signing",,0x00000000
HKU,".DEFAULT\SOFTWARE\Microsoft\Non-Driver Signing",,0x00000000
HKCU,"SOFTWARE\Policies\Microsoft\Windows NT\Driver Signing\BehaviorOnFailedVerify",,0x000000

These keys are not added inside the target registry, notice the difference:

RegWrite,"HKLM",0x3,"%HiveKey%\Microsoft\Driver Signing","Policy","00"

RegWrite,"HKLM",0x3,"%HiveKey%\Microsoft\Non-Driver Signing","Policy","00"

Similar but different as Bashrat mentions:

a question to the registry-experts: in the registry it's in fact this key:
HKLM,"SOFTWARE\Microsoft\Driver Signing\Policy",,0x00000010
then why is it
HKLM,"SOFTWARE\Microsoft\Driver Signing",,0x00000010
in the HIVESFT.INF?

And some distressing informations from here:

"Driver Signing Registry Values Cannot Be Modified Directly in Windows"

A possible solution (txtsetup.sif is supported?)
"How to Add OEM Plug and Play Drivers to Windows XP"

Will keep testing or return to older files..

I still have the same unsigned messages when running the project - tried a few modifications but no good - still shows up the dialog box and takes a really long time to start compared to previously.


Been reading more and it seems that PE network script do disables the unsigned warning but there are other things that were not mentioned, including some aditional registry keys that could be added.

Look here: http://www.msfn.org/...p...st&p=247232



These keys are not added inside the target registry, notice the difference:

RegWrite,"HKLM",0x3,"%HiveKey%\Microsoft\Driver Signing","Policy","00"

   RegWrite,"HKLM",0x3,"%HiveKey%\Microsoft\Non-Driver Signing","Policy","00"

Similar but different as Bashrat mentions:


And some distressing informations from here:

"Driver Signing Registry Values Cannot Be Modified Directly in Windows"

A possible solution (txtsetup.sif is supported?)
"How to Add OEM Plug and Play Drivers to Windows XP"

Will keep testing or return to older files..

@Nuno:
Bad news and good news!

• Bad news: You are completely wrong
• Good news: I found the root of the troubles
• Build LiveXP with all scripts enabled besides 'Apps\Network\Smart FTP' : No 'Unsigned Driver' message
• Build a minimum runnable configured LiveXP with all scripts disabled besides 'Apps\Network\PENetwork' and 'Apps\Network\Smart FTP' : 'Unsigned Driver' message

Which script is the bad boy?

Peter

Hmm? That's a tough one!
Rembrandt!?

Hmm? That's a tough one!
Rembrandt!?

[German (slang)]
Watt iss Rembrandt?
[/German]
[English]
????
[/English]
I know the painter (makes me to be a Guru of arts?).

Peter

[German (slang)]
Watt iss Rembrandt?
[/German]
[English]
????
[/English]
I know the painter (makes me to be a Guru of arts?).

Peter

I expected a lot of people to , but thought you would get it.

It's from an old Otto joke
He does a parody of a quiz show, where the area of expertiece of one of the candidates is Rembrandt.
The questions go something like that.
Who is the son of Rembrandds mother.
or
Who painted Rembrandts self portrait.

The candidate never understands the question and asks just something including the word Rembrandt and immediately gets the point.

The joke knows of course a second candidate, she always gives answers that make absolutely no sense in the context.
Like: Of which season is sung in this song?
Answer: Egypt!?

Those two answers has been become sort of a short hand for eighter giving answers, that don't need to be given, for being too obvious or not getting the point of something.

Both answers are still used in the company i work in, but this reaction makes me wonder, if it is maybe me who keeps them alive in the first place.

Maybe 30 years is alittle too long for a joke to survive in general public, even a brilliant one like that.

If you wanna see the original for yourself... (It's in german, but you get it also without it, imo.)

Otto - Quizshow

I just needed a simple script because miscsettings is most times too far away from common people's attention - look how even edborg wasn't aware of the option to disable numlock at startup..

Well, I was aware , and it was disabled.
Problem was that another script enabled it again later (not all scripts are consistent, you know, and often they interfere one each other so that you're never sure of your current settings ) .
Moreover, I hadn't realized that my keyboard malfunctioning was due to numlock , otherwise i'd have unlocked it without posting here.
Have a nice vacation!
edborg

SmartFTP was the reason why the message box was displayed!!

Good find Peter!


Now, which dependency added by smartFTP can be causing this interference?

SmartFTP was the reason why the message box was displayed!!

Good find Peter!


Now, which dependency added by smartFTP can be causing this interference?

Currently I do not have a real motivation to research for that.

Maybe in five (Brazilian) minutes ...

Peter

I've just had the same problem with FileZilla. The complicating file I have narrowed down to RSAENH.DLL

Not sure what to do about this yet -- but the driver-signing message is annoying!

Regards,
Galapo.

rsaenh.dll is responsible for a bunch of crypto related things, but not all programs need it.
Get yourself a program that does not require it or have an autoit script running that will close it automaticly.

Yes, I have essentially four options:

1) see if somehow these messages can be disabled even with this file;

2) use autoit to kill the message(s);

3) use autoit or cmd to copy the file across to system32 before starting the ftp program (requires writable systemdrive);

4) try different software, either i) which doesn't require the file, or ii) can tolerate having the file located in its program folder.

Hmmm. Maybe 4 is my best bet. Any suggestions?

Regards,
Galapo.

OK, I've answered my own questions in finding a workable solution.

Came across CoreFTP, which doesn't require RSAENH.DLL (or any other files to be added to system32).

Done up a script which can now be downloaded from my site.

Regards,
Galapo.

I've just had the same problem with FileZilla. The complicating file I have narrowed down to RSAENH.DLL

Can you please post the FileZilla script.
I want to try some build time registry work to avoid the 'driver signing'

Peter

Gday Peter,

Here's the script: http://galapo.boot-l...ileZilla.script

Should be uploaded in a couple of minutes...

I've used the portable version, so the running of the program requires that the program's directory be writable (with BootSDI, FBWF, etc).

Hope this helps.

Regards,
Galapo

3) use autoit or cmd to copy the file across to system32 before starting the ftp program (requires writable systemdrive);

Got a neat litle script builder trick for ya, that might help.
Change the path variable in the PE registry to include a path to the ramdrive, like B:\system32.
Hold rsaenh.dll in a folder that is not in Path. And only copy it to B:\system32 after all installations have finished, but before you run your software. Maybe the start of your software can copy it?

Please note: Once found, rsaenh.dll will stay active, even if deleted from B:\system32!

Got a neat litle script builder trick for ya, that might help.
Change the path variable in the PE registry to include a path to the ramdrive, like B:\system32.
Hold rsaenh.dll in a folder that is not in Path. And only copy it to B:\system32 after all installations have finished, but before you run your software. Maybe the start of your software can copy it?

Please note: Once found, rsaenh.dll will stay active, even if deleted from B:\system32!

I'll have to remember that one. Thanks!