home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.amiga.programmer
- Path: sparky!uunet!news.univie.ac.at!chx400!rzusuntk.unizh.ch!cschneid
- From: cschneid@amiga.physik.unizh.ch (Christian Schneider)
- Subject: Re: Getting a valid FileSysStartupMsg pointers.
- Message-ID: <1992Dec22.143308.26492@rzu-news.unizh.ch>
- Sender: root@rzu-news.unizh.ch (Operator)
- Organization: ICU - University of Zurich, Dept. of Computer Science
- X-Newsreader: TIN [version 1.1 PL8]
- References: <1gnma8INNou3@nz12.rz.uni-karlsruhe.de>
- Date: Tue, 22 Dec 1992 14:33:08 GMT
- Lines: 28
-
- Angela Schmidt (ry53@rz.uni-karlsruhe.de) wrote:
- > or not. TypeOfMem() only works with RAM, but some of the entries in
- > the fssm can be in ROM or even in the expansion space as well. So
-
- But a valid fssm is always in ram, wrong?
- I'm currently using TypeOfMem() for dn_Startup only, I don't think
- this should miss some devices.
-
- > for now, I assume that non-zero-values mean that there is a valid
- > fssm. I tried TypeOfMem() but I really missed some devices after that,
-
- 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).
-
- > because their device name (and I think the environment vector, too)
- > was in ROM.
-
- Which devices did you miss? But fssm itself was in ram?
-
- : \ /&\ Angela Schmidt cand. inf. (Nessy@IRC) | Amiga //
- ^^^^ *grin*
-
- - Chris, stud.inf.ing.eth ;-)
-
- --
- Chris Schneider - cschneid@amiga.physik.unizh.ch BIX: hschneider IRC: cschneid
- It's impossible to enjoy idling thoroughly unless one has plenty of work to do
-