Self-extracting archives

As a workaround, you should just be able to sofload this version. I’ll give it a quick test myself and update the IOMD build to use it if everything is OK (In lieu of any of us having enough spare time to rewrite the module)

That softload version passes my quick tests – everything extracts easily now, and the results look reasonable.

Has anyone else encoutered the ‘Memory cannot be moved’ error after creating an archive and then extracting (under either the WIMP or CLI)? I’m using a RAM disc to save time – rather than USB - but there’s ample spare space.

I initially created an archive of my entire HardDisc4.$ contents and encountered this error. I then moved Public to another archive in case it was a size issue. I’ve now also moved !Boot to a separate archive.

!Boot extracts fine (uncompressed size 20MB) but the rest (uncompressed size 13MB) produces this error and exits without writing all of the data. This may be difficult to comment on without seeing the specifics of what I’m doing but if anyone else has had similar results, I’d be interested to know. (Note that I’ve only tried the WIMP creation process.)

Edit: If I download the self-extracting HardDisc4 I can re-encode the extracted contents on the BB with no problems.

Can you let us know what you are using to build the archive and how you are extracting? I assume you are using the current version of CreateSEC and then decompressing by running the resulting self-extracting code e.g. from a task window. Is this on a Beagle Board? Xm? Touch Book? How much RAM is available and what’s the size of the next slot? Also, if you count the size of the thing you are archiving, how big is it (I think you’re saying around 33MB uncompressed)? Finally, is it the compression or decompression stage that generates the error message?

Ta.

Steve, I’ve sent you an email When you find time, please let me know if any other info is required. Thanks.