| Foreword | p. xv |
| Acknowledgments | p. xvii |
| Bulletproofing: A Unique Approach to PC Support | p. 1 |
| Welcome to Windows 95 | p. 1 |
| Welcome to Bulletproofing | p. 2 |
| Aspects of Bulletproofing | p. 5 |
| About this Book | p. 7 |
| Windows 95 and Today's PC | p. 9 |
| Microsoft's View of the World | p. 9 |
| Your View: Does Upgrading Make Sense? | p. 10 |
| What About Alternatives? | p. 12 |
| Planning for Windows 95 | p. 15 |
| Defining Organizational Goals for Windows 95 | p. 16 |
| Sample Organizational Goals for Windows 95 | p. 16 |
| Where Windows 95 Fits in Your Organization | p. 17 |
| Setting up Test Systems | p. 17 |
| Steps in a Phased Implementation Strategy | p. 18 |
| Identifying Hardware Migration Issues | p. 22 |
| Device Driver Issues | p. 22 |
| RAM Planning | p. 23 |
| BIOS Issues | p. 23 |
| Identifying Software Migration Issues | p. 23 |
| DOS Software | p. 23 |
| Win16 Software | p. 24 |
| Win32 Software | p. 24 |
| Stand-alone versus Server-Based Execution | p. 25 |
| Windows 3.x Compatibility Features | p. 27 |
| Planning for Backup Capability and Virus Protection | p. 27 |
| Backup | p. 27 |
| Viruses | p. 28 |
| User Education during the Transition | p. 28 |
| Empowering Support Staff | p. 29 |
| During the Transition | p. 29 |
| After the Transition | p. 29 |
| Summary | p. 31 |
| Bulletproofing Installation | p. 33 |
| The Windows 95 SETUP Process | p. 33 |
| Initialization | p. 34 |
| Safe Recovery | p. 36 |
| Gathering User Information | p. 36 |
| Hardware Detection | p. 36 |
| Component Selection | p. 37 |
| Startup Disk Creation | p. 38 |
| File Copying | p. 39 |
| OS Replacement | p. 39 |
| Final Configuration | p. 39 |
| Run-Once Configuration | p. 39 |
| Second Restart | p. 39 |
| Guide to Installation Bulletproofing Tips | p. 41 |
| Windows 95 installation freezes with third-party memory managers | p. 41 |
| We're using Ontrack Disk Manager and don't know if Windows 95 is compatible | p. 42 |
| Windows 95 refuses to install on some 80386 machines | p. 43 |
| Windows 95 won't complete installation successfully on PCs with virus protection | p. 44 |
| SETUP won't progress past the automatic SCANDISK phase | p. 45 |
| SETUP indicates there's enough room on a compressed disk, but it fails later | p. 46 |
| SETUP complains about an incompatible TSR | p. 47 |
| SETUP reports a "bad" diskette #2 and terminates | p. 48 |
| The PC powers down in the middle of installing Windows 95 | p. 49 |
| SETUP fails inexplicably and won't complete after repeated attempts (1) | p. 49 |
| SETUP fails inexplicably and won't complete after repeated attempts (2) | p. 50 |
| AUTOEXEC.BAT and CONFIG.SYS still have many settings after SETUP | p. 52 |
| Windows 95 didn't install properly, and we can't uninstall | p. 54 |
| We installed Windows 95 from diskette, and a lot of files are missing | p. 55 |
| We need to run some Windows 3.x software that's incompatible with Windows 95 | p. 57 |
| Windows 95 won't start and we suspect file corruption | p. 58 |
| After running SETUP, DOS HELP is unavailable | p. 60 |
| Devices under Windows 95 won't work properly after SETUP | p. 60 |
| Installers make inappropriate choices when running SETUP interactively | p. 62 |
| Users have too much "read me" information after SETUP | p. 67 |
| Bulletproofing Memory and DOS Support | p. 69 |
| Primary Memory Types | p. 69 |
| Conventional Memory | p. 70 |
| Expanded Memory | p. 70 |
| Extended Memory | p. 70 |
| Upper Memory | p. 71 |
| Virtual Memory | p. 71 |
| Windows 95 and the 80386 Architecture | p. 71 |
| Protected-Mode Memory | p. 72 |
| 32-Bit Linear Addressing | p. 73 |
| Private Memory Space | p. 73 |
| Virtual Machines | p. 74 |
| Windows 95 and DOS Support | p. 75 |
| Separate Virtual Machines | p. 75 |
| PIF Files | p. 76 |
| MS-DOS Mode | p. 76 |
| Guide to Memory and DOS Support Bulletproofing Tips | p. 77 |
| We don't know how much RAM Windows 95 programs really need | p. 77 |
| Our 8MB networked PC is swapping constantly | p. 80 |
| We use RAM doublers, and DEFRAG corrupts files | p. 82 |
| Users report "System Resources" errors | p. 82 |
| Users report occasional "parity errors" | p. 83 |
| Windows 95 virtual memory seems too slow | p. 84 |
| We need expanded memory support, but Windows 95 reports it's unavailable | p. 86 |
| We still need more DOS session memory | p. 86 |
| We'd like to have DOSKEY available without using up conventional memory | p. 88 |
| DOS programs lock up or crash Windows 95 | p. 89 |
| When users enter MSDOS Mode, they can't see CD-ROM or network drives | p. 90 |
| When users enter MSDOS Mode, their shared resources are unavailable to others | p. 90 |
| DOS programs run too slowly under Windows 95 | p. 92 |
| DOS programs have trouble writing to the screen | p. 93 |
| When a DOS program switches from text mode to graphics mode, garbage appears | p. 95 |
| DOS communications programs seem slow | p. 95 |
| Miscellaneous DOS apps have various problems | p. 96 |
| A DOS program that worked fine under Windows 3.x doesn't work anymore | p. 96 |
| DOS users can't find deleted files in the Recycle Bin | p. 97 |
| DOS programs complain about "Incorrect MS-DOS Version." | p. 97 |
| Bulletproofing the File and Display Systems | p. 99 |
| The Windows 95 File System | p. 99 |
| IFS Manager | p. 99 |
| VFAT | p. 101 |
| CDFS | p. 101 |
| Third-Party FSDs | p. 102 |
| Block I/O Subsystem | p. 102 |
| Real-Mode Drivers | p. 102 |
| Workstation Directory Structure | p. 103 |
| The Windows 95 Display System | p. 104 |
| Dance of the APIs | p. 104 |
| Display Architecture Pros | p. 105 |
| Display Architecture Cons | p. 105 |
| Guide to File and Display Systems Bulletproofing Tips | p. 107 |
| Windows 95's file system runs in "compatibility mode" on some PCs | p. 107 |
| Explorer has problems with filenames having extended characters | p. 109 |
| Users forget to run SCANDISK and DEFRAG regularly | p. 110 |
| DEFRAG leaves some files fragmented | p. 113 |
| The wrong application runs when a user opens a data file | p. 113 |
| DriveSpace volumes won't mount | p. 115 |
| Long File Names are being corrupted or destroyed | p. 116 |
| The root directory of a drive fills up earlier than it used to | p. 117 |
| File system performance profiles don't work properly | p. 118 |
| Users report "Error Reading from Drive A:" when accessing diskette drives | p. 120 |
| Windows 95 freezes when we use our old CD-ROM drive | p. 120 |
| Large CD-ROM file transfers hang the system | p. 121 |
| CD-ROM jukeboxes slow Windows 95 down | p. 122 |
| Autorun slows performance | p. 122 |
| Windows 95 doesn't seem to find our PCI SVGA card | p. 124 |
| When troubleshooting video problems, the acceleration slider has no effect | p. 124 |
| The video card refresh rate is too low in Windows 95 | p. 125 |
| Users need faster graphics | p. 126 |
| Users report various video problems | p. 127 |
| Users have difficulty changing monitor settings | p. 128 |
| Bulletproofing Printing | p. 131 |
| Advantages of Windows 95 Printing | p. 131 |
| Enhanced Metafile Spooling | p. 132 |
| Plug-and-Play | p. 133 |
| PostScript Level 2 | p. 133 |
| Mini-Driver Architecture | p. 134 |
| Fonts | p. 134 |
| Guide to Printing Bulletproofing Tips | p. 137 |
| Windows 95 won't auto-configure a new bidirectional printer | p. 137 |
| Users have trouble installing and configuring printer drivers | p. 138 |
| Jobs don't print at all | p. 141 |
| Some DOS and Windows programs can't print to UNC pathnames | p. 142 |
| Windows 95 prints garbage to a new bidirectional printer | p. 143 |
| Applications don't print text on inkjet printers | p. 143 |
| Complex documents that printed under Windows 3.x don't print under Windows 95 | p. 144 |
| Windows 95 won't print with some printer-sharing devices | p. 146 |
| Printing starts, but stalls out | p. 147 |
| HP Laser Jets log frequent "Error 20" or "Error 21" codes | p. 148 |
| Applications report "Driver Not Found" errors | p. 148 |
| Printing is slow, but EMF spooling is on | p. 149 |
| Drag-and-drop printing isn't working | p. 151 |
| Print files aren't editable | p. 152 |
| There's no "work offline" option for local printers | p. 152 |
| Users deleted some fonts and they're really gone | p. 153 |
| Screen fonts and printer fonts don't always match up | p. 154 |
| Users can't keep track of all their fonts | p. 156 |
| Users can print from DOS, but not from Windows 95 | p. 157 |
| Some programs have trouble printing to a shared printer | p. 158 |
| Bulletproofing Networking | p. 159 |
| Protected-Mode Drivers | p. 160 |
| Modular Network Architecture | p. 160 |
| LAN Card Drivers | p. 160 |
| Transport Protocols | p. 160 |
| Transport Programming Interfaces | p. 163 |
| Redirectors | p. 163 |
| Network Providers and APIs | p. 163 |
| File System Integration | p. 164 |
| Multiple Network Support | p. 164 |
| Guide to Networking Bulletproofing Tips | p. 165 |
| Users report poor network performance | p. 165 |
| New network cards sometimes work with Windows 95 and sometimes don't | p. 167 |
| Notebook PCMCIA network cards that worked with Windows 3.x don't work with Windows 95 | p. 169 |
| Users report a variety of errors when opening files on NetWare 3.11 servers | p. 170 |
| LFNs don't work on our NetWare servers | p. 171 |
| Users can't find network servers | p. 172 |
| Windows 95 doesn't properly see network volumes larger than 2GB | p. 174 |
| Windows 95 didn't ship with protected-mode drivers for our network | p. 175 |
| Windows 95 didn't ship with protected-mode drivers for our LAN cards | p. 176 |
| Users report intermittent network errors | p. 178 |
| We couldn't install real-mode network drivers after Windows 95 was already installed | p. 178 |
| Users are having trouble running network login scripts | p. 179 |
| Users aren't receiving network messages | p. 180 |
| Network clients on NT or NetWare don't keep good time | p. 182 |
| We've installed File and Printer Sharing for NetWare, but Windows 3.x machines can't see the shared resources | p. 182 |
| We're using NDS and aren't sure which Windows 95 LAN client to use | p. 184 |
| "Chat" and some other applications no longer work under Windows 95 peer subnets | p. 185 |
| Users can't see other peer servers | p. 186 |
| Mapped drives don't seem to work | p. 187 |
| Users attach to NetWare occasionally, but login scripts don't run | p. 188 |
| Bulletproofing Communications and Remote Access | p. 191 |
| The Windows 3.x Dilemma | p. 191 |
| The Windows 95 Solution | p. 192 |
| TAPI | p. 193 |
| Unimodem | p. 194 |
| VCOMM and Port Drivers | p. 194 |
| Bundled Applications | p. 195 |
| Guide to Communications and Remote Access Bulletproofing Tips | p. 196 |
| Users have to manage too many different e-mail systems | p. 196 |
| Exchange has problems with the Personal Message Store | p. 196 |
| Undocking a notebook causes a Windows 95 crash | p. 199 |
| V.34 modems aren't fast enough | p. 199 |
| PCMCIA modems appear twice in Device Manager | p. 201 |
| Programs can't seem to find the modem | p. 201 |
| U.S. Robotics and Hayes modems don't work reliably | p. 204 |
| Modems don't reach their maximum speed | p. 205 |
| Users report data loss and file transfer failures | p. 206 |
| Voice modem features are inaccessible | p. 209 |
| We have to set different "AT" command strings for different modems | p. 210 |
| Users can't use Direct Cable Connection with LapLink or InterInk | p. 212 |
| Users need quick access to online resources | p. 213 |
| Briefcase doesn't perform record-level reconciliation | p. 214 |
| Everybody has to share a Briefcase when user profiles are enabled | p. 216 |
| Notebook users need access to the central LAN | p. 216 |
| Dial-Up Networking clients report poor performance | p. 218 |
| Windows 95 users don't all have their own Fax line | p. 219 |
| Windows comm programs are "unable to initialize port" | p. 222 |
| File transfers with HyperTerminal seem slow | p. 222 |
| Bulletproofing the User Interface | p. 225 |
| Principles | p. 225 |
| Essential Information Only | p. 225 |
| Retracing One's Steps | p. 226 |
| Object Orientation | p. 226 |
| Consistency | p. 226 |
| Key New Features | p. 226 |
| "Start" Button | p. 227 |
| Taskbar | p. 227 |
| Object Manipulation | p. 227 |
| Dialog Box Enhancements | p. 228 |
| Shortcuts | p. 228 |
| New, Improved DOS Box | p. 229 |
| Guide to User Interface Bulletproofing Tips | p. 230 |
| Is there some way to provide convenient, custom "help" info to users? | p. 230 |
| There's no similar tool to Windows 3.x Recorder for automating operations | p. 232 |
| Users need to "Quick View" a wider variety of files | p. 232 |
| Many text files have nonstandard file extensions, but "Open With" is tedious | p. 233 |
| Users complain that the desktop feels sluggish | p. 234 |
| With nested folders, the desktop can quickly become cluttered | p. 236 |
| It's inconvenient to open Explorer at the top level every time | p. 237 |
| Explorer doesn't seem to save user preferences | p. 237 |
| Users are confused about "My Computer" vs. "Explorer." | p. 238 |
| It takes much longer to start and exit Windows 95 than Windows 3.x | p. 239 |
| Users without a sound card can't play WAV files | p. 241 |
| When running applications full screen, users can't [Alt]-[Tab] to the Desktop | p. 242 |
| Most users need to change desktop defaults | p. 242 |
| Users want to use the old Windows 3.x compatibility interfaces | p. 244 |
| Copying files to network locations and subdirectories is a chore | p. 245 |
| Multiple users of a given PC need to see their own desktop settings | p. 247 |
| Training labs need to restore standard desktops after class | p. 248 |
| Users sometimes delete files they shouldn't | p. 249 |
| Users can't easily see or extract files in .CAB format | p. 250 |
| We'd like to move, remove, or rename "special" desktop icons | p. 250 |
| Bulletproofing Security and Desktop Management | p. 255 |
| Security Issues | p. 255 |
| Access Control | p. 255 |
| Accident Recovery | p. 257 |
| Desktop Management Issues | p. 258 |
| Seeing What You Expect To See | p. 258 |
| Remote Access | p. 259 |
| The Central Role of the Registry | p. 259 |
| Registry Structure | p. 261 |
| Keys and Values | p. 261 |
| Main Branches | p. 261 |
| Guide to Security and Desktop Management Bulletproofing Tips | p. 264 |
| Users have trouble remembering multiple passwords | p. 264 |
| Users have too much access to key system settings via the Control Panel | p. 266 |
| Users have too much access to the Registry | p. 268 |
| Users have too much access to the network | p. 268 |
| We use mandatory user profiles for security, but can't control machine settings | p. 270 |
| Systemwide policies are too broad | p. 271 |
| We need to protect resources shared with peer services | p. 272 |
| Windows 95 clients use peer sharing under NT or NetWare, but we've heard it's not secure | p. 273 |
| The Registry is corrupt | p. 274 |
| Data from deleted files is showing up in documents | p. 275 |
| Our backup utility doesn't support long filenames | p. 275 |
| Windows 95 Backup doesn't support SCSI tape drives | p. 276 |
| Users don't back up as often as they should | p. 276 |
| The "Documents" list is a security hole | p. 279 |
| Our Windows 3.x antivirus utilities don't work anymore | p. 279 |
| Dial-Up Networking servers aren't secure | p. 279 |
| We can't run the risk of notebook thieves accessing our LAN | p. 282 |
| Technicians spend too much time managing desktops on-site | p. 283 |
| Users occasionally need to run the Windows 3.x desktop natively | p. 284 |
| Network user profiles aren't working | p. 286 |
| References and Resources | p. 287 |
| Glossary | p. 313 |
| Index | p. 341 |
| Table of Contents provided by Syndetics. All Rights Reserved. |