44 replies to this topic

[patsch]

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

Thanks

you misunderstood

and what version of WB did you use before?

as I mentioned I built several vistape projects but now (I only changed 2 of my scripts) I have this error. And now if I download a fresh version (without my scripts) I have the same error. I did not change anything concerning my working directory or my OS or whatever ...

[allanf]

you misunderstood

Oh. Sorry.

I have seen that error before but can't find it searching.

The best thing to do would be to edit the script so as to to open and hold open bcdedit in a command prompt just to see what it's actually doing. Maybe run a few other bcdedit commands at the same time.

First though, can you post a log of a small unsuccessful build.

Thanks

[PaPeuser]

I just tried a new WB76 and a new DL of Vistape
And it gave me a Boot Error with standard download

So I just redid everything and tried a complete DL of VistaPE
With a slipstreamed SP1 (vlight) and another Boot Error

So I went back to SP0 and tested again and another Boot Error

I am not sure where the problem is BUT it may not be you

I will do some more testing,

SP1 (vlight) and SP0 both work with my good build,

[patsch]

thx all for your help ..
I can not post any log files because I formatted my system to setup a fresh OS to exclude faults concerning the OS
I will post results with the fresh OS

[PaPeuser]

Ok I just succeeded in getting a new Vistape to boot
I used SP0 and clean downloads of WB and a complete VistaPE

All WB was left default – just source was selected
Remember I have WAIK installed

LandSpy and Parted Magic eroded and where unchecked

This gave me a boot error

Then

I unchecked the APP folder or all apps and it built (no boot error)

Now I have to go back and see what APPs are the problems and try SP1

tested no problems withh SP1(vlight) and systems folder enabled only under apps

this may take awile,

ALL tests done with Vmware

[PaPeuser]

Tested with Vista SP0 as source and with WAIK installed

Winbuilder 76 default settings - I just selected source

With Winbuilder 76 and a recommended download of VistaPE (RC1)
Boot error, even after unchecking all Apps
I can not make a recommended download of VistaPE work at all

With Winbuilder 76 and a complete download of VistaPE (RC1)
All default settings and scripts checked
Boot error with defaults checked
BUT
I found that by unchecking APPs\Disk Tools folder all together VistaPE booted

Something has changed, maybe someone is working on VistaPe

[allanf]

These may be the lines in the PostConfig script that are failing patsch.
I'm not familiar enough with bcdedit to convert them to cmd.exe commands. In particular, I'm uncertain why the last argument is "%WindowsDir%\system32", because that refers to the Host OS, doesn't it? ... : ...

paraglider also mentioned that not all bcdedits are the same. It would be worth finding out whether the bcdedit comes from the Install DVD's boot.wim or WAIK's winpe.wim. And dera pointed out that VistaPE will search for the WAIK even though it is not selected in a check box. But AFAIK, the winpe.wim is not mounted to allow access to it's bcdedit... ... or is it?

ShellExecute,Hide,#$q%TargetDir%\Windows\System32\bcdedit.exe#$q,"/store #$q%TargetDir%\boot\bcd#$q /set {default} device ramdisk=[boot]\vistape.wim#$c{7619dcc8-fafe-11d9-b411-000476eba25f}","%WindowsDir%\system32"



ShellExecute,Hide,#$q%TargetDir%\Windows\System32\bcdedit.exe#$q,"/store #$q%TargetDir%\boot\bcd#$q /set {default} osdevice ramdisk=[boot]\vistape.wim#$c{7619dcc8-fafe-11d9-b411-000476eba25f}","%WindowsDir%\system32"

Regards

[dera]

... or is it?

No

[PaPeuser]

I know I get bcdedi.exe errors

Boot\WimSrc\windows\system32\bcdedit.exe
and
syatem32\en-US\bcdedit.exemui

Clean load no apps or anything I get 5

I read in here some where ,, because i use both Vista DVD as source and WAIK some files are copied over once and not second time,, as in language files, and some boot stuff
Winbuilder just gives me a warning that these files could not be copied over

Because they already exist? Does that make any sense

You do the script stuff ,,, i just test ,,,,

on my way over to my that new project ,, pe21.003..

[allanf]

Because they already exist? Does that make any sense

Yes. That's what I was wondering... Where do the existing ones come from and what is the source of the ones trying to be copied? Same? Or could this lead to some sort of version conflict?

A log may help, rather than going through all the scripts.

I've seen this error before. PaPeuser, Have you? I even had a log downloaded with the title 'exception_handle....' (?), but recently trashed it. I'm not sure if that log showed anything useful tho.

Regards

[PaPeuser]

Yes i have seen that error before I THOUGHT it had to do with antivirus
I think my AVG gave a warning,,, and build failed ---I cant remember either,,
BUT jaclaz asked him in second post about having any antivirus running

[PaPeuser]

http://www.boot-land...p;hl=msvcrt.dll

read this,

I need to keep better notes,, i should have remembered this ,,,

[allanf]

http://www.boot-land...p;hl=msvcrt.dll

read this,

I need to keep better notes,, i should have remembered this ,,,

Thanks for finding it.

But the mystery still remains. Why does it happen? And why didn't it happen earlier for patsch? I can only speculate.

Regards

[PaPeuser]

some people call it


Now that we know what to tell him I hope he comes back after he gets his computer reloaded,

[allanf]

@patsch

To see if bcdedit is actually functional, you could try adding the following to the postconfig script - somewhere near the other bcdedit lines, making sure that it's in a script [Section] that will be run.

It opens a cmd window and simply enumerates entries in the Target Directory's BCD store. (The /enum switch is not really required because it's bcdedit's default operation.) Cllose the opened window to continue the build.

ShellExecute,Open,"cmd.exe","/k %TargetDir%\Windows\System32\bcdedit.exe /store #$q%TargetDir%\boot\bcd#$q /enum"

Then there's that strange argument that could be stuck on the end of the line - perhaps add a second line with it when editing the script to see if there is a difference in the output.

,"%WindowsDir%\system32"

... including the comma.

Regards

[PaPeuser]

Thanks I will give that a try

Right now I am working with the recommended down load and trying to find out why a recommended download will not boot with default settings,

It has something to do with a script in ADDons ,, I just have not figured out which one is the problem yet.

Good thing for VMware

[allanf]

It has something to do with a script in ADDons ,, I just have not figured out which one is the problem yet.

I see that MapNetworkDrive is in AddOns. It has been identified in the forums as causing some trouble with AntiVirus - purely because it's AutIT, I think. An AV with it's sights set on it will prevent imagex/wimutil from capturing the Target Directory to vistape.wim.

(Lost your notes again? ... ...)

Regards

[PaPeuser]

Notes - I had so many notes I could not find anything,, so I started over

I think the problem is more than one script ,, which makes it harder to figure out

But then a recommended Vistape builds fast

yes
map network drive and maybe MMC, PnetCfg and Windows Vista recovery env

the other 5 test and build ok

[PaPeuser]

Ok,

Downloading winbuilder from
http://winbuilder.ne...oad.php?view.37

When Winbuilder is launched it will automatically go to a download page
If first Vistape server is selected a recommended download will happen
Under ADDons uncheck map Network drives
This should build without error and boot,

If you go back to download center and do a complete download of VistaPE (RC1)
Sometimes
Network\LanSpy will error and stop build (download server problem) uncheck and build again
Other OS\Parted Magic may error but not stop build
I found that by unchecking APPs\Disk Tools\Victoria 4.3 freeware (Beta version) worked and VistaPE booted first time

If these scripts are not disabled at build time you will get a Build Successfull message in Winbuilder
BUT
You will also get a boot error when you try to boot VistaPE (RC1)

Tested with Vista SP0 source and WAIK 1.1 installed
It would be nice to have someone else verify this.
edited because

[patsch]

ok, I think I found the reason for my error concerning msvcrt.dll.
the "_except_handler4_common" is only part of the Vista version of msvcrt.dll , not part of the xp-version. Even with WAIK and CRT8 redist. installed this error occurs on my XP-machine
I don't know why this did not happened before ... i'll now try building under Vista