dan.eagleton@canremote.uucp (DAN EAGLETON) (06/17/89)
I use this sys ( will work without any special add-ons ) to find the
name of the last accessed file.
SYS62913
Of course the file name data has to be stored in memory somewhere but I
haven't tracked down the exact spot yet. If youu could find the place
then you wouldn't have to be in direct mode to find the filename you
could go into your ML monitor in the background and look at the
filename. If you find the spot, let me know.
Hope this helps you.
Later - Dan Eagleton
Co-SYSOP: CONNECTed II 'THE BBS' - Peterborough, Ontario!
* QNet 1.03a2: CONNECTed II 'THE BBS' - Peterborough, Can. (705) 743-7296.rschofie@silver.bacs.indiana.edu (06/21/89)
>I use this sys ( will work without any special add-ons ) to find the >name of the last accessed file. > > SYS62913 > >Of course the file name data has to be stored in memory somewhere but I >haven't tracked down the exact spot yet. If youu could find the place >then you wouldn't have to be in direct mode to find the filename you >could go into your ML monitor in the background and look at the >filename. If you find the spot, let me know. The file name is right before $A000 if you start with clean memory, that is, from a cold boot. Thank you everyone who responded. Unfortunately, I still have not been able to solve the original problem. (What does "DLINK" try to load, or do, from the Final Cartridge III). The reason is that from the Desktop, where DLINK is accessed, anything you do wipes memory, including the drive's command buffer. Even going to the Freezer from the Desktop clears memory! I can't examine cartridge ROM either, due to some tricks by the designers. I guess my only hope is to write to the company. Robert B. Schofield {pur-ee,ihnp4!inuxc,rutgers,pyramid}!iuvax!silver!rschofie rschofie@silver.bacs.indiana.edu (192.12.206.2) rschofie@iubacs.bitnet (forwarded)