Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!spool.mu.edu!uunet!pdn!myrddin!tct!jim From: jim@tct.com (Jim Kunzman) Newsgroups: comp.os.os2.misc Subject: Re: New OS/2 v2.0 features (rumored) Message-ID: <286D0686.54F0@tct.com> Date: 29 Jun 91 22:15:34 GMT References: <1991Jun27.232315.1845@digi.lonestar.org> Distribution: usa Organization: TC Telemanagement, Clearwater, FL Lines: 45 According to jgay@digi.lonestar.org (john gay): >New features rumored to be in OS/2 v2.0 include: (rumored because it was in >the June 24 issue of PC Week - not exactly the most reliable source) > >* New FAT file system called Super FAT - a faster running implementation of > the FAT used in DOS. Super FAT is completely compatible with current > files and disks, achieving its speed increase through 32-bit code. > "It's faster than the HPFS [currently] in 2.0", (Lee) Reiswig (assistant > general manager of programming at IBM) said, noting that IBM intended to > boost the speed of HPFS before the release of 2.0. > >* A multiboot feature that allows users to choose between multiple operating > systems, such as DOS, OS/2 1.3 and OS/2 2.0, when they turn on their PCs. > >Well, I don't know about the super FAT file system, but I do know that the >multiboot feature was asked for here on the net. Do ya'll suppose that >somebody is actually listening AND hearing what is said here (other than >Larry). > Hey, on just the odd chance that there is, how about getting with Adaptec to ensure that the hooks are there in OS/2 2.0 so Adaptec can update their AHA1542B SCSI drivers to work with OS/2 2.0. According to one source, IBM pulled the hooks to LADDR (whatever that is) and now vendors are having problems updating OS/2 device drivers for HPFS and SCSI controllers! :v( Super FAT will be nice, but so are longish file names, e.g. to append .Z for compressed files ~ for EMACS backup files, etc. By the way, can anyone explain LADDR and why we should care? Is it some sort of Libyan viper? :-) -- Jim Kunzman at Teltronics/TCT , !(This space intentionally left blank.)