Hi John
I think that this behaviour can be explained. The operation of the uFileSystem -
a very small file system implementation but with some rules to follow - is fully explained in
http://www.utasker.com/docs/uTasker/uTaskerFileSystem.PDF.
In addition you can see the file system use in the demo project in the document in the project folder:
\Applications\uTaskerV1.3\WebPages\WebPagesM5223X\FileSystem\FileSystemM5223X.doc
The demo project is designed to run on both the smaller and larger M5223X chips. For this reason it only uses 28k of file system space for the web pages (the whole project will then run on a device with only 128k FLASH).
The document
\Applications\uTaskerV1.3\WebPages\WebPagesM5223X\FileSystem\FileSystemM5223X_160k.doc shows how the file system is however really set up for use by chips with 256k (which is also necessary to do SW uploads into internal FLASH!!).
You will find that when you added more lines to the file 0memu.html you made the file longer than the 2k space allocated for it. This causes it to 'bulldoze space for itself by deleting the file 1Lan.html.
Since you had a link to 1Lan.html (which is no longer valid) the browser will see the end of the first file and so display something strange.
With more file system space it is of course useful to have the SMTP configuration in the menu and to have the set up page always loaded. This is also done in some uTasker demo projects (eg. the STR91Xf which has 512k FLASH and so there is bags of space - see the STR91XF project including SMTP setup intergrated in menu at
http://84.79.5.2 ).
The reasons for not doing this in the M5223X project are:
1.
The project will run on the smallest device, as explained above.
2.
It illustrates a technique of temporary HTML page swapping which can be useful in projects with limited file system space:
The SMTP set up side has the same 'name' as the administration side so 'overwrites' the admin side when loaded via FTP. When the SMTP set up has been completed and the settings saved, the original administration html page can be loaded - it overwrites the 'temporary' configuration side which is no longer needed.
This requires no additional FLASH space for the SMTP page at all!
Such a technique is, for example, impossible when web pages are compiled into code.
Another example would be uploading a development page allowing viewing and manipulating critical variables and such - this can temporarily overwrite a production page until the work is finished. Then the origianal page is replaced again. Remote debugging support is thus possible without having to integrate it into the project, but rather borrow a bit of file space when needed. Also the remote debugging is not available to 'normal' web viewers.
In summary: the uFileSystem is simple and efficient to allow a good level of comfort and useful techniques as explained above. It does however have some rules and the exact use of the file system needs to be 'designed' for the project in hand.
Good luck
Regards
Mark