Marcus Comstedt wrote:

> --- In vmu-dev@egroups.com, Soeren Gust <sgust@i...> wrote:
> > I did some tests by error when developing my SerialToVM, filetype 0
> > means no directory entry, but the blocks are allocated in the FAT,
> > filetype 1 was not erasable with the VM (System Error 8b) and any
> other
> > file upload aborted when sending the header.
>
> Hum. Are you sure this is the _VMI_ filetype? It's not the same as
> the one used in the VMS directory (0x33 = data, 0xcc = game).

Good point. I'm just talking about VMU files. I noticed an interesting thing
last night. There are two VMU routines that I've encountered (so far) that
search through the file directory. The "count files" function counts all
files that are not type 0. The "select file based on index" function (i.e.
lookup the 5th file) only counts files of type $33 or $CC. The two use
incompatible ways of counting files. If other file types are to be
supported, then the VMU won't handle them well. It will include the odd-type
file in the count, but then not list it. When you try to select a file
beyond the listed files (but below the total file count), you'll set error
bit $80. (hope this description makes sense).

Also, (and it may say this in the manual), the white-on-black characters
indicates a file is copy-protected.

john

update to previous table:
** FLASH_ERRORCODE: bit 7 is set if file index is too big and can't find
filename.
Since the count counts non-zero files and the file lookup only counts
$33 or $cc files, if
a non-zero non-$33 non-$cc file type exists, then you'll get this
error.