Reports from frustrated users complain about an annoying BUG present in all Windows XP editions, which seems to plague also some early Windows 95/98 releases: one canNOT take advantage of the handy "Copy To",
"Move To" and/or "Send To" context menu (shell) right-click functions available in any My Computer, Windows Explorer, Drive and Folder browser window/dialog box. But this can be FIXed by using the
Registration (.REG) file below.MANDATORY: You MUST log on as Administrator or Power user (or be part of a user group with administrative privileges) to be able to make Registry
changes!Copy & paste the contents between the lines below into Notepad → save it with the REG file extension (file name doesn't matter)
→ merge (register) it into your Registry by double-clicking on it → answer OK/Yes to all following prompts
→ fire up Windows Explorer → right-click on any file or folder
→ look for the "Copy To", "Move To" + "Send To" options →
How many times have you typed too many characters at the DOS prompt, only to perform common/repetitive tasks over and
over, that could actually be automated just by creating simple DOS based BATch (.BAT) files? I know I have. :( I'm
talking here about editing your MS-DOS mode boot files (if using any!): AUTOEXEC.BAT + CONFIG.SYS, located in the root
directory of your boot drive/partition (default is C:\).MEANING:
AUTOmatically EXECuted BATch file.
CONFIG.SYS = CONFIGuration SYStem file.
Windows + MS-DOS = *VITAL* BACKUP ISSUES" in READ1ST.TXT [part of both W95-11D.EXE and W31-11D.ZIP] for more details.A MUST for ALL Windows ME
users: Microsoft REMOVED COMPLETELY the access to native/real/true/pure MS-DOS mode from Windows Millennium Edition (ME)
[a.k.a. MS-DOS 8.00]! :( But you CAN get it back by applying the Unofficial DOS Patch, which
modifies COMMAND.COM + IO.SYS (from %windir%\COMMAND\EBD) + REGENV32.EXE (from %windir%\SYSTEM), in order to be able to boot
to native MS-DOS and use DOS mode startup files (AUTOEXEC.BAT + CONFIG.SYS), Windows 95/98 style, to be able to use your
(old) MS-DOS based apps/games that do NOT work from within a Windows DOS session/box, and tweak your CUSTOM AUTOEXEC.BAT +
CONFIG.SYS files to free MAXimum conventional DOS memory. Instead of going through all these annoying, time consuming
steps: shell out to a DOS prompt window (if doing this from within Windows GUI), type something like:EDIT
C:\AUTOEXEC.BATor:NOTEPAD C:\CONFIG.SYSthen press Enter, and finally type EXIT
and hit Enter [again :(] to close the DOS box (if running Windows) when done, you could simply use these 2 DOS style batch
files [11 KB, ZIPped; use one of these "Free Windows 9x/NT4/2000/ME/XP/2003/Vista/2008/7 File Shrinkers" to extract them]:
EAB.BAT + ECS.BAT [also part of both W95-11D.EXE + W31-11D.ZIP], for convenience and to save precious time. Both these
BATches bear suggestive names:
EAB.BAT = Edit
ECS.BAT = Edit Config.Sys.
I strongly recommend to place them
in a directory/folder listed in your PATH, to avoid changing directories in order to run them. Type PATH and hit Enter
from any DOS prompt to display your current path line. Alternatively you can create a new dedicated directory/folder
(example):MD C:\BATCHESbut make sure to add it to your "SET PATH=" statement (if any),
in CONFIG.SYS or AUTOEXEC.BAT, which should look something like this (examples using default install locations; modify if
different on your system):
Start by creating a handy MS-DOS shortcut (.PIF = MS-DOS
Program Information File) for each of them:
Windows 9x/ME users: right-click on an
empty Desktop spot → select New → Shortcut → browse to the directory where you have placed EAB.BAT (and when done repeat
all these steps also for ECS.BAT) → (double)-click on it → click Next → click Finish → right-click on your new MS-DOS
shortcut → select Properties → Program tab → check the "Close on exit" box → Misc tab → uncheck the "Warn if still
active" box → click Apply/OK. I recommend to rename these 2 PIF shortcuts to something more suggestive: right-click on
each one [one at a time ] → select Rename → type "Edit AUTOEXEC.BAT" instead of EAB.BAT, and then "Edit
CONFIG.SYS" instead of ECS.BAT (but don't type the quotes) → hit Enter. Optional: if you'd like to change the default
"ugly" MS-DOS icon (assigned by default to all PIF files from %windir%\SYSTEM\PIFMGR.DLL): right-click on each PIF shortcut
[one at a time ] select Properties → Program tab → click Change icon → browse to your favorite icon file (.ICO) or icon
library (.DLL, .EXE or .ICL) → scroll through the icons if more than one → (double)-click the one you want → click
Apply/OK. Note that by default the .PIF file extension is hidden in Win9x/ME, unless you use File Manager (FM =
%windir%\WINFILE.EXE) to "see" it.
Windows/WfWG 3.1x users: open (if not already running) Program Manager (ProgMan = %windir%\PROGMAN.EXE) → create/open/select desired
Program Group → click File → select New → check Program
Item → type "Edit AUTOEXEC.BAT" for EAB.BAT, and then "Edit CONFIG.SYS" for ECS.BAT in the Description box
(but don't type the quotes) → browse to the directory where you have placed EAB.BAT (and when done repeat all these steps
also for ECS.BAT) → double-click on it → click Change Icon → browse to your favorite icon file (.ICO) or icon library
(.DLL, .EXE or .ICL) → scroll through the icons if more than one → double-click the one you want → click
From now on you will be able to edit your boot files from within Windows with a single mouse (double)-click. If running them
from native MS-DOS mode (outside Windows), just type EAB (or ECS) and press Enter. That's it.NOTES: Both EAB.BAT + ECS.BAT are "smart" enough  to...
Take in consideration if you dual-boot between Win9x/ME and MS-DOS 6.xx, and open the correspondent boot files
(only if present) for editing.
Use a different text/ASCII editor/viewer depending on current Windows/DOS mode:
Notepad (%windir%\NOTEPAD.EXE = Windows 3.1x/9x/ME default editor) if running them from a
Windows DOS prompt box/session/window.
EDIT.COM (%windir%\COMMAND\EDIT.COM in Win9x/ME, or C:\DOS\EDIT.COM or
C:\MSDOS\EDIT.COM in MS-DOS 6.xx = MS-DOS default editor) if running them from the native/real/true/pure MS-DOS
6.xx/7.xx/8.00 mode C:\> prompt.
Use the built-in VER command for OS detection to check for running MS-DOS
and/or Windows versions, thus editing the proper boot files (only if present):
AUTOEXEC.BAT + CONFIG.SYS = used by ALL Windows 95/98/ME + MS-DOS 6.00/6.20/6.21/6.22
AUTOEXEC.DOS + CONFIG.DOS = MS-DOS 6.xx AUTOEXEC.BAT + CONFIG.SYS files renamed by Win9x/ME Startup Manager
when booting to Windows 9x/ME.
AUTOEXEC.W40 + CONFIG.W40 = Windows 9x/ME AUTOEXEC.BAT + CONFIG.SYS files
renamed by Win9x/ME Startup Manager when booting to MS-DOS 6.xx.
Abort and exit if using ANY MS-DOS release older
than 6.00, because Win9x/ME do NOT support dual-booting with MS-DOS 5.0 or ANY other earlier build. :(
automatically upon completion, returning control to the running OS.
Automatically create BACKUPS of your ORIGINAL
files in C:\ root, BEFORE you start making ANY changes:
AUTOEXEC.D6X + CONFIG.D6X =
if using MS-DOS 6.xx.
AUTOEXEC.W9X + CONFIG.W9X = if using Windows 9x/ME.
Require ALL these files for
proper operation: ATTRIB.EXE, CHOICE.COM, FIND.EXE, MEM.EXE, START.EXE [Win9x/ME only], NOTEPAD.EXE + EDIT.COM
to reside in their DEFAULT directories/folders, which are normally listed in the system PATH!
Of course, you
could use the SysEdit tool (%windir%\SYSTEM\SYSEDIT.EXE) bundled with ALL Windows 3.1x/95/98 releases to modify
your AUTOEXEC.BAT + CONFIG.SYS, but SysEdit canNOT edit boot files other than the ones used by the current OS, or with
different file extensions (.DOS or .W40). :( The only advantage is that SysEdit creates backups of your original system
files (BUT ONLY IF you modify them first!) with the .SYD extension: AUTOEXEC.SYD + CONFIG.SYD in C:\ root. Microsoft
removed SYSEDIT.EXE from Windows ME. :( See "RESTORE SYSEDIT", also in TIPSME.TXT [part of
W95-11D.EXE], for details on how to get it back.You can view and/or further modify EAB.BAT + ECS.BAT if
you wish, to adapt them to your particular needs, by opening them in Notepad in Windows or EDIT.COM in DOS.IMPORTANT: If you experience any problems/errors/lockups after modifying your boot files, you can always
RESTORE your ORIGINAL AUTOEXEC.BAT + CONFIG.SYS files (if any) from the existent BACKUPS (ONLY IF you have ALREADY used
EAB.BAT + ECS.BAT!), by copying the respective *.D6X and/or *.W9X files located in C:\ root back to *.BAT, *.SYS, *.DOS
and/or *.W40, respectively. Examples:
Using Windows 9x/ME:COPY
Using MS-DOS 6.xx:COPY C:\CONFIG.D6X
In case your PC locks up, you can either:
(Re)boot from a
bootup/startup backup floppy diskette or CD-ROM (only if this feature is supported by your motherboard BIOS) containing the
system files (MSDOS.SYS, IO.SYS + COMMAND.COM) for your specific MS OS, or
Then restore your original files as described above. You MUST reboot when done.A
MUST: If you DO use boot files and/or DOS based programs/games, especially certain ones that canNOT run properly
from within Windows, see MEMORY.TXT [part of both W95-11D.EXE and W31-11D.ZIP]
for detailed guidelines on how to MAXimize your memory resources and speed up the bootup sequence in Windows 9x/ME and MS-DOS
6.xx, by tweaking your MSDOS.SYS [Win9x/ME only], AUTOEXEC.BAT + CONFIG.SYS files.
Courtesy of Freetone."Norton Internet Security and Norton Firewall (all versions) have a
hidden ATGuard-like desktop bar function from which you can control almost everything in the firewall. How to activate:
Create a shortcut on desktop for Iamapp.exe, located by default in the C:\Program Files\Norton
SystemWorks\Norton Internet Security folder. Rename the shortcut to something convenient like Norton Toolbar or
whatever you like.
Right-click on this shortcut and click Properties. In the destination box type " -appbar" at
the end of the line (without the marks but with the leading space). The line should look like this:"C:\Program Files\Norton SystemWorks\Norton Internet Security\Iamapp.exe" -appbar
Start the program first (or else an error message will occur) and then double-click the shortcut you've just created.
A bar on top of your desktop will open.
You can right-click on it for various options, drag it anywhere on the
desktop, enable autohiding, and tweak almost all firewall functions. As you surf the web you can watch statistics,
connections etc. Left-click on every indicator for a summary. If the bar is disabled, just double-click the shortcut to
get it back.There is also another hidden fuction which starts the firewall in no time and with no graphical interface
(Norton menu). Follow steps 1 to 3 above and use the " -load" parameter instead. Example:"C:\Program Files\Norton SystemWorks\Norton Internet Security\Iamapp.exe" -loadUse "
-unload" (same as above) to disable the firewall, and these: " -eventlog", " -trashcan", "
-settings", " -statistics" for other functions."
Even if your motherboard BIOS Setup doesn't support/include an option to turn off the annoying NumLock key
upon (re)boot, you can still do this by hacking your Windows NT4/2000/XP/2003 Registry. Start by copying & pasting the
lines below into a blank Notepad window, then save this file as NLOCKOFF.REG and finally (double)-click on it from
Windows Explorer or File Manager (FM = %windir%\WINFILE.EXE = NOT available in Windows 2000/XP/2003/Vista/2008/7/8/8.1/2012!) to turn OFF
NumLock:-----Begin cut & paste here----- REGEDIT4; All users: [HKEY_USERS\.DEFAULT\Control
Panel\Keyboard] "InitialKeyboardIndicators"="0"; Current user only: [HKEY_CURRENT_USER\Control
Panel\Keyboard] "InitialKeyboardIndicators"="0"------End cut & paste
here------To turn NumLock back ON, replace the "InitialKeyboardIndicators" value of 0 with
2, save the file and run it.Alternatively you can use NumLock
(freeware).TIP: To learn how to turn ON/OFF NumLock in Windows 95/98/ME, see "NUMLOCK ON/OFF", also in REGISTRY.TXT [part of W95-11D.EXE].
THE BUG:In Windows 98/2000/ME/XP/2003 [they all install MS IE 4/5/6 upon initial
setup :(] and in Windows 95/OSR1/OSR2/NT4 with MS IE 4/5/6 installed, there is an annoying Internet Explorer (IE)
vulnerability. Certain web sites force the opening of a hidden popup tracking minimized window upon your first visit, or when
you leave their web site, or when you close your browser while one of their web pages is still displayed. This is an
outrageous invasion of privacy, if you ask me! They do this by using the little known "about:" browser built-in
command into their HTML/DHTML/XML code. There is not much you can do, except close it by right-clicking on it and
selecting Close/Exit, or by highlighting it with a single mouse left-click and then pressing simultaneously Alt + F4. That is
if you can detect its small taskbar icon, because it won't allow to be restored or maximized, unlike the other well behaved
windows. :(THE FIX:You can kill ALL MS IE "about:" URLs permanently with
this Registry hack. Create a REG file in Notepad (save it as NOABOUT.REG for example), with these
Then run NOABOUT.REG from
Windows Explorer or File Manager (FM = C:\WINDOWS\WINFILE.EXE) to merge (import) this info into your Registry. This will
place all "about:" URLs into the MS IE Restricted Zone "hell", which means they will not open anymore when using IE to surf
the net. UPDATES:
"There is a downside to this fix - namely it will disable the
MS IE internet keyword for the www.about.com site, and also, it will kill
the use of a blank page as the startup browser page. There's not a lot that can be done for the former, as it seems that IE
cannot be made to differentiate between the keyword "about" and one of those annoying about: URLs. However, I've had good
success with fixing the latter by adding "about:blank" both under: Control Panel → Internet Options → click Security
tab → highlight Trusted sites → click the Sites... button → uncheck the "Require server verification (https:) for all
sites in this zone" box → highlight "Add this Web site to the zone:" box → type about:blank→ click the Add button
→ click OK twice, and this DWORD Value: "about:blank"=dword:00000003 under the same
Registry key above." [Thank you PC Mechanic!]
"This also kills Yahoo Messenger scripting, not allowing users to see any outgoing
or incoming typed text." [Thank you CC!]
Courtesy of Greg."I have applied this neat little trick from Virtual Plastic to get rid of the text from the Taskbar
buttons, leaving only the icons for all open windows and apps/games. Works with ALL Windows 95, 98, ME, NT4, 2000, XP +
2003 releases. Open Regedit and go to:HKEY_CURRENT_USER\Control Panel\Desktop\WindowMetricsIn
the right-hand pane → right-click on an empty spot → select New (if not present) → String
Value → name it MinWidth→ click OK → right-click on it (if present) → select
Modify → give it a value of -255 (which represents Taskbar size in pixels multiplied by 15) if your Taskbar size is 17 pixels→ close
the Registry Editor. You can adjust the "MinWidth" numeric value to match your Taskbar size (trial and error may be necessary):
Taskbar size can be changed from: Control Panel → Display →
Appearance → Item: →Active Title Bar→ push the up or down arrows and peek at the Size: box until it looks to
your liking → click OK/Apply. Default "MinWidth" setting is either -2310 or -2400 depending on your Windows version. You must
restart Windows for this change to take effect. This can be also done by running this REG file (i.e. name it
MINWIDTH.REG), you can create in Notepad (example using -255 for "MinWidth"):-----Begin cut & paste here----- REGEDIT4[HKEY_USERS\.Default\Control
Panel\Desktop\WindowMetrics] "MinWidth"="-255"------End cut & paste
here------from Windows Explorer or File Manager (FM = C:\WINDOWS\WINFILE.EXE) to merge (import) this information
into your Registry."Another way to achieve this is to use NanoSkin [40 KB, freeware].To (re)order/(re)arrange your Taskbar icons any way you want, get Taskbar Commander for Windows 9x/ME ONLY WITH MS IE 4/5/6
installed [17 KB, freeware].
This BUG FIX applies to ALL owners of NVidia TNT/TNT2, Vanta, GeForce/2/3/4 or Quadro/2/3/4 PCI/AGP video controllers
using Windows 95 B/C OSR 2.x, 98 retail, 98 SP1, 98 SE(U) or ME who installed NVidia Video Drivers v22.xx.NOTE: Windows 95 retail (original release) and 95a OSR1 (95 retail upgraded with SP1) do NOT support
AGP based video adapters! Windows 95B OSR 2.0 must be upgraded to OSR 2.1 with USB Service Update Pack
(USBSUP) to add AGP support!UPDATE: Tweaked Unofficial NVIDIA Display Driver 82.69 for Windows 98/98 SP1/98 SE/ME: NV8269.EXE [14.5 MB, multilingual]. Official NVidia Driver 81.98. List of all NVidia supported GPUs. NVidia Video drivers for older GPUs. BOTH BUGs described
here are finally FIXED! Therefore if using Drivers 27.xx or ANY other newer ones, you do NOT need to apply these BUG
FIXes!NVidia released on October 26 2001 yet another unofficial beta Detonator driver update, v22.80, or
4.13.01.2280 as displayed in Control Panel → Display → Settings tab → Advanced...
button → GeForce tab → Driver Version Information box. According to hardware dedicated web site reviewers 22.80 Detonators speed up DirectX 3D and
OpenGL apps and games by 5%. Worthy upgrade, if you ask me. NVidia Corp. Driver Division is well known for unleashing
frequent driver updates, aimed to provide their customers with better features and increased video performance. This is due in part to the increasingly tough competition, especially with ATI's Radeon 8500 64 MB DDR AGPx4 flag chipset catching up to the PC market leader's GeForce3 [code named
NV20] "heels". And now you're ready to see...THE BUG:If you have upgraded your Detonator set
from any 21.xx (or older) release [21.83 seems to be the most stable in these series] to any of the newer 22.xx (22.40, 22.50 or 22.80)
or 23.xx (23.10 or 23.11) drivers, you may [or may not] have noticed that NVidia changed [maybe on purpose, but I
believe this is a BUG?] these 2 OpenGL settings: Control Panel → Display icon → Settings tab → Advanced
button → GeForce tab → Additional Properties button → OpenGL Settings tab →
"Enable anisotropic filtering" (moved to a separate "Anisotropic Filtering" menu in Detonator 22.xx/23.xx) and "Disable support for enhanced CPU
instruction sets" check boxes.I'll explain here my case, running WinXP Pro in dual-boot with Win98 SE + all up-to-date
patches/fixes/updates/etc on my ol' "trusty" GeForce 256 AGPx2 32 MB DDR SDRAM Annihilator Pro vid card from Creative Labs:
in the Detonator 21.83 Display Properties panel I have cleared the "Disable support for enhanced CPU instruction sets"
box (see above) to take advantage of my Pentium III CPU SSE (Streaming SIMD Extensions) instructions, which includes
also the older MMX (MultiMedia eXtensions) set, built into all older Intel Pentium, Pentium Pro and Pentium II
processors, and upgraded to SSE2 in Pentium IV. These extra CPU instructions (called 3DNow! if you own an
AMD K7/Athlon/Duron/Iron/Thunderbird/etc CPU) allow all capable multimedia applications and games using audio, video and
movies to use the computer's hardware (much faster) for processing/rendering the audio/video streams, instead of relying on
the software to perform these CPU cycle consuming tasks (much slower). Later I have upgraded to 22.40, 22.50, 22.80 and
finally 23.11 Detonator release, and each time reopened the GeForce Display panel. Guess what? That $#@& [censored! ] tick
box had a check mark in it! :(On the other hand, "Anisotropic Filtering" (when enabled) filters out (blends)
uneven, non-uniform 3D textures by calculating the shape of a given area (i.e. an ellipse), mapping it onto the required
texture, and then taking an average of the colors from up to 32 texels (bilinear textured pixels) within the area, to
determine the final color plotted onto the target surface. Such areas can have any height / width ratio, depending on the
angle they are tilted at from the viewer standpoint. The sampled texel arrangement is almost always variable (rarely
consists of rows or columns of an equal number of texels), and can be calculated only at runtime. This is actually a
sophisticated trilinear filtering "fix" for uneven 3D shapes, and is pretty taxing on the GeForce GPU (Graphics Processing
Unit), thus slowing down screen rendering a bit, depending on the 3D chipset processing power, because it requires tons of
calculations to plot a single pixel, and until recently was available only on expensive 3D video hardware.FYI: See anisotropic
filtering at work.Does this mean that 3D anisotropy and my "beloved" P3's SSE extensions have been disabled by simply
installing a new video driver?! No way! I can't allow that to happen, so I have "readjusted" those 2 settings once
again. And this bug is present ONLY in Win95, 98 and ME, which leads me to conclude it is an intentional
change.THE FIX:To avoid this BUG to resurface in the future, whenever I upgrade to a
newer Detonator driver version [just in case NVidia decides not to fix it ], I created a REG file for Win98 SE (also valid
for ALL Win95, 98 + ME builds) with these lines, by using Notepad (example):
and named it 22XX.REG. Then I created a shortcut to 22XX.REG with this command line (example):%windir%\REGEDIT.EXE /S %windir%\CONFIG\22XX.REGto allow the information in this REG file to
be merged (imported) into the Registry completely unattended. Finally, I placed this shortcut (.LNK) into my
C:\Windows\Start Menu\Programs\Startup folder, to have it run every time Windows GUI loads, and force these buggy
settings to revert back to "normal".See "UNATTENDED REGISTRATION", also in REGISTRY.TXT
[part of W95-11D.EXE], for more details on how to run your REG files "hands-free".This actually
"translates" into these 2 Win95/98/ME Registry DWORD [REG_DWORD] Values, valid for all newer Detonator releases, and found
under the Registry subkey above:
"RenderQualityFlags": "00000011" is necessary
to enable "anisotropic filtering" in Detonator 22.xx/23.xx, opposite to "00000013", which is needed to properly
activate this same setting in all 21.xx and older NVidia drivers.
"ForceGenericCPU": "00000001" is
necessary to enable "enhanced CPU instructions" in Detonator 22.xx/23.xx, opposite to "00000000", which is needed to
properly activate this same setting in all 21.xx and older NVidia drivers.
Note that the "0001" Registry subkey
above may have different values on different systems, depending on the location in your Registry where NVidia drivers are
installed. Generic is "00nn", and nn can take any integer value between 00 and 50.See "REG Files" [Intro Chapter], also in REGISTRY.TXT [part of W95-11D.EXE], for
more details on how to create/modify/export/import a REG file.The good news is Windows NT4, 2000 and XP NVidia Drivers
(ALL releases) are NOT affected by these BUGs!
Windows (all editions beginning with Windows 3.10) 16-bit and 32-bit applications and games written to take advantage of displaying 3D-style raised/depressed buttons, window borders, dialog boxes, windows etc
NEED these DLLs (Dynamic Link Libraries), which NEED to reside in these directories (folders) [%windir% = usually C:\WINDOWS (Win31/95/98/ME + Win2000/XP/2003) or C:\WINNT (WinNT/2000)]:
ONLY Win98 retail, Win98 SE (Second Edition), WinME (Millennium Edition), Win2000, WinXP (eXPerience) and Win2003
Server install (some of) these files properly when you install respective OSes. ALL other Windows editions DO NOT include NOR install (some of) these files! Therefore you need to place them into proper locations (see above)
by hand.IMPORTANT: You MUST DELETE ALL your (older, obsolete) 3D Control DLLs, EXCEPT the ones in your Windows SYSTEM(32) directories/folders, to ensure ALL your programs/games perform
properly! To do this: open Windows Explorer [C:\Windows\Explorer.exe = 9x/NT4/2000/ME/XP/2003 users] or File Manager [FM = C:\Windows\WINFILE.EXE = 31/NT/95/98/ME users]
→ start a Find/Search operation on ALL your local fixed (hard) drives/partitions for CTL3D*.*→ DELETE ALL FILES you found EXCEPT the ones residing
in the default locations (see above).To display any Windows file version using:
Windows Explorer: highlight a file → right-click on it
→ select Properties → click Version tab → in Item Name: box scroll down to Product Version
→ look at the number shown in the Value: box.
File Manager: highlight a file → click File menu → select
Properties → look at the number shown in the Value: box.
ONLY IF the files you found in default locations (see above):
older versions: overwrite them with the ones included here (except the special versions installed by Windows XP + 2003 = do NOT replace them!);
are missing: move the ones included here to the locations above.
be able to overwrite (replace) files already in use, you may need to:
exit or reboot (eventually using an emergency bootup disk) Win31/9x/ME to native/real/true/pure MS-DOS mode and then replace the
older files in your %windir%\SYSTEM directory;
reboot (eventually using an emergency bootup disk) WinNT/2000/XP/2003 to Safe mode or to Command prompt [if the Windows Recovery Console (WRC) tool is installed in
Win2000/XP/2003] and then replace the older files in BOTH your %windir%\SYSTEM32 and %windir%\SYSTEM32\Dllcache folders: see "MS IE 5.5 SP2 + 6.0 FIX" (step 6. SOLUTION), also in
MYTIPS95.TXT [part of W95-11D.EXE], to learn how to replace Windows 2000/XP/2003 system files already in use.
Restart or reboot Windows when done.NOTE: To be able to use
CTL3D32.DLL + CTL3D32S.DLL under Windows/WfWG 3.1x you need to install Microsoft Win32s 32-bit Extensions Add-on v1.30c [2.41 MB, free], to allow Windows/WfWG
3.1x to run 32-bit (Win32) applications/games supporting this implementation.
This works with all Windows 95/98/NT4/2000/ME/XP/2003 Explorer.exe releases. To control the specific target path (drive/partition/folder) where Windows Explorer opens, create a shortcut to Explorer with this
command line to open it (for example) at the host/local root directory of the boot drive/partition, usually C:\ (dual pane view: drives/directories listed in the left hand pane and (sub)directories/files listed in the right hand
pane):%windir%\Explorer.exe /e,/root,C:\or (single pane view):%windir%\Explorer.exe /n,C:\Of course, you can replace C:\ with any other valid
drive/partition/folder name (complete path required). This Explorer shortcut opens in the root directory of any valid drive/partition or in the lower level subdirectory (if any) of any upper level directory this command is
run from (dual pane view):%windir%\Explorer.exe /e,/root,%1similar to this one (dual pane view):%windir%\Explorer.exe /e,/IDLIST,%I,%LThis Explorer
shortcut opens at the mydir directory located on the myserver remote server (dual pane view):%windir%\Explorer.exe /e,/root,\\myserver\mydirThe path to Windows Explorer doesn't need to be
mentioned because Explorer.exe is located in your main Windows folder [%windir%, %winbootdir% (Win9x/ME/NT4/2000/XP/2003), %homepath% or %systemroot% (WinNT4/2000/XP/2003) = usually C:\WINDOWS (Win9x/ME/2000/XP/2003) or
C:\WINNT (WinNT4/2000)], listed on the default PATH statement and winbootdir/windir/systemroot/homepath SET <environment> variables which load in memory upon every bootup.Command line syntax:EXPLORER.EXE [/e] [/n] [[(,)/root],<object|servername>] [[(,)/select],<subobject>]Command line parameters:/e = Opens Explorer in dual/multiple (side by side)
pane view./n = Opens Explorer in single pane view (default)./root,<object|servername> = Opens Explorer using the folder specified by <object> as root level view. Default is My Computer
in Win95/98/NT4 and My Documents in Win2000/ME/XP/2003. Object or subobject (see below) can be a local/UNC path, CLSID or IDLIST. You can use the UNC (Uniform Naming Convention) standard for <servername> to open
Explorer at a internet/network/remote/shared path/location/URL/server/directory/file./select,<subobject> = Opens Explorer using the file/folder/application specified by <subobject> as selected
(highlighted) view. Default is root/parent drive/partition/folder letter/name or first file/folder/application in root/parent drive/partition/server/directory./IDLIST,%I,%L = I expects a valid file/folder unique
ID/handle. L expects a valid Long File Name (LFN). In case no parameters specified this opens at Desktop level./inproc = Stops the display of any window altogether./s = Runs the entire command line
silently and uninterrupted if accompanied by other switches. By itself opens Explorer at the root directory of the boot drive (default is C:\) in full screen mode.Defaults are assumed for all switches not enumerated
on the command line. LFN (Long File Name) files/folders and shared/remote/network server/directory/file UNC names are almost always case sensitive. Explorer command line switches are case insensitive. Multiple switches
must be listed on the same command line separated by commas (,).More info @ MSKB: