Thanks both for the comments
I added a script which runs as very first in a build. It checks, whether for the actual configuration required applications / drivers are present. If not, it gives a message and exits the build.
A suggestion to improve the pop up message.
add following text.
* Options include
- Selecting "No Emulation" if you dont want to test Final Output on Virtual Machine
- Selecting "No Emulation" and Choosing option to Burn ISO to CD/DVD, etc..
- Selecting "VirtualBox" as testing virtual Machine. Default Option.
*Download and install Freeware "VirtualBox" from [ https://www.virtualbox.org/
- Selecting "Vmware Workstation" as testing Virtual Machine if it is already installed.
*Download / Buy / Install Vmware Workstation [ https://www.vmware.com/
- Rerun Winbuilder Project
GREAT! I see that by default you have "Boot Image" to "no Image". That way first time users will go straight to creating an ISO. Specially if they dont know what an Imdisk is.
As above. Suggest adding:
* ImDisk is a Virtual Disk Driver
- It can create virtual hard disk, floppy or CD/DVD drives using image files or system memory
- It helps to easily create a RAM Boot Image.
- Download/Install Freeware ImDisk fromhttp://www.ltr-data....de.html/#ImDisk
- Rerun Winbuilder Project once installed
- Change Options in PEFactory
Success test for WinBuilder082.exe, XP Build, new SystemCheck Script, and Ram Bootable build with multipe.winbuilder.net/Projects
as WinBuilder Download Server
Since Vmware launching the Virtual test might take some time to come up. As is does for me. It seems if nothing is happening. But I know better.
Suggestion. When a person chooses PEFactory-Emulation-VMware/VirtualBox . Can you make it show a popup that tells the user:
It might seem like nothing is happening, but
Virtual Machine is being launched.
Last post with unsusseful boot was from : http://reboot.pro/fi...ile/61-multipe/
Further mounted RAM drive: That happens, when the build is stopped with an mounted RAM drive. I'll try to unmount in such case.
Both fixes available tomorrow.
Drive Z: RAM_XP.img still mounted even after closing Virtual Vmware Test, closing Winbuilder. When does the unmounting start. Is it when you close Winbuilder.
I cannot reproduce your txtsetup.sif issue. Please give me details about your host OS etc.
Using the Scripts frommultipe.winbuilder.net/Projects
The Error txtsetup.sif issue is not showing up.
Tested Xp Only.