3 replies to this topic

[htm775]

Hi,

I am running Winbuilder [78 SP2] under Windows XP and attempting to build a VistaPE iso. After the build certain software does not show up. I have selected passwords and unlockers under the apps/security branch of VistaPE CAPI v.12(RC1b common API) but they do not end up in the build. The log shows that the scripts have executed. Under Passwords for instance there is NT-2K-2K3 Server Domain Pass Changer, NTPWEdit 0.3 and sala's Password Renew 1.1-Beta but none of them show up in the completed build. Other scripts such as the antivirus script under the security branch work ok. Is there something beyond just putting a check in the check box that needs to be done to allow these apps to be installed in the build? I have attached the log.

Attached Files

•  WinBuilder__078_SP_2____Project_log_dated_from_9_27_2009.zip   88.66KB   441 downloads

[JonF]

That's a puzzler. It sure looks as if the programs were copied and the shortcut specifications were passed to the loader. You're sure that they don't appear under Start | Programs | Security?

Can you look in VistaPE-Core.iso with 7-ZIP or equivalent and see if the programs are there in the Programs directory? And that the shortcuts are listed in vistape.cfg in the root of the ISO?

[htm775]

Thanks for the quick reply. Under Start | Programs I have Ghost, Network, Startup, and System. I have also searched the x: drive for the files such as ntpwedit.exe and could not find them.


Under the root of VistaPE-Core.iso I have a programs folder. It contains folders for 7-zip, dc-pass, diskpartitioner, dreampackpl, ntpweditm, salapasswd, and windowsgate. None of these show up when I boot the image under VMWare. I am not sure what to look for in the vistape.cfg file. It is in the root of the iso. I have attached the file for you to take a look at. Thanks

Attached Files

•  VISTAPE.zip   991bytes   406 downloads

[htm775]

Just to follow up with this....

I tried building on another PC and it worked fine so the problem is with the particular PC I was useing. I have no idea why, but if anyone should run into this type of problem in the future try building on another PC.