No it's certainly not a bug in laddiealpha. The file transferred to m100 correctly. It was just that LOAD"A-DUEL.DB" returned a no file found?
Is this normal, that BASIC's picky about the second letter of the extension? Willard Sent from Samsung tablet -------- Original message -------- From "John R. Hogerhuis" <[email protected]> Date: 02/19/2017 2:20 PM (GMT-07:00) To Model 100 Discussion <[email protected]> Subject Re: [M100] Auto-mangled file extension? You effectively loaded it as a-duel.db. Once transferred I guess you're accessing the file from BASIC. From basic we're you opening it as a-duel.db or a-duel.do? Then you renamed it from tsdos. Maybe tsdos sees .db and .do as the same file. Or maybe it's a bug in laddiecon. -- John On Sun, Feb 19, 2017 at 1:03 PM Willard Goosey <[email protected]> wrote: So I had my fist experience with LaddieAlpha's automatic file extension mangling, and I'm a little confused. So it started with (on the linux side) file a-duel.ba which was ascii source. Such sloppiness is a good way to visit Cold Start City, so Laddie presented it as a-duel.db to tsdos, which happily saved it in m100 RAM as such.... So far so good. The trouble started when BASIC returned NM error, couldn't find file... OK I tried to use tsdos to rename it to a-duel.do but tsdos claimed file already exists. Deleted file, reloaded it as a-duel.do and everything works. So, am I missing something here, or is that just how it is? Willard Sent from Samsung tablet
