Vista SP2 And Vista PE Build Errors

GDay All,

I'm trying to build VistaPE using a copy of Vista with SP2, however, I get the following error:

FileCopy - Failed to copy [%BaseDir%\Temp\VistaPE-Core\InstallWimSrc\Windows\System32\DriverStore\FileRepository\acpi.inf_97916753\*.dll] to: [%BaseDir%\Target\VistaPE-Core\Windows\System32]

The problem is that I can't find the code that is creating this error. HELP!!

I'm confident that the error is caused because the acpi.inf_97916753 folder does NOT contain any .dll files, or at least it doesn't in my SP2 install, and I'm unable to change the code to correct this.

Anyone have any ideas?

Also, I'm looking for an easy way to view the contents of a .wim file.

Can anyone suggest any programs that will help?

No guarantees that SP2 will work at all.

The actual code is in 00-api-main.script, called by a line somewhere that starts out "CopyDrv,...".

In 00-api-main.script, change:

[Copy_Drv_Process]If,ExistFile,"#1\*.sys",FileCopy,"#1\*.sys","%TargetDir%\Windows\System32\Drivers"Else,Echo,"No #1\*.sys files to copy"If,ExistFile,"#1\*.dll",FileCopy,"#1\*.dll","%TargetDir%\Windows\System32"Else,Echo,"No #1\*.dll files to copy"If,ExistFile,"#1\*.inf",FileCopy,"#1\*.inf","%TargetDir%\Windows\Inf"Else,Echo,"No #1\*.inf files to copy"

I'm working on an updated version of VistaPE that will have this update incorporated.

7-zip is a good tool for viewing WIM files, and is indispensable for opening many of the attachments you'll see here. If yo want to modify WIM files you'll need to get fancier.

No guarantees that SP2 will work at all.

7-zip is a good tool for viewing WIM files, and is indispensable for opening many of the attachments you'll see here. If yo want to modify WIM files you'll need to get fancier.

Thanks for replying JonF. I hope you are able to get it working and of course if I manage to stumble upon a solution I'll post it here

Somehow I missed the fact that 7zip was able to read .wim files .... Doh!!!!

In any case, I googled for an answer and found GimageX which seems to do everything. I haven't tried it yet, but it looks promising.

In combination, these 2 programs should help me get the job done .... lol!!

Is there a quick reference for WinBuilder commands and variables around?

It would help if I had something to 'lookup' now and then. The old grey matter is running low on memory space ... lol!!!

WinBuilder and its projects are implemented by technophiles and change rapidly. As is often the case in such situations the documentation lags significantly. It's the way such things go, and I'm just as guilty as anyone else.

There's a recent but slightly out of date guide at http://winbuilder.net/help/.

There's also a widely-used set of commands that actually call "subroutines" that are made up of the lower-level commands. This set is called the API. The idea is to make it easier to write scripts that are usable in several projects. Alas, the API implementation differs significantly from project to project. The problem you ran into was a combination of an API command that exists only in VistaPE and a recent version of WinBuilder that has more strict definitions of what things are errors.

The VistaPE version of the API is described at http://www.vistape.n...istape-api.html ... it takes some study to figure it out since the author is Russian and has some difficulty with English. http://www.boot-land...?showtopic=8191 is useful.

The most fully developed API is by Pedro Le for LiveXP. He has a VistaPE API script that is somewhat more developed than the standard VistaPE API but is well behind the curent LiveXP api. He's working on an API script that will work with LiveXP, VistaPE, and the up-and-coming Win7PE. Don't know if he will succeed, but it sure would be nice.

The main developer of VistaPE hasn't been seen in well over a year. There's some issues of grabbing his baby and making it someone elses. Nonetheless, I'm working on an updated version of VistaPE that will have several signiifcant updates and make it much easier for Pedro to develop his common API. It's not totally settled how this VistaPE will be distributed.

@trumpy81 : are you using Winbuilder [077 RC 1] ?
look here, seems to be the same error. Dera pointed me to the right direction.

No guarantees that SP2 will work at all.

The actual code is in 00-api-main.script, called by a line somewhere that starts out "CopyDrv,...".

In 00-api-main.script, change:

[Copy_Drv_Process]If,ExistFile,"#1\*.sys",FileCopy,"#1\*.sys","%TargetDir%\Windows\System32\Drivers"Else,Echo,"No #1\*.sys files to copy"If,ExistFile,"#1\*.dll",FileCopy,"#1\*.dll","%TargetDir%\Windows\System32"Else,Echo,"No #1\*.dll files to copy"If,ExistFile,"#1\*.inf",FileCopy,"#1\*.inf","%TargetDir%\Windows\Inf"Else,Echo,"No #1\*.inf files to copy"

I'm working on an updated version of VistaPE that will have this update incorporated.7-zip is a good tool for viewing WIM files, and is indispensable for opening many of the attachments you'll see here. If yo want to modify WIM files you'll need to get fancier.

@JonF:

You are not in all cases right with your suggestion.

See here and follow the other 'here' link.

Peter

I'm trying to build VistaPE using a copy of Vista with SP2

I am not sure either,
but nowhere seen such statement that the project (which was created at 21.10.2008)
is compatible with Vista SP2 source,
myself cannot test it as i have no Vista with SP2 integrated by MS

That is an important point.

@trumpy81: the source DVD must be a DVD as issued by Microsoft. If it has been updated by some procedure you carried out, such as vLite, it is almost certain that it is not usefual as the source of a VistaPE build.

GDay All,

First off, PSC, JonF's solution did indeed work and I see no reason why it wouldn't.

You have to remember that the subroutine is a FILECOPY not a FOLDERCOPY command and naturally it won't recurse into sub folders.

Anyhow, I built the project and it works perfectly in VMWare except for networking. This was not unexpected, but when I burnt the ISO and tried it out on this machine, it boots all the way but then just as the boot process completes, the screen freezes and it locks up everything. A little disappointing but then this machine (i7core 920) wont install XP either, it crashes and burns also.

On my AMD Semperon Laptop it will boot almost to the desktop but then it blue screens with a stop error: C000021a

Obviously it's going to take a lot more work to get this going.

That is an important point.

@trumpy81: the source DVD must be a DVD as issued by Microsoft. If it has been updated by some procedure you carried out, such as vLite, it is almost certain that it is not usefual as the source of a VistaPE build.

Thanks JonF, I am using an MSDN copy of the 32bit DVD, so I shouldn't have any issues with it.

First off, PSC, JonF's solution did indeed work and I see no reason why it wouldn't.
You have to remember that the subroutine is a FILECOPY not a FOLDERCOPY command and naturally it won't recurse into sub folders.

Of course I do remember, because I wrote the code.

FileCopy with wildcards in WinBuilder 074 and 076 works non-recursive (in spite the documentation tells so).
FileCopy with wildcards in WinBuilder 077 beta / RC works recursive (can be switched of by an additional argument 'norec')
I made this modification in order to be syncronous with the documentation:

FileCopy
FileCopy,"FromFile","ToDir"

This command will copy all files and respective sub folders from a given source to a specified destination. It uses Win32 API as a silent operation overwriting any previously existent files. You can view the result of this operation on the respective log entry.

FileCopy supports wildcards ( *.* )

Syntax example:
FileCopy,"c:\MyPath\*.txt","c:\AnotherPath"

On this example FileCopy will copy all text files (*.txt) from MyPath to AnotherPath

The error message you mention in your first post, only occurs in WinBuilder 077 and later, and there my explanation to JonF is valid.

did indeed work

If you read the explanation carefully and try to understand:

Depending on the situation it may work or not work.
In both cases you do not get an error message.


Peter

Of course I do remember, because I wrote the code.

FileCopy with wildcards in WinBuilder 074 and 076 works non-recursive.
FileCopy with wildcards in WinBuilder 077 beta / RC works recursive (can be switched of by an additional argument 'norec')

My apologies PSC, I wasn't aware that the FILECOPY command had changed. I guess I need to read the docs some more!!

Using Vista SP2 as source
maybe it is worth to try what ctmag suggested here

so in 'Base\04-additional.script'
comment out the line 25 and line 27
[codebox]#SP1//If,ExistDir,"%BootSRC%\Windows\System32\DriverStore\FileRepository\megasr.inf_707e247f",Run,%ScriptFile%,AddDrivers_SP1#SP0//If,NotExistDir,"%BootSRC%\Windows\System32\DriverStore\FileRepository\megasr.inf_707e247f",Run,%ScriptFile%,AddDrivers_SP0[/codebox]and at the end of the [Process] section add[code]DirCopy,"%BootSRC%\Windows\inf","%TargetDir%\Windows"DirCopy,"%BootSRC%\Windows\system32\drivers","%TargetDir%\Windows\system32"DirCopy,"%BootSRC%\Windows\system32\driverstore","%TargetDir%\Windows\system32"FileDelete,"%TargetDir%\Windows\inf\*.pnf"DirDelete,"%TargetDir%\Windows\inf\BITS"DirDelete,"%TargetDir%\Windows\inf\RemoteAccess"[/code]

Using Vista SP2 as source
maybe it is worth to try what ctmag suggested here

Thanks Dera!! That got it going!!

I can confirm that it works in VMWare and on my i7core desktop, but it fails on my AMD Semperon Laptop. Error message indicates that pci.sys is missing or corrupt.

I haven't looked into yet but I hope that it won't be too difficult to correct. At least I have a starting point.

And thanks to ALL the guys here that helped make this work!!

Do you use the original vpeldr.exe by NightMan
or the modified one by ctmag found here?
(should extract the attached file 'system32.7z' from 'Base\07-config.script'
called 'Basic configuration and tools' in the WB Interface,
then replace the 'vpeldr.exe' in 'system32.7z' then reattach the new 'system32.7z')

Do you use the original vpeldr.exe by NightMan
or the modified one by ctmag found here?

Dera, I used the original vpeldr.exe by nightman, but I will try ctmags' version. I'll post back the results after I have had a chance to sort my laptop out.