You are welcome to use any or all of the suggestions below; of course, I cannot assume any responsibility for any bad things that happen to you because you follow (or fail to follow) my instructions. However, I will gladly accept credit for any of the good things that happen.
As a point of departure, I installed Win 95 onto a new disk using the OEM (not the "upgrade") version. The OEM version will not bring in previously installed apps from an existing copy of Win3; in fact, it won't even proceed to install (after a 10 minute penalty) if it finds a Windows directory on your disk.
After using Windows 95 for a while, I started to run into some hard to solve problems, which I have also tried to document herein.
The first thing I do after an initial setup is to install MS Powertoys. This is a free download from MS. I do it right away because it allows me to turn off "add 'shortcut to' to all shortcut names".
I like to use letter E: for my CDROM, and do this on all the machines that I set up, regardless of operating system, if I can.This leaves D: free for adding another hard disk later.
I also found that, since I had called the CDROM E: when I originally set up Win95, that Win95 wanted to look for E: whenever it needed more file from the CD at a later date, such as when adding a printer driver. It would be more convenient to have the CDROM as E: for this reason also.
REGEDIT.EXE, in the Windows directory, gets used so often when setting up Windows that I recommend putting it right on the start menu before proceeding any further.
Logo=0to the
[Options]section.
Before editing MSDOS.SYS for the first time, you will have to remove the hidden, readonly, and system attributes. This is done from the command line with the following command:
attrib -s -h -r msdos.sys
The simple way is to open up any "explorer" window and choose View/Options from the menu, then click on the File Types settings page.
Highlight any file type and you will see the associated program. To change it, click "edit" or simply double click on the file type. This opens up a dialog box.
In the dialog box, double click on "open". Specify what program you want to associate with the file. That's usually all you have to do.
Next time you double click on a file of that type, the app you specified will be called, with the name of the file as a parameter, unless you checked "use DDE" in the dialog. If you use DDE, the target application is passed the name of the file you clicked via DDE. The advantage to this is that, if the target app was already open, it can accept the new filename via DDE and act on it. If DDE is not used, a second (or third or fourth) copy of the target app needs to be started in order to receive the name of the file you clicked via the command line. This takes extra time and uses up system resources.
Unfortunately, to use DDE, you have to know exactly how to set up the call in the dialog box. I do not know how to do this, but usually when a program installs file associations, it puts them in DDE format. Just how this is (was) done for that application is one of the key pieces of information you lose when another app clobbers the association that was already set up.
The second way to set up an association involves using REGEDIT. Inside the registry, under HKEY_CLASSES_ROOT, is a list of all of the registered file extensions, followed by a list of all of the registered file types. By looking at some of the associations that are already set up, you will see that each extension points to a file type. Each file type, under its "shell" suboption, lists the "open" action and, under that, defines what happens when that action is undertaken.
I had been connecting in that manner. I found that once I had accessed one page using the MS browser, I could then start Netscape or Eudora and they would work. This was before I found where the dialer is hidden.
The dialer can be found in the "Accessories" group under the start menu. If you browse ("open") the start menu, go into the accessories folder, and try to open "Dial up networking", you get a window containing an icon to set up a new connection, plus an icon for each connection that you have already set up. Set up a connection, then right click on it and choose "create shortcut". This lets you put a shortcut to the dialer on the desktop, which is then easy to move to wherever you really want it.
Click on the icon you thus created and log in before you start Netscape and/or Eudora.
Put shortcuts to items in that folder in the usual manner. Once this has been done, choosing those menu items after right clicking on a file system object will do the same thing as dragging the file system object and dropping it on the item which the shortcut represents.
I put Vuern Buerg's LIST, NOTEPAD, and my Laserjet printer on the "send to" menu, and removed the 5.25" B: drive, which I don't seem to ever use any more.
I wanted to find a way to control which application launches when a data file is clicked on.
The program associated with a given data file is set in the "settings" notebook within Explorer. Windows lumps files together by extension; for instance, all .BMP files will have the same associated app(s).
It happens that if you right click on a data file object, you get a menu, the topmost part of which varies according to the extension of the file you clicked on. For instance, on my system, if I right click on a .BAT file, I get three choices in the context-sensitive part of the menu: Open, Print, and Edit.
It turns out that these context-sensitive items are configurable by you, the user. They also are configurable by program actions, and sometimes get altered when you install a new program (for instance, after installing Corel Draw, the "open" item on the menu for .JPG files runs Photo-Paint, where it used to run IEXPLORE.)
To see what a menu item does, change it, remove it, or add a new one:
This technique offers a partial solution to the problem of newly-installed apps changing file associations: if you have taken the time to copy the attributes of the "open" item to a new item with another name, this new item may survive a later app install and thereby preserve your previous settings.
REGEDIT4 [HKEY_CLASSES_ROOT\Unknown] "EditFlags"=hex:02,00,00,00 [HKEY_CLASSES_ROOT\*] "EditFlags"=hex:02,00,00,00Find the file you just created and right click it. Choose "merge" from the context menu that appears.
Long filename support is provided by adding the OS/2 name space support to the server volume.
Here are brief instructions:
:LOAD OS2
:LOAD PATCHMAN
:LOAD SHORTAFX
:LOAD OS2OPNFX
:ADD NAME SPACE OS2 TO volname
Down the server and copy the two files you previously put on a
floppy to the same directory as SERVER.EXE in the DOS partition. (I assume
that VREPAIR.NLM, INSTALL.NLM, and other necessary files are already there.)
On startup, "LOAD OS2" must be done before the volume is mounted. LOAD
OS2 must be placed in the STARTUP.NCF file if the SYS: volume supports
long filenames, since this volume mounts automatically before AUTOEXEC.NCF
is processed. This is why OS2.NAM was placed in the DOS partition. If the
SYS: volume is not going to support long filenames, :LOAD OS2 can be placed
anywhere in AUTOEXEC.NCF before the applicable MOUNT command, or can be
placed in STARTUP.NCF anyway. I recommend placing LOAD OS2 in STARTUP.NCF
since this supports the general case.
Also add the load commands for the patches to the AUTOEXEC.NCF file.
Restart the server. It now supports long filenames. Check the available
cache buffers in MONITOR to see what the addition of the OS2 namespace
did to your server memory requirements.
Test for long filename support by trying to rename a file from within Explorer. If it works, you're done.
LOAD OS2.NAM
LOAD PM410
LOAD NSWILDFX
ADD NAME SPACE OS2 TO VOLUME {name}Add the load commands for the patches to AUTOEXEC.NCF.
MEM says that there is no high or upper memory available. Where did it go?
MAPMEM and DEVICE report that there are no extra drivers loaded beyond the ASPI drivers and mouse driver that I had had loded previous to the problem.
Looks like MS forgot to include MSD with WIn95. Quarterdeck's Manifest, the latest version of which was a dual-mode (dos/win) program, comes up in the Win mode whether I run it from the GUI or from a DOS command line in a DOS session, and in that mode it immediately hangs. Only by setting BOOTGUI=0 in MSDOS.SYS and rebooting can I start MFT in the DOS mode, where it works, and immediately shows me that all that memory is being used by DBLSPACE.
DBLSPACE? I'm not using doublespace! How does it get loaded? There are no references to it in MSDOS.SYS, CONFIG.SYS, AUTOEXEC.BAT, or and .INI files I can find. How did it get loaded? I have no idea. I know that I have not compressed any drives with it, so the problem is simply to get rid of it.
Using FIND in the dtart menu and looking for DBLSPACE.*, I find a likely culprit: DBLSPACE.BIN is a hidden file in the root directory. Maybe it gets loaded automatically if it's there. I rename this file, and also rename both instances of DBLSPACE.SYS that the FIND utility turns up. After doing this and rebooting, everything is back to normal.
It taks a little fancy typing (or cut from here and paste it in) to set this up, but it only has to be done once (per install). If you get it right, you will see the familiar icon in the start menu, and the contents will be correct. if you get it wrong, you will see an ordinary folder icon in the start menu, and the folder will be empty. if this happens, just delete it and try again.
For instance, you can create a new folder in your Start Menu, and name it "My Computer.{20D04FE0-3AEA-1069-A2D8-08002B30309D}"
Here are the resource IDs to use for other objects: