locked
Error creating IBW disk RRS feed

  • Question

  • After installing WES7 SP1 I cannot create an IBW disk and get the
    following error:
     
    File does not exist: C:\$WINDOWS.~BT\Sources\EmbeddedDSI.dll
     
    15:17 :
    15:17 :
    15:17 : There was an error creating an IBW Disk
    15:17 :
    15:17 : System.UnauthorizedAccessException: Es wurde versucht, einen
    nicht autorisierten Vorgang auszuführen.
       bei
    Microsoft.Embedded.ComponentPlatformInterface.ShellFileCopy.CopyOrMoveFilesWithExceptions(String[]
    sourcePaths, String[] targetPaths, IntPtr hwnd, FO_Func wFunc,
    FILEOP_FLAGS_ENUM flags)
       bei
    Microsoft.Embedded.ComponentPlatformInterface.ShellFileCopy.CopyFiles(String[]
    sourcePaths, String[] targetPaths, IntPtr hwnd, FILEOP_FLAGS_ENUM flags)
       bei
    Microsoft.Embedded.CreateIBWDiskFromAnsFileDialog.okButton_Click(Object
    sender, EventArgs eventArgs)
     The file DOES exist!
    Any idea?
    Thanks, Franz
     
    Wednesday, March 30, 2011 1:25 PM

Answers

All replies

  • This is a strange issue.  Just curious... did you run IBW on the developer machine that you installed ICE?

    I suppose you have installed WES7 RTM toolkit before and you had no problem creating IBW disk.  If this issue keeps occurring, you may want to uninstall/reinstall the toolkit and see if the issue persists.

    Ivan

    Thursday, March 31, 2011 2:04 AM
  • I did not run IBW on this machine.
    I had perfectly working pre-SP1 toolkit installed before.
     
    I now removed and can not reinstall!
    The installer tries to install a file that is not in the iso:
    .... 6.1.7600.16385~1.0\WinEmb-Antimalware.cab
    and then stops with error 1722
     
    btw: The help documentation lists:
    - For Windows Embedded Standard 7: DS or DS64.
    - For Standard 7 Service Pack 1: SP1DS or SP1DS64.
    whereas the installer installs to DSSP1 .. just to let you know of this bug.
     
    I really need to get this up and running asap!
     
    Thursday, March 31, 2011 8:38 AM
  • - I did not run IBW on that machine

    - I had WES7 installed before. I assume with RTM you are speaking about the normal pre-SP1 toolkit, then yes, and it worked since mid 2010.

    I now removed the it completely and can not reinstall it!

    I run into an error where the installer wants to install a file that is not part of the iso:

    And then the installer quits:

     

    btw: The help documentation lists the following:

    For Windows Embedded Standard 7: DS or DS64.

    For Standard 7 Service Pack 1: SP1DS or SP1DS64.

    where the installer creates DSSP1, just to let you know.

     

    I urgently need to get this up and running!

    Thursday, March 31, 2011 8:39 AM
  • I did not run IBW on this machine.

    I had perfectly working pre-SP1 toolkit installed before.

    I now removed and can not reinstall!

    The installer tries to install a file that is not in the iso:

    and then stops:

    btw: The help documentation lists:

    For Windows Embedded Standard 7: DS or DS64.

    For Standard 7 Service Pack 1: SP1DS or SP1DS64.

    whereas the isntaller installst to DSSP1 .. just to let you know of this bug.

    I really need to get this up and running asap!

     

    Thursday, March 31, 2011 8:48 AM
  • Sorry for the multiple posting .. my browser crashed twice ... and to my
    surprise the postings came up even so after I used Thunderbird.
     
    Thursday, March 31, 2011 9:06 AM
  • Update:
    I removed and reinstalled successfully. I needed the RTM DVD as well -
    RTFM ;-) or more precise the release notes.
     
    However, the error when trying to build a IBW image from the answer file
    is still the same!
     
    Thursday, March 31, 2011 12:19 PM
  • Coud you review the problem and define the question again, i can't follow you what you really want/need?!
    "Mark/Propose As Answer" if you got one.
    Thursday, March 31, 2011 1:38 PM
  • Thank you for trying to help.
    Just a few minutes ago, I found the thread below which exactly discusses
    my issue and confirms it as a bug and gives a solution as well.
     
     
    • Marked as answer by F. McLion Thursday, March 31, 2011 1:58 PM
    Thursday, March 31, 2011 1:55 PM
  • Interesting.  I'm aware of the problem mentioned in the other thread but when I looked at your log, it seemed to be a completely different issue.

    Anyway, I'm glad that you've found the workaround.

    Ivan

    Thursday, March 31, 2011 7:06 PM