Jump to content











Photo
- - - - -

080 bug: nativeEx7: with x86 source dvd, it fails to build at all; with x64 dvd, hal missing or corrupt when booting the iso


  • This topic is locked This topic is locked
17 replies to this topic

#1 techvslife

techvslife

    Member

  • Members
  • 77 posts
  •  
    United States

Posted 07 April 2010 - 09:02 PM

ok, I successfully created a boot iso with latest nativeEx_win7 and winbuilder 080, on win 7 x64 using a win 7 x64 dvd (ultimate).
however, it won't boot.
I get this error:
windows\system32\hal.dll
HAL is missing or corrupt.
0xc000000f

I am using bitlocker but that doesn't prevent the original win7 installation disk from booting after getting the key. Anyway, perhaps nativeExwin7 has trouble with hal.dll off of the dvd.

If you want to see the debug log for the build that produces the iso that gives this hal error, see this post:
http://www.boot-land...?...ost&p=97210

Thank you.

p.s. to avoid a waste of support time here, note that it's possible that I didn't have the right options checked in winbuilder for nativeex7, but it did build the iso successfully. perhaps I was supposed to download something else or check options for rescuepecd also (or build that first, but there are bugs that had prevented rescuepe project from building, as noted in the other thread)?
so perhaps something basic I'm doing wrong.

#2 patsch

patsch

    Silver Member

  • Advanced user
  • 785 posts
  •  
    Germany

Posted 07 April 2010 - 10:33 PM

using a win 7 x64 dvd (ultimate).

the only project that allows 64Bit as source is afaik win7pe ... so try to build with a 32bit version as source

#3 techvslife

techvslife

    Member

  • Members
  • 77 posts
  •  
    United States

Posted 07 April 2010 - 11:31 PM

That was covered in the last message of my other thread (observation #5): from x64, it won't allow you to build on the x86 version (doesn't like the x86 dvd), so I was forced to go to the x64 dvd.

a. Here is the message box I get with an x86 win7 installation dvd in the drive after pressing
getinfo for nativeEx7: (I've attached the log report that happens after pressing GetInfo).
---------------------------
Error
---------------------------
Something wrong with your source CD: File install.wim: Error 2
---------------------------
OK
---------------------------

b. When I load the microsoft win7 rtm iso as a virtual drive (ultraiso emulator), I get a different error:
[Window Title]
WimInfo.exe
[Main Instruction]
WimInfo.exe has stopped working
[Content]
Windows is checking for a solution to the problem...
[Cancel]

Then:
---------------------------
Error
---------------------------
Something wrong with your source CD: File install.wim: Error 255
---------------------------
OK
---------------------------

c. Finally, if I extract the files from the original ms win7 x86 iso to a folder in the hard drive, and use that as a source, then I get no errors from getinfo. But getinfo does not show any entry under "install.wim" (doesn't show enterprise, ultimate, etc.), though it does update the language from german to english (en-US). in this case winbuilder still cannot build a nativeEx iso.

To clarify: in no case can winbuilder 080 build, or even start building, a nativeEx iso when the source is an original ms win7 x86 dvd/iso.

Attached Files



#4 techvslife

techvslife

    Member

  • Members
  • 77 posts
  •  
    United States

Posted 08 April 2010 - 01:03 AM

trying manual install, as per instructions at bottom of
Winbuilder\Projects\Tools\nativeEx\WimCaptEx.htm:

Manual installation of necessary files: (check path names!)
•Use 7z to extract from Boot.wim
!!! 7z.exe must be version 4.65 or higher !!!
◦7z e -y "-oC:\WINDOWS\System32" -r "<source CD>\sources\boot.wim" "2\Windows\System32\wimgapi.dll"
◦7z e -y "-oC:\WINDOWS\System32\Drivers" -r "<source CD>\sources\boot.wim" "2\Windows\System32\drivers\wimmount.sys"
◦7z e -y "-oC:\WINDOWS\System32" -r "<source CD>\sources\boot.wim" "2\Windows\System32\wimserv.exe"
•Apply (check before!) registry changes: http://nativeex.boot...Ex/wimmount.zip
•Download the WimCaptEx package and extract the appropriate 32 / 64 bit version as WimCaptEx.exe


First step (7z extractions) works fine.

Second step (merging reg entries in wimmount.zip) works for second reg file (wimmmount_service.reg), but fails with first reg file (wimmmount_legacy.reg).
Error thrown is:
[Window Title]
Registry Editor
[Content]
Cannot import C:\wimmmount_legacy.reg: Error accessing the registry.
Update: never resolved.

Third step: not sure what folder I'm supposed to use (where is the tools folder?), or what is the "appropriate" file (x86 because the source is x86? or x64 b/c the pc that is building the iso is x64?)
update: used same folder that WinCaptEx.htm and WimCaptEx_64 and _86 were in. copied wimCaptEx_64.exe as wimCaptEx.exe. This made no difference--exact same bug and error messages.

#5 paraglider

paraglider

    Gold Member

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

Posted 08 April 2010 - 04:02 AM

When running on win7 no need to install anything as the service / driver is built into the OS. You must explicitly elevate i.e. run as administrator otherwise the mount will fail.

wimcaptex runs fine on win7 x64, as long as you run it elevated as an administrator, and can mount both x86 and x64 win7 sources. You run the x64 version on 64bit os.

#6 techvslife

techvslife

    Member

  • Members
  • 77 posts
  •  
    United States

Posted 08 April 2010 - 04:20 AM

thanks. I don't run wincaptex or explicitly mount anything; I just run winbuilder which presumably runs it for me in some script somewhere. But winbuilder is already running elevated, and therefore so should anything it calls, and I still have this problem.

p.s. wincaptex goes in the same folder that wincaptex.htm is in?
i.e.:
Winbuilder\Projects\Tools\nativeEx\

I'm still getting this error after pressing getinfo with an x86 win 7 dvd install disk in the drive (but not with an x64 disk. otoh the x64 disk as source produces an iso that causes the hal error on boot):
---------------------------
Error
---------------------------
Something wrong with your source CD: File install.wim: Error 2

#7 patsch

patsch

    Silver Member

  • Advanced user
  • 785 posts
  •  
    Germany

Posted 08 April 2010 - 08:04 AM

I'm confused a little bit ...

Finally, if I extract the files from the iso to a folder in the hard drive, and use that as a source, then I get no errors

you have to use a win7-dvd as source or you have to copy the full content of the dvd/iso to a folder on your hard drive. Your source must be a valid source, not modified in any way like updates, driver integration etc. otherwise it will not work

As paraglider already mentioned: you do not have to copy or run anything to get the project work, simply run winbuilder as administrator

#8 techvslife

techvslife

    Member

  • Members
  • 77 posts
  •  
    United States

Posted 08 April 2010 - 11:39 AM

Yes, I am using win7-install-dvd/iso as a source.

you do not have to copy or run anything to get the project work, simply run winbuilder as administrator

It failed just running winbuilder (winbuilder always runs after elevation as a full admin). Therefore I tried to follow the special manual install instructions for wimcaptex. The error messages strongly suggest a problem with the wim loading system. (Probably some bug when loading an x86 wim on an x64 system? don't know if that makes any technical sense--i'm trying to speculate from my tests so far.)

Sorry for the confusion:

1. winbuilder/nativeEx7 always completes a build when win7 x64 is the source (the source is: original ms rtm iso of win7 x64). Note: though the winbuilder/nativeEx iso gets built in this case, that iso fails to boot with the hal error. Probably nativeEx should not allow the creation of an unbootable iso (i.e. when x64 is the source for the build).

2. With the ms rtm win7 x86 installation dvd/iso as a source, it always fails even to build the winbuilder/nativeEx iso.
--a. it fails when the source is the x86 win7 dvd in the drive.
--b. it fails when the source is the x86 ms win7 iso (i.e. the microsoft rtm iso of win7 x86) mounted virtually as a drive.
--c. it fails when the source is the x86 win7 iso extracted to a folder in the drive.
Pressing getinfo always results in some sort of error in case #2, except in 2c the error is not a message box, but a blank box under the "install.wim" selection (i..e doesn't show enterprise ultimate etc.). In case #2 the iso never builds--never even starts to build.

In no case have the source isos been altered from microsoft; they are the original isos from microsoft, md5 checked and all. They have never produced any errors except the ones by winbuilder/nativeEx7 now discussed in this post.

I confirmed just a few minutes ago that the x86 dvd that I am using as the source boots fine on my machine (loads windows setup and recovery tools). It seems likely to me that there's a bug in winbuilder 080 or nativeEx7 when building win7 on x64--using any source version, x64 or x86.

In all cases I have been running winbuilder as an administrator. (winbuilder 080 is marked to automatically require and request elevation anyway, and I do elevate it.)

p.s. in the alternative, just in case this bug will take some weeks to get fixed (and since I've already tried "win7rescuepe" and "nativeEx7" projects), does anyone know if the "win7pe" project supports the same scripts (besides a genuine win7 or pe3.0 boot for bitlocker decrypt, I need truecrypt, ultraiso, 7-zip, and terabyte / image for windows)? or is that not advisable. thanks.

#9 techvslife

techvslife

    Member

  • Members
  • 77 posts
  •  
    United States

Posted 09 April 2010 - 04:35 PM

To clear up what's been happening, I'm posting a summary with logs.
Note that having an x64 dvd as the source will allow nativeEx7/wb80 to build successfully, but the iso that results from that build will not boot (the "hal missing or corrupt"). So the following is about x86 as the source dvd.

In this post:
Using: winbuilder 80.
Source: x86 (original microsoft win7 x86 installation dvd).
Project: NativeEx7.
(Always building on my x64 laptop: win7 x64.)

Before building, I delete the contents of the \winbuilder\temp folder.
Before building, I do the "get info" routine:
Get info under "ImageIndexX" submenu:
Does NOT pick up or show UPDATED source information
(it shows either a blank or the last (outdated) information I had,
which was from an x64 source dvd.)
Pressing "Get Info" produces this error message:
>Something wrong with your source CD: File install.wim: Error 2

If one ignores and tries to build anyway,
it does start to build but won't finish.
The build process triggers two error messages:
>Something wrong with your source CD: File install.wim: Error 2

Then (at step 7: BaseBuildEx), it gives the following error:
----
Access violation at address 004041F2 in module 'WinBuilder.exe'. Read of address 3F0028E8: Run,%ImageIndexScript%,Halt,Something#$swrong#$swith#$syour#$ssource#$sCD:#$sFile#$sinstall.wim:#$sError#$s%ExitCode%
----
Log attached.

Attached Files



#10 techvslife

techvslife

    Member

  • Members
  • 77 posts
  •  
    United States

Posted 09 April 2010 - 04:54 PM

In this post:
Using: winbuilder 80.
Source: x86 (original microsoft win7 x86 installation dvd).
Project: Win7rescuepe v.13.
(Always building on my x64 laptop: win7 x64.)

Before building, I delete the contents of the \winbuilder\temp folder.
Before building, I do the "get info" routine:
Get info under "Build, Preconfig" submenu shows:
Language is correct (en-US) and path to waik is correct.
Shows install.wim as Windows7 "enterprise" (no "ultimate" option).
--that may or may not be correct.

Pressing "Get Info" produces no error messages.
Pressing the little green arrow in this "preconfig" section
does produce this error:
---
Information
Mount Win7 boot.wim files with imagex.exe returned with 2
---

If one ignores and tries to build anyway,
it does start to build but won't finish.
The build process triggers three error messages
at step 4 (preconfig section):
1. Mount Win7 boot.wim files with imagex.exe returned with 2
2. Error: Please run PreConfig script. Exiting...
3. Error:
Access violation at address 004041F2 in module 'WinBuilder.exe'.
Read of address 3F0028E8: Run,%API%,NotConfigured

Log attached.

Attached Files



#11 patsch

patsch

    Silver Member

  • Advanced user
  • 785 posts
  •  
    Germany

Posted 09 April 2010 - 05:02 PM

Note that having an x64 dvd as the source will allow nativeEx7/wb80 to build successfully, but the iso that results from that build will not boot (the "hal missing or corrupt").

sorry, but I don't know what to write more ... no 64bit as source is supportet in win7rescuepe and nativeEx_win7 ... "hal missing" is one of the typical faults

It seems likely to me that there's a bug in winbuilder 080 or nativeEx7 when building win7 on x64--using any source version, x64 or x86.

no ...
my host : win7 prof 64bit
my sources : win7 prof 32bit (special version from my university), win7 ultimate 32bit, win7 enterprise 32bit (evaluation version that is free downloadable from microsoft, 90 days trial).

in a special case I had an access violation fault with win7rescuepe but I know what to do and this fault will be fixed with next version of wb.
I never had the "error 2" with neither win7rescuepe nor nativeEx_win7

what I noticed in my circle of friends:
- source was not valid even with correct checksum (nearly always the prof version from our university, but these versions work well for installation)
- some problems with UAC in vista and win7 (advice to deactivate during build)
- some problems with antivir software (advice to deactivate during build)
- some problems with app scripts written by myself, but that is not necessary for the build from scratch without apps

If you do not get a result in "get info" I assume that your source is not valid ... do you have the possibility to try another win7 version? perhaps the evaluation enterprise version?

#12 techvslife

techvslife

    Member

  • Members
  • 77 posts
  •  
    United States

Posted 09 April 2010 - 05:45 PM

Thanks.
1. The problem with x64 as a source is that ALLOWS you to build an x64 iso (no error message). So it should give an error message (or it should produce a correct bootable iso).
2. Don't have access to another source but it is a valid x86 win7 dvd, direct from microsoft msdn, correct md5 matching, and bootable and operational, and has been used to install win7 without issue.
3. I'll try the uac and av suggestions.

#13 patsch

patsch

    Silver Member

  • Advanced user
  • 785 posts
  •  
    Germany

Posted 09 April 2010 - 05:55 PM

2. Don't have access to another source but it is a valid x86 win7 dvd, direct from microsoft msdn, correct md5 matching, and bootable and operational, and has been used to install win7 without issue.

yes, for some of my friends too (valid source, installation possible), but there exist some problems ... therefore change of source (don't you have the posibility to download the win7 trial from microsoft?)

#14 techvslife

techvslife

    Member

  • Members
  • 77 posts
  •  
    United States

Posted 09 April 2010 - 06:41 PM

changing UAC and av made no difference: same error messages.

(don't you have the posibility to download the win7 trial from microsoft?)


I thought it had to be full, not an eval/trial version. What download link in microsoft provides a trial version that can work with winbuilder?

#15 patsch

patsch

    Silver Member

  • Advanced user
  • 785 posts
  •  
    Germany

Posted 09 April 2010 - 06:46 PM

changing UAC and av made no difference: same error messages.



I thought it had to be full, not an eval/trial version. What download link in microsoft provides a trial version that can work with winbuilder?

I tested with this version
http://technet.micro...r/cc442495.aspx
(tested german and english version)

#16 techvslife

techvslife

    Member

  • Members
  • 77 posts
  •  
    United States

Posted 10 April 2010 - 05:45 AM

Using winbuilder080:
This is a report on the failure of Multi7 pe to build win7 x64 on a win7 x64 system.

Note that although I got all "needed files" to build, the documentation on "needed files" is poor, and I may have gotten the wrong versions. I picked the 64 bit version where there was an ambiguity and I could find an x64 version. (special note: I couldn't find "fltmgr.inf" on my system, so I used a win2000 version of that.)
See this post:
http://www.boot-land...?...ost&p=97463

Trying to building multi7 x64 pe results in several errors:
1. Error with mounting source!
2. Error with mounting Boot.wim!
3. 'Halt' is not a valid integer value: message,Install.wim#$sfile#$snot#$smounted,#$scheck#$splease!,Halt
4. 'Halt' is not a valid integer value: message,Explorer#$sfile#$scan't#$sbe#$sfound#$sin#$sTargetDir,#$sCheck#$splease!,Halt

Detailed log is attached.

Attached Files



#17 techvslife

techvslife

    Member

  • Members
  • 77 posts
  •  
    United States

Posted 10 April 2010 - 07:39 AM

I tested with this version
http://technet.micro...r/cc442495.aspx
(tested german and english version)


ok, thanks. I was able to get an x86 iso to build using NativeEx7 (haven't tested booting yet). However, it was not enough to switch to your linked eval source, since that still produced these errors:

1&#58;

---

WimCaptEx Program version 4.1.1

Copyright &#40;C&#41; 2009, 2010 Peter Schlang

Found wimgapi.dll version 6.1.7600.16385

Found wimserv.exe version 6.1.7600.16385

wimmount service is detected

Found wimmount.sys version 6.1.7600.16385

WimCaptEx.exe -A&#58;A -W&#58;G&#58;\sources\Install.wim -I&#58;4 

	-D&#58;C&#58;\Winbuilder\Workbench\nativeEx_Win7\Cache\4I4en9617600 -P 

	-T&#58;C&#58;\Winbuilder\Temp\nativeEx_Win7

3&#58; Error capturing image

Error occurred

Press <Return> to finish ...

---



2&#58; Error loading image.

But turning Disabledot8.3NameCreation off seems to have done the trick (or conceivably merely the reboot required in doing that was the cause), along with using the ms x86 eval version rather than ms x86 rtm. I'm not sure what the cause really was. I'll do some more tests and see what the issues still are.

#18 techvslife

techvslife

    Member

  • Members
  • 77 posts
  •  
    United States

Posted 11 April 2010 - 04:00 AM

Have tested nativeEx7 win7 x86 building and booting using eval version of x86 win7, and with uac on and no 8dot3 name creation.
Things seem to be working now. Will report comments in other thread; closing this one.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users