Jump to content











Photo
- - - - -

Problem Building a VistaPE Project


  • Please log in to reply
44 replies to this topic

#1 patsch

patsch

    Silver Member

  • Advanced user
  • 785 posts
  •  
    Germany

Posted 12 March 2009 - 01:23 PM

Hello together,

I have a problem building my vistape project.
I use:
Winbuilder [076] with VistaPE Core v.12 (RC1) and VistaSP1 as source (waik only for DaveXP PEIMG driver script)
I modified the Basic Config script described here
My Problem: I got this error message while proceeding the PostConfig script (but I can finish building the iso, in spite of everything this iso is not working)
bcdedit.exe - Einsprungpunkt nicht gefunden

Der Prozedureinsprungpunkt "_except_handler4_common" wurde in der DLL "msvcrt.dll" nicht gefunden
in english something like that "The procedure entry point "_except_handler4_common" could not be located in the dynamic link library "msvcrt.dll".
My error shows me the following warnings (no errors):
[Warning] FileCopy - Failed to copy [%BaseDir%\Temp\VistaPE-Core\BootWimSrc\windows\System32\bcdedit.exe] to: [%BaseDir%\Target\VistaPE-Core\windows\System32\bcdedit.exe]

[Warning] FileCopy - Failed to copy [%BaseDir%\Temp\VistaPE-Core\BootWimSrc\windows\System32\de-DE\bcdedit.exe.mui] to: [%BaseDir%\Target\VistaPE-Core\windows\System32\de-DE\bcdedit.exe.mui]

 [Warning] FileCopy - Failed to copy [%BaseDir%\Temp\VistaPE-Core\InstallWimSrc\windows\System32\de-DE\diskcopy.dll.mui] to: [%BaseDir%\Target\VistaPE-Core\windows\System32\de-DE\srvsvc.dll.mui]

[Warning] FileCopy - Failed to copy [%BaseDir%\Temp\VistaPE-Core\InstallWimSrc\Windows\System32\wdi.dll] to: [%BaseDir%\Target\VistaPE-Core\Windows\System32\wdi.dll]

[Warning] FileCopy - Failed to copy [%BaseDir%\Wallpaper\winpe.bmp] to: [%BaseDir%\Target\VistaPE-Core\Windows\system32\winpe.bmp]

[Warning] FileCopy - Failed to copy [%BaseDir%\Temp\VistaPE-Core\BootWimSrc\windows\System32\dbgeng.dll] to: [%BaseDir%\Target\VistaPE-Core\windows\System32\dbgeng.dll]

[Warning] FileCopy - Failed to copy [%BaseDir%\Temp\VistaPE-Core\BootWimSrc\windows\System32\dbghelp.dll] to: [%BaseDir%\Target\VistaPE-Core\windows\System32\dbghelp.dll]

Any hints to fix this problem?

tia
Patsch

#2 was_jaclaz

was_jaclaz

    Finder

  • Advanced user
  • 7100 posts
  • Location:Gone in the mist
  •  
    Italy

Posted 12 March 2009 - 01:51 PM

What is you "%basedir%" ?

Any spaces in the name?

Do the SOURCE files generating the errors exist?

Are you running some "Antivirus/Malware" program? (with resident scanner)

jaclaz

#3 patsch

patsch

    Silver Member

  • Advanced user
  • 785 posts
  •  
    Germany

Posted 12 March 2009 - 02:32 PM

thx jaclaz for your quick reply

What is you "%basedir%" ?

my %basedir% is the directory win076 in the root directory of my data hdd

Any spaces in the name?

nope

Do the SOURCE files generating the errors exist?

no ... I tried 2 different original VistaSP1-DVDs, but i can't find the needed files (bcdedit.exe, bcdedit.exe.mui,diskcopy.dll.mui). The wallpaper-bitmap exist.

Are you running some "Antivirus/Malware" program? (with resident scanner)

no, not during builing

#4 patsch

patsch

    Silver Member

  • Advanced user
  • 785 posts
  •  
    Germany

Posted 12 March 2009 - 06:19 PM

ok, I downloaded a fresh version of winbuilder and vistape, took also a third VistaSP1-DVD, started building (no changes, built from scratch) ... the error still occurs
I also took an english version of Vista with the same result

#5 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 12 March 2009 - 06:33 PM

First -not very serious-:

Your decision, to use Vista. Therefore the results are something YOU have to live with!

Now seriously:

In the past a couple of users (me included) have had troubles to build a 'fresh downloaded' VistaPE.

And until now no universal working project is published.

We only can hope that the collection of user success and user unsuccess will finally lead to a usable VistaPE project.

BTW: Maybe the new Windows7 projects can replace the VistaPE project which (in my opinion) is currently not supported by the author .

Peter

#6 patsch

patsch

    Silver Member

  • Advanced user
  • 785 posts
  •  
    Germany

Posted 12 March 2009 - 07:05 PM

@psc: I use VistaPe for a couple of months now, I have several working builts. I now wanted to update my scripts (my last successful built was 3 weeks ago). I changed nothing but 2 app-scripts (that I deactivated for debugging). VistaPe runs fine till this day. I don't know what went wrong
I use VistaPe because I had trouble to build a NativeXP with the scripts and drivers I need (but that shoul not be part of this thread)

#7 was_jaclaz

was_jaclaz

    Finder

  • Advanced user
  • 7100 posts
  • Location:Gone in the mist
  •  
    Italy

Posted 12 March 2009 - 07:15 PM

Something is however strange, the *.mui may not be there, but bcdedit.exe is one of the "base" files of Vista (needed to edit the BCD store) :cheers:

.mui files are "localised" versions, should be in something like \en-us\ or \pl-pl or something like that:
http://en.wikipedia...._User_Interface

Seems like a problem with source.

Maybe a faulty SP1 integration? :cheers:


jaclaz

#8 patsch

patsch

    Silver Member

  • Advanced user
  • 785 posts
  •  
    Germany

Posted 12 March 2009 - 07:22 PM

I have not an integrated SP1-Version (means I did not integrate SP1 by myself), I have 2 new DVDs Vista with SP1 included and one iso-image Vista Business 32Bit german (from MSDNAA).
As I mentioned above, I changed nothing and I built successfully VistaPE-projects till this day

#9 was_jaclaz

was_jaclaz

    Finder

  • Advanced user
  • 7100 posts
  • Location:Gone in the mist
  •  
    Italy

Posted 12 March 2009 - 07:49 PM

OK. I have no more "general" ideas. :cheers:

But still bcdedit.exe must be somewhere in the source.

Anyway something MUST have changed, possibly unwantingly, but I don't believe in little green men or, as psc would call it, voodoo :cheers:

Did you re-download anything?

Do you have a copy, backup or image of the building-with-no-errors-and-working-at-the-time project/environment to make a comparison?

jaclaz

#10 patsch

patsch

    Silver Member

  • Advanced user
  • 785 posts
  •  
    Germany

Posted 12 March 2009 - 08:29 PM

But still bcdedit.exe must be somewhere in the source.

possibly the file is part of a pack or packed or ... i did not found the file neither on DVD incl SP1 nor on DVD without SP1

Did you re-download anything?

jap.

Do you have a copy, backup or image of the building-with-no-errors-and-working-at-the-time project/environment to make a comparison?

no, unfortunately not. I only have one working directory

Anyway thx jaclaz for your response and your advice.
I will make a clean installation of my OS next weekend to check if my OS is the troublemaker.

#11 PaPeuser

PaPeuser

    Silver Member

  • Advanced user
  • 787 posts
  •  
    United States

Posted 14 March 2009 - 01:22 AM

Hello

Most of these errors look to be in reference to WAIK do you have WAIK installed?
And is it same language as your Vista?

#12 patsch

patsch

    Silver Member

  • Advanced user
  • 785 posts
  •  
    Germany

Posted 14 March 2009 - 10:42 AM

hello PaPeuser,
as I pointed out in my first post, I only use WAIK for the DaveXP PEIMG driver script. There I can explicit point to the WAIK folder (in german, therefore the same language).
I did not point to WAIK in the PreConfig-script in the Base section. Also I do not have any scripts activated that use WAIK like WIMMaster (except the above mentioned).
I also mentioned that I sucessfully built some projects before and there I also did not point to WAIK.
A fresh downloaded winbuilder/vistape throws the same warnings and error and I think that for a clean built from scratch WAIK ist not needed

#13 paraglider

paraglider

    Gold Member

  • .script developer
  • 1729 posts
  • Location:NC,USA
  •  
    United States

Posted 14 March 2009 - 01:40 PM

bcdedit is in boot.wim / install.wim found in the sources directory on every Vista DVD I have looked at.

The vista version of bcdedit is incompatable with windows 7. You have to use the windows 7 version of bcdedit on windows 7.

I gave up using vistape. Instead I now use YahooUK's win7_pe project as a base for my own project. That project does however lack functionality compared to vistape - explorer / mmc is not included.

Spent several days fighting winpeshl.ini. It is supposed according to the docs to support passing command line parameters to the process being launched. Turns out however that only the first parameter is passed.

#14 PaPeuser

PaPeuser

    Silver Member

  • Advanced user
  • 787 posts
  •  
    United States

Posted 14 March 2009 - 02:17 PM

Hello
Here are a few things I have noticed about VistaPE and trying a new clean build
When you open winbuilder and download VistaPE from server.
A Minimum download may not boot I have had to go back and do a complete download of VistaPE files from server.

Then I have had corrupt download script, sometimes you will see a ZLB Archive error
These scripts need to be deleted and downloaded again.

Trying many different ways. I have not been able to build a VistaPE disk without having WAIK installed

I have tried
Vista Ultimate SP0
Vista Ultimate SP1
2 versions of WAIK
unchecking scripts

I say all of this not only for you but for anyone reading this post.

So PLEASE if and when you figure out what your problem is, Pease let all of us know!

Good luck

Edited I am looking for another project to ...

#15 dera

dera

    Gold Member

  • .script developer
  • 1335 posts
  •  
    Hungary

Posted 14 March 2009 - 08:30 PM

Regarding the FileCopy Warning look here

so e.g. in \Projects\VistaPE-Core\Base\03-base-files.script
look at the lines 92-93 or 307-308
CopyOrExpand,"%InstallSRC%\windows\System32\%DistLang%\diskcopy.dll.mui","%TargetDir%\windows\System32\%DistLang%\srvsvc.dll.mui" _linenums:0'>If,ExistFile,"%InstallSRC%\windows\System32\%DistLang%\diskcopy.dll.mui",<strong class='bbc'>CopyOrExpand</strong>,"%InstallSRC%\windows\System32\%DistLang%\diskcopy.dll.mui","%TargetDir%\windows\System32\%DistLang%\srvsvc.dll.mui"
doesn't give warningif the WAIK installed on the system then VistaPE will use \Windows AIK\Tools\x86\imagex.exe to mount the source boot.wim / install.wimEdit: look into '01-preconfig.script' at the section [AutoFindImagex] at lines 80-82,regardless of you point to WAIK in the PreConfig-script or notif WAIK not installed then the build will halt using a fresh downloaded VistaPEcaused by a bug in the '01-preconfig.script'in this case have to go to Projects\Tools and manually run the command 'WimUtil.exe install'
look here and look here

Edited by dera, 14 March 2009 - 11:21 PM.


#16 PaPeuser

PaPeuser

    Silver Member

  • Advanced user
  • 787 posts
  •  
    United States

Posted 14 March 2009 - 08:41 PM

Hello

Ok your are saying to run 'WimUtil.exe install' from the tools folder and when during the building process should you run this??

#17 dera

dera

    Gold Member

  • .script developer
  • 1335 posts
  •  
    Hungary

Posted 14 March 2009 - 08:53 PM

Hello

Ok your are saying to run 'WimUtil.exe install' from the tools folder and when during the building process should you run this??


run it before the first build

or
in the 01-preconfig.script
at Line #213
write: System,ERROROFF
before the line:
RegRead,"HKLM","SYSTEM\CurrentControlSet\Services\WimFltr","DisplayName","%RegName%"
and
comment out the line 226 at the section [WinUtil]
//ExtractFile,%ScriptFile%,WIM,"WimUtil.exe","%Tools%"

Edit:
of course if WAIK installed these steps are not needed

Edited by dera, 14 March 2009 - 08:57 PM.


#18 patsch

patsch

    Silver Member

  • Advanced user
  • 785 posts
  •  
    Germany

Posted 15 March 2009 - 08:12 AM

thanks dera, your hints solved fixing the warnings.
But my primary problem still exists ("The procedure entry point "_except_handler4_common" could not be located in the dynamic link library "msvcrt.dll")

#19 allanf

allanf

    Gold Member

  • .script developer
  • 1256 posts

Posted 15 March 2009 - 08:34 AM

But my primary problem still exists ("The procedure entry point "_except_handler4_common" could not be located in the dynamic link library "msvcrt.dll")


@patsch,

AFAIK, bcdedit is used to modify the Boot Configuration Data (? BCD) in the Target Directory for VistaPE. The Project copies bcdedit from the Install DVD's boot.wim (or possibly from WAIK's winpe.wim), then executes the copy in the Target Directory. Is there a possibility of a version or architecture mix-up?

You should be able to boot, but not the VistaPE Multiboot - just the plain WinPE boot. What happens when you boot the Project?

Regards

#20 dera

dera

    Gold Member

  • .script developer
  • 1335 posts
  •  
    Hungary

Posted 15 March 2009 - 08:40 AM

Sorry, I have no more idea
(in my builds I have never seen such msvcrt.dll and bcdedit.exe error)

#21 patsch

patsch

    Silver Member

  • Advanced user
  • 785 posts
  •  
    Germany

Posted 15 March 2009 - 12:12 PM

AFAIK, bcdedit is used to modify the Boot Configuration Data (? BCD) in the Target Directory for VistaPE. The Project copies bcdedit from the Install DVD's boot.wim (or possibly from WAIK's winpe.wim), then executes the copy in the Target Directory. Is there a possibility of a version or architecture mix-up?

i downloaded a fresh version of winbuilder and the vistape project, only using VistaSP1-DVD as source, still the same error

You should be able to boot, but not the VistaPE Multiboot - just the plain WinPE boot. What happens when you boot the Project?

if I enable the virtual test to run the project in my VM, i always get an BSOD with stop error 0xc0000017

#22 allanf

allanf

    Gold Member

  • .script developer
  • 1256 posts

Posted 15 March 2009 - 12:25 PM

i downloaded a fresh version of winbuilder and the vistape project, only using VistaSP1-DVD as source, still the same error

if I enable the virtual test to run the project in my VM, i always get an BSOD with stop error 0xc0000017


With VistaSP1 as your source, you'll need to do a full copy of the entire boot.wim because the folder names are different to the RTM which VistaPE supports. In earlier versions of VistaPE, there used to be a check box for doing that.

Not sure if that will help.

Regards :good:

#23 PaPeuser

PaPeuser

    Silver Member

  • Advanced user
  • 787 posts
  •  
    United States

Posted 15 March 2009 - 02:16 PM

Hello
I have been trying to reproduce your errors, without using Ct’s Peloader and I have WAIK installed

If I only do a recommended download of VistaPE from the Download center
I get a Boot manager warning status 000f in Vmware
even with WAIK installed
this did not work - If I do a complete VistaPe download in WB it works,, - edited NO it did not!!!!!!!!!!!!!!!!

Have you tried a complete download and maybe uncheck stop build on errors in WB tools?

and what version of WB did you use before?

#24 patsch

patsch

    Silver Member

  • Advanced user
  • 785 posts
  •  
    Germany

Posted 15 March 2009 - 02:28 PM

Have you tried a complete download and maybe uncheck stop build on errors in WB tools?

I downloaded winbuilder from here:
http://winbuilder.ne...oad.php?view.37
and then downloaded vistape per download center within winbuilder

and what version of WB did you use before?

075 and some Betas (from the psc's signature)
076
with both versions i got successful builts

#25 allanf

allanf

    Gold Member

  • .script developer
  • 1256 posts

Posted 15 March 2009 - 02:38 PM

...

with both versions i got successful builts


Great to hear that. Can you say what the problem was and how you fixed it?

Thanks




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users