Jump to content











pscEx's Content

There have been 1000 items by pscEx (Search limited from 01-April 14)



Sort by                Order  

#185360 multiPE

Posted by pscEx on 02 July 2014 - 04:58 PM in Projects

Version 77 is ready for download.

 

What's New in Version 77

  • Some smoothing of screen reader support.

 

The build boots without user interaction into hearable NVDA  with:

  • Win7 booting with boot.wim: VirtualBox, ISO CD, UDF
  • XP booting with RAM Disk: VirtualBox, ISO CD, UDF
  • XP flat booting: VirtualBox, UDF.

 

 

Peter




#185143 PE for blind people

Posted by pscEx on 25 June 2014 - 12:04 PM in Development

I'll tell the project to include it automatically when Screen Reader Support is installed.

 

For now you can add it manually by selecting multiPE > Apps > System > MountStorePE

 

Peter




#185128 PE for blind people

Posted by pscEx on 25 June 2014 - 06:58 AM in Development

There are two differences between your and my configuration:

 

First: You appearently defined a physical CD drive as source. I did the same and it worked with me:

 

Second: Your host is Win7 x64, mine is XP x86. I'm going to check

 

Peter




#185120 PE for blind people

Posted by pscEx on 24 June 2014 - 07:29 PM in Development

I did a test:

 

I downloaded multiPE 076 from the download center and expanded into the empty directory C:\scratch\multipe

Started C:\scratch\multipe\winbuilder.exe, and followed EXACTLY the desription in post #2.

 

My entries are local paths, would propably be different for you:

SourceDir="Q:\CDs Standard\W7_32_DE_ENT_SP1" Attention: Path enclosed in quotes because of space in the path

Entry1=PortableNVDA=C:\Scratch\NVDA_Port\NVDA2013.3

 

Started the build, restarted, etc. as requested. Successful result: Run into VirtualBox with working NVDA

 

When you do the same and do not have success, we have to find the difference between our systems, an I have to do some changes which respect the differences.

 

Peter




#185115 PE for blind people

Posted by pscEx on 24 June 2014 - 07:00 PM in Development

I do not understand the troubles.

Before upload I expanded the whole version 76 package into an empy directory, and it worked well.

 

I'll re-upload. perhaps something is brokem in the uploaded file.

 

Do not waste time with removing something from the project. The project "As Is" should work well and run into VirtualBox

 

Peter




#185113 Need Scripts for 'Win8.1SE' and Grub4dos Menu for 'Win8.1U1SE_x64...

Posted by pscEx on 24 June 2014 - 06:50 PM in Grub4dos

(OT):

Wonko!

 

I really like your poetical desription :thumbup:

 

It meets human bevaviour to 100%!

 

Peter
 




#185110 [script]PENetwork

Posted by pscEx on 24 June 2014 - 06:34 PM in Development

Hi Holger,

 

didn's see you a long time.

 

Thanks for the upgarade. I'll merge into my projects.

 

Peter :cheers:

 

Just a question: Is your new PENetwork only usable in Win7PE, or can it also be used in a dinosaur time dated XP PE?




#185106 Need Scripts for 'Win8.1SE' and Grub4dos Menu for 'Win8.1U1SE_x64...

Posted by pscEx on 24 June 2014 - 05:15 PM in Grub4dos

I do not feel well reading this post.

 

reboot.pro is a community of members who create, develop, debug, enhance something by communication, suggestions and examples.

 

Your post gives me the impression that you see reboot.pro as warehouse, where you can order something.

 

I suggest:

Try to solve your issue using your brain, your experience, your knowledge.

Maybe you should first become familar with Grub4Dos.

And when you have troubles, ask with description of the (for you) unsolvable issue.

 

Peter




#185098 PE for blind people

Posted by pscEx on 24 June 2014 - 01:13 PM in Development

Depending on my age, I seem to become forgetful.

 

Number two is already implemented.

 

In the hostAud, hostNIC and hostVID scripts there are checkboxes AUTOSTART.

 

When you uncheck them, hostDriver has to be started manually, when wanted.

 

I will change the shortcuts to be all in Startmenu System.

 

Peter




#185095 PE for blind people

Posted by pscEx on 24 June 2014 - 12:13 PM in Development

...

 if YOu would have some time to make .exe program to copy .drivers from running system which would generate The Winbuilder script with this driver, this would be ideal solution.

 

...

if You would add button, which would enable users to choose, if they want to have hostdriver.exe started automatically or no.

If it is possible, if hostdriver.exe do not make somethink magic to enable sound support at all, so it is necessary to start it.

 

To number one: There already exists a tool LocalDriver which creates a script by catching the host's driver.

 

To number two: A good suggestion. I'll implement.

 

Generally: Many thanks for yout tests and suggestions.

 

Peter




#185093 multiPE

Posted by pscEx on 24 June 2014 - 11:04 AM in Projects

Version 76 uploaded.

 

What's New in Version 76
  • Fixed an issue with syncronisation problems after new installation. That caused NVDA not beeing copied to the PE.

 

Blind users, please have a look at the small tutorial

 

Peter

 




#185049 PE for blind people

Posted by pscEx on 23 June 2014 - 11:31 AM in Development

Before official upload the current mutiPE 76 is available at http://multipe.exec-.../multiPE_76.zip

Peter



#185038 PE for blind people

Posted by pscEx on 23 June 2014 - 08:22 AM in Development

Thanks for the log.

 

It is a synchronisation issue. I'm working on solving.

 

I think that I'll upload version 76 soon.

 

Peter




#185003 I am very lonely

Posted by pscEx on 22 June 2014 - 02:39 PM in Site feedback

I deactivated AVAST for 10 minutes.

 

I'm still the only user ...

 

Peter




#184994 PE for blind people

Posted by pscEx on 22 June 2014 - 12:50 PM in Development

Thanks for your comments, Janusz!

 

You mentioned hostdriver alreaydy some time ago.

 

And following your suggestion in multiPE version 75 NVDA is started independent from hostdriver by the multiPE central boot loader easyDriveLetter:

 

 

Peter




#184989 PE for blind people

Posted by pscEx on 22 June 2014 - 10:08 AM in Development

A new version of the multiPE project is available for download.

 

It realises the content of this topic.

 

Peter :)




#184988 multiPE

Posted by pscEx on 22 June 2014 - 09:08 AM in Projects

Version 75 is ready for download.
What's New in Version 75

  • In the project: For blind users input to file boxes via editable text file.
  • During PE boot: Automatic answer to "Driver Signing" dialog.
  • After the screen reader is started: Switching between the different audio endpoint devices, until the blind user hears something.

Base for the changes is the discussion in the topic "PE for blind people"

Post #2 of that topic contains a short tutorial, how a blind user can build and start a PE.

Peter

 




#184980 I am very lonely

Posted by pscEx on 21 June 2014 - 06:09 PM in Site feedback

Bump!

 

Just to check whether the forum now shows new posts.

 

Peter




#184972 PE for blind people

Posted by pscEx on 20 June 2014 - 02:59 PM in Development

Pre-scan (as part of the "main" accessibility-enabled-project) all the "checked for inclusion .scripts" and *somehow* create on-the-fly a .ini file with all the files required, whenever such a "choose file" or "choose folder" is present in the .script interface.

I added the AccessibilityIni.Script which can be found in the GUI project tree as Tools > AccessibilityIni.
It uses a modified version of the good old myOptions application.
accessibility.gif
On click on "Create" myOptions scans all scripts having the Accessibility=True definition in the [Main] section and writes the needed information into %ProjectDir%\Accessibility.txt
This looks like:
Spoiler

The user can modify Accessibility.txt and then click "Save" to update the scripts with the modified contents.
At the end of Accessibility.exe you can define the SourceDir.

I added the Accessibility=True filter, because without the filter there would be a mass of files in Accessibility.txt, and most of them have standard definitions without the need of modifying by the user. Searching a certain file in Accessibility.txt would be difficult for the blind user.

When the user wants to include a new script in the list, he just has to write the flag into [Main]

There is a way provided to fill file boxes for individual scripts.
Some scripts, especially myNVDA, have now in the very bottom

A key "Create"
A check box "Automatically save changes on exiting the text editor"

"Create" builds Accessibilty.txt and opens it in the standard text editor.
BTW: Do not forget to save changes in the editor before exiting.
When the check box is checked, changes are automatically applied after leaving the editor.

Peter



#184958 I am very lonely

Posted by pscEx on 18 June 2014 - 05:13 PM in Site feedback

Whenever I look at the "Online Users" at the end of the forum's page, I only see me.

 

Even Google, Facebook, etc. which usually are very curious, seem to not visit reboot.pro any more.

 

Or is it just only a forum's software issue with missing information?

 

Peter




#184928 Hello!

Posted by pscEx on 16 June 2014 - 08:10 PM in Hello world!

See here: http://reboot.pro/to...lp/#entry184923

 

Peter




#184927 Hello World!

Posted by pscEx on 16 June 2014 - 08:08 PM in Hello world!

Welcome in our community

(inspite we currenly seem to have some server issues)

 

Peter :cheers:




#184926 PE for blind people

Posted by pscEx on 16 June 2014 - 07:57 PM in Development

BTW: If somebody wants to try the actual develop stage, there is a nightly downloadable as http://multipe.exec-.../multiPE_75.zip

Unzip into an empty directory, recommended is a folder in the drive's root

Define your source CD or source folder resp.
multiPE can process CDs as source, but the build process is much faster, when you once have extracted the CD into a local folder.
You can use an XP or Win7 SP0 / SP1 source. Vista is not implemented.
The language will be of your choice.

In the project's script, check "Screen Reader Support"

In the project tree, at V:\multi Test\Projects\multiPE\Core\6 - Core Apps\Accessibility\myNVDA.script define the path to a portable NVDA version on your host.
You should have run this portable NVDA once before, in order to avoid welcome screens etc.

These three steps have only to be done once. Maybe you ask a non-blind friend for assistance.

Start the build by using the shortcut SHIFT ALT P which virtually clicks the "Blue Play Button"

After a while of system checking you hear a bounch of messages to tell you about "Source CD has been changed" etc.
Maybe it interfers with currently coming NVDA messages.
But the sence is simply: Restart the build by SHIFT ALT P some seconds after this message is done.

After about 2 minutes you will run into VirtualBox if it is installed.
The ISO %BaseDir%\ISO\multiPE_Win7\multiPE_Win7_S.iso will be available to be burned to CD

Peter

BTW2 @Wonko: I do not understand the actual sence in the link you gave.



#184921 Unable to register at REBOOT.PRO please help!

Posted by pscEx on 16 June 2014 - 06:21 PM in Requests

"Now I also get "forbidden" when I want to enter the download center."
Me too.


Please be a bit patient ...


I assume that EVERY member currently gets this message.
Peter



#184920 PE for blind people

Posted by pscEx on 16 June 2014 - 06:18 PM in Development

But if there is this issue HOW exactly the visually impaired people managed to ever build a project till now? :dubbio:

@our blind members: Please give some answers how the choose control is managed in current projets.

Peter



#184918 PE for blind people

Posted by pscEx on 16 June 2014 - 06:14 PM in Development

Wonko, you are a slave-driver :cheers:

 

But your idea makes so much sence for me, that I'm going to try.

 

Peter




#184915 PE for blind people

Posted by pscEx on 16 June 2014 - 04:57 PM in Development

I would say mission accomplished. :thumbup:

Let me refine: Mission #2 accomplished.

Now to issue #3:

Sometimes inside WinBuilder (or a project) you have to choose a file or directory.

The non-blind user clicks onto the small "folder" button to open the built-in file chooser.

But the blind user does not see that button, and NVDA does not tell him anything about the existence / place of the button.

My brainstorming idea:

Put a text file into the project dir with a content like

[Accessibility]
Source=Q:\CDs Standard\W7_32_DE_ENT_SP1
PortableNVDA=C:\Scratch\NVDA_Port\NVDA2013.3

If that file exists, the project handles the job and makes working with the filechoosers unnecessary.

Any comments / suggestions?

Peter




#184914 Unable to register at REBOOT.PRO please help!

Posted by pscEx on 16 June 2014 - 04:50 PM in Requests

Appearently we currently have some troubles with the server.

 

It has been some time offline today.

 

Now I also get "forbidden" when I want to enter the download center.

 

Please be a bit patient ...

 

Peter




#184887 PE for blind people

Posted by pscEx on 15 June 2014 - 04:14 PM in Development

#3 is the answer. I used D-Speech: http://dimio.altervista.org/eng/

The voice is M$ Mary. It is choosen in the D-Speech app, when the wav is generated.

Undocumented right now: The user can generate his own AudioChooser.wav and overwrite that one in %Target_Sys%

Peter



#184884 PE for blind people

Posted by pscEx on 15 June 2014 - 03:36 PM in Development

Why? :w00t:

 

If all you have to communicate to the user is a single sentence, in this case the message "If you can hear this message, press ENTER within n seconds" (I would have something more for n than just two seconds, 5 seconds "sounds" better to me), you don't need no stinkin' text to speech engine, you need to simply record that sentence and save it as .wav and use it like *any* normal, plain, "windows sound".

 

How do you think PABX messages have worked for years, long before text to speech was avaialble? :unsure:

 

 

:duff:

Wonko

Thanks, Wonko! :clap:

 

I added the single sentence as wav, and it works like a charm.

 

Peter :cheers:




#184881 PE for blind people

Posted by pscEx on 15 June 2014 - 10:59 AM in Development

Thanks again Wonko! :clap:

 

I found it as STRING resource #12707 in shell32.dll.mui

 

Now some time to code getting this string at boot time ... :suda:

 

Peter

 

Now the new ExtractString.exe application does some work when building the project:

[process]
ExtractFileEx,%ScriptFile%,Folder,WatchUnsigned.exe,%Target_Sys%
// The unsigned driver dialog has a caption depending on the source CD language.
// We need the caption for the FindWindow() function
// This piece of code extracts the code from from shell32.dll.mui
Set,%ExtractExe%,%tools%\ExtractString.exe
Set,%resultIni%,%ProjectTemplates%\result.ini
If,Not,EXISTFILE,%ExtractExe%,ExtractFileEx,%ScriptFile%,Folder,ExtractString.exe,%Tools%
ShellExecute,Hide,%ExtractExe%,"#$q%ShellDLL%#$q 12707 #$q%resultIni%#$q Local Caption"
IniRead,%resultIni%,Local,Caption,%DriverSigning%
Set,%DriverSigning%,%DriverSigning%,PERMANENT

Peter




#184868 PE for blind people

Posted by pscEx on 14 June 2014 - 04:59 PM in Development

you need to simply record that sentence and save it as .wav and use it like *any* normal, plain, "windows sound".

Looks like that once again have to thank you, if that works, an "unlimited thanks"

 

Maybe I'm too unexperienced in the audio area (You know that I did intentionally not include audio in multiPE, because my opinion was "the PE is for rescue, not to hear the latest mp3")

 

I'll try the *.wav

 

Peter

 

Tomorrow ... :cheers:




#184864 PE for blind people

Posted by pscEx on 14 June 2014 - 03:32 PM in Development

Wonko the Sane, on 14 Jun 2014 - 4:38 PM, said:snapback.png

An engineer/programmer approach :whistling: would be however to find which files (very likely .exe or .dll or similar) contain those strings and "extract" during the build the corresponding text (that will likely be in the same "resource" in the binary) to make a "language independent" script.

 

BTW: This reply brought me to the intention, to have a look at some special *.mui

 

Thanks again Wonko! :clap:

 

I found it as STRING resource #12707 in shell32.dll.mui

 

Now some time to code getting this string at boot time ... :suda:

 

Peter




#184863 PE for blind people

Posted by pscEx on 14 June 2014 - 03:02 PM in Development

Peter,

I updated my post (cross-posting) have a look at the "WinText" approach (if feasible it would be much matter than adding n translated strings)-

 

:duff:

Wonko 

I also have written a function FindWindowByExe, but it only can detect windows created by an exe or dll.

 

I currently do not know which exe or dll pops the unsigned dialog up, and when it came from a dll, my program would treat all upcoming windows of this dll.

 

Nevertheless I'll have a deeper look into the WinText area.

 

Peter




#184862 PE for blind people

Posted by pscEx on 14 June 2014 - 02:55 PM in Development

An engineer/programmer approach :whistling: would be however to find which files (very likely .exe or .dll or similar) contain those strings and "extract" during the build the corresponding text (that will likely be in the same "resource" in the binary) to make a "language independent" script. 

Correct! :thumbup:

 

But I postponed (or striked through) this idea previously, because I'm not sure where to find the caption.

Maybe it is inside any setup / install dll, maybe it is a ressource e.g. in shell32.dll.mui. So for the first solution I decided to use this somewhat hardcoded way.

 

Peter

 

BTW: This reply brought me to the intention, to have a look at some special *.mui




#184860 PE for blind people

Posted by pscEx on 14 June 2014 - 02:43 PM in Development

After the first issue seems to be solved, I would like to introduce issue #2.

 

I hope that I already solved it in an acceptable manner.

 

Fact:

Audio Drivers usually support output to several devices. Standard is a choice of

  • Speaker
  • Head Phone
  • Digital Audio

In a running system the actual output device is stored in the registry.

 

But in a PE (which on every boot is "new") there is no standard output device defined.

Therefore during the boot the PE chooses one of the output devices, IMO rather randomly.

 

As a result:

When the "wrong" output device is choosen, there is no audio output for NVDA.

 

A non-blind user just can open the audio control panel, click onto the valid output device, and immediatelly hears NVDA speaking.

 

And the blind user? How can he use the audio control panel, when NVDA is not hearable? :frusty:

 

Here a first solution:

 

I added a small app "SwitchAud" which can choose the different audio devices.

 

The blind user can use <Windows-Key> R to open the start program dialog

Then he can type either "SwitchAud zero, one, two" (as number).

When he met the actual device, he hears NVDA.

 

I know that this is only a quick and dirty solution, and can be increased.

 

Currently I am working on an app which in a loop switches between the devices, and asks "When you can hear something, hit Enter within two seconds"

But for that I have to install the MS SAPI into the PE, and that will taker some days ...

 

Let's conclude with the statement:

 

The multiPE project version 75 ( to be published next days) will propably allow blind people to build a Win7PE and boot / use it without visual help.

 

Peter




#184857 PE for blind people

Posted by pscEx on 14 June 2014 - 02:16 PM in Development

Thanks, Wonko!

 

It took a while before I could try, because I have been rather busy in different items.

After a different actual NVDA discussion disappeared, I had some more time and worked on your suggestion :cheers:

 

Following your idea, I wrote a small application which:

  • Waits in a loop for a window with caption ???
  • If it detects that window,
    • Sends a "TAB" key stroke to the window (to move focus to "Yes, Install"
    • Sends a "RETURN" key sroke to the window (to install the driver)

??? is a little problem. It is language depending.

 

Therefore I defined in the WinBuilder script:

// The unsigned driver dialog has a caption depending on the source CD language.
// We need the caption for the FindWindow() function
// The user may add his language code

[de-DE]
Set,%DriverSigning%,"Windows-Sicherheit",PERMANENT

[EN-US]
Set,%DriverSigning%,"Windows Security",PERMANENT

[process]
If,EXISTSECTION,%ScriptFile%,%DistLang%,Begin
  Run,%ScriptFile%,%DistLang%
  ExtractFile,%ScriptFile%,Folder,WatchUnsigned.exe,%Target_Sys%
End

As to be seen, currently only German and English are supported.

I would be glad, to get other language captions here. Please EXACT caption with correct uppercase / lowercase letters!

 

With English and German the solution works like a charm in ISO CD and UFD.

 

Peter




#184854 The NVDA project is not supported anymore by aljo...

Posted by pscEx on 14 June 2014 - 01:09 PM in Projects

Next step is already started. :rofl:

 

In the topic "Can't build ISO' a post disappeared by some :wodoo: . That makes my answer rather ununderstandable.

 

Please tell me and all the other forum's members how you decided from the log, that the source CD is invalid?

 

Please respect QuentinX5's latest reply.

 

If you can explain, I am happy to have some voodoo included in WinBuilder.exe, which detects problems in the source CD :clap:

 

Peter

 

Topic boring for me. Closed. When the originator wants some more help, he may PM me

 

 

Here the disappeared post, rebuilt from my notification:

 

pscEx,

al_jo (http://reboot.pro/user/32393-al-jo/) has just posted a reply to a topic that you have subscribed to titled "Can't build ISO?".

----------------------------------------------------------------------
Again, Mr Mastermind (Peter Schlang) is swambling.
It is 100% clear that that Quentin is using a bad source...
----------------------------------------------------------------------

The topic can be found here: http://reboot.pro/to...view=getnewpost

 

Peter




#184815 Can't build ISO?

Posted by pscEx on 13 June 2014 - 06:33 PM in Support

Please tell me and all the other forum's members how you decided from the log, that the source CD is invalid?

 

Please respect QuentinX5's latest reply.

 

If you can explain, I am happy to have some voodoo included in WinBuilder.exe, which detects problems in the source CD :clap:

 

Peter

 

Topic boring for me. Closed. When the originator wants some more help, he may PM me




#184810 Can't build ISO?

Posted by pscEx on 13 June 2014 - 06:09 PM in Support

The complete log tells me, that you are trying to build an "old" LiveXP project using WinBuilder 083, which is proprietary to the multiPE project.

The package contains WinBuilder 083, a slightly modified clone of the official WinBuilder 082.
Do never use WinBuilder 083 for other projects. It cannot be guaranteed that it works and does not cause any harm.

 

Try to use LiveXP 2012, which (propably) works with WinBuilder 83, or use WinBuilder 082.

Some "revolutiontionary suggestion": Try the multiPe project.

 

BTW: It is not wise, in the first trial to include "everything". Make a choiche of the scripts you need. later you can add scrips to the build.

 

Peter




#184792 Trojan Buzus.aKdo founded by Baidu antivirus

Posted by pscEx on 13 June 2014 - 02:00 PM in Win7PE

Usually by installing a different scanner :cheers:

 

Seriously: There exist so many binaries with so many virus-like patterns, that sometimes scanners report "false positives"

 

Do a check with https://www.virustotal.com/en/, which tries many scanners for the test candidate.

 

IMO a file is suspicious, when more than about 30% of the scanners report a virus.

 

Peter




#184761 alnera.eu & Virus

Posted by pscEx on 12 June 2014 - 09:27 AM in News

I have latest AVAST running under XSP x86.

Browser is latest FireFox.

 

My AVAST does not have concerns.

 

Peter




#184660 PE for blind people

Posted by pscEx on 03 June 2014 - 06:07 PM in Development

Short tutorial how a blind user builds and runs a Win7PE

There is no way for NVDA to recognise the toolbar buttons e.g. Blue Play Triangle.
Now by a slightly modified WinBuilder.exe, there are some hot keys provided.
All hot keys use as trigger SHIFT ALT

  • P meaning Play: Start the build
  • E meaning Edit: Open the Edit area, where you can change the script source code
  • A meaning Abort: Go back to the main project tree, aborting changes
  • S meaning Save: Go back to the main project tree, after saving the changes
  • T meaning Tools: Open the Tools area
  • X meaning Exit: Go back to the main project tree from Tools area

Build

  • Prepare
    • Download multiPE and unzip it into an empty folder. Recommended is a folder in the root of a drive, e.g. D:\multiPE
    • Create a portable version of your screen reader in a separate folder, e.g. D:\multiPE\PortableNVDA
    • Run the portable version once and set the configuration like you want to have it in the PE
      That also avoids appearing of a welcome screen in the PE
  • Configure and build
    • Make sure that your standard text editor is not open. That would cause unpredictable results.
    • In the project GUI, check the box Screen Reader Support
    • In the project tree, navigate to Core > 6 - Core Apps > Accessibility > myNVDA
    • Click Create in the bottom left of the Script GUI window.
    • A text file appears in your standard text editor
    • Define SourceDir with the directory of an extracted Win7 or XP install CD. If the path contains spaces, enclose in quotes
    • Define Entry1 with the path to the portable screen reader copy.
    • Save and exit the editor. You will get a voice message:
      "Due to source CD change WinBuilder is restarted now. Please restart the build. And then restart the build a second time, as requested."
    • Hit SHIFT ALT P. That will emulate the blue Play button. After about 10 seconds, you will hear a voice message:
      "Due to source CD change the source parameters are refreshed.#$xPlease check the choosen indexes in 'Core\1 - Core Basics\ImageIndexEx.script' and restart the build"
    • Hit SHIFT ALT P again. That will do the build and after about 2 minutes you will run into VirtualBox if it is installed.
  • Create Live CD
    • The ISO %BaseDir%\ISO\multiPE_Win7\multiPE_Win7_S.iso is available.
    • Burn it to CD
    • Boot from CD
      After boot time of about 2 minutes you will hear something. Then hit the Return key. That will choose the correct Audio Endpoint Device index.

For a new build after e.g. adding scripts, from now on you only have to hit SHIFT ALT P

BTW: Some scripts, where a file or directory must be defined, have also the Create button in the left bottom, e.g. Apps > Develop > ProcExp
You also should have a look at Tools > Accessibility.ini




#184659 PE for blind people

Posted by pscEx on 03 June 2014 - 06:06 PM in Development

Short explanation of the issue:

 

The PE wich can be used by blind people, must contain:

  • An audio driver working in the current hardware
  • A screen reader like NVDA

Seems to be easy, but there is an issue:

When during boot, the audio driver is installed, sometimes Billy the Door has some concerns, and asks whether this driver should be installed inspite of missing author certification or whatelse.

 

For a non-blind user that is no issue. He sees Billy's popup and clicks on "Yes"

 

Because the screen reader is not installed yet, the blind user does not hear Billy's question, and after a while he thinks that something hangs.

His usual (and logical) reaction is to restart the PE:

Same game again ...

 

To first install the screen reader, and then install the audio driver, would not help.

When the screen reader is started without a valid audio driver accessable, it remains silent. And there is no way for blind users to define the audio driver for the screen reader later.

 

Maybe in this topic we'll find a working solution ...

 

Peter

 

BTW: I mainly see "visual impaired" in posts, rather than "blind". Is it an aggression when I use "blind" ?




#184631 localDriver

Posted by pscEx on 02 June 2014 - 07:47 AM in Project forge

There is a bug wich lets hang localDriver when running under win7.

 

I'm going to fix next days.

 

Peter




#184618 Batch replace text in Unicode .reg Files?

Posted by pscEx on 01 June 2014 - 04:11 PM in Requests

As it often happens with this kind of tools, particularly the most powerful ones, the documentation is scarce, non-existent or too cryptic for any practical use, and obviously (like it happens as an example to say 99% of any Linux originated tool) there are a zillion options that are not supported by corresponding examples.

 

I fully agree!

See my first post here:

After some try and error ...

Peter :cheers:




#184616 Batch replace text in Unicode .reg Files?

Posted by pscEx on 01 June 2014 - 03:34 PM in Requests

A. No. Yes, by cleverly using the support for escape characters. (something that is not explicited in the tool's page, nor readme.txt)

But it is displayed when using the help function ...

  The replacement argument text may include:
      - Standard escape characters ( \\ \a \b \e \f \n \r \t \u???? \x?? )
      - Pattern group matches ( \0 \1 \2 \{10} )

Peter




#184613 Batch replace text in Unicode .reg Files?

Posted by pscEx on 01 June 2014 - 02:59 PM in Requests

Hi Peter. Thanks for the link. The following program is also from the same author - Simple Search and Replace (SSR).

I tried SSR prior to Wonko posting a working search and replace string for gsar - it worked well. I do however really like gsar due to it's very small size and portability. And it was handy - and redistributable.

Regards,

Misty

My reason to use rxrepl was, that is was the only app I found to do:

 

Replace in the line:

<entry key="!Version">????.??.??</entry>

(? can be any actually unknown number) by the actual version, e.g. 2014.06.01

 

The command line is:

rxrepl -I rxrepltest.xml !Version\x22\x3e....\...\... -r !Version\x22\x3e2014.06.01

BTW: Wonko's last FAQ is answered wrong. AFAIK rxrepl can replace every multi byte hexcode by a different multibyte hexcode, even with different lengths. Of coure there is no pointer update or similar in cpmiled and linked files (see the hex-escapes in the above command line).

 

Peter




#184609 Batch replace text in Unicode .reg Files?

Posted by pscEx on 01 June 2014 - 01:09 PM in Requests

I have been some days away, so late answer.

 

For my 2013 projects / plugins delivery I use rxrepl

 

After some try and error I'm very satisfied with the functionality.

 

Peter




#184554 live repair disk for blind people

Posted by pscEx on 28 May 2014 - 07:25 PM in Support

Hi friends,

 

I am leaving now and go for some days vacation.

I am back on Monday

 

Peter




#184552 live repair disk for blind people

Posted by pscEx on 28 May 2014 - 06:59 PM in Support

Unfortunatelly I do not have influence on the forum's software.

 

But back to the initial issue: Please try this:

 

Open your notepad comment text

Select all by CONTROL A

Copy by CONTROL C

Create a new topic (I will delete later) and paste your text by CONTROL V

 

Peter




#184549 live repair disk for blind people

Posted by pscEx on 28 May 2014 - 06:27 PM in Support

Just a test:

Copy and Paste some code from notepad file "test.txt" when NVDA is running.

HERE IT COMES:

Hello World

SUCCESS

 

The issue was:

 

When I selected the text by hitting the "Shift" "End" keys, the cursor did not move, and the text was not selected.

You as blind person cannot recognise that.

I saw the result and therefore selected the text by moving the cursor to the end, using the "right" key.

 

Copied as usual with control c and paste with control v.

 

Peter




#184548 live repair disk for blind people

Posted by pscEx on 28 May 2014 - 06:16 PM in Support

Sadly the editors of some forum software is quite inaccessible with the screenreaders.

 

That seems to be a "feature" of NVDA  or screan readers generally, because they catch some key strokes.

 

I have similar problem when I am in my development IDE and NVDA is running :frusty:

 

I am sure we find a way ...

 

Peter :cheers:




#184546 live repair disk for blind people

Posted by pscEx on 28 May 2014 - 06:03 PM in Support

I do not have an idea what the problems are when posting contents of another editor.

 

I suggest:

Either: Save your text into a plain notepad file and copy here

Or: Attach the document.

Or: Paste into "Quote" or "Code"

 

Peter




#184543 live repair disk for blind people

Posted by pscEx on 28 May 2014 - 03:26 PM in Support

 

Because hostaudio script display dialog window which prompts me to select The driver, it display founded broadcomm extreme network cart.

And because blind user can not interact with dialog when NVDA is not speaking, user must run NVDA by pressing WIndows start menu, pressing p, by pressing a

In my tests I recognised this issue.

 

Since two hours I am trying to suppress the confirmation dialog.

 

I hope that I will have success.

 

 

Would be possible to only install USB audio driver and VIrtualbox related sound driver and not tryiing to search The host system?

To install VirtualBox audio would not help. The audio drivers must match the hardware, and very truelly a real PC has not the VirtualBox sound card integrated.

 

 

Try to force MMULTIPE so it would play welcome startup sound,and shortcut for starting NVDA would be assigned to The shortcut CTRL+ALT+N.

Some days / weeks(?) research to implement, but I will try.

The issue is:

When NVDA starts before the audio system is working, NVDA will not be heareable, even after the audio system works.

 

 

And Win 7 source must be SP0 or SP1 X86 source?

Must be x86. With the CDs I tested there is no dependency from SP0 or SP1. But I do not have CZ. Maybe you can upload anywhere?

 

A lot to do.

 

Let's go on!

 

Peter




#184539 live repair disk for blind people

Posted by pscEx on 28 May 2014 - 01:54 PM in Support

If hostaudio find Soundmax integrated digital audio driver on The host system, will be this device automatically available by Windows sound service and by NVDA?

I have testet hostaudio and it is very good tool, but i was able to use Soundmax only when i have manually confirmed, that thissound driver can be used.

Number one: Yes, but only in PE's where the windows directory is writable, and the driver can be installed.

That is the case with PE on USB stick. With PE on ISO it is not possible.

 

I wrote a tool localDriver which grabs the host's driver and creates a multiPE script to add the driver to the PE build.

You can downolad it at http://reboot.pro/fi...81-localdriver/.

It should be possible to create a multiPE script for Soundmax with localDriver and add it to the multiPE project.

 

Number two: That question is asked by Bill Gates and cannot be influenced by multiPE / hostAudio.

 

Peter




#184538 localDriver

Posted by pscEx on 28 May 2014 - 01:34 PM in Project forge

Uploaded new version

What's New in Version 2.0.2
  • Fixed bug which caused "Unknown Software Error" when running in a path with space in name.

Peter




#184530 Win8pese wireless aerthos

Posted by pscEx on 28 May 2014 - 08:28 AM in Win8PE

And I have a cellular phone that does not work.

 

Help!

 

Peter :cheers:




#184507 live repair disk for blind people

Posted by pscEx on 26 May 2014 - 09:47 PM in Support

 

Why hostaud must be used?

Is it because NVDA autostart depend on hostaud.exe? Or does it somethink with Windows sound service?

hostaudio is not a MUST, it is a goodie.

 

Depending on the computer's hardware, for audio support, besides the standard hdaudio drivers, local audio drivers must be installed.

 

Therfore theoretically the user must add an audio driver for his individual sound card.

 

The hostDriver functionality of multiPE looks into the actual host, where the PE is started, (optionally) for audio, video and network drivers, and installs them during PE boot.

 

So in most cases, you do not need to add special audio, video, nic drivers to your PE build.

 

It would not make sence to ask the user for the driver, because hostAud should find the only one which is valid for the host PC.

And you are right, that the hostDriver functionality is not necessary in VirtualBox or similar.

 

The NVDA autostart is historic and not longer performed. I have to fix the script in the next upload (hopefully I remember ...)

 

I know, that it requires much patience from developers in some cases, apsecially while reading my bad English. May be, that in some times, i can make somebody engry or sad, but believe me that my goal is only to bring 100 % legal and functioning live projects to all visually impaired users and administrators who live in this world.

Be sure that I always try to find solutions for visually impaired people and never will refuse a request. But sometimes some things exceed my programmer's experience and knowledge, and google is not always my friend.

 

Peter




#184490 Error with PeNetwork Version[40]

Posted by pscEx on 26 May 2014 - 08:20 AM in Win7PE

There is something scrambled in your project.

It looks like that the script contains PeNetwork files from an older version 5.7.x or 5.8.0, but wants to add files from version 5.8.1

 

But probably you can fix it quick and dirty by yourself.

 

Look in the section [EncodedFolders]

There is something like:

[EncodedFolders]
Inifile_HS
PeNetworkLST
PeNetwork0572
MoreLng0572
configdot3svc
StartANetwork_x86
StartANetwork_x64
Licence

Search for

ExtractAllFiles,%ScriptFile%,PeNetwork0581,%ProjectTemp%\PeNetwork0581

and replace the 0581 by the actual digits, in this case 0572

 

Analogue do for lines containing

Set,%PENMArc%,PENetwork_x??_v0581.7z
ExtractFile,%ScriptFile%,MoreLng0581

Peter




#184478 live repair disk for blind people

Posted by pscEx on 25 May 2014 - 04:11 PM in Support

Would be possible to make project, which would build live system by using only WAIK or Windows assessment and deploiment kit?

...

Does WAIK or Windows assesment and deploiment kit contain Windows sound service?

...

Must be really directx used to run NVDA if live project is based on WAIK or windows assessment and deployment kit?

"Sound" has been my first worry, too.

 

My projects multiPE XP and Win7 track for WinBulder 82 as well as win7PE for Winbuilder 201x do not need directX.

 

I will check and report.

 

Peter




#184477 live repair disk for blind people

Posted by pscEx on 25 May 2014 - 04:04 PM in Support

Done. :clap:

 

Version 74

 

Peter




#184476 live repair disk for blind people

Posted by pscEx on 25 May 2014 - 03:40 PM in Support

Dear Peter,

I Am getting the following bug when i try to run MuLTIPE and if XP have been selected as source.

V:\multi Test\Projects\Tools\nativeEx\7z.exe  dialog  V:\multi Test\Projects\Tools\nativeEx\7z.exe

System can not find The specified drive.

So all external .exe tools, which Yours scripts want to call can not be executed, so i have kill winbuilder.exe process from task manager.

Thank You very much for The repair.

Sorry, a local path slipped into the upload.

 

I will change as soon as possible.

 

Peter




#184438 live repair disk for blind people

Posted by pscEx on 22 May 2014 - 03:42 PM in Support

Sorry I am writig from mobil. So maybe some mistakes
NVDA 2014.1 errors when startimg from xp pe

Currently latest runnong version is 2013.3

Peter



#184368 multiPE

Posted by pscEx on 16 May 2014 - 01:47 PM in Projects

Version 73 uploaded.

Small enhancement:

 

What's New in Version 73
  • When eSpeak is not installed on the host, use Windows SAPI from multiPE internal vbscript to speak message box texts.

Peter




#184366 Does the CurrentVersion Registry Key Exist in Non-English Windows?

Posted by pscEx on 16 May 2014 - 01:19 PM in Requests

@ misty

 

As far as I remember all registry keys in XP are in English, as they are in Win7 (confirmed).  But I'll verify this and let you know ASAP.

Confirm for XP SP3 x86 German.

 

Peter

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion]
"SubVersionNumber"=""
"CurrentBuild"="1.511.1 () (Obsolete data - do not use)"
"InstallDate"=dword:4a717a98
"ProductName"="Microsoft Windows XP"
"RegDone"=""
"RegisteredOrganization"=""
"RegisteredOwner"="Peter Schlang"
"SoftwareType"="SYSTEM"
"CurrentVersion"="5.1"
"CurrentBuildNumber"="2600"
"BuildLab"="2600.xpsp_sp3_qfe.130704-0421"
"CurrentType"="Multiprocessor Free"
"CSDVersion"="Service Pack 3"
"SystemRoot"="C:\\WINDOWS"
"SourcePath"="D:\\I386"
"PathName"="C:\\WINDOWS"
"ProductId"="BlaBla"
"DigitalProductId"=hex:BlaBla
"LicenseInfo"=hex:BlaBla
"HWID"="Nicht verwendet"




#184342 Enhanced multiPE project for blind users

Posted by pscEx on 15 May 2014 - 04:40 PM in News

See here

 

Peter




#184341 multiPE

Posted by pscEx on 15 May 2014 - 04:27 PM in Projects

Version 72 published.

 

What's New in Version 72

  • Added NVDA script to Win7 track
  • Enhanced support for NVDA users
  • Redesigned WBManager functionality

Some technical details:

 

NVDA script is added to the build only by checking "Add NVDA Support" in the project GUI. All necessary scripts (depending on XP / Win7 track) are added to the build automatically.

The NVDA to be added to the build, must be a portable version (generated from the installed NVDA).

In multiPE\Core\Core Apps\Accessibility\myNVDA there must be defined, where to find NVDA portable in the host's file system.

 

Classic WinBuilder (Delphi coded) has Message boxes wich only show the buttons to NVDA. Test is not recognised.

By checking "Audio for blind Users" in the project GUI, the user hears the text of the message box, while it is displayed.

Unfortunatelly the NVDA build-in eSpeak is not accessable by multiPE.

Therefore this feature needs eSpeak installed.

When eSpeak is not installed, multiPE generates a voice output by using Windows SAPI.

 

Until now, NVDA does not see any (delphi feature!) labels in the different script GUIs.

Now by a slightly modified WinBuilder.exe, the labels are recognised by NVDA.

 

There is no way for NVDA to recognise the toolbar buttons e.g. Blue Play Triangle.

Now by a slightly modified WinBuilder.exe, there are some hot keys provided.

All hot keys use <Shift> <Alt> as trigger.

  • P meaning Play: Start the build
  • E meaning Edit: Open the Edit area, where you can change the script source code
  • A meaning Abort: Go back to the main project tree, aborting changes
  • S meaning Save: Go back to the main project tree, after saving the changes
  • T meaning Tools: Open the Tools area
  • X meaning Exit: Go back to the main project tree from Tools area

Peter

 

Download page




#184287 Questions about USB Booting on UEFI systems

Posted by pscEx on 13 May 2014 - 01:56 PM in Boot from USB / Boot anywhere

P.s. If I follow all of Wonko's links (+ links to links to links, etc) how many years older will I be :P

:clap:

Peter :cheers:




#184259 Defrag VHD using WinContig

Posted by pscEx on 11 May 2014 - 01:25 PM in Community forum

Maybe the partition with win2003.vhd has not enough free space to create a contig file of the candidate :dubbio:

 

Peter




#184201 Detect OS version 32/64bit in script

Posted by pscEx on 08 May 2014 - 03:58 PM in Support

Just a remark:

 

I have the feeling that you are searching in the wrong direction.

 

As far as I understand, you want to start by shortcut either an x86 or x64 application in the running PE.

 

Why the OS of the PE-building program determines whether x86 or x64 is started? :dubbio:

 

That should depend on the architecture of the generated PE! :whistling:

 

Peter




#184200 Detect OS version 32/64bit in script

Posted by pscEx on 08 May 2014 - 03:24 PM in Support

So i change the shortcut line to:
if,true,%WOW64%,Add_Shortcut,StartMenu,Security\%ProgramTitle%,%PE_Programs%\%ProgramFolder%\%ProgramEXE64%,%ProgramTitle64%,else,Add_Shortcut,StartMenu,Security\%ProgramTitle%,%PE_Programs%\%ProgramFolder%\%ProgramEXE%,%ProgramTitle32%

Would that work?

 

Syntax should be:

If,%Wow64%,EQUAL,True,Add_Shortcut,StartMenu,Security\%ProgramTitle%,%PE_Programs%\%ProgramFolder%%ProgramEXE64%,%ProgramTitle64%
Else,Add_Shortcut,StartMenu,Security\%ProgramTitle%,%PE_Programs%%ProgramFolder%\%ProgramEXE%,%ProgramTitle32% 

Take care of the new line instead comma before else.

IMO there is a backslash missing in the first line behind %ProgramFolder%

And in the second line behind %PE_Programs%

I do not know how the shortcut is generated in your project, but distinguishing between x86 and x64 should work.

 

Peter




#184198 Detect OS version 32/64bit in script

Posted by pscEx on 08 May 2014 - 02:25 PM in Support

I'm not sure whether you mean the architecture of your host OS, or the architecture of the source CD.

WinBuilder variable %Wow64% is True or False, depending on the architecture of your host.

 

Peter




#184169 Wonko back into the asylum?

Posted by pscEx on 07 May 2014 - 10:37 AM in News

Has gate been open for a while?

 

Wonko.gif

 

Peter :dubbio:

 

 




#184141 M$ XP mystery

Posted by pscEx on 04 May 2014 - 06:10 PM in News

Hi all,

 

I made a strange and (for me) unexplainable experience I want to share with the community.

 

It is due to my Ice-Aged standard OS XP, which is still running, and the host for all my development including WinBuilder 2013 / 2014

 

As known, M$ stopped XP support anywhen in April 2014.

 

But today I got a new UPDATE, which told me that it will be installed on shutdown.

 

I clicked restart.

 

Something happened, some log messages were shown, but no shutdown / reboot after all.

 

After about one hour I hard rebooted.

 

Now the surprises in the coming up XP:

 

#1:

Previously TaskManager showed me a list of processes, which did not fit onto one screen height. So the scroll bar was visible.

Now TaskManager has a list which fits into one screen height, and has about 5 lines free.

#2:

Previously right clicking on an item in Explorer (to get context menu) needed sometimes several seconds until result.

Now: Right-click and see the context menu

 

Does somebody have similar experience?

 

IMHO: As long as M$ supported XP, there have been several spies in the system, which reported WHAT? to Billy the Door.

 

Peter

 

BTW: Until now I have no troubles with the changed OS.




#184018 Where to Find MsDos 6.22?

Posted by pscEx on 30 April 2014 - 09:23 AM in FreeDos and Dos

:cheers:

 

Peter




#184000 Where to Find MsDos 6.22?

Posted by pscEx on 29 April 2014 - 06:39 PM in FreeDos and Dos

It's got the correct hash so it is the official file and it's on a safe site.

First view: The hash you are trusting, is published by the author who offerred the MSDOS622 copy.

How can you be sure that the hash equals the hash of the M$ files?

 

Did you compare with the hash of the original M$ publication?

 

Second view:

 

If you can find a file named en_msdos622.exe with an SHA1 of d01aa47a5d85908185f8987e972afc66dc92a735

 

then you're good to go.

 

Maybe in case of correct hash, your URL points to a valid (M$) file :cheers:.

 

Peter




#183998 Where to Find MsDos 6.22?

Posted by pscEx on 29 April 2014 - 06:17 PM in FreeDos and Dos

Here you go, this one is good:

 

http://www.google.co...rive.google.com

Betrand asked for '(semi) official'.  :dubbio: 

 

Peter




#183995 Where to Find MsDos 6.22?

Posted by pscEx on 29 April 2014 - 05:38 PM in FreeDos and Dos

Maybe someone can find the URL, where my backup copies are located ... :dubbio:

Unfortunatelly there is no French backup...

 

Peter

 

msdos622.jpg msdos622us.jpg




#183974 LiveXP project with 70 app scripts included

Posted by pscEx on 29 April 2014 - 11:03 AM in Projects

Try multiPE.

 

IMO it is the only XP based PE offerring NVDA.

 

Peter




#183242 change the basic folder

Posted by pscEx on 09 April 2014 - 08:54 AM in Support

The basic folder is allways the folder where you copy winbuilder.exe in.

 

BTW: I moved the topic from tutorials to support

 

Peter




#183175 Winbuilder 082 DirCopy - Unknown error

Posted by pscEx on 04 April 2014 - 03:28 PM in Support

The $RECYCLE.BIN and System Volume Information are also copied though, so I suspect that this might cause errors when they are copied back to the USB drive after it's been repartitioned and formatted.

Why not doing some deletes after copy?

 

Peter :smiling9:




#183173 Accessibility

Posted by pscEx on 04 April 2014 - 03:23 PM in Win7PE

In order to explain why JoshW thanks whom, here a copy of the latest PM coversation:

 

Sorry Josh!

 

It took a while because I have been really full engaged with the new Winbuilder.

 

But I found something:

 

http://msdn.microsof...2(v=vs.85).aspx

http://forums.mydigi...s)-via-reg-file

 

Following that it should be sufficient to add an registry entry

HKEY_CURRENT_USER\Control Panel\Accessibility\StickyKeys, "Flags"="511"

 

I tested in WinBuilder 2013 win7pe and it works fine.

 

When you use still WinBuilder 82, you can add the command 

RegWrite,HKCU,0x2,"Control Panel\Accessibility\StickyKeys",Flags,511

at a suited place.

 

Because I do not know which project you are using, i cannot recommend a script where to add this.

In every case you must take care that the hive is open by RegHiveLoad.

 

Peter




#183168 Winbuilder 082 DirCopy - Unknown error

Posted by pscEx on 04 April 2014 - 01:37 PM in Support

Not sure whether is works.

For me, WinBuilder 82 is dead since a while.

So I do not have it anymore to test.

 

Try: DirMake,"%BaseDir%\Projects\Cache\usb.contents"

FileCopy,"D:\*.*","%BaseDir%\Projects\Cache\usb.contents"

 

Peter




#182934 Unapproved posts

Posted by pscEx on 21 March 2014 - 07:22 PM in Site feedback

It more and more happens that posts of new members are "unapproved" and invisible for standard forum members.

 

Intended or a forum's software bug?

 

Peter

 




#182897 Bug Reports, Requests, HowTo's about Tiny PXE Server

Posted by pscEx on 19 March 2014 - 05:35 PM in Tiny PXE Server

i can't see my post ,why?

 

Your post has been "unapproved".

I looked into your profile and saw no flags like "spammer" or "banned" etc.

And the content is also not "forbidden".

So for me there is no reason to hide your posts.

 

I approved it (made visible for non-admin users)

 

Peter




#182853 Request: Memorable quotes

Posted by pscEx on 16 March 2014 - 05:39 PM in Tutorials

Neither HBCD or any other WinPE boot disc are designed as an alternative operating system. Their purpose is rescue and recovery ...

http://reboot.pro/to...ns/#entry182820

 

Peter




#182852 Programmer logic

Posted by pscEx on 16 March 2014 - 02:40 PM in Community forum

A programmer is asked by his wife:

"Please go to the supermarket and buy a package of milk. If they have eggs, bring ten."

 

The programmer came back with 10 packages of milk.

 

Wife: "Why did you get 10 packages of milk?"

Programmer: "Because they have eggs!"

 

 




#182843 Defraggler for Win8PE, LiveXP and Win7PE (Winbuilder 82)

Posted by pscEx on 16 March 2014 - 09:26 AM in App Scripts

Piriform granted me to distribute their apps with Win7PE.

 

Just an e-mail to ask for ... :)

 

Peter




#182835 Defraggler for Win8PE, LiveXP and Win7PE (Winbuilder 82)

Posted by pscEx on 15 March 2014 - 06:02 PM in App Scripts

See http://reboot.pro/to...82/#entry182832

 

Peter




#182832 Recuva for Win8PE, LiveXP and Win7PE (Winbuilder 82)

Posted by pscEx on 15 March 2014 - 01:53 PM in App Scripts

What about this?

 

 

3. PRODUCT LICENSE

In consideration of your agreeing to abide by the terms of this License and subject to your compliance with the terms of this License, Piriform grants you a non-exclusive, non-transferable license to use the Product for the following purposes and in the following manner:

- You may NOT ...

- You may NOT repackage, translate, adapt, vary, modify, alter, create derivative works based upon, or integrate any other computer programs with, the Product in whole or in part.

- You may NOT  ...

 

Peter




#182821 1920x1200 missing from screen resolutions?

Posted by pscEx on 14 March 2014 - 03:49 PM in Hiren's Boot CD

Neither HBCD or any other WinPE boot disc are designed as an alternative operating system. Their purpose is rescue and recovery ...

:1st:

 

Peter




#182816 Winbuilder 2015 HowTo create own plugins

Posted by pscEx on 14 March 2014 - 11:29 AM in Development

0. Prerequisites

  • $BaseDir$ is the directory where WinBuilder is installed
  • Paths are relative to $BaseDir$
  • <Key> means the actual value of "Key"
  • Always keep in mind that path and file names are case sensitive when the project is built in an OS other than Windows.
  • In this tutorial paths are written with the Windows backslash separator. When you work in a different host OS, then maybe the separator is a slash
  • "INSTALL" means the INSTALL command in the running WinBuilder CLI
  • Just a reminder: Empty keys have the format <entry key="KeyName"/>

1. Preparation

  • Be sure to have your personal registration key in $BaseDir$, e.g. "thatsme.wbc".
    Some developers already have it. Seriously developing members can get it on request (PM to pscEx or Nuno Brito).
  • Download the plugin template to $BaseDir$\downloads
  • Choose an (3 digit numerical) ID and a name for your plugin
  • Rename the Template to <ID>-<Name>.zip
  • Create a new folder downloads\<ID>-<Name>
  • Unzip the contents of <ID>-<Name>.zip into <ID>-<Name>

2. General customization

  • Edit $BaseDir$\downloads\<ID>-<Name>\settings.xml
  • Change the first part (up to the first blank line) according your project names etc.

3. Add plugin application

 

Decide for one of three possible methods:

  • Attach the application to the plugin.
    The user can INSTALL the plugin and has nothing more to to. The plugin is ready to be added to the PE build.
    This method is recommended exclusivelly for own applications.
    Use step 3.1
  • Prepare to download the application and store locally during INSTALL. 
    The user can INSTALL the plugin and has nothing more to to. The plugin is ready to be added to the PE build.
    This method is recommended for applications which can be downloaded and extracted easily by 7-zip (WinBuilder internal extractor)
    Use step 3.2
  • Applications not covered by 3.1 and 3.2.
    Use step 3.3

3.1 Provide the plugin application locally

 

This method uses a zipped image of the application which during build is unzipped into the wim-boot or bootdisk directory.

  • Edit $BaseDir$\downloads\<ID>-<Name>\settings.xml
  • Define <entry key="InstallFromLocal">False</entry>
  • Define <entry key="IsAttached">True</entry>
  • Save <ID>-<Name>\settings.xml
  • Create an empty plugin_APP.zip file in $BaseDir$\downloads\<ID>-<Name> folder
  • Zip the contents of your plugin application directory into this zip.

3.2 Download the plugin during INSTALL

  • Edit $BaseDir$\downloads\<ID>-<Name>\settings.xml
  • Define <entry key="InstallFromLocal">True</entry>
  • Define: <entry key="DownloadURL">http://app.deliverer.com\myapp.zip</entry> with your actual link
  • Define <DoExtract>
    • $Default

    • True

    • False

$Default: Extract:

  • *.paf.exe
  • *.7z
  • *.zip

All other files types are copied.
 

True: Force extract, independent from file type. This can be done e.g. with install *.exe files.

False: Do not extract, independent from file type

 

This method causes a download during INSTALL, and copying / extracting the app files into <LocalFolder>.

 

Remark: Usually *.paf.exe files can be extracted. But there is a bug in the used SevenZipBindings, which prohibits some files to be extracted correctly.

Maybe also install *.exe files cannot be extracted into an usable application.

In this case set <DoExtract> = False

 

3.3 Make the user responsible to provide the plugin application

  • Edit $BaseDir$\downloads\<ID>-<Name>\settings.xml
  • Define <entry key="InstallFromLocal">False</entry>
  • Define: <entry key="DownloadURL"/>
  • Define a install message for the user:
    Edit $BaseDir$\downloads\<ID>-<Name>\Readme.txt and uncomment the message you want to show, or add your own message.
    In this case during INSTALL the user will get a log message like

 

2014/03/26 15:26:09 [INFO] Before you can add the PiriformClamWinPortable plugin in your project, you have to install it into V:\WB2_A\WB2\winbuilder\run\lib\plugins\AntiVir\PiriformClamWinPortable.
2014/03/26 15:26:09 [INFO] Then run it once in order to do some initialisations / updates, etc.

and has to act accordingly.

 

Sorry, there is no way that you perform that user's job.

 

4 Advanced

4.1 Shortcuts

 

Shortcuts are also defined in $BaseDir$\downloads\<ID>-<Name>\settings.xml.

 

By default, there is no shortcut on the desktop, and a shortcut with default values in StartMenu\<!Category>.

When you agree to this behaviour, you usually can continue.

There is one exception: When the application executable is different from <!Name>.exe, you must replace $Default by the real exe name in <entry key="ShortcutTarget">$Default</entry>.

 

All other shortcut definitions may be changed optionally, according your preferences.

 

4.2 RunFromRAM

 

There is an entry <entry key="RunFromRAM"> in $BaseDir$\downloads\<ID>-<Name>\settings.xml.

It defines where the applicaton directory is placed

  • True: $BaseDir$\output\wim-boot: Is added to the PE's boot.wim
  • False: $BaseDir$\output\bootdisk: Is added to the ISO body

That is valid for all three methods 3.1, 3.2 and 3.3.

When there are files to be placed independent of RunFromRAM, zip them into:

  • plugin_RAM.zip: Place into $BaseDir$\output\wim-boot.
  • plugin_CD.zip: $BaseDir$\output\bootdisk.

Take care, that in this case differently from 3.1 the zip file must contain the complete path inside wim-boot / bootdisk.

Example: Windows\inf\mydriver.inf

 

4.3 main.bsh

 

There is a file $BaseDir$\downloads\<ID>-<Name>\main.bsh.

It defines actions of the plugin during INSTALL and during BUILD.

Usually it can be used unchanged. But sometimes you want to have some additional actions when the plugin is added to the PE source.

You can see comments in $BaseDir$\downloads\<ID>-<Name>\main.bsh informing you about the possibilities.

 

5 Finalise

  • IMPORTANT: Close open editors with $BaseDir$\downloads\<ID>-<Name> files and save then on close.
  • IMPORTANT: Copy the contents of the $BaseDir$\downloads\cache\settings-<ID>.xml to $BaseDir$\downloads\<ID>-<Name>\settings.xml (overwrite!)
  • IMPORTANT: Zip the contents of the $BaseDir$\downloads\<ID>-<Name> directory into $BaseDir$\downloads\<ID>-<Name>.zip
  • Upload your plugin to the reboot.pro download center.

6 Examples

  • Download examples: http://winbuilder.ex...wCollection.zip
  • Unzip into the $BaseDir$\downloads directory and rename as if you would create your own plugin (See above).
    - most of the work is already done in the examples.
  • INSTALL the plugin.



#182684 How to have program Files (x86) in 64 bits build ?

Posted by pscEx on 08 March 2014 - 05:04 PM in Win8PE

Allow me to first ask the standard question:

Why do you want to build a x64 PE?

  • Usable memory bigger 2 gigabyte? (I do not know any project where this is needed)
  • Because you do not have a x86 source?
  • Why else ???

To your question itself:

**** In WinBuilder generally:

Where the added applications are placed, is defined by the WinBuilder app script.

Inside the script there must be a "procedure how to copy me into the PE build". This procedure should copy to either "Program Files" or "Program Files (x86)", depending on the build environment.

 

BTW: In the app script there should be also a decision where to write into registry. There should be some entry with "WOW6432Node" or perhaps something similar.

 

**** When the project or the app script neglects the WinBuilder standard rules, I cannot help here.

 

Peter




#182621 Copy via command promt

Posted by pscEx on 06 March 2014 - 07:24 PM in Tutorials

Imo in Windows command line a context menu is not provided.

And there is also no way to bring the source directory into the clipboard for copy.

Peter



#182612 Copy via command promt

Posted by pscEx on 06 March 2014 - 05:09 PM in Tutorials

When you mean the Windows command prompt, it's easy:

 

xcopy "<sourceDirectory>" "<targetParentDirectory>\<targetDirectoryName>" /e /y /i

(Quotes only necessary when spaces in the path)

 

Example:

xcopy "C:\Dokumente und Einstellungen\Peter\Desktop\WIMs\wim-boot" V:\WB2_A\WB2\winbuilder\run\output\wim-boot /e /y /i

 

I do not understand what you mean with "paste by right click by cursor"

 

Peter




#182428 Win7PE on USB Flash Drive

Posted by pscEx on 26 February 2014 - 07:00 PM in Win7PE

Hi, I'me new here, I searched for an answer and I didn't find (problably there is, but I wasn't able to catch it sorry).

 

I used winbuilder_2013.09.01 to create Win7 live CD, it was my first time using this program and it's absolutely amazing. It did everything and I've got a CD Live that works perfectly.

 

But I need to use it on a laptop without optical disc reader, so I have to make a usb drive version of Win7 live.

I read the forum, but I still have no clue about how to do it.

Thank you in advance.

First of all: Welcome in our community!

 

Sorry that I have overseen your question!

 

I got to know the post by dummyano's answer.

 

WinBuilder builds exclusivelly an ISO, because this can be burned on "all" OSs, not only on Windows. Generating a bootable USB pen, is different on Windows, Linux, Mac, etc ...

 

Under Windows it is rather easy to build a booting flash drive using RmPrepUSB and Grub4DOS. In my multiPE project I use this method.

 

Tomorrow I'll post a (hopefully working) description how to create such a flash drive with your Win7PE ISO.

 

Peter




#182394 error installing plugins, please help

Posted by pscEx on 24 February 2014 - 08:53 AM in Support

Looks like the new plugins are not compatible with the old Win7pe version you use.

Try in Winbuilder window:
uninstall win7pe
install win7pe

Peter



#182257 Windows boot question

Posted by pscEx on 13 February 2014 - 11:34 AM in Boot from USB / Boot anywhere

Thanks, ilko!

 

I got it to run with your explanations. :clap:

 

Peter




#182247 Windows boot question

Posted by pscEx on 12 February 2014 - 05:37 PM in Boot from USB / Boot anywhere

Let me first tell something about history:

 

I still(!) use XP x86 as the primary platform for my developments. I do not like, when e.g. in Win7 Billy the Door always knows better than me, what I want to do.

 

For some test reasons I had to install XP x64 in a different partition. That brought no issue, in the boot menu I could do my choice.

 

For some other test reasons I had to install Win7. After that, in the boot menu, I had the choice between "previous" XP x86 and Win7.

That has been also no problem, because I usually wanted to boot XP x86, not to use x64.

 

Now, in the WinBuilder development, I wanted to check some x64 issues, and tried to reanimate the sleeping XP x64 partition.

 

I used EasyBcd 2.2 to add XP x64 to the boot menu. Result: BSOD

Then I added XP x64 manally to boot.ini. Result: othing new happened.

After some "fishing in the dark", which I cannot exactly remember (sorry !!!) , suddenly my PC booted into XP x64 !!!

 

But it was not longer possible to boot into XP x86.

 

Checking the file system, I found in my primary boot disk a new file ebcd.001 with the contents:

; This boot.ini was automatically generated by NeoSmart Technologies' BootGrabber.exe
; Use EasyBCD from http://neosmart.net/dl.php?id=1 to manage your bootloader

[boot loader]
timeout=15
default=multi(0)disk(0)rdisk(1)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="Windows XP on H:\" /fastdetect

And now my current procdere:

When I want to boot into XP x64, I let ebcd.001 untouched.

When I want to boot into XP x86, I rename this file to _ebcd.001.

 

Is there any way to use BCD or an editor to bring the x86 / x64 option into the boot menu?

 

For experts, here some contents:

BCD:

Spoiler

C:\Boot.ini:

Spoiler

 

Peter