|
Misc Problems and Error Messages |
You can save yourself the trouble of going to that article.
The solution is, "To work around this problem, press the same Windows
key that you originally pressed, and then press ESC or click the desktop."
What that means is there's no possible way to test software i.e.; all
the possible keys you typed, mouse movements....you name it???
It would be almost impossible. It's happens to me once. I use WRP registry
backup and restore. And I make a backup everyday after a successful boot.
So I simply shutdown to does and let WRP restore all for me and the problem
was gone.
Download WRP
HERE
Microsoft Windows 98
Microsoft Windows 95
When you try to access your CD-ROM drive in Windows, you may experience one of the following symptoms:
You cannot run executable (.exe) files.
You cannot view complete directory listings.
You receive the error message "Device not found."
These problems can occur if you are using an older version of the Mscdex.exe file that is not compatible with Windows 95 or Windows 98.
When you install certain real-mode CD-ROM drivers, an older version of the Mscdex.exe file is copied to the hard disk, and the Autoexec.bat file is updated to point to this older version of the Mscdex.exe file.
The FIX:
Modify the Autoexec.bat file to reference the correct version of the Mscdex.exe file. To do so, follow these steps:
1. Make a backup copy of the Autoexec.bat file.
2. Use any text editor (such as Notepad) to open the Autoexec.bat file.
3. Modify the line containing Mscdex.exe to read
<drive>:\<windows>\command\mscdex.exe <parameters>
where <drive> is the drive letter on which the Windows folder is located, <windows> is the name of the folder in which Windows is installed, and <parameters> are the parameters from the original line containing Mscdex.exe.
NOTE: To maintain compatibility with the installed CD-ROM driver, make sure to use all the parameters exactly as they are used in the original line.
4. Save and then close the Autoexec.bat file.
5. Restart your computer.
VMM32.VXD and Why You Should Never Extract a New One
Vmm32.vxd is a monolithic driver file made up of a number of various *.vxd files. It is a W4 format archive using the MRCI compression of Drivespace. However, to keep things simple, you can think of it as a archive of different *.vxd files combined into one library file that can loaded as one file but that the individual files within it can be used as if they were individually loaded. Basically vmm32.vxd just contains a collection of different *.vxd files your system needs for startup, each file is stripped of the headers that are required if that same file was loaded separately. Between the stripped headers and the compression used in vmm32.vxd it is considerably smaller that all the individual files, contributing to its faster load time. One of the most important things about vmm32.vxd is that the actual *.vxd files it contains is determined for each system on an individual basis during the original Win9X installation to that system, and that the vmm32.vxd file on one system may be quite different than the one on another system. So if your file gets corrupted you can't just copy the one from you buddy's system and expect it to work unless his system was 100% identical to yours at the time you each installed the exact same version of Win9X. You also have to know that the vmm32.vxd file that can be extracted from the Win9X cab files, is just a skeleton file that is used to build upon during the Win9X installation process, so just extracting it will not restore a corrupted vmm32.vxd file. If you did extract vmm32.vxd from your cab files and overwrote the one in your \Windows\system directory with it, the result would be a system that you could not start Win9X on.
The files are not missing, they are actually part of vmm32.vxd, which is why you normally will not find them as individual files on your system. The fact that users could not find these files on their system may have led to the acceptance that the Win9X did not install them. By the way, the Device Manager, Driver File Details type of entry that reads something like C:\Windows\System\vmm32.vxd (configmg.vxd) is absolutely correct. It is telling you that the driver being used is configmg.vxd but that is it loaded from vmm32.vxd instead of as a stand alone file. If it was loaded from a stand alone file then the entry would read C:\Windows\System\configmg.vxd.
Now there may come a time, when one of the *.vxd files built into vmm32.vxd needs to be updated, and Win9x provides a very simple means for this. Each system has a \Windows\system\vmm32 directory. Any *.vxd file in this directory will be automatically loaded and used during Win9X startup, instead of the one in the vmm32.vxd file if it exists in both places. In other words files in this directory take precedence over same files within vmm32.vxd. So when these web sites have you put the individual files in this directory all they are doing is putting a copy of the same code that is already within vmm32.vxd into this directory as stand alone files which will actually cause Win9X to take longer to load. Microsoft says that Extracting system files that are rolled into VMM32.VxD will not increase system performance, once you are started, there will be no difference. The reason for bundling VxD's into VMM32 was to improve system boot time.
To see a list of all the files included in your vmm32.vxd file use regedit.exe and go to the key HKEY_LOCAL_MACHINE \ System \ CurrentControlSet \ Control \ VMM32Files. All files listed in the right side of the display are within your system's personalized copy of vmm32.vxd.
As you may have gathered, since the VMM32.VXD in use on your system was custom created for you system based on its requirements, it is one file that you can not simply extract from your Win98 cabs files if it should become corrupt or if it accidentally gets erased from your system. So RIGHT NOW is a good time to stop reading and make a backup copy of it in case you ever need it.
Why would you ever need to rebuild:
I can only think of two reason for ever needing to re-build your vmm32.vxd file. The first is because your current copy is no longer usable or was deleted. So as I said just above, back it up now and you don't have to worry about this.
The other reason may be that at some point in time due to updates, etc, you may have a large number of updated *.vxd files in your \Windows\system\iosubsys directory and would like to return to having the files load via the faster loading vmm32.vxd. Personally I don't think that the load time difference is worth the effort but since vmm32.vxd can be rebuilt I will tell you how.
Procedure:
Notes:
Some of the steps only tell you what needs to be done and not how to do it. If you don't know how to do it, then I suggest that you should re-consider attempting this procedure. In this archive are samples of what the 2 batch files you are going to create should look like. As written they may not be appropriate for you system, so please follow the steps below to create batch files for your system, and use the samples only as a guide to what your completed batch files should look like. The entire procedure can be run from within the Win9X GUI, there is no need to start in Real Mode DOS as is the case with the earlier version of this procedure. Note that in my examples in some of the steps, I only show 3 entries for file lists that will be much larger (probably 40 or more lines). Also for these batch files you will be creating case does not matter.
1.First you must know what files are in your current vmm32.vxd file. You can get a list from the registry at HKEY_LOCAL_MACHINE \ System \ CurrentControlSet \ Control \ VMM32Files. Since the list is rather long, and because this procedure involves creating a batch file using this list of file names, the easiest thing to do is export this key to VMM32.REG
2.Open VMM32.REG in any editor that you want. An editor with Search and Replace (abbreviated as S&R in this procedure) capability is best (thus NotePad will not do, but WordPad will). The steps in this procedure are written to take advantage of S&R. The editor you use must allow you to save the results to an ascii text file.
3.Delete the first few lines so that you are left with a list that looks something like the following:
"biosxlat.vxd"=hex:00
"combuff.vxd"=hex:00
"configmg.vxd"=hex:00
4.Save what you have so far as WININIT.INI which we use later in this procedure.
5.Now continuing editing VMM32.REG and using S&R enter "=hex:00 (Note the leading quote mark in this text) as the search string and leave the replace text blank and then do a Replace All. You should now have a list that looks something like:
"biosxlat.vxd
"combuff.vxd
"configmg.vxd
6.Now replace all occurrences of " (a single quote mark) with one of the following text strings:
extract /a /y H:\win95\win95_02.cab (for Win95 users)
or
extract /a /y H:\win98\base4.cab (for Win98 users)
Note: In the above commands you have to change H:\win95 or H:\win98 to the actual path that your Win9X cab files can be found at whether it be a CD directory or some HD directory. Also note that there needs to be a SPACE at the end of the replace string. When you have completed this step your file needs to look similar to:
extract /a /y H:\win98\base4.cab biosxlat.vxd
extract /a /y H:\win98\ base4.cab combuff.vxd
extract /a /y H:\win98\ base4.cab configmg.vxd
7.Now ADD the following 5 lines to the TOP of the file:
@echo off c:
cd \windows\system
extract /a /y H:\win98\ base4.cab vmm32.vxd
cd \windows\system\vmm32
The C: in the second line must be changed if you have Win9X installed on a different drive. Also if \Windows in not your base Win9X directory, you need to change the two CD commands accordingly. These commands are necessary to ensure that the files get extracted from the cab files to the appropriate locations on your HD.
8.Now ADD lines similar to what's below to the END of the file. The purpose of these lines is just to give you some sort of an on-screen message when GETVXD.BAT finishes so that you will know it, and also know that it is OK to close the Dos Window that will be left open:
cls
echo extraction of files is complete, it's ok to close the dos window now.
9.Now compare your list of file of files to be extracted to those files that currently exist in your \Windows\system\vmm32 directory. If any files in your list already exist in this directory chances are that they are newer versions than what is on your CD. It is up to you to determine this. If you determine that the version of a file in your \Windows\system\vmm32 directory is newer than what is in your cab files, then Delete that entry from the list because we don't want to overwrite a newer version already existing in the directory with an older one that will be extracted from your cab files.
10.Save your work as GETVXD.BAT
11.Load the WININIT.INI saved in step 4 into your editor.
12.Using S&R enter "=hex:00 (Note the leading quote mark in this text) as the search text and for the replacement text enter =c:\windows\system\vmm32.vxd (adjust the drive\path if necessary) and then perform a Replace All. You should now have a list that looks something like:
"biosxlat.vxd=c:\windows\system\vmm32.vxd
"combuff.vxd=c:\windows\system\vmm32.vxd
"configmg.vxd=c:\windows\system\vmm32.vxd
13.Using S&R enter " (a single quote mark) as the search text and c:\windows\system\vmm32\ (adjust drive\path if necessary) as the replacement text and perform a Replace All. You should now have a list that looks something like:
c:\windows\system\vmm32\biosxlat.vxd=c:\windows\system\vmm32.vxd
c:\windows\system\vmm32\combuff.vxd=c:\windows\system\vmm32.vxd
c:\windows\system\vmm32\configmg.vxd=c:\windows\system\vmm32.vxd
14.At the TOP of the file add a section header of [SetupOptions] and under it Combine=1, Under this add another section header of [CombineVxDs]. Your file should now be similar to:
[SetupOptions]
Combine=1
[CombineVxDs]
c:\windows\system\vmm32\biosxlat.vxd=c:\windows\system\vmm32.vxd
c:\windows\system\vmm32\combuff.vxd=c:\windows\system\vmm32.vxd
c:\windows\system\vmm32\configmg.vxd=c:\windows\system\vmm32.vxd
15.Once you have your file looking like the above example save it keeping the name WININIT.INI
16.Move WININIT.INI and GETVXD.BAT from wherever you saved them with your editor to your \Windows directory
17.Although not required for the rest of the procedure to work, I strongly suggest that you backup any files that already exist in your \Windows\system\vmm32 directory as well as your current vmm32.vxd file and your current registry. How you backup these files is up to you.
18.In the Start > Run dialog enter GETVXD and click on OK to start the batch file which should log you on to the HD that contains Win9X, change to the appropriate directories and extract all file to these directories, automatically overwriting any files that exist with the same filename. Depending on your system speed this batch file may take a while to execute due to the simple way it was written which caused only one file to be extracted from the cabs at a time. I don't think you will be using this batch file often enough to worry about combining filenames on an extract command line to save a little time by extracting multiple files at a time.
19.Restart Win9X and during the startup process, WININIT.INI will be processed. While wininit.ini is being processed you will get a Please wait while Setup updates... message on your screen, as the new vmm32.vxd file is created from the individual files in the \Windows\system\vmm32 directory. During the process, all files combined into vmm32.vxd will be deleted from the \Windows\system\vmm32 directory leaving only those that do not belong in vmm32.vxd (were not listed in your wininit.ini file) which should have been there before starting this procedure.
That's it, you should have re-built your vmm32.vxd file. If everything is working, BACKUP your new vmm32.vxd file now, so if anything happens to it you don't have to repeat this procedure.
What if I can't start Win9X or have other problems:
Recovery is quite simple if you followed my suggestion to make backups.
All you should have to do is replace \Windows\system\vmm32.vxd and delete
any files in the \Windows\system\vmm32 directory that were not there when
you started. If you made backup, then you should be able to delete everything
in this directory and just restore it from your backup. The procedure causes
NO changes, additions or deletions to your registry, so you should not
need to restore it. However if you can't start Win9X, then you did something
wrong and since regedit.exe was used you may have accidentally corrupted
your registry and if this is the case you may have to restore it from you
backup. So you can either do it now or wait and see if it is required after
you attempt to restart Win9X after restoring your original vmm32.vxd and
\Windows\system\vmm32 files.
DIR00001 appears as a directory on your hard drive. You can't remove it, and it is using up considerable amount of your hard drive space. If this has happened to you, read on.
After researching, I have found that the problem is with MS-DOS Microsoft ScanDisk creates DIR000<x> directories when it finds directory structures that are damaged beyond repair. All the files in these directories have read-only and hidden attributes. The MS-DOS ATTRJB command does not change the attributes on these files and the MS-DOS DELTREE command does not remove these directories.
Microsoft's solution is to use a third-party disk utility to remove
these directories. We have successfully used Symantec's Norton Utilities'
Diskedit command. To remove these directories, the procedure is as follows:
1.Log-off network
2.Check hard drive for virus (we used McAffe's Virus Scan)
3.Change to the directory with Norton Utilities.
4.Type diskedit
5.Choose DRIVE...from the object menu
6.Use the arrow keys, place the cursor under the first character of
the directories name
7.Press ALT F5
8.Choose WRITE CHANGES... from the Edit menu .
9.Select WRITE
10.Choose EXIT from the object menu
11.Reboot the computer and log-in to the network
Please Note: DIR00001 is an indication you may have a bigger problem as relates to your hard drive. It's recommended that you contact your hardware vendor.