I'm pretty sure that the club100 library has diskmanager or something like that which can do tpdd operations. Maybe check that out.
-- John On Thu, Jul 12, 2018, 11:42 AM Kurt McCullum <[email protected]> wrote: > Thanks, > > I was hoping there was an easy way to get that data. Looks like a little > coding will be involved to pull the TPDD directory. > > Kurt > > > On Thu, Jul 12, 2018, at 10:21 AM, John R. Hogerhuis wrote: > > I agree with Ken, I don't think so. But the memory filesystem is probably > easy to poke a string variable at and loop over. And you know the tpdd disk > commands. > > A little hidden embedded ML using the recently discussed techniques would > go a long way. > > -- John. > > On Thu, Jul 12, 2018, 9:13 AM Ken Pettit <[email protected]> wrote: > > Doesn't look like it, at least not using any built-in method. The FILES > and TS-DOS LFILES hook both print to the screen. The only two ways would > be: > > 1. Write and install a "print to screen" hook to intercept the data prior > to the actual printing and save the data off to a string. Then uninstall > the hook when done. > 2. Trapse through the TS-DOS disassembly and perform OptROM calls > directly to the appropriate functions responsible for obtaining the > filenames. > > Ken > > > On 7/12/18 8:09 AM, Kurt McCullum wrote: > > Is there any way to capture the FILES or more specifically lFILES commands > into either a string or array? > > Kurt > > >
