I have an interesting problem. I'm trying to build a LiveXP CD using WinBuilder 074 based on Windows XP w/ SP2 slipstreamed. This is all being done on a Windows Vista Business x64 machine as a user w/ admin privileges and UAC turned off.

If I unpack the LiveXP.zip file, open WinBuilder, and add ShellWM and Paragon Hard Disk Manager and then simply start the build, it completes without error and the CD works (though a small handful of the programs won't open for some reason).

But if I go to the download section and select Recommended updates (for LiveXP only but including the entire Tools folder as recommended), download them, and then try to do the same build, I get a ton of errors. Near the beginning of the build, when it seems to be verifying the project with the WBVerify script I get a few warnings that pop up in notepad:



If I close notepad the build continues, but shortly after I get a Windows error dialog box popping up that says:



If I close it, another pops up in its place. This continues to happen for a total of 9 error dialog boxes with that exact error. Beyond that it runs for awhile, but I continue to get missing file errors about other missing files. Some of them are missing in the WinBuilder program folder itself, while others are in the build folder. When the build is done and QEMU opens, it boots as far as a gray screen with a mouse cursor, but then the virtual machine reboots and it does this in loop endlessly until I close QEMU. There are a massive ton of registry related errors like so:



If I remember right, there were something like 1300 errors with a vast majority of them registry-related. Why does the build bomb so badly if I try to update the scripts?

The current build available through the WinBuilder download center is only compatible with the latest WinBuilder executable (that is, 075b5).

WBVerify always seems to throw those warnings on a fresh build. On a re-run they disappear. Peter (psc) is looking into it.

Regards,
Galapo.

Ah. Ok, thanks.

BTW, how can I get Winbuilder 075b5? Every time I try to get to the download link, I get an internal server error. Are there any mirrors?

Edit: nm, got it finally.

Too many visitors at the same time, we're working to solve out this matter by improving the performance of the server.

It helps to visit the download site on times of slower activity in the night or fresh or in the morning, sorry about this.

Thanks. I got the 075b5 version and it ran like a charm, aside from an apparently known issue with PENetwork on a build based on XP SP3. I've since rebuilt it on XP SP2.

I do have one question though... Paragon Hard Disk Manager still will not open. It shows the splash screen, but never opens the actual program. I chose the download option in the script for it. Are you familiar with this problem at all?

No, I haven't tested that option for a while as I have the app installed and so use that option. I'll try to test and reproduce the next few days.

Thanks,
Galapo.

A couple more things... more informational than anything but if you have input on either one, please let me know:

1. I rebuilt using the "Extract from installer file" option for Paragon Hard Disk Manager and selected the installer file that WinBuilder previously downloaded, and am having the same problem. Next, I'm going to try to grab the program and install it on my computer and use that option.

2. I decided to try out MinLogon just for the heck of it. So I found a copy of that and put that in the build. On my first attempt at this build, when it booted into QEMU there was an error saying something like "PELoader doesn't need to use a hacked WinLogon in order to disable resource limits. Please use a normal WinLogon." And then when I clicked ok it rebooted the VM. I went back and rebuilt using XPELogon instead of PELoader, and it seemed to work fine initially, but I noticed the Opera icon on the desktop was one of those generic "I can't find the program" icons. Sure enough, if I double-clicked it, it said the shortcut was missing. When I look in X:\Program Files\CD-Opera in the VM, the program is installed and I can click on opera.exe and it works fine. If I click on the Start menu and then Programs, it says "(Empty)" but all my stuff is in X:\Program Files and works from executing the EXEs directly. I had not had this problem with any previous builds. I'm not sure if it's related to minlogon or XPELogon or what, but I suspect it's one or the other or both.

Hi scottws,

Regarding #1, thanks, if you could test using the install option, that would be quite helpful to me. I haven't gotten to testing yet, so if you do the one last test, that will indeed help me.

Regarding #2, it seems to me from testing minlogon.exe that it doesn't support or enumerate some environment variables correctly (I was having problems with %allusersprofile in a test I ran). I had noticed the issue with peloader also, so probably a notice in the script regarding such would be good.

Thanks,
Galapo.

Ok, I'll test Paragon tonight.

As for MinLogon, it seems that to really use it you need to use a shell other than explorer.exe:


Source: http://msdn.microsoft.com/en-us/library/ms838653.aspx

I'm going to see if I can figure out how to get LiteStep integrated as the shell.

Ok, installing Paragon Hard Disk Manager was a no-go. I think it has something with me running Windows Vista x64 as my OS. Because Paragon Hard Disk Manager 8.0 wouldn't run on my PC, giving me the error "Unknown windows version." When I changed compatibility mode to Windows XP SP2 it worked; however, WinBuilder won't build from my local instal on my PC. It bombs out during that script and gives 4 errors:

OK, I ran tests also. If attempting to run HDM under qemu (ie the from the finish script), the spash screen displays for a moment, then disappears with the application never opening. However, if I run the same ISO under VMWare (my own setup, not a finish script), then it works fine. I'm not sure what the issue with qemu is, though, but I'm not sure it matters unless you were intending to run it always under it.

Regards,
Galapo.

Hm yes, that's odd but I confirm as well that Paragon HDM doesn't open when running under QEMU but it works fine when running under VMware Server 1.05

New qemu script has HDM working: http://www.boot-land.net/forums/index.php?...ost&p=47793

Regards,
Galapo.