I had a disk image I was working with, and everything worked fine. Then one day I got the Unable to load ATINIT error on booting it with Prodos 8, 2.4.2. I then put Prodos 2.03 on it, and same thing. The only thing I could do to fix it was to open
Ciderpress, copy all the files, and move them to a new image.
No configurations were changed, both KEGS and GSplus did the same thing, it's just really weird. What would cause that?
On Prodos v2.4.2, I isolated the error to the GetInfo call at $2390, where the error returned is compared with #$46. This is a file not found error, but instead I think I was getting a "Volume not Found" error, which is #$45 and thus causes the "Unable
to load ATINIT" error.
I can't remember what I isolated to the cause of it as. I may have deleted a file, then recovered it. But the recovery didn't update the file count correctly, which causes a volume error.
Boot from your good disk now, and insert the bad disk into Slot #7, drive #2. Type "BLOAD /volumename,TDIR,A$2000" replacing volume name with the name of the volume. Then do a CALL -151. And enter: 2025 <press Return>.
This will give you the file count in hex. Convert to decimal and count the actual number of files on the disk. They should match.
Or now that you created a new disk, and if you haven't saved anything to it yet, you can do the same BLOAD and check memory address 2025. They should match.
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)