🚀 go-pugleaf

In article <1992Aug26.142405.23478@nmt.edu>, jreynold@nmt.edu (John Reynolds) writes:
|> (Dennis Yelle) writes:
|> >Has anyone here gotten FSFILTER.SYS to do anything useful?
|> >
|> >I put "DEVICE=FSFILTER.SYS" in the CONFIG.SYS file for MS-DOS 5.0
|> >in the hopes that it would allow me to read and write the HPFS
|> >partition on my disk from DOS.  It didn't have ANY effect.
...
 
|> I THINK (please correct me if I'm wrong) that fsfilter.sys is used when
|> one literally BOOTs a specific DOS kernel from within OS/2 (the "DOS from
|> Drive A" icon). If fsfilter.sys is used to boot dos straight, THEN its useless.
|> 
|> -John
|> 
|> 
|> -- 
|> MS-DOS is an interrupt handler with a brain-dead interface.
|> Windows is a pathetic attempt at.....????
|> OS/2 is the future....that's here right now!

You are right. Look at the size of fsfilter.sys. Something
around 25K if I remember that right. Anyway, it's small compared
to the files related to HPFS support in OS/2. You cannot put that in
such a small driver, can you? Besides, HPFS is proteced mode code...
From my point of view, FSFILTER.SYS serves to access a HPFS
system that is *already* running. That means OS/2 must be booted.