Jump to content











Photo
- - - - -

Win7PE cant get it to finish building

i am new to this win7pe

  • Please log in to reply
10 replies to this topic

#1 Stephen Traiforos

Stephen Traiforos
  • Members
  • 2 posts

Posted 30 March 2012 - 09:53 PM

Hi I am having trouble with win7PE(building x64 with my win7 64bit OEM DVD) I try to build it and it gets to the last part and give me the error:

You can get my log on my website: http://digitaleyepc....330_171913.html

I am new to all of this i already built windows pe but it has no good functionality.

Than ks for your time,

Stephen T.

#2 pscEx

pscEx

    Platinum Member

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

Posted 01 April 2012 - 03:23 PM

Hi I am having trouble with win7PE(building x64 with my win7 64bit OEM DVD) I try to build it and it gets to the last part and give me the error:

Following the log, the project decided that the source CD is x86! :wodoo:

Peter

#3 Stephen Traiforos

Stephen Traiforos
  • Members
  • 2 posts

Posted 01 April 2012 - 05:28 PM

hi i used a 64bit windows haha woops last time i used the wrong one haha but i tried it with the right CD and it gave me the same error but with x64 instead of x86

http://digitaleyepc....401_132856.html i have no idea what i am doing wrong other than my stupid mistake because i followed the tutorials and put the right files in so i don't know

Edited by Stephen Traiforos, 01 April 2012 - 05:31 PM.


#4 patsch

patsch

    Silver Member

  • Advanced user
  • 778 posts
  •  
    Germany

Posted 01 April 2012 - 05:55 PM

do you have a program open that blocks creating your cd? Like an antivirus or antimalware prog? Last time I had that fault my version control system (GIT) was running and stopped wb from creating my iso
Do you use wb with admin rights?

#5 ChrisR

ChrisR

    Silver Member

  • .script developer
  • 783 posts
  •  
    France

Posted 02 April 2012 - 05:46 PM

Everything seems OK in building except the creation of the iso at the end !
When you are at this step, in the script "Finals4 - Create ISO" you can try the button "Create new ISO file"

You can try also manually with a small batch (for grub4dos) to put in Base directory in this example


set pedir=%~dp0

set project=Win7PE_SE

set mkisofs=%pedir%ProjectsTools%project%mkisofs.exe

set ISO=%pedir%ISOWin7PE_x64.ISO

Set Target=%pedir%Target%project%



"%mkisofs%" -iso-level 4 -l -J -joliet-long -R -volid "Win7PE" -A "GRLDR/MKISOFS" -sysid "Win32" -b "Boot/grldr" -no-emul-boot -boot-load-size 4 -hide boot.catalog -duplicates-once -o "%ISO%" "%Target%"

pause



#6 pscEx

pscEx

    Platinum Member

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

Posted 02 April 2012 - 07:47 PM

mkisofs is case sensitive!
In the older mkisofs.exe which I know, UC / LC discrepancies of file names, paths, e.g. in the -b switch, lead to an ISO size of 34 kb.

Maybe newer versions in case of LC / UC discrepancies do not produce any ISO.

Peter

#7 sbaeder

sbaeder

    Gold Member

  • .script developer
  • 1,283 posts
  • Location:usa - massachusettes
  •  
    United States

Posted 03 April 2012 - 03:59 PM

I also had an issue the other day after I had upgraded all the files from the server. There seems to be a newer version of mkisofs.exe that needs a cygnus dll (If I recall, it is the cygwin1.dll). Going to another mkisofs.exe from another project solved that issue...

ChrisR...Please check into this...

Stephen...Did you try the manual approach listed above by Chris? Try that and see what you get for output...My guess is that this is the issue? Did you use just the downloaded set of files, or did you do an updated/download from the server?

Another quick check is to just double click on the exe...if you have the missing DLL, you will get an error dialog...(of course, clicking on it doesn't really do anything useful, but it does check to see if all the dlls are available.

#8 sbaeder

sbaeder

    Gold Member

  • .script developer
  • 1,283 posts
  • Location:usa - massachusettes
  •  
    United States

Posted 03 April 2012 - 05:39 PM

OK, it looks like the version in the latest version archive posted in the pinned thread is OK (Win7PE_SE_20120216_Small) but the one on the server (accessd by the downloads button) is incorrect. So go back to the one in the archive, and you should be OK to go...In the mean time, I am poking around on the cdrtools web site to see what's up...

Found links in searching to this posting (http://reboot.pro/16...post__p__145039 ) where WONKO clearly id's the issue - two ways to build the tools, and also looked around and found link to this site ( http://www.student.t...t/thomas.plank/) that has a zip of all the binaries already compiled - BUT without the other dlls...

In accessing the exe's and using the -version command, I see they are both 2.01, but the newest one on the server is an "a66 variant, and as wonko pointed out, built with cygwin, and not mingw...

A bit more searching, and I found this link (http://opensourcepac...ngw-binary.html) that has a mingw version of the latest/greatest version! BUT...It doesn't like the -force-uppercase option :dubbio: They must have changed it somewhere along the way......

Using the all linked into one exe might be a better approach, but at least you should be able to move forward, (either grab the older version out of the posted archive - RECOMMENDED, or grab the DLL's from that site above, or the new all in one from that last link) and we can work to "fix" up the win7PE_SE server...

:cheers:
Scott

Edited by sbaeder, 03 April 2012 - 08:58 PM.
add info/link to mingw based current 3.01 version


#9 ChrisR

ChrisR

    Silver Member

  • .script developer
  • 783 posts
  •  
    France

Posted 03 April 2012 - 09:44 PM

A bit more searching, and I found this link (http://opensourcepac...ngw-binary.html) that has a mingw version of the latest/greatest version! BUT...It doesn't like the -force-uppercase option :dubbio: They must have changed it somewhere along the way......

It doesn't like the -duplicates-once option too, not a good choice ;).



Oups, apparently I made a mistake on mkisofs version on the server after many tests I've done :blush:

Story:
The old and previous version worked well but only with files less than 2Gb.

I changed mkisofs version following a comment of patsch http://reboot.pro/16...post__p__150739
and a comment of livedude http://reboot.pro/16...post__p__151461

And after several test and the support of cdob, I chose a Mingw32 version which seems to work properly with files up to 4 GB (sufficient for all windows installation Iso) http://fy.chalmers.s...RW/tools/win32/ :thumbsup:

There are also other cygwin verions that works fine but additional components are required cygwin1.dll, ... and additional Kb.
some links provided by cdob http://reboot.pro/16...post__p__151462


For info, according to my tests, all these versions are case sensitive and here "Boot/grldr" is OK.


I Updated the server with mkisofs.exe (Mingw32 4GB) from http://fy.chalmers.s...n32/mkisofs.exe
and for now I keep the previous version of the project (Mingw32 2GB) renamed in mkisoforg.exe.

ps: I do not know why, but currently I am not receiving email notifications !!!

Regards
:cheers:

#10 cdob

cdob

    Silver Member

  • Expert
  • 902 posts

Posted 03 April 2012 - 09:47 PM

A bit more searching, and I found this link (http://opensourcepac...ngw-binary.html) that has a mingw version of the latest/greatest version!

That's a broken release: output path may not be parent of source path
Most current developments are not supported too, no fseeko() support.
In addition: read files are limited to 2gb.

Does anybody knows a full working current mingw version?

BUT...It doesn't like the -force-uppercase option

Yes, that's based on official sources.
-force-uppercase and duplicates-once are note supported.


At any rate, to debug a issue.
store real used command line to the log file.
And store output messages to a the log file.

We are guessing currently. More messages are required.

#11 sbaeder

sbaeder

    Gold Member

  • .script developer
  • 1,283 posts
  • Location:usa - massachusettes
  •  
    United States

Posted 04 April 2012 - 05:55 PM

Thanks Chris...I was pretty sure that it was the version on the server as the root cause...Looks like over the years the source has had a lot of changes and it would be good to find a working "superset" already compiled for us :) But at least we shoul dhave things back to functional...I'll double check things.

Not sure why the notifications aren't working for you, but with the server maintenance this weekend, maybe it will be working after that? At least we should wait until then to check it out.

Hope your having a good "spring"...

:cheers:
Scott




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users