38 replies to this topic

[allanf]

Hi 枯道曦风 (sorry I can't read your name in my browser. I hope it's OK. ... ...)

The first post has been corrected, including Full Winbuilder Package Downloads (WB076). And the WB Server has been updated. Please try again... if you are game enough ... ...

I hope no damage done.

EDIT: You must DELETE the offending file - 'PortableApps.com_Platform_Setup_1.1.exe' - from 'pe2ArchiveDir' before you run the project again.

Regards

[TheHive]

Same sheep you mention with no color, no restrictions
http://www.fundraw.c...-Cartoon-Sheep/


Here is an alternative hashed up

[allanf]

Same sheep you mention with no color, no restrictions
http://www.fundraw.c...-Cartoon-Sheep/

... it's amazing you could find that! ... ...

Here is an alternative hashed up ...

Cool! ... ... If I called it PortabaaaalApps.com, I wouldn't need to go around sticking those little ®s everywhere.



... next version ... ...

Things are a little mixed up here ATM.

Regards

[TheHive]

I was going to test the project but I got a bit confused with the selections and options available.

[allanf]

TheHive,

Thanks for considering. ... ...

I haven't got the wording right.

1. The first drop-down scrollbox under 'PortableApps.com':

If selected "The Full Suite", every Portable Program listed will be downloaded (if it does not already exist in 'pe2ArchiveDir') and extracted/installed to the Target build. NB. Except 7-zip and FreeCommander whose scripts are presently disabled because they do not allow silent install.

If selected "Individual Select", only the Portable Programs whose boxes are checked (ticked in Aussie) will be extracted/installed. If you don't wish to install any Portable Programs, use this option and deselect every Program.


2. The second drop-down scrollbox under 'Configuration':

If selected "Individual Settings", only the Settings whose boxes are checked will be implemented.

If selected "Default", the following will be implemented
a. The Programs will be run from RAM
b. There will be no prompt to press a key to boot the CD
c. No Drivers will be added
d. FBWF will be 32MB
e. wpeinit - for PNP and Network support - will start automatically at boot-time
f. At boot-time, there will be no wait time for Mass Storage Devices to initialize


3. The third drop-down scrollbox under 'Windows Tools':

If selected "All WAIK Tools", all WAIK Tools will be copied to the build.

If selected "Individual Tools", only the tools whose boxes are checked will be included. And here you can select to install no tools at all.


4. The fourth drop-down scrollbox under "Packages":

If selected "All Packages", the three listed packages will be installed. NB. the 'xml' and 'scripting' packages are not listed, because they are always installed by default - they seem universally required, although maybe they should be listed as an option, so someone could make an absolute minimum build if required.

If selected, "Individual Packages", only the packages whose checkboxes are checked will be copied to the build. I haven't tested thoroughly, but it may be likely that the 'HTA' packaged is required for some Programs to run properly.



NOTE: If the Text Labels in Winbuilder's Interface disappear (under XP-Style on the host PC), it is necessary to minimize then restore the Winbuilder Window.


I hope this helps.

For a first build, I recommend selecting the "Individual ..." selections and settings from the drop-down scrollboxes, and unchecking every box, so that the build is totally minimized... just to start with. If everything works, then make individual selections and settings... then try "The Full Suite" and "All WAIK Tools".

Regards

[allanf]

I should also mention that four files will be created in your '...\Winbuilder\Projects\pePA.com\' folder.

Posted here in text format:






EDIT: Please note that the paths in the files are not hard-coded, but are written in when the files are created.

In particular, I mention that your Anti-Virus Program ought to object to the running of the vb scripts! If it doesn't you need a new AV!

It is up to you whether or not to allow the scripts to run - and I post them here for your perusal.

The VB scripts came from MS's 'The Scripting Guy' for the shortcut script, and http://www.robvander...l#CopyHereUNZIP for the unzip script... with minor modifications.

The DriveLetter.cmd is based on a communication I had with jaclaz where I somehow managed to turn an elegent batch file into... well... something less elegent, but functional (as far as I can tell).

In my list of things to do (firstly for pe21, then for this project), is a note to make all shortcuts at boot-time rather than do some of the easier ones at build-time.

Regards

[allanf]

Lastly, for the time being... I'm trying to reveal the project 'Warts and All', since someone (TheHive) indicated an interest in trying it.

There is a flaw in the creation of shortcuts at boot-time. The DriveLetter.cmd searches all drives for the actual Program. As a result, if the Program actually exists in '...\Program Files\...' on an accessible drive other than the boot media, and the drive letter is earlier than the boot media's in the search order (or, for some reason, the Program failed to install on the boot media or in RAM X:\) the link will point to the Program on the wrong drive.

List of more things to do ... create a tag file to search for rather than the Program.

EDIT: Wrong project! The above only applies to a limited extent to the Windows Tools and the PortableApps Platform/Menu executable. The 'shortcuts' to PortableApps Programs are actually in the PortableApps Menu and should be immune from the flaw. d'oh!

Regards

[TheHive]

Thanks for the info.
I ran the Project with all settings. mmm!


During build this is the only thing that stoped it from proceeding. I pressed cancel and after that the project build accordingly.


I get this when booting up. Good thing it suggests to also try the right click on desktop.




After hitting ok. We get the the baby showing its colors. Very cool!



One thing needed in the project is a description of whats needed to build the project. Just like the info on youre first post.

Great Job!

[allanf]

Great! I'm glad you gave it a shot.

Regarding GIMP: I tried to explain to another poster about my lack of download capacity. Now, I must confess that I did my tests with an earlier version I have, which seems no longer available for download. I renamed it to the newer version to run the project, not expecting them to remove the ability for a silent install. What a shame. I really liked GIMP, even though I rarely have a chance to play with it.

Now there are three on the list that need modifying - 7-zip, FreeCommander and GIMP.

Thanks TheHive.

[枯道曦风]

Thanks very much for your so kindly replies.
I deleted Port*1.1.exe file, than tried, two files still to be produced under root folder, but partition icon does not change, all shortcut dose not work in resutled ISO.
than I deleted Port*1.1.exe and script.project files, then none file to be produced under root folder, but there still have popup windows for shortcut problem, after cancel these windows I could open menu by click curly arrow, but only Backup and Options two shortcuts do work, others e.g. Explorer etc. do not respond.

[allanf]

Thanks very much for your so kindly replies.

Not at all. Thank you for trying the project and reporting back. ... ...

In your first screenshot, I can see that the 'Scripting' package is not installing to the PE This should not affect the PortableApps Menu - it only has an effect on the Right-Click>Start Menu>Programs, which include non-PortableApps such as A43. What is the source of your winpe.wim? WAIK 1.1 (Vista SP1) or WAIK 2.0 (Win7 beta)?

In your second screenshot, it looks like no PortableApps are being installed at all. Perhaps the downloads are failing? I cannot guess the problem. Can you provide a Winbuilder log.html of your build? It may help. Please note that 7-zip Portable, FreeCommander Portable and GIMP Portable do not install to pePA.com Project. If you try "The Full Suite", you should cancel the prompt to install GIMP.

I shall try to reproduce your errors. Firstly, I would delete the entire pePA.com folder and contents in the '...\Projects\' directory. Then go to Winbuilders 'Download Center' and redownload fresh scripts - only 100KB or so. (You may have tried this already.)

It may also be necessary to verify that the PortableApps.com_Platform_Setup_1.1.exe is the same as the one that I have.

I have downloaded md5.zip from http://www.fourmilab.ch/md5/. It is a command-line tool. The result for my file is:
28AD41F6793A0193EFD212D305C0E05F

Regards

[allanf]

... but only Backup and Options two shortcuts do work, others e.g. Explorer etc. do not respond.

I forgot to mention that elements in the right-hand panel - Documents, Music, Pictures, Videos and Explore - do not work in this Project. I can only assume that they are linked to Windows Explorer, which is not available in the basic Windows PE. (I wonder if there is a script for PortableApps Menu in VistaPE, which does have use of Explorer.)

Recently, I have been looking for an alternative Menu, and came across Geek_Menu:
http://geek-menu.sourceforge.net/
It has more options, but I don't know if it can be configured to work with a File Manager other than Explorer. Has anyone tried it?

Regards

[枯道曦风]

MD5 is right, I had seen your post about Port*1.1 line and checked with script.project file.

I can not find any log file under WB folder

My processing followed yours that use WAIK 1.1 tools and WAIK 2.0 winpe.wim file

yes, I have not selected any PortableApps in the last posted ISO to minimize the problems.
just now I tried again with a few PortableApps, it seems PortableApp do work, but more shortcur errors, please see pictures below:

[allanf]

My processing followed yours that use WAIK 1.1 tools and WAIK 2.0 winpe.wim file

Ah! This project uses peimg to install the required Operating System Packages - by default, the 'Scripting' and 'XML' packages.

In the words of MS, 'peimg has been deprecated'! (Deprecated?! Sounds like something my pet dog might do on its walk!) In other words, it doesn't work for the WAIK 2.0 (Win7 beta) winpe.wim.

In my first post, I tried to briefly describe the steps that would allow you to exchange the new winpe.wim for the old. It is necessary to add the OS packages to the new winpe.wim using the new dism.exe tool in the new WAIK, before swapping the winpe.wims.

Unfortunately dism does not work too well under XP, so I had to make a basic bootable Windows PE 3.0 (from WAIK 2.0)., boot to it, and use dism to 'add-packages' to the new winpe.wim on my Hard Drive.

dism.exe is already included in the new winpe.wim. I think you can make a basic Windows PE 3.0 from the pePA.com Project if you keep the new winpe.wim in the 'Windows AIK' sub-folders. However, do not include the Optional 'Windows Tools' because they may affect the operation of dism.

Before booting to the basic Windows PE 3.0 made from pePA.com, you should make a copy of the new winpe.wim in a place easy to find - say, c:\winpe.wim. Then boot up, and try to add the packages with dism, remembering that you must first run wpeinit or you will receive an error when trying to mount (read/write) your c:\winpe.wim with dism /mount-wim. Also, beforehand, create a folder to mount the image (/index:1), say c:\mount.

... if you have Vista as your host, it may be much simpler to run dim.exe from there.

I am glad you are trying the new Win7 winpe.wim. I think it's fantastic!

If you need more assistance, do not hesitate to ask.

Good Luck