211 replies to this topic

[pscEx]

Blow me!

I'm sorry. The offer does not please me, and I'll forget it.
But I will continue to monitor the infringement of copyright rake.

Peter

[Galapo]

Unfortunatelly this project seems to use some LiveXP 'features'.

The project can be very easy made WB 081 compliant (Without hurting some back compatibility) by replacing %ISOFile% in some scripts 'intelligent' by %BurnISO%

Peter, the %ISOFile% variable is a WB variable. It is not a LiveXP "feature", it was a WB feature up until 081rc1.

On the other hand, %BurnISO% is truly a nativeEx variable! It is a nativeEx invention and you want JFX's project to adopt its use. You make a snide comment about LiveXP, but then want JFX's project to adopt a nativeEx "feature". I don't get it.

Regards,
Galapo.

[paraglider]

If you a going to force a variable rename on project developers then I suggest %ISOFileName%. %BurnISO% sounds more like a boolean i.e. do I burn the iso to a CD or not.

However don't understand why %ISOFile% cannot be a variable instead of a constant. Cannot be a huge winbuilder change to do that.

I also do agree that 00-5_ISO_Name_Dynamic.script is a very strange script. It seems overly complicated in just allowing the source architecture to be appended to the base iso file name. The base file name should only be set from the source tab as now you have 2 places where the base iso file name can be set.

[brninitdwn]

Is this still being actively worked on? I think the latest release was great, but was wondering about getting System properties and plug and play (for thumbdrive use as I burn this to a CD)working as it has not worked on any version I have used. If anyone has any ideas on areas to look or known fixes please let me know!

[PaPeuser]

Is this still being actively worked on? I think the latest release was great, but was wondering about getting System properties and plug and play (for thumbdrive use as I burn this to a CD)working as it has not worked on any version I have used. If anyone has any ideas on areas to look or known fixes please let me know!

Hello
No I do not think any Win7 project is being worked on at this time..

Yes System Properties works in the Ludo7PE Project.
Pictures and package downloads can be found in the Screenshots section.

I have been testing some Ludo7PE project scripts in Win7PE_SE

But I was having trouble with Winbuilder 8 becoming non-responsive and hanging, So I gave up….


Thanks 06122010

[Altorian]

I have now created a stand-alone shell script from BlackBox for Windows
I have tested with win7pe_SE and it works very well
all necessary files are loaded from the win7 DVD
I hope you enjoy it

Advantages of this shell is small and fast looks very good
virtual desktops are also supported and the look is extremely customizable

Download:
http://archiv.to/GET/FILE4C3A000DCB9E3

Style Pack (2500 styles!)
http://www.boxshots.org/styles.zip

[Lancelot]

Thanks a lot Altorian,

all working verrry smoothly

[vvurat]

Altorian. Can you explain how did you get the files list and why every file need for?

ReqSys32,actxprxy.dll
ReqSys32,apphelp.dll
ReqSys32,browseui.dll ok
ReqSys32,diskcopy.dll
ReqSys32,msxml3.dll ok
ReqSys32,msxml3r.dll ok
ReqSys32,msxml6.dll ok
ReqSys32,msxml6r.dll ok
ReqSys32,query.dll
ReqSys32,rshx32.dll
ReqSys32,shsvcs.dll
ReqSys32,winrnr.dll
ReqSys32,explorerframe.dll ok
ReqSys32,msi.dll ok
ReqSys32,oleacc.dll
ReqSys32,oleaccrc.dll
ReqSys32,osbaseln.dll
ReqSys32,appwiz.cpl

especially diskcopy.dll 1.43mb that every time i remove because it is big and didnt gave me any problem. want to learn about files that don't have ok near.

[Altorian]

hi vvurat
It is certainly not all the files needed but it should work.
the script is still not optimized.
it went with the files actually just at the explorer as a file manager, so that he starts.

[PaPeuser]

Amazing,,,, great work

It will take me weeks Months trying out all the styles!! edited



Should this be a new topic??

[Altorian]

I do not know whether it should be a new topic
I have a stand alone script actually created for you 7pe_se Users

and a tip of the styles, extract the shell and add all the styles in the styles folder
then you can switch the styles quickly in the menu

[Altorian]

a question to you
Do you need some desktop icons for the Black Box
or is the Quick Launch toolbar enough

[paraglider]

Think it would have been better as a separate post as this is an addition to the project not a fix.

[Virtual-R]

Hello, and thank you for a great work with Multi 7PE SE.

I am having one problem though. It's with the explorer shell.
Even if show_run is activated, no Run.. will show in Start Menu.

I have attached a picture showing you how the startmenu looks, and how it looks
in the settings and registry after PE has started. Also showing the scriptsettings.

Any1 know what's wrong here? Thanks in advance! Take care!

[Altorian]

I think paraglider has right
I want the BB4WIN script extend and there is better to make a separate topic
could ask a moderator to outsource the BB4WIN posts

[Lancelot]

Hi Altorian,

At current stage better you open a new topic for the script than moving posts
(and if further questions comes to here or there, i will move to that new topic)

[Altorian]

have now a topic created for the BB4WIN shell script

http://www.boot-land...showtopic=11968

and it is now also optimized
it will be loaded only the most necessary files from the win 7 dvd

[Altorian]

I have the common-files.script filled with life, I hope it helps you a little

[Main]

Title=6 - Common Files

Type=Script

Locked=false

Level=1

Selected=True

Author=JFX, Modified by Altorian

Credits=

Contact=

Version=2

Mandatory=False

Download_Level=0

NoWarning=False

Description=common library (VB5, VB6 and etc)

Date=2010



[Variables]

%Wow%=%InstallSRC%\Windows\SysWow64

%tWow%=%TargetDir%\Windows\SysWow64

%Manif%=%InstallSRC%\Windows\WinSxS\Manifests

%tManif%=%TargetDir%\Windows\Winsxs\Manifests

%SXS%=%InstallSRC%\Windows\WinSxS

%tSXS%=%TargetDir%\Windows\Winsxs

CopySysWoW=Run,%ScriptFile%,Process-CopySysWoW

CopySys32=Run,%ScriptFile%,Process-CopySys32



[Process]

Run,%ScriptFile%,CopyFiles_SyStem32

If,EXISTDIR,%tWow%,Run,%ScriptFile%,CopyFiles_SySWoW64



[CopyFiles_SyStem32]

CopySys32,avifil32.dll

CopySys32,avifile.dll

CopySys32,msacm32.dll

CopySys32,msacm32.drv

CopySys32,msvbvm60.dll

CopySys32,msvcp60.dll

CopySys32,msvfw32.dll

CopySys32,msxml6.dll

CopySys32,msxml6r.dll

CopySys32,ntvdm.exe

CopySys32,oledlg.dll

CopySys32,quartz.dll

CopySys32,query.dll

CopySys32,shellstyle.dll

CopySys32,wdi.dll

CopySys32,wow32.dll

CopySys32,ddraw.dll

CopySys32,avicap32.dll



[CopyFiles_SySWoW64]

CopySysWoW,avifil32.dll

CopySysWoW,msacm32.dll

CopySysWoW,msacm32.drv

CopySysWoW,msvbvm60.dll

CopySysWoW,msvcp60.dll

CopySysWoW,msvfw32.dll

CopySysWoW,msxml6.dll

CopySysWoW,msxml6r.dll

CopySysWoW,oledlg.dll

CopySysWoW,quartz.dll

CopySysWoW,query.dll

CopySysWoW,shellstyle.dll

CopySysWoW,wdi.dll

CopySysWoW,wow32.dll

CopySysWoW,ddraw.dll

CopySysWoW,avicap32.dll



[Process-CopySysWoW]

//System,ErrorOff

If,EXISTFILE,%InstallSRC%\Windows\SysWow64\#1,Begin

If,Not,ExistFile,%TargetDir%\Windows\SysWow64\#1,FileCopy,%InstallSRC%\Windows\SysWow64\#1,%TargetDir%\Windows\SysWow64\#1

End

If,EXISTFILE,%InstallSRC%\Windows\SysWow64\%DistLang%\#1.mui,Begin

If,Not,ExistFile,%TargetDir%\Windows\SysWow64\%DistLang%\#1.mui,FileCopy,%InstallSRC%\Windows\SysWow64\%DistLang%\#1.mui,%TargetDir%\Windows\SysWow64\%DistLang%\#1.mui

End



[Process-CopySys32]

//System,ErrorOff

If,EXISTFILE,%InstallSRC%\Windows\system32\#1,Begin

If,Not,ExistFile,%TargetDir%\Windows\system32\#1,FileCopy,%InstallSRC%\Windows\system32\#1,%TargetDir%\Windows\system32\#1

End

If,EXISTFILE,%InstallSRC%\Windows\system32\%DistLang%\#1.mui,Begin

If,Not,ExistFile,%TargetDir%\Windows\system32\%DistLang%\#1.mui,FileCopy,%InstallSRC%\Windows\system32\%DistLang%\#1.mui,%TargetDir%\Windows\system32\%DistLang%\#1.mui

End

[PaPeuser]

Hello Altorian
With your modified 6-Common Files script I get 6 File copy errors during build.
The System cannot find the file specified
System32\avfile.dll
System32\msvbvm60.dll
System32\ntvdm.exe
System32\wow32.dll
SysWow64\avifile.dll
SysWow64\ntvdm.exe

Does adding these files enhance your - y-BB4WIN - SCRIPT?

I am a little confused with your (package download) BB-7PE looks to be based on Multi Win7PE by Yahoouk and not on JFXs Multi Win7PE_SE project.

When I view build scripts and check authors I am not sure what version you are using?

But the y-BB4WIN shell stand alone script works well with JFXs newest version of Multi Win7PE_SE

I would like to know what version of Multi Win7PE or Multi Win7PE_SE you are using for testing

A little history with Multi Win7PE_SE
When JFX was developing Win7PE_SE there was some discussing as to what files to include in the basic build. It was decided if a script required any files not included in build then that script should copy files. This was to keep Win7PE_SE as small as possible. Why include files that a user might not use?

I hope this makes some sense.

[Altorian]

hi PaPeuser

the here published version of the BB-7PE is still based on multi Win7PE
but the version I use now, is a customized version of Multi Win7PE_SE
I will publish the new version here soon, it will include many improvements

what now regards the Common Files script
I have tested it several times with win7 DVD and Multi Win7PE_SE without errors
and the files in the script are that it takes a whole series of programs
and a blank Common Files script is also not good

PS: I modified the script above again slightly

[PaPeuser]

Hi. Altorian...

the here published version of the BB-7PE is still based on multi Win7PE
but the version I use now, is a customized version of Multi Win7PE_SE
I will publish the new version here soon, it will include many improvements

Thanks for Confirming.. no problem,

what now regards the Common Files script
I have tested it several times with win7 DVD and Multi Win7PE_SE without errors
and the files in the script are that it takes a whole series of programs
and a blank Common Files script is also not good

Ok - i build with a Win7 x64 Pro host
I again tested your Common files script,
when i use a Win7 x86 source to build i do not have file copy problems,
file copy problems are with using Win7 x64 source to build.

I do not have a problem adding files with the common files script. in fact i suggest adding files this way to get some addon scripts to work. but I was informed this was not correct way to do it.

the idea is\was addon or app scripts should work with any build from liveXP to Vista, so it was desided that these scripts should do there own file copy.. this kept project small and made addon or app scripts work with most\any project.
this is just something to keep in mind..

I look forward to your updates.. keep up the good work

[Altorian]

I've adapted the script
64-bit only missing two files

avifile.dll = 16-Bitprozeß there is no longer on win7 64 (DOS)
ntvdm.exe = 16-Bitprozeß there is no longer on win7 64 (DOS)

[jimmsta]

I'm considering using this project as the base for my BootZilla-v6 project. Should I make my project inherit bits from your project, or should I create a separate fork for my own developements?

[Virtual-R]

Any1 found a solution for missing Run... in startmenu?

[Virtual-R]

SOLVED!!! Finally!

I don't know if anyone else than me was affected, but I feel it's my duty to tell you anyway.
As you may know, i couldn't get the Run.. command to get visible in the startmenu (using the explorer shell).
It ended up being Runscanner 1.0.0.24 that gave this problem. I updated to 1.0.0.25 by paraglider and the problem is gone!

Greets // VR