595 replies to this topic

[Wonko the Sane]

First of all, MR Schlang is The only one most active Rebootpro developer, who is constantly improving Winbuilder.exe, it is complex program written in Borland Delphi.

Without ANY irony I suspect that Peter (Mr. Schlang) being the ONLY person to have access to Winbuilder source code (besides Nuno Brito which charged Peter with the developing) may explain why he is the ONLY developer improving Winbuilder.exe.

This of course doesn't in the least diminish the very good work that Peter has done, is doing and will hopefully do

Mistakes (and expecially very minor ones like forgetting to fix a local/absolute path) can happen to everyone, and it would be nice if they were treated as such, without the need of sarcasm/attacks, nor for "defense attorneys".

The fact that Peter is a nice guy doesn't makes him "untouchable", and I believe that - if touched - he can defend himself allright, but let's not make a "big thing" out of nothing, OK?




Wonko

[pscEx]

... but let's not make a "big thing" out of nothing, OK?

Thanks "Jaclaz". I agree.

Peter

[pscEx]

Mistakes (and expecially very minor ones like forgetting to fix a local/absolute path) can happen to everyone, and it would be nice if they were treated as such, without the need of sarcasm/attacks, nor for "defense attorneys".

In order not to make such a mistake, I created a tool to do such things automagically.

But this tool had a until now unrecognized glitch ...

Version 57 will be uploaded which hopefully contains no more local paths.
Version 56 deleted from server.

Peter

[pscEx]

Version 57 uploaded.

What's New in Version 57

• Version 56 had some initialisation issues. Some local paths remained in script.project. Version 56 deleted from server.

Peter

[pscEx]

Version 58 uploaded
What's New in Version 58

• There have still been some glitches in initialisation by version 57 (e.g. paths with x64 rather than amd64). Version 57 deleted from server.

Peter

[JanuszChmiel]

Dear Peter,
You are The man, who is full of wisdom and programmers experience.
But please, there is really no other way to build Windows 8 live project with Multipe than downloading whole .iso image with waik file? According to my opinion, if all users would use Windows Xp while building Yours project, there may would not be any bug related to wincapt.exe.

Or I can not use
Windows8-ReleasePreview-32bit-English.iso
image as source, so Winbuilder is executing Java and java code is downloading WIndows waik .iso image?

Because i like YOurs project and i have saved all Yours previous, may be that not all, but mayor of them, i will really run The one from August with WIndows Xp and i will try resulted produced image.

[ccl]

Dear pscEX, do you having any guidelines building Win8PE by using multiPE ?

[pscEx]

Version 59 uploaded.
What's New in Version 59

• fixed bug in multiPE ISO naming
• rearranged program start from RAM, System Drive and Boot Media
• added .net framework and EasyBCD scripts
• fixed bug in ImageIndex script, wich sometimes caused partly delete of stored WIM files
• added build from Win8 source

Win8PE is still in development.
When it has booted, hit F5 to get into the desktop.

I hope that some members will help to add full functioning explorer, taskbar etc.

Peter

[JanuszChmiel]

Dear Peter,
First of all, i would like to thank You very much for Yours outstanding entusiashm, and thank You very much, that You are developing Multipe for so long time.
Yours previously published MULTIPE stable project really reliably supported boot to RAM, so scripts are creating .img file, which is being loaded to RAM.
I have only one kind suggestion, do You think, that You would enable users to create .wim boot image on future?
Or this would really break all scripts so it would require many time to make this?

My next kind pleasment is related to drivert host auto import.
I have found out, that You are trying to automatically import drivers from host system.
What about let users to choose, if they want this feature, so if users of NVDA would press button activate NVDA, driver host import feature would not be automatically used?
The sense of my pleasment is to have NVDA started automatically without errors or prompts related to driver host modules.
I like rather one reliable USB headsets device, which will be reliably detected by using build in Yours script, than host driver import script, which will produce questions and some error messages.

I know, that for sighted users Yours approach is very revolutionar, but for people like me, it is not very happy solution.

I will test, if NVDA is still working when XP source have been selected in Yours latest version of project.
Previous release produced reliable bootable project with functional NVDA incorporated. I had to run NVDA manually, but it worked. Even if i had specified pefactory setting to create RAM image, .img file.

If You are sure, that host driver script is not causing those problems, would You remove other code with questions for users to let Multipe to run NVDA smoothly with USB headsets support enabled?

I do not want to suggest somethink, what majority of users would dislike, so what about making this release specifically presetup for visually impaired users, You would never had to make this setting in Yours next stable release.

I have decided, that i will stop dream about USB headsets support if Windows 8 source have been selected. Windows 8 to go will work fine and it would require many lines of code to automatically register this device driver.

So Peter, continue in Your enthusiasm, Yours project is working smoothly.

Next plans would include support for massstorage drivers atleast for XP source, because i do not know, if it would work for now by adding .7z archive to The special folder created by driverimport script when user press one special button of user interface of this script.

Thank You for icluding Easy BCD program, it is very good boot manager.

[JanuszChmiel]

Hello Peter,
First of all, i can write You, that latest MULTIPE is supporting NVDA perfectly, even USB headsets.
Second positive think, USB boot of Yours project is working perfectly.
So excellent job Peter.

Please, would You explain me, why portable apps, which You have made as special script are not being The part of resulted project if i press attach button? Download process is working perfectly, but The downloaded portable application is not become The part of The project.
I can not find The apps after boot.
Or must i move files downloaded by Yours script to other location first?
Thank You, what You have included clamwin Portable, Pyriform products and even my favourite remote desktop client.
AA_v3.exe
But how to make those tools The part of resulted live project?
I have good notice, it is not necessary to modifi project, host auto driver, host aud, host nic are not causing problems related to NVDA.
Thank You very much for Yours advice.
And thank You very much for new script.

[JanuszChmiel]

Dear Peter,
Portable applications downloaded by Yours scripts are being correctly downloaded to The following folder.
C:multiPE_latest14WorkbenchCommonPortable
What should i do to have those applications incorporated in to The resulted live project.
Yes, it is true, that i can also stop to bother You about this and i can put .exe programs to The root of my USB stick. But when You have created so excellent .script files, it is sad to not have them working correctly.

[pscEx]

I'm currently looking the portable apps issue, and when necessary, to apply a fix.

Peter

[pscEx]

For me, the portable apps work correctly.

Did you forget to select the script for run?

By default, shortcuts are generated in start menu.

You can add desktop and quichlaunch by checking these boxes in the script.

They are in the middle left of the GUI.

Or is there an issue with the GUI that NVDA does not see these check boxes?

Peter

[JanuszChmiel]

Dear Peter,
GUI of all portable apps related scripts is excellently accessible with NVDA, You have been coded GUI very well. I have checked The checkbox desktop and start menu.
How to start The script to let it run? I have thought, that i only have to press attach button and that cript will run automatically when i will activate The big blue play button in Winbuilder user interface.

If no, how to make script to run?
I AM afraid, that error is caused by setting, which are being applied when user press add NVDA support.
So scripts are not being executed.

So attach button will not allow scripts to run automatically when user press play blue button inside WWinbuilder user interface?

I have chosen only The settings add NVDA support and setting to create bootable USB stick, i have not changed other pefactory setting , so MULTIPE will not create .img file to boot faster to RAM.
If You want, i can run whole procedure again by erasing Multipe folder, extracting whole archive and i can activate The debug log feature and i will upload all log to The server and i will send link to this support topic Peter.

[pscEx]

You have to select it for run in the normal way:

Check the box in the build tree on the left.

The box is not automatically selected by the download.

Peter

[JanuszChmiel]

Dear Peter,
When i have used The context menu available when focus is placed on The name of one of The portable apps script, when i recalled this menu and when i have choosen run this script, script executed correctly. But there is still no portable application inside The resulted live PE project.
Or there is really other build button available?
NVDA can not locate this button even while NVDA is using display hooks based on GDi32 functions and procedures call, NVDA is even supporting mode of flat view, but there is no build button.
Run this script from context menu not help, eventhough application is correctly downloaded and placed in The right folder.

If build this script button is other task than selecting run this script from The script tree context menu, would You create buttons inside The GUI of all portable scripts so i could activate this button?

I Am very sorry, but i Am really doing my best to run script.

[JanuszChmiel]

Dear Peter,
Here is The texts fetched by NVDA when NVDA is using flat review feature.
I can also use other technique, which is getting objects from mSAA, by using ole and User32 calls and oleacc.dll calls.

So my Winbuilder window is maximized.
WinBuilder [083]
WinBuilder [083]

Play Tools Download
Play Tools Download
Script
multiPE
Core
Apps
Develop
Portable
AMMYY Admin
AusLogic Disk
Piriform CClea
ClamWin Port
This project needs
Piriform Defra
mulPiriform Recu p
Create shortcuts in :
me
Productivity
It pscEx's
System Desktop
Drivers
StartMenu
Finalize
Quick Launch
PEFactory
Tools
This project has only
But it has some crimi
It can steal applicatio
But it has some crimi
Before the first use you must (download and) attach AA_v3.exe!
It can steal applications from other projects
Yes, i can also use object hiearchical navigation technology. So i can really only reach The run this script context menu item.

[pscEx]

I) tried with NVDA. The result is not very amazing:

No chance to check the value of a check box. And a click toggles between checked and unchecked.

I'll try to add select and unselect to the context menu.

Peter

[JanuszChmiel]

Dear Peter,
Yes, i can use all checkboxes inside GUI of portable apps scripts, i can use run this script from The context menu of script, but yes, i can not use The checkbox.
It is sad, that You can not place it on The same place, where check boxes add NVDA support, audio message boxes are located.
You will be may be sad, that You would had to modifi winbuilder Pascal source code to enable visually impaired to run Yours portable scripts and others, which are requiring to use those check boxes.
You are very kind and thank You very much for Yours hard programmers work.

Today, i will try to force Multipe to support SATA harddrives by adding masstorage .7z archive to The driver import Pe right folder.
If it will work for me.
Yes, sighted users can use BIOS setup to use IDE instead of SATA emulation, but it is not possible for us.
Thank You very much for Yours help with checkboxes.

[pscEx]

WinBuilder 83.0.0.14 already has in the build tree's context menu the menu items

• Select this script
• Unselect this script.

I'll include in the next multiPE upload.

Coming soon.

Do not worry about your wishes.

After a long time I feel again a real challenge.

Peter

[pscEx]

Uploaded version 60
What's New in Version 60

• fixed bug in shortcut creation, which made e.g. ShutDownPE unstartable.
• Added "Select this Script" and "Unselect this script" to project tree context menu. This is the only way for blind users using NVDA to add / remove a script to the build.

To get the second fix, please put WB82 into your project directory. Then start WinBuilder, which automatically updates to the 83.0.0.14 version.

Peter

[JanuszChmiel]

Dear Peter,
Thank You very much. Believe, that i would never intrude You, but i was not able to force NVDA to access The checkbox, thank You very much for this.

I will try it just now.

[JanuszChmiel]

Dear Peter,
Very, very, very well done.
Thank You very much for adding new context menu items inside winbuilder.exe.
Thank You for speed up of algorithms, which are being executing scripts.
For now, i Am really able to use portable apps without issues according to The settings, which i have been applied inside GUI or one of The portable apps scripts.

I Am only fighting with one issue.

Auslogic disk defragment portable script not allow Winbuilder.exe to display context menu, so i can not select or deselect it. I have tried it for several times. But it is really not possible, all other portable scripts can be selected or deselected thanks to Your new two context menu items.

Next issue is much more sad than first issue.

Winbuilder GUI is making somethink wrong. When i want to change The pefactory setting, create iso or make bootable USB, Winbuilder is only displaiing create iso and NVDA is speaking also this item.
Winbuilder can not change The item to other item than create iso image.

Inside The pefactory, configure, create image, i can select USB stick by using ammazing find removable drives button, but i can not change The previous PE-factory related setting.

Other thinks are working, NVDA, host driver, host network driver, there are no hydden errors except two, which i have mentioned.

Would You try to look at those strange behaviour in The following days dear Peter?

And really, thank You for Yours work.
I Am also very positively appreciating Yours licensing and legal polici protection, You are not including some modified setupldr.bin, or ntldr or other binary components of Microsoft Windows operating system.

My pleasment related to this problematic is, why it is inpossible to use 7-zip command line program to create .wim image, so Windows 8 sources would be used without no need to download whole Waik.

And my last pleasment til The end of this year is:
How complex would be to add SATA drivers to Yours PE?
I think, that it will be much more better to let this task on You, because i think, that it is not so simple, only add one .7z driver to The right folder of Multipe.

Now, i Am running piriform defraggler, I AM defragmenting free drive space by using live project created by Multipe 60.
Thank You for Yours hard, very patient and extremely difficult programmers work.
And thank You again for Winbuilder.exe modiffication.

[pscEx]

I Am only fighting with one issue.

Auslogic disk defragment portable script not allow Winbuilder.exe to display context menu, so i can not select or deselect it. I have tried it for several times. But it is really not possible, all other portable scripts can be selected or deselected thanks to Your new two context menu items.

Next issue is much more sad than first issue.

Winbuilder GUI is making somethink wrong. When i want to change The pefactory setting, create iso or make bootable USB, Winbuilder is only displaiing create iso and NVDA is speaking also this item.

I cannot reproduce the Auslogic issue. Maybe you did something wrong?

The ISO issue is my fault, and will be fixed in multiPE 61, coming soon.

Peter

[pscEx]

Version 61 uploaded

What's New in Version 61

Winbuilder GUI is making somethink wrong. When i want to change The pefactory setting, create iso or make bootable USB, Winbuilder is only displaiing create iso and NVDA is speaking also this item.

• fixed bug in PEFactory, which made build of USB stick impossible.
• Deleted version 60 from server.

Peter