+ Reply to Thread
Results 1 to 4 of 4

Thread: Memory could not be read

  1. #1
    Join Date
    Mar 2004
    Location
    San Antonio, Texas, US
    Posts
    35

    Default Memory could not be read

    Hi Friedrich,

    This is easy to duplicate:

    1. Compile a setup
    2. Run it, leave it running, for example waiting on the welcome secreen.
    3. Switch back to SB
    4. Compile. You will get an error message about not being able to write to the file.
    5. Hit the compile button again. This results in "Memory could not be read" error. - see screenshot

    Best regards,
    Attached Images Attached Images  
    Arnor Baldvinsson
    Icetips Creative, Inc.

  2. #2
    Join Date
    Mar 2004
    Posts
    4,307

    Default Re: Memory could not be read

    Hi Arnór,

    Hmm, strange. I get a "The process cannot access the file because it is being used by another process" compiler warning. I'll check this, thank you!

  3. #3
    Join Date
    Mar 2004
    Posts
    4,307

    Default Re: Memory could not be read

    Hi Arnór,

    Fixed. If an installation executable is in use during the compilation process, the compiler presents the developer with a retry option that gives the opportunity to close the .exe, and allow the new .exe to be created.

    Thanks,

  4. #4
    Join Date
    Mar 2004
    Location
    San Antonio, Texas, US
    Posts
    35

    Default Re: Memory could not be read

    Hi Friedrich,

    Cool

    Best regards,
    Arnor Baldvinsson
    Icetips Creative, Inc.

+ Reply to Thread

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Read Only Destination Issue - SB5
    By NewsArchive in forum SetupBuilder - NNTP
    Replies: 14
    Last Post: 09-16-2005, 09:12 AM

Tags for this Thread

Posting Permissions

  • You may post new threads
  • You may post replies
  • You may not post attachments
  • You may not edit your posts
  •