Copyright: Copyright ©1995 Mike McCormick
Citation: Copyright ©1995 Mike McCormick


32-bit File Access FAQ
Frequently-asked questions about 32-bit File Access

by Mike McCormick  (mtm4@rsvl.unisys.com)	Revision 0.7  April 27, 1995

The information in this help file is of interest only to users of Windows for Workgroups version 3.11.

Introduction to this document

The FAQs:

Background

Configuration

Troubleshooting

Incompatibilities

Revisions

Needs

How to get this FAQ

Conversion credits	Trademarks

© Copyright by Mike McCormick, 1995.  All rights reserved.


Conversion credits
Converted to WinHelp format (with no text changes) by:

Mike Robinson

Sundial Services;  8232 E. Coolidge Street;  Scottsdale, AZ  85251-1718

(602) 946-8259

sundial@mailhost.primenet.com


How to get this FAQ

USENET: The 32-Bit File Access FAQ is posted monthly (more or less) on Usenet, in the newsgroups comp.os.ms-windows.misc, comp.os.ms-windows.setup, and comp.sys.ibm.pc.hardware.storage.  (It may eventually be registered with news.answers once it is fairly stable, if users want that.)

FTP: Thanks to Kevin Martinez, the current FAQ is available by anonymous FTP:  <ftp://ftp.rahul.net/pub/lps/hard-drive/32bfa-faq>

WWW: The FAQ is not (yet) available on World Wide Web.

E-MAIL: The latest version of the FAQ can be obtained by sending a request to the author at mtm4@rsvl.unisys.com.  You have the option of getting it once (default), or getting all future revisions (approximately one a month).  The monthly FAQ "subscribers" receive an advance "sneak preview" draft about 24 hours before it gets posted to Usenet.

HELP FILE: Thanks to Mike Robinson of Sundial Services, the FAQ is available as a Windows Help file.  The .HLP format is only available by e-mail (see above): specify "uuencoded" or "uuencoded and ZIPped".


Introduction to this document

This is of interest only to Windows for Workgroups (WFWG 3.11) users.

Usual disclaimers apply.  The author does not warranty or guarantee factual correctness of all details.  The author does not speak here for Unisys, nor for Microsoft.  Windows is a Microsoft trademark.  Microsoft is ultimately the only real authority on their products.

This is a "sneak preview" of an evolving FAQ.  The author considers this FAQ a work-in-progress.  Your mileage may vary.  You have been warned!

This FAQ may be posted to any USENET newsgroup or BBS, as long as it is posted in its entirety and includes this disclaimer section.  This FAQ may be archived at any public FTP or WWW location, as long as it is archived in its entirety, following the "Archive-name" (see above: the "/partx" part can be omitted if the FAQ is stored as a single file) naming convention. If you want your site mentioned in the FAQ, contact the author.

This FAQ may not be distributed for financial gain.  This FAQ may not be included in commercial collections, publications, or applications without express permission from the author.

Thanks to all the folks here at Unisys and out on the Net who helped with comments on the earlier versions.

I am still looking for corrections and feedback.  Particular areas where this FAQ needs some help are called out in a section at the end of the FAQ called NEEDS.  Send to: Mike McCormick (mtm4@rsvl.unisys.com).

This FAQ makes reference to MSDOS pathnames C:\WINDOWS and C:\WINDOWS\SYSTEM.  If you have Windows installed elsewhere or keep your Windows System directory elsewhere, adjust accordingly.

Before you decide to go ahead and configure 32-bit file access on your PC, you should look over this entire FAQ, esp. the INCOMPATIBILITIES section.


Needs

This beta FAQ still needs certain information confirmed or expanded before it is complete.  If you can help with anything below, please contact Mike McCormick at mtm4@rsvl.unisys.com.  Thanks!

N1:  [removed in 0.5]

N2:  [removed in 0.5]

N3:  Need a good (not too technical) definition of "INT13 compatible".  (see Q3a)

N4:  Confirm levels of DoubleSpace, DriveSpace, SuperStor, or any other disk compression utility that has a 32BFA problem.  Also patches, work-arounds.  (see Q13)

N5:  [removed in 0.7]

N6:  Which LAN drivers are incompatible with ifshlp.sys?  Confirm product, level, patches, work-arounds.  (see Q21)

N7:  Need better guidelines for Smartdrv double buffering.  (see Q3A6)

N8:  Any explanation and/or work-around for IF EXIST *\NUL bug?  (see Q18)

N9:  Need Microsoft Knowledge Base citations for as much of the FAQ as possible.  Also magazine article or book references.

N10: Are there Virus scanners that don't work with 32BFA?

N11: Is CachedFileHandles setting in SYSTEM.INI affected by 32BFA?  Is it affected by vcache?  Does it default to 12 or 14 (WFWG Resource Kit manual contradicts itself on this.)

N12: Is there a SmartMon-like utility for Vcache?

N13: Need more details about ASSIGN & JOIN 32BFA impact (see Q20).

N14: [removed in 0.7]

N15: Does Vcache definitely do an automatic periodic write cache flush?  Is it about every 5 seconds like Smartdrv?  (see Q5a)

N16: Need more info about the ForceMapper command.  (see Q8a)


Revisions

0.1  Sep. 1994  Initial version circulated within Unisys.

0.2  Nov. 1994  More explanation & Troubleshooting.  Circulated in Unisys & Internet.

0.3  Dec. 1994  Added Incompatibilities.  Posted on comp.os.ms-windows.misc|setup.

0.4  Jan. 1995  More Incompatibilities, other corrections.  Posted on comp.os.ms-windows.misc|setup,comp.windows.ms.

0.5  Feb. 1995  Added new Configuration questions, & misc. corrections.  Posted on comp.os.ms-windows.misc|setup.

0.6  Mar. 1995  Added info about resources, TSRs, incompatibilities, etc.  Posted on comp.os.ms-windows.misc|setup, comp.sys.ibm.pc.hardware.storage.

0.7  Apr. 1995  Added WFW3.11RK and more SMARTDRV info.  Posted on the same newsgroups as revision 0.6.


The FAQS:  Background

1.	What is 32-bit file access?

1a.	Why would you want to use 32-bit file access?

1b.	Is it different than 32-bit disk access?

1c.	Isn't 32-bit file access a Windows NT feature?

2.	What PCs can run 32-bit file access?

Q1: What is 32-bit file access?

A: Without 32-bit file access, Windows has to perform every file access through DOS and the underlying BIOS.  This requires switching the CPU into 16-bit real mode.  With 32-bit file access, Windows stays in control of the file operation, and executes in 32-bit protected mode. [cf. WFWG Resource Kit Manual Addendum for 3.11]

Q1a: Why would you want to use 32-bit file access?

A: Performance.  Combined with Windows internal caching (VCache), it outperforms all previous caches (Smartdrv, Cacheclk, NCache, etc.) on standard benchmarks.  It even outperforms them running on a comparatively smaller cache.

Q1b: Is it different than 32-bit disk access?

A1: 32-bit file and disk access are similar but different, which is a source of confusion to users.  32-bit disk access pre-dates WFWG 3.11. It allows Windows to bypass BIOS & DOS, and remain in 386 protected mode while directly accessing the disk bus and remaining at CPU speeds.  It does less for performance than 32-bit file access.  It comes with its own set of problems, and is NOT the subject of this FAQ!

A2: 32-bit file access does not require 32-bit disk access.

A3: 32-bit file access does not replace 32-bit disk access.

Q1c: Isn't 32-bit file access a Windows NT feature?

A: This is another source of confusion.  ALL file access in Windows NT (and Windows 95) is 32-bit when possible.  But in Windows for Workgroups, 32-bit file access is optional, and defaults to 16-bit even if your system is capable of 32-bit.  This FAQ is only about 32-bit file access in Windows for Workgroups.

Q2: What PCs can run 32-bit file access?

A: Normally any 386/486/586 PC running Windows for Workgroups 3.11 (as opposed to regular Windows 3.11) in 386 Enhanced Mode.  Unlike 32-bit disk access, it does not usually depend on your disk type.  If the 32-bit File Access checkbox appears in your control panel (see Q3A1), then Windows at least *thinks* your system can use it.  But the only way to be sure is to configure it (see Q3), then verify your machine is actually using it (Q4).


The FAQS:  Configuration

3.	How do you turn on 32-bit file access?

3a.	How can you get the latest version of RMM.D32?

3b.	Is it true you can't use 32-bit file access on your swapfile drive?

4.	How do you tell whether 32-bit file access is working on your PC?

4a.	What about the WFW3.11RK "32-Bit File Access Status" program?

5.	Should you run SMARTDRV if you have 32-bit file access?

5a.	Should you use write caching or "store-through" caching?

5b.	If you use write caching, how do you manually "flush" the cache?

5c.	How can you optimize your cache efficiency?

5d.	How does Windows cache affect system resources?

Q3: How do you turn on 32-bit file access?

A: Here are the configuration steps.  Backing up your hard drive first is recommended.  To perform these steps you will need to decide whether you wish to use Smartdrv and whether to use write caching.  If you're unsure, you can peek ahead to questions Q5 and Q5a.

(1)	[As explained in the MS Workgroup Add-On for Windows User's Guide:] Double click Control Panel, double click 386Enh icon, click Virtual Memory, click Change, click the 32-bit File Access checkbox (it doesn't matter which drive is selected above).  Be ready for these side-effects:

(1a)	The Cache Size value will probably change automatically at this point.  Optimizing cache size can add considerably to the performance improvement you get with 32-bit file access.  Try 1024KB for now and experiment with this later, if in doubt.  See Q5c for optimizing tips.

(1b)	The Swapfile settings may also change automatically at this time.  Do not attempt to reset swapfile to "Temporary"; that is not allowed with 32-bit file access.  Also don't set the Swapfile Size to the "Recommended Size" displayed.  That is based on disk space available, not on what is really best for your system.  (A small but non-zero amount of Permanent swapfile, typically 1-5MB, seems to work best.  See also Q3b.)

(1c)	Click OK to close the control panel.

(1d)	Click "Continue" -- do not restart Windows yet.

(2)	Use File Manager to find RMM.D32 in C:\WINDOWS\SYSTEM.  It should be there, and it should have a 12/93 date or later.  (Note:  an inefficient version dated 11/93 was shipped to many Windows buyers.)  If it is not there, see Q3a before proceeding.

(+3)	Use File Manager to find IFSHLP.SYS in C:\WINDOWS.  If it is not there, obtain it or disable 32-bit File Access; running 32-bit file access without the "Installable File System Helper" (IFSHLP) is not recommended.  However, IFSHLP does have drawbacks -- see Q12.

(3a)	Start up the System Editor (in a pinch, Notepad will do) and examine your C:\CONFIG.SYS file.  It should contain the statement "device[high]=[path]ifshlp.sys".

If IFSHLP.SYS is not there, add it.  If your PC is on a network, see question Q21.

(4)	This next step (4a) disables write caching by Windows.  Skip this step if you want write caching.  See question Q5a if you're unsure.

(4a)	Use System Editor to edit your C:\WINDOWS\SYSTEM.INI file.  Find the section labeled "[386Enh]".  Add the following statement anywhere in that section: "ForceLazyOff=C"; or if your PC has a partitioned hard drive, insert "ForceLazyOff=Cx", where "x" is a string of letters representing other partitions.  The only partitions you can safely omit are those that contain only temporary and/or read-only data.  For instance, a D: drive containing just \TEMP plus your swapfile could be omitted for even faster performance.

(5)	As long as you are in the [386Enh] section, make sure you have the statement "device=vcache.386" somewhere in there.  By default it is always present, but some people have removed it from their systems to prevent unwanted caching.

(5a)	And while you're still in the [386Enh] section, check for the statement "NoEMMDriver=ON".  If it's there, you may need to REMOVE it, or at least make a note of it in case you get a Windows hang later when you restart WFWG with 32-bit file access (see Q11).

(6)	This next step (6a) removes double buffering from your SMARTDRV cache.  If you want to keep SMARTDRV on your system (see Q5), this step is not required but it does seem to improve performance for many users.  You may choose to skip (6a) for now, especially if you know your PC has a bus mastered DMA disk controller, or if your PC owner's manual says you need double buffering to run SMARTDRV.

(6a)	Use System Editor to edit your C:\CONFIG.SYS file.  Look for a command of the form "device=smartdrv.exe /double_buffer".  If it is there, remove it.  (Or if you have DOS 6.0 or higher, you can just "REM it out" instead of actually deleting it.)

(7) If you want to keep SMARTDRV on your system (see Q5), do the following:

(7a)	Use System Editor to edit your C:\AUTOEXEC.BAT file.  Find the SMARTDRV call.  If the /L switch is present, remove it.  The two numbers at the end of the line are the sizes (in KB) of the DOS and Windows caches.  Set the Windows cache size (2nd number) to 0 unless you use floppy disks, CD-ROMs, or optical disks heavily in Windows.  If you do use any of those, then set it to 128.  (See Q5c.)

(7b) If you do not want write caching (see Q5a), make sure none of the drive letters are followed by a "+" sign on the SMARTDRV call.  Remove any "+" sign you find post-fixed to a drive letter.  If any drive letters are missing (excluding compressed volumes), add them to the SMARTDRV call because omitting a [non-compressed] drive is the same as specifying it with the "+" sign.

(7c) Use System Editor to edit your C:\CONFIG.SYS file.  Look for a command of the form "buffers=<value>", typically "buffers=3,0". If the typical value of "3" or "3,0" is there, do nothing.  But if a larger value is present, change it to "buffers=3".

(8)	If you want to disable SMARTDRV on your system (see Q5), do the following:

(8a)	Use System Editor to edit your C:\AUTOEXEC.BAT file.  Find the SMARTDRV call, and prefix it with "REM " to disable it.

(8b) Use System Editor to edit your C:\CONFIG.SYS file.  Look for a command of the form "buffers=<value>", typically "buffers=3,0". Change it to "buffers=10".

(9) Close System Editor.  Exit Windows.  Reboot the PC.  Restart Windows.  Check whether 32-bit access is working (see Q4).

Q3a: How can you get the latest version of RMM.D32?

A: You may need the latest RMM.D32 file dated 12/93 or later to get the best possible performance from 32-bit file access (see Q3A2).  Some PCs show no measurable improvement moving from an old to new version of RMM.D32.  Other PCs show major improvement.  A few cannot use 32-bit file access at all without it; for example, if you run disk compression (DoubleSpace, Stacker) and your hard disk is not INT13 compatible.  You can obtain the latest version of RMM.D32 by anonymous FTP from Microsoft:

<ftp://ftp.microsoft.com/softlib/mslfiles/wg0973.exe>

Q3b: Is it true you can't use 32-bit file access on your swapfile drive?

A: No.  This is a persistent but unfounded rumor.  What is true though, is that you can only use a Permanent swapfile with 32-bit file access.  A Temporary swapfile is not allowed.  Running with swapfile set to "None" is allowed, but will not perform as well with 32-bit file access as a small permanent swapfile (see Q3A1b).  Note a major change in your swapfile type or size may require you to resize your cache as well (see Q5c).

Q4: How do you tell whether 32-bit file access is working on your PC?

A: Double click Control Panels, double click the 386Enh icon, click Virtual Memory.  If 32-bit file access is not working, an error box will probably pop up at this point.  Otherwise you get an information display window.  Check the "File Access" panel at the bottom.  If it says "32-bit" then 32-bit file access is now being used.  (If your hard drive has more partitions than just C:, then all should show "32-bit".) If it says "16-bit" then it is not working (see Q8).  Note it is normal for drives other than hard disks (RAM disk, CD-ROM) to show 16-bit access.  Click Cancel.

Q4a:  What about the WFW3.11RK "32-Bit File Access Status" program?

A:This program reports the exact same status as the 386Enh control panel.  If you own the WFWG 3.11 Resource Kit, you may prefer to install this and use it to check whether 32-bit file access is in effect instead of the control panel, but only if you prefer it.  (The software is provided as part of Microsoft's "Windows for Workgroups Resource Kit Addendum for Version 3.11".)

Q5: Should you run SMARTDRV if you have 32-bit file access?

A: The best answer seems to be "it depends".  Removing SMARTDRV (see Q3A8) frees up about 31K of lower memory and 512K of extended memory, but DOS runs slower and Windows takes longer to load.  Keeping SMARTDRV (see Q3A7) slightly reduces memory availability but makes DOS faster and makes Windows start up more quickly.  Once Windows is up and running, it will only use SMARTDRV for floppy disk (or CD-ROM or optical disk) access, but not for the hard drive.  (This is true even if C drive letter appears on the SMARTDRV command.)  So the reasons to keep SMARTDRV in addition to 32-bit file access would be for running DOS applications, using floppy or CD-ROM, or booting up into WFWG more quickly.  The price you pay is less memory.  You can run Smartmon in Windows to determine to what extent SMARTDRV currently is caching your floppy or CD-ROM drives.  (Note DOS 6.2 or higher is needed to cache a CD-ROM.)

Q5a: Should you use write caching or "store-through" caching?

A: If you cache writes to your hard disk as well as reads, you will reap an even greater performance benefit for your PC.  However, you also risk file corruption or data loss if a write never makes it from your cache in RAM onto your hard disk.  Both Smartdrv and the Windows cache give you the option of "store-through" caching to eliminate the risk.  You should probably avoid write caching if your PC is subject to unexpected interruptions (power loss, hangs, toddler hitting reset) or if it is connected to a network.  If you do use write caching, both Smartdrv and Windows cache do seem to force a save to disk at periodic intervals (as short as 5 seconds during system idle).

Q5b: If you use write caching, how do you manually "flush" the cache?

 A: If you are about to do something risky to your PC that could possibly hang or crash it, you can manually flush all the writes out of your RAM cache and force them onto your hard disk.  For the Smartdrv cache, enter "SMARTDRV /C". For the Windows cache, open a DOS box and type control-C.  If you do get hung you should use Ctrl-Alt-Del to recover.  Ctrl-Alt-Del also flushes the caches when working properly.  A hard reset does not.  Never push reset while Windows is running if you use write caching!

Q5c: How can you optimize your cache efficiency?

A: Your goal is to maximize the cache "hit rate", but minimize its size to conserve memory and reduce "thrashing".  For the Smartdrv cache, a Windows program called SmartMon will display the hit rate.  Try it while running a typical heavy mix of applications, or while running a standard performance benchmark (e.g. WinBench).  (If you don't have SmartMon, you can get cache hit rate by entering "SMARTDRV /S" in a DOS box.)  Now adjust the cache size for Windows until you achieve the highest possible hit rate.  Do all this with 32-bit file access turned OFF.  Then re-enable 32-bit file access, and set the Windows cache size to the same amount you found using SmartMon. Disable or reset Smartdrv per the instructions in Q3A7-Q3A8.

Q5d: How does Windows cache affect system resources?

A: An amount of memory equal to the configured Windows cache size is consumed at Windows start-up time.  It is allocated from system resources.  This is not the same as the "system resources" reported by Program Manager's Help (About...) menu command, which is an aggregate measure of the system, GDI, and USER heaps.  The GDI and USER heaps are not affected by the Windows cache.


The FAQs:  Incompatibilities

12.	You can't restore a deleted file with MWUNDELETE or MS-DOS UNDELETE.

13.	Is it safe to run 32-bit file access with disk compression?

14.	You get errors from Powerpoint when you access ClipArt Gallery.

15.	Is there any hard drive you can enable 32-bit file access with, but with which it is incompatible?

16.	You have to manually reinitialize Microsoft Scenes each time you start Windows.

17.	Can you run other disk cache utilities at the same time Windows is caching?

18.	DOS command "IF EXIST *\NUL" does not work from within Windows if 32-bit file access is on.

19.	Does 32-bit file access work on secondary (slave) hard drives?

20.	Does the DOS SUBST command (drive letter substitution) remain in effect in WFWG with 32-bit file access?

21.	Is 32-bit file access incompatible with some networks?

22.	Do some TSR programs interfere with 32-bit file access?

Q12: You cannot restore a deleted file with MWUNDELETE or MS-DOS UNDELETE.

A: Files deleted in WFWG (File Manager, or even a DOS box) while running 32-bit file access in conjunction with IFSHLP (see Q3A3) cannot be undeleted in Windows (MWUNDELETE) nor in DOS (UNDELETE - Sentry).  Files deleted from real DOS (not a Windows DOS box) can be UNDELETEd from real DOS.  Note the Undelete capability in Norton Desktop and PCTools does work with 32-bit file access.

Q13: Is it safe to run 32-bit file access with disk compression?

A: The DOS 6.2 version of DoubleSpace works with 32-bit file access; the 6.0 version does not.  Stacker 3.1 works with 32-bit file access, but version 4.0 only works with a patch [cf. Microsoft Knowledge Base Q108152].  The problem was fixed in Stacker 4.05.  There are unconfirmed rumors that SuperStor (part of IBM DOS 6.3) may not work with 32-bit file access.

Q14: You get errors from Powerpoint when you try to access ClipArt Gallery.

A: There is a bug in Powerpoint 4.0 that causes the clipart "thumbnail file" to get corrupted when 32-bit file access is enabled and VShare is also enabled.  If you disable 32-bit file access, restart Windows, restart Powerpoint, and reaccess ClipArt Gallery, it will rebuild the "thumbnail file" from its clipart library.

Q15: Is there any hard drive that WFWG will let you enable 32-bit file access with, but with which it is incompatible?

A: Yes, there is a confirmed problem [cf. Microsoft Knowledge Base Q119742] with the Quantum LPR 540MB drive if installed with older versions of the driver.  Contact the manufacturer for the latest driver.

Q16: You have to manually reinitialize Microsoft Scenes each time you start Windows, in order to get the wallpaper set correctly.  Then wallpaper and screen saver work fine for the rest of that Windows session.

A: This is a confirmed problem in MS Scenes 1.00, which Microsoft says they corrected in the subsequent releases of that product.  Either upgrade, stop using 32-bit file access, or put up with the annoyance.

Q17: Can you run other disk cache utilities at the same time Windows is caching?

A: Only SMARTDRV is safe.  Microsoft discourages use of all other cache utilities in conjunction with Windows caching or 32-bit file access.  None- theless, some do actually work.  See file C:\WINDOWS\SETUP.TXT for details about your particular utility.

Q18: DOS command "IF EXIST *\NUL" does not work from within Windows if 32-bit file access is on.

A: True.  Referencing the null device file is a common trick for checking whether a particular drive or directory exists.  (For example, "IF EXIST C:\NUL" checks the C-drive, or "IF NOT EXIST C:\MYDIR\NUL" checks MYDIR.) Microsoft documents this technique in "HELP IF".  However, the \NUL file never appears to exist under 32-bit file access.

Q19: Does 32-bit file access work on secondary (slave) hard drives?

A: It is supposed to, although a few users claim to have problems.

Q20: Does the DOS SUBST command (drive letter substitution) remain in effect in WFWG with 32-bit file access?

A: The SUBST remains in effect, but Windows disables 32-bit file access for that particular session.  If you exit Windows, undo the SUBST, and restart Windows, then 32-bit file access will come on.  (Note: You may not enter SUBST from within a Windows DOS box, regardless of 32-bit file access.)  The related ASSIGN and JOIN commands may also affect 32-bit file access.

Q21: Is 32-bit file access incompatible with some networks?

A: It works with Novell Netware and Microsoft Windows Network.  However, the IFSHLP.SYS driver (see Q3A3) is incompatible with some other networks, including Artisoft LANtastic and Microsoft LAN Manager.

Q22: Do some TSR programs interfere with 32-bit file access?

A: Yes, some Task-and-Stay-Resident programs that are loaded at boot time can prevent Windows from activating 32-bit file access.  See Q8 for details.


The FAQs:  Troubleshooting

6.	PC seems slower with 32-bit file access than it did with 16-bit.

7.	PC hangs when you exit Windows.

8.	You know your PC supports 32-bit file access, but it does not take effect.

8a.	What if it only takes effect on certain drives or partitions?

9.	When you exit Windows after configuring 32-bit file access, Windows automatically restarts itself.

10.	Sometime after configuring 32-bit file access, you start getting "File is damaged" error messages from Windows.

11.	PC hangs during WIN startup, while Windows logo is on screen.

Q6: Windows seems slower with 32-bit file access than it did with 16-bit.

A: Make sure you have the correct copy of RMM.D32 (see Q3a).  You can also try decreasing your Windows cache size (see Q3A1a,Q5c) or adjusting or swap- file settings (see Q3b).

Q7: PC hangs when you exit Windows.

A: Make sure you disabled SMARTDRV double buffering, as explained above in Q3A6.

Q8: You know your PC should support 32-bit file access, but it does not take effect.

A: Make sure you have the VCACHE.386 driver (see Q3A5).  Make sure you do not have a SUBST command in effect (see Q20).  Finally, try disabling TSRs temporarily.  When a TSR accesses a file while Windows is starting up, or any DOS application has left a file open, WFWG disables 32-bit file access. Common examples of such TSRs are print caches and background FAX handlers.

Q8a: What if it only takes effect on certain drives or partitions?

A: Check the [386Enh] section of C:\WINDOWS\SYSTEM.INI to make sure there are "device=ios.386" and "device=vxdldr.386" commands present.  If that isn't the problem, try adding a command of the form "ForceMapper=<drives>" where <drives> is a string of drive letters representing the partitions that are still getting 16-bit access (e.g., "ForceMapper=C").

Q9: When you exit Windows after configuring 32-bit file access (step Q3A9 above), Windows automatically restarts itself.

A: This seems to be a harmless nuisance.  Just reboot the PC with Ctrl-Alt-Del.

Q10: Sometime after configuring 32-bit file access, you start getting "File is damaged" error messages from Windows.

A: If you let system cache file writes as well as reads, you can get dangerous file corruption.  If you decide to cache writes (see Q5a), this indicates you may want to rethink that choice.  You can switch to safer (but slower) "store-through" caching by carrying out steps Q3A4a and Q3A7b.

Q11: PC hangs during WIN startup, while Windows logo is on screen.

A: Check in your SYSTEM.INI file in c:\windows in the [386Enh] section for a command of the form "NoEMMDriver=On". If you remove this command, you will probably be able to restart Windows.  (However, it may not work if your PC does not use the RMM.D32 driver for 32-bit file access.  See Q3A2.)  This is a confirmed problem that Microsoft plans to fix in an upcoming WFWG release [cf. Microsoft Knowledge Base Q108818].


Trademarks
Trademarks:

"Windows" and "Windows for Workgroups" are trademarks or registered trademarks of Microsoft Corporation.  Any other trademarks used in this document are the property of their respective companies.