Hi Hervé
I have made a modification to the utility that should help in these cases (uTaskerFileCreate V1.3).
So that files without extensions can be easily recognised they should be marked as follows ('|' used as terminator):
0HTTP| -w -T=MIME_HTML
This allows the parser to identify that the end of the file name has been reached and that it is not simply a space in the name.
XML?Dummy| -c=FILE_INVISIBLE -w -T=MIME_HTML
The same is true for the XML?dummy since it doesn't have an extension. The -c=FILE_INVISIBLE is not necessary but I added it so that the file is not displayed in the file system.
The new version will store the file name XML?Dummy in the embedded file but, since this is not a valid name for a file on the PC it expects to be able to find a file called "XML-Dummy". Therefore you need to put the content to be served by XML?Dummy into a file called "XML-Dummy".
This is the output from a test with these two files plus the link.htm file (I simply removed others):
uTaskerFileCreate -f userfiles.txt 1UserFiles.bin
Adding file _0HTTP
Adding file _link
Adding file _XML?Dummy
Output files 1UserFiles.bin and 1UserFiles successfully created
Embedded user file collection target address = 0x60000
Embedded user table location = 0x6002c
The C-File output looks correct:
static const unsigned char _0HTTP[] = {
0x31,0x32,0x33,0x34,0x35,0x36,0x37,0x38,
};
static const unsigned char _link[] = {
};
static const unsigned char _XML?Dummy[] = {
0x74,0x65,0x73,0x74,
};
static const USER_FILE user_files[] = {
{"0HTTP", (unsigned char *)_0HTTP, sizeof(_0HTTP), MIME_HTML, FILE_VISIBLE},
{"link.htm", (unsigned char *)_link, sizeof(_link), MIME_HTML, FILE_VISIBLE},
{"XML?Dummy", (unsigned char *)_XML?Dummy, sizeof(_XML?Dummy), MIME_HTML, FILE_INVISIBLE},
{0} // end of list
};
Therefore I am assuming that also the binary output is now good.
Please confirm that this works for you. I don't think that these changes otherwise cause any compatibility problems with the utility.
Regards
Mark