home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!geraldo.cc.utexas.edu!geraldo.cc.utexas.edu!usenet
- From: jbodnar@ccwf.cc.utexas.edu (John Bodnar)
- Newsgroups: comp.os.os2.misc
- Subject: Re: HPFS compatability with other OS's
- Date: 23 Jan 1993 07:24:31 GMT
- Organization: The University of Texas at Austin, Austin TX
- Lines: 25
- Distribution: world
- Message-ID: <1jqrrfINN6fi@geraldo.cc.utexas.edu>
- References: <enk2.66.727573011@po.cwru.edu> <1993Jan22.145251.18157@njitgw.njit.edu>
- Reply-To: jbodnar@ccwf.cc.utexas.edu (John Bodnar)
- NNTP-Posting-Host: flubber.cc.utexas.edu
-
- According to dic5340@hertz.njit.edu (David Charlap):
- >I'd be really surprised if they get DOS to mount HPFS. Considering
- >that the OS/2 driver (which is 16-bit code also) occupies about 512K
- >of memory. It might be smaller if desiged with the assumption of
- >single-tasking, but that would cripple Windows (the same way FAT does
- >now!).
-
- DOS 5.0 does have the IFS= command for CONFIG.SYS. Check out a genuine
- MS-DOS 5.0 Upgrade manual for this.
-
- Of course, I have no idea how the hell DOS could handle an installable file
- system. DOS just can't support the kind of memory requirements for this.
- I bet Windows could be made to use an IFS (just stick it in the
- SYSTEM.INI).
-
- Of course, this would be quite a restriction. You'd probably need a
- separate volume formatted for the IFS, and it'd be accessible under Windows
- only. Not a particularly clean implementation. The file system ought to
- more or less be invisible to an application, so this kind of precludes
- Windows having an IFS since it's an application and not an OS.
- --
- John Bodnar : Friends don't let friends use Windows!
- The University of Texas at Austin :
- Internet: jbodnar@ccwf.cc.utexas.edu : OS/2 and Rush Limbaugh! Succeeding
- UUCP: ....!cs.utexas!ut-ccwf!jbodnar : despite the media's best efforts!
-