home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!mcsun!sunic!dkuug!diku!bombadil
- From: bombadil@diku.dk (Kristian Nielsen)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: Getting a valid FileSysStartupMsg pointers.
- Message-ID: <1992Dec14.145907.3739@odin.diku.dk>
- Date: 14 Dec 92 14:59:07 GMT
- References: <1992Dec13.030020.13319@mail.cornell.edu> <37848@cbmvax.commodore.com>
- Sender: bombadil@rimfaxe.diku.dk
- Organization: Department of Computer Science, U of Copenhagen
- Lines: 25
-
- jesup@cbmvax.commodore.com (Randell Jesup) writes:
-
- >chris@alchemy.tn.cornell.edu writes:
- >>However, apparently dol_StartUp does NOT always point to a valid
- >>FileSystemStartupMsg (hereafter abbreviated FSSM) even though IsFileSystem()
- >>returns true. I have particularly found this to be the case on devices
-
- > This is an ugly area. Unfortunately, early in the Amiga days (or
- >perhaps back in tripos), someone though strings would be neat to hold
- >parameters for handler startups. So they implemented BSTRs as an alternative
- >to FSSMs. They also thought that passing small integers would make it slightly
- >easier on whoever was writing the port-handler (SER/PAR/PRT). So they also
- >added support to pass an integer. So, startup can hold 3 things: an integer,
- >an BPTR to a BSTR, or a pointer to an FSSM (actually I think it's a BPTR).
- >Ugly, eh?
-
- YES! I've found this out the hard way while developing XFH: (a
- compressing file system handler).I pass a string to the handler in the
- 'Startup' field of the mountlist. Even system programs like C:Info seem
- to try to interpret this as a FSSM and cause enforcer hits.
-
- I was under the impression that passing a string to a handler as startup
- is a completely legal thing to do, but perhaps this is not so?
-
- - Kristian (author of XFH).
-