I would like to make a VistaPe CD or USB, but I don't now what is wrong when a test in WinBuilder.
Here is my log:
Jump to content
Posted 20 February 2009 - 09:47 PM
Posted 20 February 2009 - 09:56 PM
Posted 21 February 2009 - 07:12 AM
Posted 21 February 2009 - 10:04 AM
It wasn't always the case. So, I checked the preconfig script from the download center, and found the following:
WinBuilder assumes (maybe it is declared anywhere) that you have the WAIK, but it seems not to be installed on your system.
It appears that the error is in the first line shown - in cases where the Reg Key cannot be read, there is no avenue to continue the script and install WimUtil.exe.
If,notExistFile,"%Tools%\wimutil.exe",Halt,"Something wrong with WimUtils..."
Posted 21 February 2009 - 02:03 PM
Posted 21 February 2009 - 02:46 PM
Posted 21 February 2009 - 10:42 PM
If you use VistaPE default setting or default scripts included or checked in Winbuilder download you will need to have WAIK installed on build machine. Some default scripts ask for WAIK others ask for Vista DVD source. You can check this by highlighting scripts in left tree view and viewing options.
Posted 21 February 2009 - 11:13 PM
Posted 21 February 2009 - 11:48 PM
AllenF is this easier to read???
Posted 21 February 2009 - 11:52 PM
Posted 22 February 2009 - 12:59 AM
Sorry i cant help you with keyboard,
YFI i dont hear very well ,, so yell at me,,LOL
Posted 22 February 2009 - 01:24 AM
Posted 22 February 2009 - 01:52 AM
It was imagex CPU usage that caused my computer to overheat (plus dust) and eventually break. Especially unmounting/capturing big, complex images.
... it makes my server HD work hard.
I assumed it was being updated, especially now for the newer versions of Winbuilder. For newbies without WAIK installed, that Reg Key not found error would be a turn-off. Once the key value is there, it's OK. Other filecopy errors/warnings reported with newer WBs seem to be the result of trying to copy files that already exist in the target. I don't think it would be too difficult to clean up the scripts.
And I am sorry to say I have no idea who is maintaining VistaPE anymore I would hate to see Vistape die
The driver pack was tied to vpeldr (sp?). I saw a member, I can't remember the name, has valiantly tried to create a 'Kill vpeldr' to get around this issue. ... ...
I guess you could edit additional files and drivers script if you wanted or didn't need that script and write one that you want.
Customize Vista to your needs
It's been a long, long time.
I always hope when you don't see people in forms that they are working on a new version
Posted 22 February 2009 - 02:11 AM
Posted 22 February 2009 - 03:30 PM
Posted 22 February 2009 - 03:41 PM
My one finger for typing has problems finding the right keys on this balck keyboard I have. (Don't worry, I do have seven more fingers... plus two thumbs. ... ...)
Posted 22 February 2009 - 10:05 PM
Posted 22 February 2009 - 10:18 PM
Posted 22 February 2009 - 10:32 PM
... Sory the problem is that when vistape try to start it say's that it can, becose same ddrivers did change, so it tells me to put original Vista dvd and try with Recovery....
Wish me luck!
0 members, 0 guests, 0 anonymous users