High Performance File System: Difference between revisions

Revision as of 15:51, 28 November 2020

Revision as of 19:40, 18 December 2020

Line 48:

*''HPFS386'' provided with certain server versions of OS/2, or as added component for the server versions that did not come with it

HPFS386's cache is limited by the amount of available memory in OS/2's system memory arena<ref>{{cite web|title=Virtual Memory Problems under OS/2|url=http://www.os2voice.org/VNL/past_issues/VNL0708H/feature_3.html|publisher=www.os2voice.org|accessdateaccess-date=11 June 2015|archive-url=https://web.archive.org/web/20150924061927/http://www.os2voice.org/VNL/past_issues/VNL0708H/feature_3.html|archive-date=24 September 2015|url-status=dead}}</ref> and was implemented in 32-bit [[assembly language]]. HPFS386 is a [[Ring (computer security)|ring 0]] driver (allowing direct hardware access and direct interaction with the kernel) with built-in SMB networking properties that are usable by various server [[daemon (computing)|daemon]]s, whereas HPFS is a [[Ring 3 (computer security)|ring 3]] driver. Thus, HPFS386 is faster than HPFS and highly optimized for server applications. It is also highly tunable by experienced administrators.

Though IBM still had rights to HPFS, its agreement with Microsoft to continue licensing the HPFS386 version is contingent upon the company paying Microsoft a licensing fee for each copy sold. This was a result from the Microsoft and IBM collaboration that both IBM and Microsoft had right to use Windows and OS/2 technology. Microsoft used HPFS in Windows NT.

Line 106:

|work=The Graham Utilities for OS/2 - Version 2

|url-status=dead

|archiveurlarchive-url=https://web.archive.org/web/20060210154146/http://www.warpspeed.com.au/Products/OS2/GU/Manual/appg.htm

|archivedatearchive-date=2006-02-10

}}

* [https://archive.today/20130130020814/http://homepage2.nifty.com/bayer/hpfs_w2k.html%23English How to get Windows NT 4, Windows 2000, and Windows XP to read HPFS partitions]