I've recently gotten a NanoPEB (yay!) and am messing around with disk management for the first time on my TI 99/4A (never had a PEB, back in the day). Now, from what I understand, the procedure for mounting a disk is essentially going into BASIC and using CALL MOUNT(DSK,VOL), with execution of any program contained therein achieved via OLD "DSK#.PRGNAME". Unfortunately, I don't seem to be getting anywhere with that.
The NanoPEB came with a formatted CF card, and TI99Dir shows two formatted volumes (volumes 1 and 2). When mounted, Disk Manager 3 (executing that via FlashROM 99) appears to show a collection of programs in the volume CFHDX_V12 mounted as DSK2, with those programs named CFHDXP1 through CFHDXP4 and CFHDXS1 through CFHDXS4. Evidently, these are disk manager files, though I've had no success executing them via OLD "DSK2.CFHDXP1" for example, as this results in an ERROR 57 in BASIC. If the volume isn't mounted at all, it's an ERROR 50, instead. Disk Manager 3 simply tells me DSK1 is *not initialized*, when mounted, on the other hand.
Since I gather the collection of key utility programs (CATALOG and such) downloadable from the NanoPEB homepage are supposed to be in Volume 1 (or at least were at some point in history), I had first tried simply running
But that just produced ERROR 57 likewise. As a fallback plan, I downloaded and recopied the VOL1 files via TI99Dir, but to no effect. Same result (as far as OLD giving me the old ERROR 57).
I've also tried using TI99Dir to copy a Tunnels of Doom game disk to Volume 3 (the one with PENNIES and QUEST on it), mounting that, and loading it via ToD, with no luck (though like OLD, it demonstrates different responses/errors based on whether the volume is mounted, so at least I know that's doing something).
Any ideas on what I'm doing wrong? I'm certainly a neophyte when it comes to TI 99/4A disk management. But I'm determined to get this figured out. Thanks in advance for any advice.
I've also tried writing volume 3 using a Tunnels of Doom game disk (the one with PENNIES and QUEST on it), mounting that, and loading it via ToD, with no luck (though like OLD, it demonstrates different responses/errors based on whether the volume is mounted).