home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!munnari.oz.au!network.ucsd.edu!rutgers!cbmvax!jesup
- From: jesup@cbmvax.commodore.com (Randell Jesup)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: Getting a valid FileSysStartupMsg pointers.
- Message-ID: <38162@cbmvax.commodore.com>
- Date: 28 Dec 92 19:40:46 GMT
- References: <1gnma8INNou3@nz12.rz.uni-karlsruhe.de> <1992Dec22.143308.26492@rzu-news.unizh.ch> <1992Dec23.052714.25037@mail.cornell.edu>
- Reply-To: jesup@cbmvax.commodore.com (Randell Jesup)
- Organization: Commodore, West Chester, PA
- Lines: 24
-
- chris@alchemy.tn.cornell.edu writes:
- >I -think- that a valid FSSM and a valid DosEnvec vector (obtained from
- >the FSSM) are always in RAM and thus only check those two entries with
- >TypeOfMem. So far haven't run into any problems using this method.
-
- I think DF0-DF3 may well be in ROM (and TypeOfMem has no MEMF_ROM).
-
- >> This is rather dangerous. No enforcer hits? Did you have devices
- >> with all (five?) possible dn_Startups (NULL, four letter ASCII, char *,
- >> int, valid fssm are the possibilities I think to remember).
-
- >Four letter ASCII???? Ack! Randell didn't mention this as a valid
- >possibility in his original reply. Can anyone give me some examples of
- >devices which use this?
-
- 4-letter ascii is NOT valid. char * is not either - it's a BSTR
- (i.e. BPTR to <length><chars>).
-
- --
- To be or not to be = 0xff
- -
- Randell Jesup, Jack-of-quite-a-few-trades, Commodore Engineering.
- {uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.cbm.commodore.com BIX: rjesup
- Disclaimer: Nothing I say is anything other than my personal opinion.
-