home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.hp48
- Path: sparky!uunet!mcsun!fuug!funic!nntp.hut.fi!nntp.hut.fi!mheiskan
- From: mheiskan@hut.fi (Mika Heiskanen)
- Subject: Re: 'WICKED' post
- In-Reply-To: robf@cs.umr.edu's message of 19 Jul 92 08:14:03 GMT
- Message-ID: <MHEISKAN.92Jul30010759@vipunen.hut.fi>
- Sender: usenet@nntp.hut.fi (Usenet pseudouser id)
- Nntp-Posting-Host: vipunen.hut.fi
- Reply-To: mheiskan@.vipunen.hut.fi
- Organization: Helsinki University of Technology - Finland
- References: <5462@umriscc.isc.umr.edu>
- Date: 30 Jul 92 01:07:59
- Lines: 28
-
- In article <5462@umriscc.isc.umr.edu> robf@cs.umr.edu (Rob Fugina) writes:
-
- In regards to the 'wicked' post about accessing the hidden directory... I
- read that, to carry out the procedure, I need a PEEK/POKE program (which I
- have) and I need to be familiar with the 'internal' debugger. I am familiar
- with the INTERNAL debugger, but the reference to the debugger is confusing.
- The instructions say, and I quote, 'enter the debugger, go to F0592. Read
- the first five nibbles.' The debugger that's built into the hp48sx (which
- is what I'm assuming is the 'internal' debugger, doesn't have any features
- that I know about that can be used to reference memory directly. I tried
- to view the memory locations using PEEK, but the answers didn't check out.
-
- Well, I haven't read the wicked post, but I have my internals list, so:
-
- 64023 HP:RclHiddenVar (1:ID -> 2:contents 1:True / 1:False)
- 64037 HP:WithHidden (Sets hidden dir for the next command only)
- 64078 HP:StoHiddenVar (2:Any 1:ID)
- 6408C HP:PuHiddenVar (1:Id)
- 640BE HP:SetHiddenRes (Changes to hidden dir)
-
- 0B9D4 HiddenDir@ (Rcls hidden dir -> 2:DIR 1:True / 1:False)
- 0BA7D MkNullHiddenDIR (Stores an empty directory as hidden dir)
- 0BB40 MkNullHiddenDIR? (Above if hidden dir doesn't already exist)
-
- Ones marked with HP: are supported, others may work on rev. E only.
-
- --
- --> mheiskan@vipunen.hut.fi
-