Archive-name: ms-windows/32bfa-faq/part1Posting-frequency: monthlyLast-modified: July 24, 1995Version: 1.0 32-BIT FILE ACCESS Frequently Asked Questions (Part 1 of 5) ---------------------------------------------Copyright (c) 1995 by Michael McCormick, all rights reserved.This is of mainly interest to Windows for Workgroups (WFWG 3.1x) users.Windows NT and Win95 users may benefit from some parts also.Usual disclaimers apply. The author does not warranty or guarantee factualcorrectness of all details. The author does not speak here for Unisys, norfor Microsoft. "Windows" and "Windows for Workgroups" are Microsofttrademarks. Microsoft is ultimately the only real authority on theirproducts.To be sure you are reading the latest version of the FAQ, see "How to Getthis FAQ" section at the end.This is still an evolving FAQ. The author considers this FAQ to some extenta 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 isposted in its entirety and includes this disclaimer section. This FAQmay be archived at any public FTP or WWW location, as long as it is archivedin its entirety, following the "Archive-name" (see above: the "/partx" partcan 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 beincluded in commercial collections, publications, or applications withoutexpress permission from the author.Thanks to all the many people around the world who helped with commentsor suggestions on the earlier versions.I am still looking for corrections and feedback. Particular areas wherethis FAQ needs some help are called out in a section at the end of theFAQ 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 your Windows System directoryelsewhere, 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.____________________________________________________________________________CONTENTS (*=new,+=changed)PART ONE: 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 / 95 feature? 2. What PCs can run 32-bit file access? 2a. Does it work with CD-ROM?PART TWO: 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?+ 3c. How do you deinstall (permanently disable) 32-bit file access? 3d. How can you just turn off 32-bit file access temporarily? 3e. How do other WIN command switches affect 32-bit file access? 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?PART THREE: Optimization 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?PART FOUR: 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? 8b. What if it only takes effect when 32-bit disk access is on? 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. 11a. You get an error message during WIN startup: "Microsoft 32-bit disk driver (WDCTRL) cannot be loaded". 11b. You get an error message when you run a Windows .EXE: "Segment Load Failure".PART FIVE: 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?+Revisions Needs+How To Get This FAQ____________________________________________________________________________ BACKGROUNDQ1: What is 32-bit file access?A: Without 32-bit file access, Windows has to perform every file accessthrough DOS and the underlying BIOS. This requires switching the CPU into16-bit real mode. With 32-bit file access, Windows stays in control ofthe file operation, and executes in 32-bit protected mode. [cf. WFWGResource 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), itoutperforms all previous caches (Smartdrv, Cacheclk, NCache, etc.)on standard benchmarks. It even outperforms them running on acomparatively smaller cache.Q1b: Is it different than 32-bit disk access?A1: 32-bit file and disk access are similar but different, which is asource 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 modewhile directly accessing the disk bus and remaining at CPU speeds. Itdoes less for performance than 32-bit file access. It comes with its ownset of problems, and is NOT the subject of this FAQ!A2: 32-bit file access does not require 32-bit disk access. (If it seems toon your machine, see question Q8b.)A3: 32-bit file access does not replace 32-bit disk access.A4: "Any INT21H calls that are processed by VFAT are handled entirely inprotected mode. The performance increase obtained by 32-bit disk accessis now increased further with 32-bit file access." [WFWRKMA 3.11]Q1c: Isn't 32-bit file access a Windows NT / 95 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 systemis capable of 32-bit. This FAQ is only about 32-bit file access inWindows for Workgroups.Q2: What PCs can run 32-bit file access?A: Normally any 386/486/586 PC running Windows for Workgroups (asopposed to regular Windows 3.11) in Enhanced Mode (normally WFWG can't runin any other mode anyway). Unlike 32-bit disk access, it doesn't usuallydepend on your disk type. If the 32-bit File Access checkbox appears inyour control panel (see Q3A1), then Windows at least *thinks* your systemcan use it. But the only way to be sure is to configure it (see Q3), thenverify your machine is actually using it (Q4).Q2a: Does it work with CD-ROM?A: No, you cannot access your CD-ROM drive with 32-bit file access. Accesswill remain in the slower 16-bit uncached mode, but otherwise the CD-ROMwill work fine as before. MS-DOS 6.2 (or higher) users can improve theirCD-ROM performance with SMARTDRV however (see Q5).____________________________________________________________________________ CONFIGURATIONQ3: How do you turn on 32-bit file access?A: Here are the configuration steps. Backing up your hard drive first isrecommended. To perform these steps you will need to decide whether youwish 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 WindowsUser's Guide:] Double click Control Panel, double click 386Enh icon,click Virtual Memory, click Change, click the 32-bit File Accesscheckbox (it doesn't matter which drive is selected above). Be readyfor these side-effects: (1a) The Cache Size value will probably change automaticallyat this point. Optimizing cache size can add considerably to the perform-ance improvement you get with 32-bit file access. Try 1024KB for now andexperiment with this later, if in doubt. See Q5c for optimizing tips. +(1b) The Swapfile settings may also change automatically atthis time. Do not attempt to reset swapfile to "Temporary"; that isnot allowed with 32-bit file access. Also don't set the Swapfile Sizeto the "Recommended Size" displayed. That is based (mainly) on diskspace available, not always on what is really best for your system.(A small but non-zero amount of Permanent swapfile, typically 1-9MB,seems to work best. Don't assume the amount that worked best before32-bit file access will still be optimal. See also Q3b.) Be careful thecorrect drive is selected -- it may show "C:" now even if you used to keepthe swapfile somewhere else. (Note: Permanent swapfile must not be on acompressed drive.) (1c) Click OK to close the control panel. (1d) Click "Continue" -- do not restart Windows yet. +(2) If you are not running 32-bit disk in addition to 32-bit fileaccess, you are going to need the Real Mode Mapper 32-Bit Driver (RMM.D32).If that includes you, 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 (or is the older version) see Q3a before proceeding. (3) Use File Manager to find IFSHLP.SYS in C:\WINDOWS. If itis not there, obtain it or disable 32-bit File Access; running 32-bitfile access without the "Installable File System Helper" (IFSHLP) isnot 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. Skipthis step if you want write caching. See question Q5a if you're unsure. (4a) Use System Editor to edit your C:\WINDOWS\SYSTEM.INIfile. Find the section labeled "[386Enh]". Add the followingstatement anywhere in that section: "ForceLazyOff=C"; or if your PChas a partitioned hard drive, insert "ForceLazyOff=Cx", where "x"is a string of letters representing other partitions. The onlypartitions you can safely omit are those that contain only temporaryand/or read-only data. For instance, a D: drive containing just \TEMPplus your swapfile could be omitted for even faster performance. +(5) As long as you are in the [386Enh] section, make sure youhave the statement "device=vcache.386" somewhere in there. Bydefault it is always present, but some people have removed it fromtheir systems to prevent unwanted caching. Somewhere nearby should alsobe "device=ifsmgr.386" and "device=vfat.386". (And unless you run 32-bitdisk access, you will also need "device=vxdldr.386" which is the virtualdriver that uses RMM.D32.) (5a) And while you're still in the [386Enh] section, check for thestatement "NoEMMDriver=ON". If it's there, you may need to REMOVE it, orat least make a note of it in case you get a Windows hang later when yourestart WFWG with 32-bit file access (see Q11). (6) This next step (6a) removes double buffering from yourSMARTDRV cache. If you want to keep SMARTDRV on your system (see Q5),this step is not required but it does seem to improve performance formany users. You may choose to skip (6a) for now, especially if youknow your PC has a bus mastered DMA disk controller, or if your PCowner's manual says you need double buffering to run SMARTDRV. (6a) Use System Editor to edit your C:\CONFIG.SYS file. Lookfor a command of the form "device=smartdrv.exe /double_buffer". Ifit is there, remove it. (Or if you have DOS 6.0 or higher, you canjust "REM it out" instead of actually deleting it.) (7) If you want to keep SMARTDRV on your system (see Q5), dothe following: (7a) Use System Editor to edit your C:\AUTOEXEC.BAT file. Find the SMARTDRV call. If the /L switch is present, remove it. Thetwo numbers at the end of the line are the sizes (in KB) of the DOSand Windows caches. Set the Windows cache size (2nd number) to 0unless you use floppy disks, CD-ROMs, or optical disks heavily inWindows. 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 surenone of the drive letters are followed by a "+" sign on the SMARTDRVcall. Remove any "+" sign you find post-fixed to a drive letter. If anydrive letters are missing (excluding compressed volumes), add them to theSMARTDRV call because omitting a [non-compressed] drive is the same asspecifying it with the "+" sign.... Or add a /C switch to the SMARTDRVcall to change the default mode to store-through caching on all drives,or a /F switch to force frequent cache writes. (7c) Use System Editor to edit your C:\CONFIG.SYS file. Lookfor 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 alarger value is present, change it to "buffers=3". (Heavy DOS usersmay prefer a higher value, say 10. Never set it above 48!) (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. Lookfor a command of the form "buffers=<value>", typically "buffers=3,0".Change it to "buffers=10". (Heavy word processing users and users withFILES configured high [see next step] may prefer a higher value, say 30.Never set it above 48!) (9) While you are in CONFIG.SYS, look for "files=<value>".If it is not there, or if the value is less than 30, consider settingit to 30 or more. (Maximum open files allowed is 255.) (10) Go back to AUTOEXEC.BAT and look for the command line"UNDELETE /LOAD". If present, you may want to "REM" it off to conserveresources unless you delete files a lot outside Windows (in DOS). SeeQ12 for more information. +(11) Close System Editor. Exit Windows. (Optional: To get anextra performance boost, this may be a good time to run DEFRAG.) Rebootthe 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 bestpossible performance from 32-bit file access (see Q3A2). Some PCs show nomeasurable improvement moving from an old to new version of RMM.D32. OtherPCs show major improvement. A few cannot use 32-bit file access at allwithout it; for example, if you run disk compression (DoubleSpace, Stacker)and your hard disk is not INT13 compatible. You can obtain the latestversion 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, isthat you can only use a Permanent swapfile with 32-bit file access. ATemporary swapfile is not allowed. Running with swapfile set to "None" isallowed, but will not perform as well with 32-bit file access as a smallpermanent swapfile (see Q3A1b). Note a major change in your swapfile typeor size may require you to resize your cache as well (see Q5c). Also: Donot put a permanent swapfile on a compressed drive (see Q13).Q3c: How do you deinstall (permanently disable) 32-bit file access?A: If you think disabling 32-bit file access is going to solve some specificproblem, you may wish to try turning it off temporarily (see Q3d) beforecarrying out these drastic steps. You may find 32-bit file access wasnot the real cause of your problem, or that you cannot live with theslower performance of 16-bit file access. Assuming you are serious aboutdeinstalling it, here are the steps. Backing up your hard drive first isencouraged: (1) Start Windows with 16-bit mode switches: "WIN /d:cf". (2) Double-click Control Panel, double-click 386Enh icon, clickVirtual Memory, click Change, click off the 32-Bit File Access checkbox. (2a) At this moment, Cache Size will change automatically (typicallyto 512KB). If you are going to use SMARTDRV to cache your hard drives inWindows now, set Cache Size here to zero. (2b) If you wish, you are now free to change your swapfile to Noneor Temporary. In any case, make sure the correct drive is selected; it mayshow "C:" now even if you used to keep swapfile somewhere else. (2c) Click OK to close the control panel. (2d) Click on "Restart Windows". (3) You probably want to use SMARTDRV to cache your hard drive(s)in Windows now. If so, do all the following. (If not, skip to step 4.) (3a) Use the System Editor (Notepad will do if need be) to editC:\CONFIG.SYS. Search for a "REM device=smartdrv" statement. If found,remove the "REM ". If not found, don't worry about it. (3b) While in CONFIG.SYS, look for "buffers=<value>". If the valueis 10 or more, consider lowering it to something in the 3-10 range. If notfound, don't worry about it. (3c) Switch your System Editor window to C:\WINDOWS\SYSTEM.INI.Look in the [386Enh] section for "device=vcache.386". If found, insert asemicolon before it or remove it altogether. If not found, don't worry. (3d) Switch to C:\AUTOEXEC.BAT. Search for a SMARTDRV command. Ifprefixed with "REM " then remove the "REM ". Increase the last number onthe command (Windows cache size) to at least 256. If the command is notfound, you need to reinstall SMARTDRV -- consult MS-DOS manual and HELP. (3e) Exit System Editor. (4) You can start using Tracker or Sentry UNDELETE in Windows again.If you had disabled it due to the 32-bit incompatibility (see Q12) then youcan turn it back on now. The easiest way is to double-click the MWUNDELicon, pull down the Options menu, click on "Configure Delete Protection",click on the checkbox for Sentry or Tracker, and click OK. (5) Exit Windows. Reboot PC. Restart Windows. Make sure 32-bitfile access is turned off and your applications still work.Q3d: How can you just turn off 32-bit file access temporarily?A: Start Windows with the 16-bit file access switch: "WIN /d:c".32-bit file access will be disabled just for that single Windows session.Q3e: How do other WIN command switches affect 32-bit file access?A: Here is the list: WIN /d:c Disables 32-bit file access (32BFA). WIN /d:f Disables 32-bit disk access; does not affect 32BFA. WIN /d:v Disables virtual disk; might slow down 32BFA. WIN /n Disables networking; could enable 32BFA if it were inhibited by network driver problems. WIN /s Standard mode; theoretically would disable 32BFA, but this switch isn't allowed by WFWG.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, clickVirtual Memory. If 32-bit file access is not working, an error boxwill probably pop up at this point. Otherwise you get an informationdisplay window. Check the "File Access" panel at the bottom. If itsays "32-bit" then 32-bit file access is now being used. (If your harddrive 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 isnormal for drives other than hard disks (RAM disk, CD-ROM) to show16-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 thisand use it to check whether 32-bit file access is in effect instead of thecontrol panel, but only if you prefer it. (The software is provided aspart of Microsoft's "Windows for Workgroups Resource Kit Addendum forVersion 3.11". The program name is VFATSTAT.EXE) Win95 note: This programwill appear to run on Windows 95 and tell you do *not* have 32-bit fileaccess -- it is lying!___________________________________________________________________________ OPTIMIZATIONQ5: Should you run SMARTDRV if you have 32-bit file access?A: The best answer seems to be "it depends". Removing SMARTDRV (seeQ3A8) frees up about 31K of lower memory and 512K of extended memory,but DOS runs slower and Windows takes longer to load. KeepingSMARTDRV (see Q3A7) slightly reduces memory availability but makesDOS faster and makes Windows start up more quickly. Once Windows isup and running, it will only use SMARTDRV for floppy disk (or CD-ROMor optical disk) access, but not for the hard drive. (This is trueeven if C drive letter appears on the SMARTDRV command.) So thereasons to keep SMARTDRV in addition to 32-bit file access would befor running DOS applications, using floppy or CD-ROM, or booting up intoWFWG more quickly. The price you pay is less memory. You can runSmartmon in Windows to determine to what extent SMARTDRV currently iscaching your floppy or CD-ROM drives. (Note DOS 6.2 or higher is neededto cache a CD-ROM. To prevent it from caching CD-ROM, add the /U switch tothe SMARTDRV command in AUTOEXEC.BAT.) For caches other than SMARTDRV,refer to Q17.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 reapeven greater performance benefit for your PC. However, you also risk filecorruption or data loss if a write never makes it from your cache in RAMonto your hard disk. Both Smartdrv and the Windows cache give you theoption of "store-through" caching to eliminate the risk. You shouldprobably avoid write caching if your PC is subject to unexpectedinterruptions (power loss, hangs, toddler hitting reset) or if it isconnected to a network. If you do use write caching, both Smartdrv andWindows cache do seem to force a save to disk at periodic intervals (asshort 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 possiblyhang or crash it, you can manually flush all the writes out of your RAMcache and force them onto your hard disk. For SmartDrive, 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-Delalso 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 toconserve memory and reduce "thrashing". For the Smartdrv cache, a Windowsprogram called SmartMon will display the hit rate. Try it while runninga typical heavy mix of applications, or while running a standard performancebenchmark (e.g., WinBench). (If you don't have SmartMon, you can get cachehit rate by entering "SMARTDRV /S" in a DOS box.) Now adjust the cache sizefor Windows until you achieve the highest possible hit rate. Do all thiswith 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 isconsumed at Windows start-up time. It is allocated from system resources.This is not the same as the "system resources" reported by Program Manager'sHelp (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 Windowscache.____________________________________________________________________________ TROUBLESHOOTINGQ6: 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 alsotry 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 explainedabove in Q3A6.Q8: You know your PC should support 32-bit file access, but it doesnot take effect.A1: Make sure you have the VCACHE.386 driver (see Q3A5).A2: Make sure you do not have a SUBST command in effect (see Q20).A3: Make sure 32-bit disk access isn't getting in the way (see Q8b).A4: Try disabling TSRs temporarily. When a TSR accesses a file whileWindows is starting up, or any DOS application has left a file open,WFWG disables 32-bit file access. Common examples of such TSRs areprint caches and background FAX handlers.Q8a: What if it only takes effect on certain drives or partitions?A1: Check the [386Enh] section of C:\WINDOWS\SYSTEM.INI to make sure thereare "device=ios.386" and "device=vxdldr.386" commands present.A2: Try adding a command of the form "ForceMapper=<drives>", where<drives> is a string of drive letters representing the partitionsthat are still getting 16-bit access (e.g., "ForceMapper=C").A3: Make sure you are not using a temporary swap file (see Q3b).A4: Scan for viruses on the affected drive and on the boot drive.Q8b: What if it only takes effect when 32-bit disk access is on?A: There are some machines where enabling 32-bit file access without32-bit disk access could appear not to work (some P4D Gateway PCs forexample). The obvious solution is to turn on 32-bit disk access, butthat can be difficult if your hard disk is not WD1003 compliant, hasmore than 1024 cylinders, etc. If that is not an option, try startingWindows with the non-virtual-disk switch: "WIN /d:v". If that gets 32-bitfile access working for you, then make it permanent by placing this state-ment in the [386Enh] section of C:\CONFIG.SYS: "VirtualHDirq=False".Q9: When you exit Windows after configuring 32-bit file access (stepQ3A9 above), Windows automatically restarts itself.A: This seems to be a harmless nuisance. Just reboot the PC withCtrl-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 getdangerous file corruption. If you decide to cache writes (see Q5a),this indicates you may want to rethink that choice. You can switchto safer (but slower) "store-through" caching by carrying out stepsQ3A4a 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] sectionfor a command of the form "NoEMMDriver=On". If you remove this command,you will probably be able to restart Windows. (However, it may not workif your PC does not use the RMM.D32 driver for 32-bit file access. SeeQ3A2.) This is a confirmed problem that Microsoft plans to fix in anupcoming WFWG release [cf. Microsoft Knowledge Base Q108818]. Q11a: You get an error message during WIN startup: "Microsoft 32-bit diskdriver (WDCTRL) cannot be loaded".A: WDCTRL is for 32-bit disk access. First try a virus scan (eg. McAfee2.2.0 or later). If that fails, try restarting Windows without 32-bitdisk access (WIN /d:f) -- 32-bit file access should still be working.(If not, see Q8a.) Now you must either get your 32-bit disk access fixedor disable it permanently -- not the subject of this FAQ!Q11b: You get an error message when you run a Windows .EXE: "Segment LoadFailure".A: This could indicate file corruption -- see question Q10. However it mayalso indicate insufficient file handles -- look in the [boot] section of C:\WINDOWS\SYSTEM.INI for "CachedFilehandles=<value>" and try