14 replies to this topic

[MedEvil]

File Name: NaughtyPE
File Submitter: MedEvil
File Submitted: 20 Aug 2011
File Updated: 20 Aug 2011
File Category: Projects

NaughtyPE - The Multimedia PE!

NaughtyPE is meant to be a portable EmergencyOS, to be carried around on a MiniCD and is therefore just 210MB in size, while it still features such cool things as sound and requires just 128MB RAM to operate, 256MB to use the video players.
For a plain build choose download level Recommended, if you'd like to debug NaughtyPE or one of it's apps, choose Complete. Download level Minimal is not supported.

The list of goodies includes:
- explorer as shell
- working sound
- mp3 player included
- video player included (actually 2 at the moment)
- internet radio included
- browser to surf the net and even watch youtube
- picture browser
- picture retouching programs
- CD/DVD burning software
- pdf reader
- a ton of fixing and emergency tools
- ....

Before use, please go to the main topic and read the useful tips!
http://reboot.pro/38...8564#entry28564

Click here to download this file

[pscEx]

PE1_4WB82.Script now patches NaughtyPE to use with WinBuilder version 82+



There are some issues which do not depend on WB82. E.g. VirtualBox script looks for the stone-aged Innotek registry entry.

Peter

[TheHive]

pscEx can you post to this thread the NaughtyPE that is working and patched for Winbuilder 082+.
Tried to follow youre instructions for patching but its not working.
During build I get
Exec - Failed to find section [ExtractHoJoPE] in file: [%HivesFactoryScript%]

[pscEx]

I unzipped this one into a fresh directory:

Peter

[MedEvil]

Peter, where did you download the project from, cause the error Hive has, has also been the one, i was having, with your earlier version of the script.

[pscEx]

Sorry, my fault! %HivesFactoryScript% was not defined in script.project.

I added to the path.

Now you can download PE1_4WB82.Script version 8

Peter

[TheHive]

I did a new extraction to naughty.zip and then put the PE1_4WB82.Script version 8
in the same folder as the script.project. When I ran Winbuilder and selected the patch button. I ge this error.

ExtractFile - Failed to expand file: [PE1_4WB82_v8.ini] to: [%BaseDir%ProjectsNaughtyPE]
http://temp.reboot.p...g NaughtyPE.zip

[pscEx]

I cannot read the log, but from your report I alredy see what happened:

You renamed the script to PE1_4WB82_v8.script.

*.ini, *.log, *.exe names are built from the root name of %ScriptFile%.

But attached is PE1_4WB82.ini rather than PE1_4WB82_v8.ini.
The same issue you'll get with PE1_4WB82_v8.exe and PE1_4WB82_v8.log

Use the original name of the script.

Peter

[TheHive]

That seemed to have been the problem. The patching went ok.
The build finished with no errors reported. But there are errors poping up when booted up.

UPloaded a video of errors.
http://sharesend.com/bvvm7

[pscEx]

Sorry, I cannot view *.flv on my system.

Peter

[MedEvil]

@pscEx
You can download VLC portable to have a look and delete it afterwards.

@Hive @pscEx
- The SetResolution - and the PeNetwork problems are new. I never seen it before happening.
- ViStart and Visplore sometimes interfere with eachothers start and sometimes not. Never found out why and therefore could never fix it. Omitting one or starting them manually one after the other makes them work.
- The icon problem is new to me. I can replicate it though, also without the update patch, when i use an english source. WB80 seems to have already started to create different shortcuts compared to WB74, when there is a space in the path.

[pscEx]

@Medevil:

The issues "SetResolution" and "Missing Icon" (maybe also the "PENetwork") depend on spaces in the "Program Files" path, which is not handled correctly by the API.
Maybe you did not see this before, because you did not try e.g. English source, which in %ProgramFiles% contains a space, unlike in German source.

I do not want to debug scripts developed by some bakers and maintained by a bakery, but maybe you find a newer API which works.

BTW: There is a great inconsistency in creating shortcuts and associations. The used %variables% names and syntax are very different from script to script. That makes an automatic patch for WB 082 nearly impossible.
Try to have some more conistency!

Peter

[MedEvil]

Yep, there is inconsistancy.
The inconsistancy is, that my scripts do not use the API and properly format the shortcut.
While the other scripts use API to create shortcuts and use %ProgramFiles%, which was banned, due to the non reliable creation of shortcuts, if you remember.

Will have a look at the API problem, but changing the API, would require to switch out the whole base too.

[pscEx]

...ö, but changing the API, would require to switch out the whole base too.

I'm not sure. I have had similar issues with the ("daily changing") API and decided to stay on a well known version and add some "overloads".

Because the page describing that, is currently not available (Bandwith issues), here a short extract:
multiPE API use

API, realized as Common_API.script is developed to allow different projects to use app scripts without caring background project differences.

multiPE uses the API, too, but with some changes. Let's use shortcuts as example.

In the ICE-age, when creating the first Vista project, the author NightMan decided to collect shortcuts in a file, and to start a program during PE boot to generate the shortcuts.

This mechanism is used by following Vista and Win7 projects.

The API therfore in all PE2 and PE3 projects writes shortcuts into the 'shortcut - file'.

My projects write every information into the PE during build, to decrease boot time.
This is not possible with the currently used API. Therefore the multiPE project hooks some API calls and performs it's own processing.
(For those who are interested: %easyApiScript%=%ProjectDir%ToolsHookAPIEx.Script).

In the past I always tried to use the latest Common_Api.script.
But nowadays several actual Common_Api.script-s seem to exist, and new ones appear regularly w/o documentation. None of them has a certification.

Therefore I decided to use an API which in my knowledge works. I renamed to Common_ApiEx.script and included in the multiPE project.


Peter

[MedEvil]

I don't quite understand what it is you wanna say.
That i should create a own API?