Jump to content











Photo
- - - - -

iso compiles but runs windows setup, not the project


  • Please log in to reply
8 replies to this topic

#1 seanpowell

seanpowell
  • Members
  • 3 posts
  •  
    Australia

Posted 25 July 2014 - 04:33 AM

Hi there,

I am trying to compile an ISO of MistyPE's WinFE project using WinBuilder 082.  I have unselected all options other than wallpaper and ftk for this attempt.

 

My source is Win7 Ultimate 32bit.  The process completes ok and generates my iso which I have written to a usb using Rufus.  Testing it on boot up, it boots from the usb but loads to a Windows 7 setup screen as though it has recreated the source iso rather than building a new one from the project.  The logs are a little mysterious to me but I couldn't locate the cause in there.  I have also attempted using a Win7 64 bit and Win 8.1 64 bit source with the same result (ie, loads to windows setup).

 

A copy of the log is here - https://www.mediafir...37zua/Documents

 

Any help gratefully accepted.  If there is other information needed, please let me know.

 

thanks



#2 pscEx

pscEx

    Platinum Member

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

Posted 25 July 2014 - 07:19 AM

Let's first check whether the issue is generated by the project, or by Rufus.

 

Burn a physical CD and boot from it. When it has the same issue, the project is the originator.

When it boots well, Rufus is the bad boy.

 

Peter



#3 misty

misty

    Silver Member

  • Developer
  • 703 posts
  •  
    United Kingdom

Posted 25 July 2014 - 07:34 AM

@seanpowell
I don't recall having seen the warnings referenced in your log file before, however these don't appear to have stopped the build from completing successfully.

I ran a quick test. When duplicating your directory structure (obtained from your log)...
C:\_Forensic_Boot_Disk_ISO's\WinFE_Builder\
...the buld appeared to complete successfully, however the build files were not actually injected into boot.wim

I ran another test using a slightly edited path - C:\_Forensic_Boot_Disk_ISO\WinFE_Builder\ (note the omission of 's in the path). This time the build completed successfully and the files were injected into boot.wim.

This could be due to WinBuilder, or my code, or possibly wimlib not liking the use of ' in the path. I'll check this out when I have time.

Regards,

Misty

#4 seanpowell

seanpowell
  • Members
  • 3 posts
  •  
    Australia

Posted 25 July 2014 - 07:37 AM

Misty - I didn't think of the apostrophe as a potential cause of error - I did change folder names to remove spaces after seeing some other posts about that as a cause.  That will be a simple test - I will try it and post back...



#5 seanpowell

seanpowell
  • Members
  • 3 posts
  •  
    Australia

Posted 25 July 2014 - 07:55 AM

ok, that did the trick - who knew!  I took the apostrophe out of the path location of winbuilder and it booted up correctly.  Didn't replace the background for some reason, but the only other thing I had specified for the initial attempt was ftk, which loads.  Thanks very much for the super-prompt assistance, both Peter and Misty.  I will try and add a few things in and play around with it a bit more... 



#6 misty

misty

    Silver Member

  • Developer
  • 703 posts
  •  
    United Kingdom

Posted 25 July 2014 - 08:06 AM

Glad it worked. If you have any other problems I'd recommend posting in the project support thread for Mini-WinFE (here).

#7 misty

misty

    Silver Member

  • Developer
  • 703 posts
  •  
    United Kingdom

Posted 26 July 2014 - 06:07 AM

@seanpowell
I've checked and the issue is due to the wimlib-imagex command line syntax. In order to support spaces, the update add command requires the path be preceeded and ended with apostrophes/single quotes (see here) - e.g. -
wimlib-imagex.exe update boot.wim 2 --command="add 'C:\_Forensic_Boot_Disk_ISO' '\'"
Using a path with an aposthrophe a single quote in it such as C:\_Forensic_Boot_Disk_ISO's would result in the following command being passed to wimlib-imagex when running the project -
wimlib-imagex.exe update boot.wim 2 --command="add 'C:\_Forensic_Boot_Disk_ISO's' '\'"
This results in the following error -
ERROR: Unexpected argument "\" in update command on line 1
       (The "add" command only takes 2 nonoption arguments!)
Thanks for bringing this to my attention. I'll update the documentation in the next version/release to state that apostrophes single quotes should not be used in the path. For the record, I personally recommend a very simple path without spaces and use D:\Mini-WinFE or D:\MistyPE whenever testing/running the project(s).

Regards,

Misty

#8 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13600 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 26 July 2014 - 07:57 AM

To be picky (as I am ;)) and since this is going to go in the "official" documentation, the character "official name" is "single quote":

http://www.ascii.cl/htmlcodes.htm

code 39 or 0x27

 

Of course you cannot use it always, you know, like "a kiss is a pink single quote between the words je t'aime” won't sound good :whistling:

 

:lol:

 

:duff:

Wonko



#9 misty

misty

    Silver Member

  • Developer
  • 703 posts
  •  
    United Kingdom

Posted 26 July 2014 - 09:48 AM

Wonko, picky, never!!! :P

Thanks for pointing this out - I'll edit my post(s) accordingly.

:cheers:




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users