new Explorer and IE7 (v12), IE7 is now 100MB smaller External links Rating Options

[2aCD]

Hi VistaPE-Friends

now I have separate scripts for Explorer and IE7 ready.
Explorer-Tweaks now is not no more needed. I have include it in Explorer-script.
I have add some Context-Menu Entrys from Arvy (Thanks)

You must place it in folder Shell

Download:
[attachment=4293:Explorerv.7z]

IE7 I have complete new revised.
You can include Favorites before you build the CD.
When you use Standard-Copy now boot.wim is 100Mb smaller!!
On CD you can live install Activex Plugins

You must place it in folder \app\network (the same how place firefox)

Download:
[attachment=4208:IE7.7z]

Note: The IE7 needs explorer. It not work without explorer!!


many greetings
2aCD

[Arvy]

Congrats on a sensational job, 2aCD! Works perfectly in VistaPE v.11, including IE7's handling of both local HTML pages and client side script processing. The latter wasn't working well in the previous version. In fact, whether intentionally or otherwise, you've also solved a problem in the MMC 'extended' display of Windows services.

Making the Explorer shell script self-contained with its own 'policy' settings and IE7 a separate dependent script makes good logical sense, I think. At least for me, its much easier to follow and choose amongst the various available options that way. And I'm very happy to be able to get rid of a couple of my own little ad hoc addons.

If you haven't already done so, I suggest getting in touch with Nightman about coordinating with his work on VistaPE v.12 beta development. My own very limited testing suggests that there may be a few wrinkles to iron out at this very early stage.

[phox]

Hi VistaPE-Friends

now I have separate scripts for Explorer and IE7 ready.
Explorer-Tweaks now is not no more needed. I have include it in Explorer-script.

Finally!

Great work 2aCD. Thank you.

[risolutore]

thank 2aCD for this work. splitting the script is a good choice for debugging porpouse and also for making it more flexible, I will give a try an the aternoon on my italian system locale in order to verify the mui vaiablility.

[Max_Real Qnx]

I thanks my friend for great self-sacrificing job

[Arvy]

If you haven't already done so, I suggest getting in touch with Nightman about coordinating with his work on VistaPE v.12 beta development. My own very limited testing suggests that there may be a few wrinkles to iron out at this very early stage.

UPDATE:
The problem under the VistaPE v.12 pre-release was a missing common.script (DLLs from Vista DVD as source) in my beta project installation. With that added, both of the new scripts work perfectly.

MINOR NITPICK:
The explorerv.script contains two entries for "...\Windows\CurrentVersion\Explorer\Advanced","Hidden" at lines 104 and 107.

[2aCD]

@all
Thank you for the congratulations.
Then the nights were worthwhile themselves.


@Arvy,

CODE

The problem under the VistaPE v.12 pre-release was a missing common.script (DLLs from Vista DVD as source) in my beta project installation. With that added, both of the new scripts work perfectly.

You already found out, which are that. I would then already add it.

[TheHive]

Then the nights were worthwhile themselves.

Very worthwhile indeed. Some people like having both IE and Explorer and with this masterpiece of seperation you can make those that only like Explore or IE, a very happy bunch.

[Arvy]

You already found out, which are that. I would then already add it.

I'm not sure exactly which files in the new common.script for VistaPE v.12 will be required to support the Explorer shell and IE7. NightMan has combined the copying and registration of a lot of common components (WSH/MDAC/HTA/WMI/XML) available only from the Vista DVD source into that single new script. I only know that I needed to download and run it to make yours work properly in the pre-release beta.

Probably your best and easiest solution whenever v.12 is released will be to note that additional common.script dependency just as you do in noting IE7's current dependency on your own Explorer shell script. But, now that you're on board with rest of the beta team, you can decide how best to handle it between the two of you.

[online]

Really great work!

With previous releases I had not reached good results and I had abandoned them, but now they work so fine... really!