For some reason unknown to me, recently (the last month or so), every time I attempt to save any file after doing so the first time using the 8-bit version of the ProDOS version of the Merlin assembler using either the AppleWin or GS+ emulator, I receive an '40 INVALID PATHNAME' error.
What happens is...
Create a new source code file; assemble it; save the source file; save the object file. The first time I do so, both the source and object file save as expected.
Either modify the first file and save it under a new name OR create a new file with a new name, and I receive the '40 INVALID PATHNAME' error when attempting to save.
This happens in the AppleWin emulator, AND in the GS+ emulator when using the 8-bit Merlin version (2.58) that is included as part of the Merlin 8/16 package running under the GS+ emulator OR running version 2.58 under the AppleWin emulator.
This error does NOT appear when using Merlin 16 (3.50) or Merlin 16+ (4.08) (running under GS+ obviously).
Both emulators are running under Windows 10 with all the latest updates installed.
My assumption is that something has changed in Windows that is causing this, though I do not possess the technical knowledge to verify this.
Can anyone else confirm this behavior and/or offer a solution?
Thank you for taking the time to read and I hope to hear from you.
Hello,
(read the doc) when it proposes the same filename if you press enter nothing happen, if you press y it saves :)
I finally realized my error was failing to type in the complete filename at the 'Save' prompt.
When making multiple updates to a file, I was appending a number to the end of the filename to differentiate the differing versions. To speed up the process, I was just typing over only the number. For example...
Filename: test1
If I edited this file, I was just typing over the '1' to '2', '3' etc.
Typing the entire filename as they were edited appears to have solved the problem.
And, of course, if making edits to a file without changing the filename, simply pressing the 'y' key at the end of the filename works as it always has.
This is an embarrassingly stupid mistake, but perhaps its presence here may help someone else at some later date.