|
Forum Index : Microcontroller and PC projects : MMEdit V5.4.3
| Author | Message | ||||
TassyJim![]() Guru Joined: 07/08/2011 Location: AustraliaPosts: 6575 |
V5.4.3 has been uploaded. No significant changes to the editor. My next task is to try and update the syntax files. It might be time to add another syntax for the USB range of picomites MMCC has a layout change, speed improvements and more error trapping. ![]() All flash commands are moved from the file manager to the MMCC menu. (Drive A: is still accessed through the file manager.) Delete Library and delete all flash slots ask for confirmation. The number of device families has been reduced and any new or unknown device is assumed to be a member of the picomite family. File manager has also had a layout change. ![]() The top line: TFTP is available on the webmite when connected via TCPIP. Ymodem is available on some picomite variants. IF Ymodem fails to start, it will revert to Xmodem. (TFTP and Ymodem are both much faster than Xmodem) When transferring to a 'mite, you can choose to create a temporary file first. This is more secure and less likely to delete a valid file if the transfer fails. It does require sufficient drive space. Transfers TO the PC always use a temporary file. Progress indicator. It may not appear for small files. It resets to zero once the transfer is complete File name and transfer speed followed by a direction indicator. Abort lets you interrupt a transfer. If you have temporary file selected, nothing is lost. No change to the second line. Next is the device currently connected to as shown by MM.Device$ Below that are 3 "Change to drive" and 3 "copy to Drive" It is the users responsibility to know how many drive their device supports. Jim VK7JH MMedit |
||||
| Volhout Guru Joined: 05/03/2018 Location: NetherlandsPosts: 6041 |
Hi Jim, Are the "change to drive" and "copy to drive" buttons for local copy ? (i.e. from picomite A: drive to picomite B: drive )? Small bug in MMCC: when transferring a file from PC to pico, using "temporary file". When that file already exists (overwriting): everything is okay. When that file did not previously exist(a new file): the renaming fails, and a file called XMtemp.tmp is left on the pico. Volhout Edited 2026-08-19 17:00 by Volhout PicomiteVGA PETSCII ROBOTS |
||||
TassyJim![]() Guru Joined: 07/08/2011 Location: AustraliaPosts: 6575 |
Yes Drive X to drive Y on the picomite. There were buttons for drive A and drive B previously. I was hiding the ones that weren't relevant. With the much larger range of devices out there, had to let the user work out which drives he has. I don't have anything with the 3 drives to test. I have started reading the latest manuals to see what I have missed in the last few versions. What sort of picomite? I have tested with a picomite geek V6.3.0 and it transfers a new file correctly on both drive a and b Pseudo code KILL "fname$" ' will give an error message if it doesn't exist but doesn't stop things. RENAME "XMtemp.tmp" AS "fname$" ' try the first version of rename command NAME "XMtemp.tmp" AS "fname$" 'try alternatinve command to rename Jim Edited 2026-08-19 17:21 by TassyJim VK7JH MMedit |
||||
| Volhout Guru Joined: 05/03/2018 Location: NetherlandsPosts: 6041 |
Hi Jim, PicoMiteVGA V6.03.00 On the MMCC there is no error message, but on the VGA screen it is something like XMODEM RECEIVE "filename.ext" KILL "filename.ext" Error: could not find the file Visible for 0.1 seconds, then immediately the VGA screen shows the result of a FILES command (the directory listing). There is no RENAME and NAME on the VGA screen. In the directory listing is XMtemp.tmp. The behaviour is independent on file size (tested 4k...500k) or file name (also tried 4 character extensions like ".flac"). On MMCC screen there is a timout message that I cannot relate. ![]() Volhout Edited 2026-08-19 18:49 by Volhout PicomiteVGA PETSCII ROBOTS |
||||
| The Back Shed's forum code is written, and hosted, in Australia. | © JAQ Software 2026 |