1166 replies to this topic

[linuxbaby]

Here the download-links for my logfile:

the copy option is "full"

http://www.file-uplo...15308.html.html

Thanks very much for help.

Edited by linuxbaby, 21 January 2011 - 09:14 PM.

[linuxbaby]

no one can help?

Linus

[al_jo]

no one can help?

Linus

Try deselect ”Run ISO in VMware” and build again.
Run the new iso in VMware and see if you get the same message.

[linuxbaby]

Thanks for the answer.

It is the same error without ”Run ISO in VMware”

Anyway, I'm waiting soon for the new version of Peter.

[Marco Marro]

Hi Linuxbaby.
I don't know but, if the system return error to find HID.DLL maybe that HID.DLL is missing.
Where is place "HID.DLL" ? in "X:\Windows\System32\Hid.dll" and "X:\Windows\System32\it-IT\Hid.dll.mui" the language version (it-IT can change in local en-US, es-ES etc..)
Try this procedure (after yoh have compiled version and before burn iso)

1- Find GIMAGEX.EXE, lauch it, -> (tab) MOUNT -> Mount Point: D:\MOUNT (must be empty folder ) -> Source: Your WIM file -> x Read and Write than -> "Mount".
2- Copy file C:\Windows\System32\Hid.dll to target dir (D:\MOUNT\Windows\System32) and relative file C:\Windows\System32\en-US\Hid.dll.mui to (D:\MOUNT\Windows\System32\en-US\)
3- In GIMAGEX check box "Commit Changes" and click Unmount
4- Create ISO and have fun.

You can also modify the "1-files.script" and insert properly line for copy the 2 system file.

[al_jo]

Thanks for the answer.

It is the same error without ”Run ISO in VMware”

Anyway, I'm waiting soon for the new version of Peter.

You can also try in config.script to choose 4

Attached Thumbnails

• 

[pscEx]

Thanks for the answer.

It is the same error without ”Run ISO in VMware”

Anyway, I'm waiting soon for the new version of Peter.

Sorry, I forgot to report:

I did a Win7Rescue minimum build (no additional apps).
Here the error did not appear.

Maybe Al_Jo's last answer is important. I have the 4 in my build, too.
But maybe there is only one special app needing the dll in question.
And here you have the (Sorry, German) "Schwarzen Peter". To find the app by adding / removing apps from the build, you can do as well as me.

Peter

[linuxbaby]

You can also try in config.script to choose 4

That's it. Thank you very much

[linuxbaby]

And here you have the (Sorry, German) "Schwarzen Peter". To find the app by adding / removing apps from the build, you can do as well as me.

Peter

Thanks for the answer. All my active Apps works fine and i doesn't have more problems.

[tgparker2010]

I'm a relative noob to winbuilder and even though this is an "inactive" project it was one of the first Winbuilder projects that I undertook a couple of years ago. I followed the directions EXACTLY and I was pleasantly surprised how it all came together and I even managed to get it onto one of my USD flash drives.

I have recently taken up using Winbuilder again and have been experimenting with different LiveXp and Win7PE winbuilder projects.

For some reason I just couldn't get the now "inactive" Win7PE Rescue 13 project to load properly. I got all the same errors that everyone else has been complaining of.

I reread the original documentation, and I realized my problem.

During the intervening 2 years I had removerd the Vista WAIK program suite installed the Win7 WAIK program suite on my XP SP3 System. The Win7 WAIK on XP SP3 was the source of all my problems with Win7PE Rescue project script. I have since removed the Win7 WAIK and returned to the Vista WAIK and the Win7PE Rescue script ran perfectly smnoothly just the way it did 2 years ago..

[sbaeder]

Just be carefule here, since it is a known issue that the vista WAIK works with the initial release ONLY... Do NOT try to use SP1. there were changes in the internal WIM that are not handled well by the vista version. Other than that, if you are Happy, GREAT!

[tgparker2010]

Thanks for your response. Will that version of (Vista) WAIK work with WIN7PE_SE? Or do I have to upgrade to the Win7 WAIK?

[pscEx]

Mounting *.WIM with ImageX is (with same parameters) independent from the Win7 project. Therefore Scott's statement is very propably valid also for Win7PE_SE.

BTW: In multiPE (Win7 track) I also recommend to use the initial Win7 source CD, no SP1.

Peter

[sbaeder]

Yes, and in fact, that project (win7PE_SE) has code to help detect which tools to use - there are lots of other threads here on all of that - AND, what I always recommend, which is tto extract thee WIM. Yes, it adds to the "footprint" (disk space required to to a build), but it is a more stable means of accessing the wiim contents that always seems to work around the unique problems we have seen reported here).

Bottom line is that if your happy with the older projects or the older versions of Win7 as the base, then use them. If you want to stay on the bleeding edge, then you have to use the newer versions of the tools and sources...To each their own! (I love having choices!)

Scott

[Wonko the Sane]

To each their own! (I love having choices!)

Having functional/working choices being a plus....


Wonko

[pscEx]

... project (win7PE_SE) has code to help detect which tools to use ...

Just for the record:
multiPE has also code to help...
In addition it has an option 'Auto' which makes the best (?) choice for the user.

Peter

[sbaeder]

@wonko - yes! always better when they work correctly

@pscEx - yes, MultiPE is an excellent project as well (another Functional choice)...

Best of wishes to both of you!