9 replies to this topic

[cocofynspm]

How do you add WMI support to LiveXP builds? I have the 25CoreWMI.script script in Basic>Shells>Core>1System, but I can't find any reference to it in the WinBuilder GUI, and no WMI support is included in builds.

[dera]

try to activate RegFactory

in the WinBuilder GUI
in Basic\Shells\Core\CoreMain script
press the button: 'Enable Regfactory'
(this will activate a bunch of scripts)

[cocofynspm]

try to activate RegFactory

in the WinBuilder GUI
in Basic\Shells\Core\CoreMain script
press the button: 'Enable Regfactory'
(this will activate a bunch of scripts)

Thanks, but enabling RegFactory causes issues: while building, I fiurst get a warning that a driver is unsigned, and then WinBuilder experiences an Access Violation during Register (sic) Factory VM Installer processing (fails to attach virtual disk).

After disabling RegFactory, I now encounter an irritaing 'obsolete' script warning (for 25CoreWMI.script) on every build, even though the script is supposedly disabled.

[dera]

RegFactory works for me on x86 XP SP3 host
and i cannot test on x64 host.

Do you use x64 Vista or x64 Windows 7 host?
If yes try to install the latest ImDisk and make sure it is working fine before run the LiveXP project,
see ImDisk homepage.

[Lancelot]

@dera

and i cannot test on x64 host.

RegFactory've always works fine on x64 host

@cocofynspm
RegFactory build tries to install imdisk if not exists but if imdisk can not be installed (or not exists) !! on a hostwindows

I first get a warning that a driver is unsigned, .... (fails to attach virtual disk).

than this is expected result .

After disabling RegFactory, I now encounter an irritaing 'obsolete' script warning (for 25CoreWMI.script) on every build, even though the script is supposedly disabled.

Well, due to expected bug nature of winbuilder.exe and wbverify.exe I have 2 suggestions:
1- try hitting "Disable RegFactory button" again, winbuilder.exe naturally may have some bug that cause trouble, and try to build,
if you still get warning than
2- at LiveXP\Basic\!WBManager--> disable "Verify Project" script, application inside the script have unfixed bug(s) which cause troubles time to time.

[cocofynspm]

Thanks, but enabling RegFactory causes issues: while building, I fiurst get a warning that a driver is unsigned, and then WinBuilder experiences an Access Violation during Register (sic) Factory VM Installer processing (fails to attach virtual disk).

After disabling RegFactory, I now encounter an irritaing 'obsolete' script warning (for 25CoreWMI.script) on every build, even though the script is supposedly disabled.

Thanks for the help guys. I am running a Win7 x64 host, so dera's suggestion of updating my version if ImDisk helped... to a point. The errors I reported are no longer happening, but now Winbuilder attempts to run my installed VMWare Player during the "Register Factory VM Installer" script. It uses the -B command line option, which is no longer supported by VMWare Player, causing a vmplayer error. After clearing the error, Winbuilder.exe errors-out with an access violation.

I have Winbuilder version 80.0.3.0. I tried downloading a later version to see if that fixes the issue, but as winbuilder.net is not available just now I can't. Any suggestions?

[Galapo]

Rather than having it auto-detect and thus select VMWare, select another virtual machine from the options.



Regards,
Galapo.

[cocofynspm]

Thanks, Galapo, but given that I already have the lastest versions of Virtual PC and VMWare Player, it's not exactly satisfactory that I also need to install VirtualBox or QEMU just to use WinBuilder.

Even then, the RegFactory fails to build in the WMI as the VM it creates errors-out during installation of WMI, with the file VSSAPI.DLL missing. Sure, I can also add the Management Console script, but I don't want to. It does seem none of this stuff has ever been tested.

Add to that the AWOL winbuilder.net and xxx.boot-land.net web sites causing at least one of the storage driver scripts to fail, WinBuilder isn't exactly an attractive option right now.

[dera]

i don't think that QEMU needs any installation,
it is enough simply download the files of QEMU to the folder: "\Projects\Tools\LiveXP\qEmu\"
via the WinBuilder Download Center

It does seem none of this stuff has ever been tested.

as i wrote: RegFactory works for me on x86 XP SP3 host,
for me also the '25CoreWMI.script' runs without error - maybe it is because i want the MMC and in my builds the '10CoreMMC.script' is enabled

EDIT: on my host VMware Workstation 7.0.1 build-227600 is installed,
in 'Basic\Build\Register Factory API' script the option 'Virtual machine: VMWare Workstation/Player' selected,
this works for me

[Galapo]

it's not exactly satisfactory that I also need to install VirtualBox or QEMU just to use WinBuilder.

Install of qemu is not needed -- in runs stand-alone with files already in tools folder which should have already been downloaded.

Even then, the RegFactory fails to build in the WMI as the VM it creates errors-out during installation of WMI, with the file VSSAPI.DLL missing.

Is the file available in your source? Please post a log so we can see what's going on.

Sure, I can also add the Management Console script, but I don't want to.

RegFactory scripts have some dependencies. Management Console may be needed for WMI, we'd have to check this.

It does seem none of this stuff has ever been tested.

That's actually not true. The RegFactory scripts have been heavily tested, particuarly by their developer fxscrpt. Actually, RegFactory testing is the main reason LiveXP wasn't current with the 078 versions of WinBuilder due to particular WinBuilder bugs that caused RegFactory to not work.

It could be just that your particular configuration is untested and causing an issue. Like I said above, please post a log so we can see more clearly what's going on.

Add to that the AWOL winbuilder.net and xxx.boot-land.net web sites causing at least one of the storage driver scripts to fail

Sorry, that's out of my hands. I assume Nuno is doing his best to get the sites back up.

WinBuilder isn't exactly an attractive option right now.

Nobody is forcing you to use anything. This is basically a hobby prooject developed in spare personal time. Nobody is paid, so you have to take it that we'll work on things but that we're not perfect.

Regards,
Galapo.