AutosilkUtils in 17.2

Hi Dave

Correct me if I'm wrong, but I don't think a password encrypted SKILL file can be de-crypted.
A non password encrypted is however another matter and can easily be decrypted.

Best regards
Ole

Hi Ole,

Encryption with a password provides read protection but I have read that it is not "strong".
Context files have the big advantage of being quicker to load and are great for stand-alone utilities.

Cheers,
Dave

Thanks Dave!

Can the new version be used with Allegro 16.x as well as 17.2? Trying it I get the following:
W- *WARNING* context read failure: can't read 64-bit context on 32-bit platform
E- *Error* loadContext: context I/O failed - "AutosilkUtils_public.cxt"

For now I've renamed the older and newer versions of ASU and edited allegro.ilinit to:
if(axlVersion('version) >= 17 then
loadContext("AutosilkUtils_public172.cxt")
else
loadContext("AutosilkUtils_public166.cxt")
)
axlCmdRegister("silkutils" 'ASU_start ?cmdType "interactive")

While all used to be well with Allegro 16.6 I now get the following when executing ASU (still using the old version of ASU):
E- File save problem: Not enough storage is available to process this command.
E- *Error* axlGRPDrwInit: argument #1 should be any user-defined (other) type (type template = "otg") - nil

Any ideas? I'm on 16.6 S085 so maybe it was broken by a hotfix? It could have also broken since installing 17.2 as that happened since I last used ASU. Not sure...

Anyway, when launching Allegro 17.2 I see:
E- *Error* loadContext: could not open file - "64bit/AutosilkUtils_public172.cxt"

Maybe I'm just tired, but I can't figure out what might be the problem or where to troubleshoot next. I'm on Windows 7 Ultimate x64 with 8GB RAM.

TIA and we really appreciate all your work!

I checked both of the cxt files and they work for me. And I think think logic in your ilinit file is correct. I'm on s083 so I don't think that's the problem.
It may be that you do need to put the 17.2 cxt file in a "64bit" folder. That's where it is in my system because that's where creating the cxt file placed it.

Do you have enough storage space ?
E- File save problem: Not enough storage is available to process this command.

Place the 32b version in the 'normal' skill folder. The 64b you need to put in the /64bit sub-folder (create it if you dont have it yet).
Then you need only 1 load statement for 16.6 and 17.2; loadContext("AutosilkUtils_public.cxt"). 17.2 automatically looks into the 64bit folder, while 16.6 uses the main skill folder.