|
Error Messages and Fixes # 1 |
This article describes the three parts of the following error message:
Invalid VxD dynamic link call from [Part 1] to device [Part 2], service [Part 3]
MORE INFORMATION
Normally, an Invalid Dynamic Link Call error message is the result of an incompatibility between driver versions, or a damaged or missing driver. Try uninstalling and then reinstalling any programs or components that you installed recently (before the error message occurred).
The error message stated above may occur because your computer is configured incorrectly. This may be due to a device driver that was added or removed recently.
Part 1
* Part 1 may be divided into an encoded device name, object number, and offset, such as "VMM(0A) + 0000001C." This example means the problem was detected in the VMM virtual device driver, in object 0A, at offset 0000001C.
* If Part 1 is an eight-character sequence of letters and numbers, such as "C13A1EC6," a device driver jumped to an invalid location. The identity of the driver could not be determined.
For more see:http://support.microsoft.com/support/kb/articles/q137/3/35.asp
Microsoft Internet Explorer
Download Microsoft's Internet browser now, in Windows 95 (over 20 languages), Windows 3.1, Windows NT, and the Macintosh.
ISDN Accelerator Pack 1.1
The ISDN Accelerator Pack enables Windows 95 to make Dial-Up Network connections over high-speed, digital ISDN lines. Multilink allows two B channels to be bonded together for 128k performance.
WANG Imaging Software
Edit and manage Microsoft Fax documents just like other Windows 95 files with this utility from our friends at WANG.
Shareware: WUGNET Pick of the Week
The week's best Shareware for Windows 95, brought to you by Microsoft and the Windows Users Group Network.
IrDA (Infrared Driver and DDK
IrDA support enables Windows 95 users to easily connect to peripheral devices or other Windows 95 based PCs without using connecting cables.
CD-ROM Extras
Files released only on the CD-ROM version of Windows 95, available here for all Windows 95 users!
Service Packs
Our most popular updated system essentials, conveniently bundled for easy downloading!
New Technology
The latest available update files and system components, including many not yet found in the Service Packs.
International Resources
International Language versions of Windows 95 system components and updates, including Internet Explorer, ISDN Accellerator Pack, and Service Packs in Chinese (Simplified), Chinese (Traditional), Czech, Danish, Dutch, Finnish, French, German, Greek, Hungarian, Italian, Japanese (PC98), Japanese (PCAT), Korean, Norwegian, Pan-European, Polish, Portuguese (Brazilian), Portuguese (Iberian), Russian, Slovenian, Spanish, Swedish, and Turkish.
Power User Extras
Power Toys
Shortcuts, performance tweaks and custom system tools to help you get things done.
Kernel Toys
Advanced utilities and diagnostics to help expert users achieve top performance.
Installation Tools
Resource Kit Tools
Valuable support utilities, help files and troubleshooting templates to help make your transition to Windows 95 an easy one.
Support Tools
Help with installing and using Windows 95
This is lately been seen a lot with DirectX, ActiveX, Active DeskTop and a bunch of new software that seems to mess up OLE. Abbreviation of Object Linking and Embedding, pronounced oh-leh. So, the obvious and best fix I've seen so far is the Microsoft OLE update. The OLE update has helped others with the same problem:
You can download OLEUPD.EXE by clicking the following link:
http://support.microsoft.com/download/support/mslfiles/OLEUPD.EXE
METHOD 1
To remove the Windows Desktop Update, go to Control Panel, Add/Remove = Programs. Select Internet Explorer 4.0, NOT Internet Explorer 4.0 Setup = Files. Click on the Add/Remove button. Follow the on-screen = instruction to _only_ uninstall the Windows Desktop Update.
METHOD 2
Click start, select settings, select add/remove software, select MS IE4 and click remove. At the top will be three radio buttons. Select the remove Active Desktop - keep IE4 and select ok. This will remove active desktop but leave IE4 alone.
Disabling the Active Desktop
Right click on the desktop > uncheck "View As Web Page" Problems with doing so? None that I'm aware of. In fact, I read many, = many posts where disabling the Active Desktop *solved* problems.
This program has performed an illegal operation and will be shut down.
A FATAL EXCEPTION HAS OCCURED AT . . .
Invalid Page Fault...
The Big Ugly "BLUE SCREEN" again.
1st:
To Turn Off Windows Graphics Acceleration
1.Quit any open programs.
2.Right-click My Computer and on the shortcut menu, click Properties.
3.On the Performance tab, click Graphics.
4.In the Advanced Graphics Setting, drag the Hardware acceleration slider to None.
5.Click OK and Close.
6.Click Yes to restart your computer.
Due to the many possible scenarios that can cause these messages to appear on your screen, not everyone will find a cure here.. and sometimes these errors are caused by bugs in a particular piece of software. When that is the case, the only cure might be to stop using that program.
Most of the time however, the causes are traceable to a conflict between two pieces of software or a conflict between two modules within Windows itself or disk errors which are frequently caused by powering off without properly shutting down. They also tend to accumulate no matter what over a period of months. If over time you are noticing more frequent errors, always run Scandisk with the "thorough" and "automatically fix errors" options selected as a first step.
Video cards and their drivers are a common source of General Protection Faults. Always check the Web site of your video card manufacturer for updated drivers and information as a possible fix. Specifically, this type of error is often caused by a conflict between a program, (usually games or other graphic intensive software) and the accelerator chip of the video card. If you already have visited that manufacturers site and got the latest drivers and have checked for known issues listed there, the workaround is often to disable the accelerator chip on the video card. Look in your video card's utility software for an option to disable it. Then disable it through Windows by opening Control Panel, click on "System", click on "Performance", click on "Graphics". There you will see a slider labeled "Hardware Acceleration". Drag it all the way to the Left to disable it. Click OK. You will probably need to reboot for it to take effect.
Third party screen-savers are another common source of system crashes. If you're serious about pursuing maximum system stability, get rid of them.
Conflicts can take the form of two modules each trying to use the same block of memory, or two modules issuing mutually exclusive conflicting instructions to the operating system. Crash protection programs such as "CrashGuard" usually do just the opposite of what they are supposed to do. What they are best at is crashing your system. Windows doesn't need them. Get rid of them.
One of the biggest and most easily fixed causes of general protection faults is having too many unneeded protocols installed in the Dial-up Networking properties panel.. To check for this, click Control Panel. Click "Network". You should see a list of installed network components. If you have a regular ISP and you are using the Windows 95 TCP/IP connection to the Internet, and you are not on a LAN you should have only three items showing on that list.
* Client for Microsoft Networks
* Dial-Up Adapter
* TCP/IP
If you have AOL installed, you will also see "AOL Adapter". AOL being installed might also decrease your TCP/IP reliability.
If you have Microsoft Personal Web Server, that will be there too.
If you see NetBEUI or IPX/SPX or anything else on the list, highlight it and click "Remove"
Write down the changes just in case.
Next, highlight TCP/IP, Click "Properties",
* Click the DNS Configuration tab.
* Click the box that says: "Disable DNS"
* Click the "WINS Configuration" tab
* Click "Disable WINS Resolution
* Click "OK"
Now reboot and put your system to the test. You may be amazed at the improvement.
There is one peculiar aspect of Win95 worth noting that can also cause the system to crash. Windows normally controls it's disk cache automatically and determines the size of it by the amount of available ram. If you have an usually large amount of RAM, say..over 48Mb, Windows may allocate too much ram to the cache. For reasons thusfar unexplained, too large a cache can cause problems, including total system crashes. It may also be responsible for sluggish overall system performance. This cache, called VCACHE, can be controlled from SYSTEM.INI
This letter below is one from a previous posting:
I'm getting an unusual error while booting W95:
"a fatal exception 0E has occured at 0028:C002979A in VXD VCACHE(01) + 000003E2. The current application will
be terminated "..etc . .but when I press a key to continue the whole system hangs,so all I have to do is to reboot. It's not from corrupt files (I formmated my disk and set up everything from scratch)
If all your peripherals have updated drivers with no conflicts on the motherboard,and generally everything is just fine except for this -sickening- blue screen appearring with a 75% possibility every time you boot up. I suggested the following ..which has fixed this problem:
Open SYSTEM.INI for editing. Look for the following section: [vcache]. Then add the following two lines right below it. It should look like the following when done:
[VCACHE] FOR 16mg
MaxFileCache=4096
[vcache] FOR 32mg and so on
MaxFileCache=8192
I have 64mg and use this setting:
[vcache]
MaxFileCache=12288
These values represent the size of the cache, in KB The address that your system reports the error sounds suspiciously like that belonging to video ram. As a first step, try disabling the disk cache by setting both numbers to 0. Then try 1024, 2048, and 4096 to find which works best. If you are using any memory managers such as QEMM386 or EMM386, try disabling it.. They are not needed at all except for certain DOS programs. They might be conflicting with a system device or Windows module.
Most of the time, this type of error is caused by a conflict between a program, (usually games or other graphic intensive software) and the accelerator chip of the video card.
First, you should check the Web site of your video card manufacturer for the latest drivers and information. If there is no relief there, the workaround is often to disable the accelerator chip on the video card. Look in your video card's utility software for an option to disable it. Then disable it through Windows by opening Control Panel, click on "System", click on "Performance", click on "Graphics". There you will see a slider labeled "Hardware Acceleration". Drag it all the way to the Left to disable it. Click OK. You will probably need to reboot for it to take effect. Please let me know how that works.
This describes specific conditions that might interfere with starting a Windows 95 computer and how to fix them.
In general, for system startup problems, the first problem-solving method is to start Windows 95 in Safe Mode. For information about how to start in Safe Mode and use BOOTLOG.TXT for troubleshooting, see General Troubleshooting.
Windows 95 stalls during the first restart after installation.
Usually this occurs because of legacy hardware that was configured incorrectly before Windows 95 was installed. Remove settings for hardware services in CONFIG.SYS and AUTOEXEC.BAT. Also, ensure that any SCSI devices are terminated correctly. You might also need to disable the ISA enumerator. This software detects a new type of adapter that can be configured from the operating system. The detection sequence requires the ISA enumerator for I/O processes on some ports. Although every effort has been made to avoid ports commonly in use, you might have hardware that is also trying to use these I/O ports.
To disable the ISA enumerator Remove the following line from the [386Enh] section of SYSTEM.INI:
device = ISAPNP.386
Bad or missing file error occurs on startup.
If you receive a Bad or missing filename” message when the system is starting (where filename might contain HIMEM.SYS, IFSHLP.SYS, and so on), do the following:
Check the syntax of the entry in CONFIG.SYS or other startup file.
Verify the existence, location, version, and integrity of the file.
If the filename to which the message refers is a device driver the computer needs for accessing the drive where Windows 95 is installed, you need to move the device= line that contains the device driver to the beginning of CONFIG.SYS to allow access to the drive when CONFIG.SYS tries to load files from the Windows directory.
Windows 95 has damaged or missing core files.
When Windows 95 loads, it counts on key files being available and undamaged. If a system file is damaged or missing, it might prevent loading or normal operation. If VMM32.VXD or other core files are missing or damaged, you might need to run Windows 95 Setup and select the Verify option in Safe Recovery to replace the files.
System Registry file is missing.
The Windows 95 Registry file is required for operation. This is contained in SYSTEM.DAT and USER.DAT, which are backed up as .DA0 files. If only the SYSTEM.DAT Registry file is missing, Windows 95 does one of the following:
Windows 95 automatically replaces SYSTEM.DAT from the backup Registry .DA0 file.
OR
Windows 95 automatically uses Safe Mode to start Windows 95 and displays the Registry Problem dialog box. Click the Restore From Backup And Restart button to restore the Registry, which copies SYSTEM.DA0 and USER.DA0 to .DAT files.
If both SYSTEM.DAT and SYSTEM.DA0 files are missing (or if the WinDir= entry in MSDOS.SYS is not set), a message informs you that the Registry file is missing and that Registry services are not available for this session. (This means that most operations in Windows 95 will fail.) After this message appears, Windows 95 automatically starts in Safe Mode and displays another message offering an option to restore the Registry. However, if there is no .DA0 file, the Registry cannot be restored. To resolve this problem, either restore SYSTEM.DAT from backup or run Windows 95 Setup.
For information about backing up and restoring the Registry, see Windows 95 Registry.
BIOS or a BIOS setting is incompatible.
A ROM BIOS setting might prevent Windows 95 from installing or loading, because some computers have a feature that prevents applications from writing to the boot sector. This is usually in the form of anti-virus protection set through your computer’s CMOS. If this is enabled, Windows 95 cannot complete the installation or cannot start properly.
If boot sector protection is enabled in the computer’s BIOS, one of the following symptoms occurs:
1. Windows 95 Setup stalls.
2. Windows 95 stalls while starting.
3. The anti-virus software prompts you to overwrite the boot sector. Choosing Yes might allow you to complete the Setup procedure, but Windows 95 stalls when it attempts to load.
To correct this problem, disable the Boot Sector protection feature through your computer’s CMOS, then reinstall Windows 95. For information about disabling this feature, consult your hardware documentation or service center.
VxD error returns you to the command prompt.
If a VxD is missing or damaged, Windows 95 displays an error message that indicates which VxD is involved. If the VxD is critical to the operation of Windows 95, then Windows 95 does not start and the screen displays the command prompt. You might need to run Windows 95 Setup and select Verify or Safe Recovery to replace the missing VxD.
You can selectively override a VxD that is included within VMM32.VxD. If the same VxD is loaded twice, the second instance intercepts all the calls to that particular VxD. There are two ways to override this:
Copy the related .VXD file into the Windows SYSTEM\VMM32 directory.
Edit SYSTEM.INI to add the entry device= filename.vxd in the [386enh] section.
You cannot use dual boot to run a previous operating system.
To take advantage of the dual-boot support in Windows 95, you cannot install Windows 95 into an existing Windows 3.x directory, and the value BootMulti=1 must be defined in the Windows 95 version of MSDOS.SYS.
DR DOS and versions of MS-DOS earlier than 5.0 do not support Windows 95 dual-boot functionality. To return to your previous operating system, you have to remove Windows 95 and reinstall your previous operating system, as described earlier in this chapter.
Previous MS-DOS files not found message appears.
When trying to dual-boot to the previous version of MS-DOS, you might receive an error message stating that your previous MS-DOS files were not found. It is probable that either the files are missing, or that your previous version of MS-DOS was not version 5.0 or higher.
You must have MS-DOS 5.0 or higher in order to start to a previous version of MS-DOS. Any version of MS-DOS earlier than 5.0 looks for the first three sectors of the IO.SYS file in the first three sectors of the data area of the drive. In MS-DOS 5.0 or higher, IO.SYS is designed to allow itself to be located outside the first three sectors of a drive’s data area. In this situation, the only way to start to a version of MS-DOS prior to 5.0 is from a startup floppy disk.
Drivers, such as DBLSPACE.SYS, that are loaded when you start the computer using the earlier version of MS-DOS might not be available.
Required real-mode drivers are missing or damaged.
The previous operating system might have required certain real-mode drivers (compression, partitioning, hard disk drivers, and so on), and does not start correctly without them.
At system startup, press F8 and select Step-By-Step Confirmation to verify the correct loading of all specified drivers.
Verify that any drivers required to support your hardware are all specified in the appropriate startup file.
Windows 95 doesn’t recognize a device.
In some cases, Windows 95 is unable to recognize an installed device, and the device resources are unavailable to Windows 95. If Windows 95 doesn’t recognize an installed device, remove it in Device Manager, and reinstall it by using the Add New Hardware option in Control Panel. You can also use Device Manager to check resource conflicts. For information, see Devices. Or see the hardware conflict troubleshooting information in online Help.
Installing drivers causes Windows 95 system startup to fail.
If you try to install drivers for Windows 3.x from other vendors over Windows 95 (such as sound or video drivers), running the provided installation program can cause Windows 95 to fail to start or operate correctly.
To recover, when using a device that is supported by Windows 95
1. Remove all entries in SYSTEM.INI that were added by the installation software from another vendor.
2. Delete the device in Device Manager in the System properties, as described in Devices.
3. Shut down and restart Windows 95.
4. Use the Add New Hardware option in Control Panel to reinstall the device by using the Windows 95 drivers.
The wrong applications run after Windows 95 starts.
In Windows Explorer, double-click the Windows Start Menu\Programs\Startup directory, and then delete any items that you do not want to run when Windows 95 starts.
If the programs that are running do not appear in the Start Menu folder in Windows Explorer, run Registry Editor and find this key:
HKey_Current_User\Software\Microsoft\Windows\CurrentVersion
\Explorer\Shell Folders
The value of Startup= should be Windows\Start Menu\Program\Startup, where Windows is the drive and directory containing the Windows 95 files.
Sometimes, WIN95 isntall doesnt recognize existing drivers and leaves them alone; thus Leaving apps or Drivers Running. Here are some things you can check off the top. EDIT then SAVE these files:
Config.sys - see if there is a reference to the driver.. if so.. type REM at the beginning of the line
autoexec.bat - see if there is a reference to the driver.. if so.. type REM at the beginning of the line
system.ini - do a FIND on the driver.. for all references , type a SEMI-COLON at the beginning of the line
Shutdown the computer, restart..see if the error is gone.
Sometimes, OEM's have there own idea of startup files ( ACER is one ) The offending driver might also be in these types of files.
Also, some older devices ( Sound/Video cards etc...) need these drivers. If WIN95 successfully boots, but some devices dont work, you may have to re-install the drivers/software ( Always try and use WIN95 versions of the drivers/software..these ususally can be found at the device maker's web site.) Also Check these places in your registry
OTHER PLACES THAT CAUSE LOADING DEVICES:
NOTE: BACKUP YOUR REGISTRY BEFORE ENTERING AND CHANGING!!!
HKEY_LOCAL_MACHINE\Software\Microsoft\ Windows\CurrentVersion\Run
HKEY_CURRENT_USER\Software\Microsoft\ Windows\CurrentVersion\Run
HKEY_LOCAL_MACHINE\Software\Microsoft\ Windows\CurrentVersion\RunOnce
HKEY_CURRENT_USER\Software\Microsoft\ Windows\CurrentVersion\RunOnce
HKEY_LOCAL_MACHINE\Software\Microsoft\ Windows\CurrentVersion\RunServices
HKEY_LOCAL_MACHINE\Software\Microsoft\ Windows\CurrentVersion\ RunServicesOnce
HKEY_LOCAL_MACHINE\Software\Microsoft\ Windows\CurrentVersion\RunOnce\ Setup
If you have questions about your registry let me know.
(Software developers have a whole lotta nerve to assume this is a convenience. They should ask first.) There are three places where you can try to stop this annoyance:
1. The Startup folder. This is the most obvious location for a program reference. Right-mouse click on Start, select Open, double-click on Programs, then double-click on Startup. If you see a shortcut to the annoying program inside, delete it.
Your WIN.INI file. Select Start, Run, type " sysedit " no qoutes and click on OK. Inside the System Configuration Editor, make the WIN.INI window active and look for a "run=" or "load=" line under the [windows] section. Programs referred to on these lines load at startup.
2. Remove the reference to the annoying program, and save your change. (If not, have your local computer guru help you. WIN.INI is a very important file and should not be messed with unless you know what you're doing.)
3. The Registry. Select Start, Run, type " regedit " no qoutes
and click on OK to open the Registry Editor. Navigate your way to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RUN. In the right pane, you'll find programs that load when Windows 95 starts. Right-mouse click on the one giving you grief, select Delete, and close the Registry Editor. (As always, before editing the Registry, back it up. One way is to zip your System.dat and User.dat files and store them on a floppy disk.)
4. Check your autoexec.bat file to see if you have any loading calls there for the program.
Whichever method you used, restart Windows 95 and (in most cases) Happiness Ensues!
Method I.
Error "unable to initialize NTKERN" please reboot and try again.
A mixture of simms and sdram, or ram mismatch in any fashion can cause this Error.
Method 2.
This comes from:
http://www.3-cities.com/~crstrode/ntkweb.htm
C:\WINDOWS\SYSTEM\VMM32\filename.VXD On the re-boot following reinstallation of Windows 95, you get the following message: "Windows could not combine VXDs into a monolithic before starting. Windows may not run properly. If Windows fails to start, run setup again. Press any key to continue."
Once you press a key, the following message will appear: "A device that is specified in the SYSTEM.INI file is damaged.
It may be needed to run Windows. You may need to run the Windows setup program again. If the file is included in another software package, you may need to reinstall the software that uses this file.
C:\WINDOWS\SYSTEM\VMM32\filename.VXD."
This message MAY appear for each of the following
VXD files.
VWIN32.VXD,
VCOND.VXD,
VXDLR.VXD,
VPICD.VXD,
VTD.VXD,
VMCPD.VXD,
NTKERN.VXD,
VPICD.VXD,
VTD.VXD,
VXDIDR.VXD,
VWIN32.VXD,
VMCPD.VXD,
VCOND.VXD.
After going through the 13 error messages, the
following message will appear: "Configruration manager cannot load because
one of the following files is not present or has an invalid version number:
VMM32.VXD, SHELL.VXD, VTD.VXD, VXDLDR.VXD,
WPICD.VXD.
Try running setup again. Press any key to continue."
When you press a key, you will get the message
"It is now safe to turn off your computer".
On subsequent reboots you will only get the 13 error messages and "Safe to turn off" message. You will also get these error messages if you attempt to boot in Safe mode.
NOTE! IF you are just getting and error message for NTKERN.VXD, go to the HOW TO section steps 17-19
The cause of my problem was the version of Win 95 installed on my new computer was different from the version of Win 95 included on the distribution disks. This problem occurs because you are installing OSR2 (CD) over OSR2.1 (HDD). OSR2.1 is really OSR2 with the USB Supplement, but because some file versions are different, installing OSR2 over OSR2.1 will cause some problems. The main thing to remember is that when installing OSR2 over OSR2.1 you will need to overwrite many of the newer files with the older ones. If you opt to keep the newer version, this problem will occur. The below how-to steps changes the installed Windows version to 2.0. Currently Microsoft has not released an end user upgrade to go from OSR2 to OSR 2.1. However, there should be one made available as a driver as USB products come to the market.
To solve the problem, Re-install Windows 95 and each time the setup program asked if you wished to replace a newer file with an older one (as shipped on the distribution disks) answere "yes" and replaced the files. The result was that I now had a completely "new" version of the "older" Windows 95 installed on the computer. At this time, I still was receiving the message about NTKERN.VXD. I discovered an update file for Windows 95 called OEMUSB.EXE. When this file was executed, it updated the "older" version of Windows 95 to the current version as was installed on my computer to start with.
Try this, It should work for you. In case it doesn't . . .
Reinstall Windows 95 using the distribution CD. Then, be sure to overwrite
all newer VXD files with the older ones on the CD. Then remove the USB
supplement for OSR2 from Add/Remove Programs in Device Manager.
Here is the procedure:
1. Boot to command prompt only.
2. At the C:\> prompt, type: CD\windows\options\cabs
and press <ENTER>.
3. Type <SETUP>, press <ENTER>.
4. Press <ENTER> to run scandisk.
5. At the software license agreement click YES.
6. At the Windows 95 startup wizard screen click YES.
7. At the choose directory screen click NEXT.
8. At the setup options screen click NEXT (Typical
is selected).
9. At the user information screen, verify information and click NEXT.
10. At the analyzing computer screen click NEXT.
11. At the windows components screen click NEXT.
12. At the startup disk screen select NO, and
click
NEXT.
13. At the start copying files screen, click NEXT.
14. During copying, you will get a VERSION Conflict
message about the file WINOA386.VXD.
Click NO to all.
15. At the finishing Setup screen click NEXT.
Windows 95 will now reboot to the system. You
will now get only one error message for the NTKERN.VXD.
The following steps should correct the problem.
16. Follow the directions on the screen to finish setting up Windows 95.
17. Go to START; Settings; Control Panel; Add/Remove Programs.
18. In the list, double click on USB Supplement for OSR2.
19. Click YES to restart the system.
SU0168 Error During Installation -- Method #1
From the Usenet archives...
This procedure is adapted from a technique posted
on comp.os.ms-windows.setup.win95 and credited to Sergio P.G. Moreira (si17911@ci.uminho.pt),
Universidade do Minho.
How to install the Full or OEM Version of Windows 95 onto a disk with an operating system already installed:
1.Start the install process by running the Windows 95 setup program.
2.When the program tells you that you can't install
this way
(i.e., you get the "SU0168" error), press the
reset button to reboot the PC.
3.Go to the C:\WININST0.400 directory.
4.Edit the file C:\WININST0.400\SETUPP.INF
5.There is a line: ProductType = number; change the number to 2.
6.Start Windows 3.1, choose the Run command from
the File menu, and enter the line below:
C:\wininst0.400\suwin.exe /SrcDir=DD /IQ /U:xxxxxxxxxxxxxxxxx
(Change DD to the location of your Windows 95 distribution. If on CD-ROM, it will be something like D:\WIN95; for diskettes, probably A:\.)
Another technique from the Usenet archives for
upgrading a Windows
3.1x installation using the "full" or "OEM" Windows
95 distribution...
1.Reboot your PC and start up the previous installed Windows 3.1x as usual.
2.Insert your Windows 95 CD-ROM or diskette #1
into the drive.
Let's assume a drive ID of "D" for your drive
although any other identifier will do.
3.Launch the "SETUP.EXE" program, located either in "D:\" or "D:\WIN95". To accomplish this, you may either launch the file manager, change to drive "D:" and start Setup by double-clicking it's name on the file list or you may choose "File/Run....."from the program manager. See the various text files on your Windows95 distribution for additional parameters to specify for Setup.
4.Depending on the parameters you specified, several dialog boxes appear. Acknowledge them with "Ok" or "Continue", up to the License dialog box. DO NOT PRESS ANY BUTTON IN THE LICENSE DIALOG BOX !!! If you do, Setup will bring up the SU0168 error message, terminate itself and you will have to restart from stage (3).
5.Switch to the program manager (or equivalent shell) by using ALT + TAB or entering the task manager with CTRL + ESC and double clicking on the program manager entry.
6.Launch a windows text editor, NOTEPAD.EXE for example. Select "File/Open....." Examine your hard disks for a directory called "X:\WININSTO.400 or so, where "X" stands for your hard disk's identifier. Setup created this directory on the first drive, that has enough free space to hold all the files needed for the installation process. From this directory select the file "SETUPP.INF" to edit.
7.In the file, you will see a line containing the string "[data]". Insert
a new line right below the [data]-line and type the string "OEMUP=1". The
piece of text should now look like the following
[data] OEMUP=1
Save the changed file and quit the editor.
8.Now switch back to the setup program using the
methods described in (5).
You will see the License dialog box again. Read
the license text carefully. If
you agree to its contents, press the "Ok" button.
9.If everything worked out fine, the next window
you should see is the Setup
Wizard main window. From now on, follow the instructions
given by the Setup
Wizard. If you still get the "SU0168" message,
something went wrong. In this
case, repeat the whole thing, beginning with
step (3).
The Windows 95 setup program on the "full" and "OEM" distributions exits with an "SU0168" error if it thinks you are attempting to upgrade from a previous version of Windows. Nevertheless, you can perform an upgrade with the following technique:
1. Either boot directly to MS-DOS or exit from Windows 3.1x to MS-DOS.
Do not simply launch an MS-DOS prompt ("DOS box") from within Windows.
2. Locate and rename the files WIN.COM and WINVER.EXE -- WIN.COX and WINVER.EXX are good choices. They will probably be in your \windows directory. If there are other copies of these files elsewhere on your hard drive(s), remove or rename them, too.
3. Start the Windows 95 setup program. If you are loading from diskettes,
it will be A:\SETUP, where "A" is the letter of your diskette drive. For
the CD-ROM distribution, it is usually D:\WIN95\SETUP, where "D" is the
letter of your CD-ROM drive. Note: If you already have a \windows directory
(and you probably will), Setup will attempt to install Windows 95 to \windows.000.
Change this directory specification to \windows (or wherever Windows 3.1x
is installed) if you wish to perform an upgrade.
The Windows 95 setup program on the "full" and "OEM" distributions exits with an "SU0168" error if it thinks you are attempting to upgrade from a previous version of Windows. Nevertheless, you can perform an upgrade with the following technique. This approach is similar to method #3, but requires that you have a bootable Windows 95 "DOS7" diskette for the version of Windows 95 you desire to install -- i.e., a "Startup Disk." You also need to ensure that your system will not automatically run Windows when you boot to the hard drive.
1. Boot to the "DOS7" diskette. Issue the command sys c: to copy a new MS-DOS bootstrap and system to your hard drive.
2. Reboot your system from the hard drive.
3. Start the Windows 95 setup program. If you are loading from diskettes, it will be A:\SETUP, where "A" is the letter of your diskette drive. For the CD-ROM distribution, it is usually D:\WIN95\SETUP, where "D" is the letter of your CD-ROM drive. Note: If you already have a \windows directory (and you probably will), Setup will attempt to install Windows 95 to \windows.000. Change this directory specification to \windows (or wherever Windows 3.1x is installed) if you wish to perform an upgrade.
SU99 is a prefix that is added to all errors that Setup does not have a specific error
message for. These errors are often caused by low conventional memory. If you
have already created a Startup Disk, quit Setup, shut down your computer, insert
the Startup Disk, and restart the computer.
Then, run Setup from the MS-DOS command prompt.
GFP ERROR IN DDEML
DDEML.DLL
Purpose:
Provides API functions for DDE on the I/O server
include
<ddeml.h>
Definition:
1. DDE Management library
2. Dynamic Data Exchange
The DDEML functions are part of windows.lib and
provide the DDE capability for the I/O server.
These functions allow an application to make
connections to other Microsoft Windows applications that support DDE.
This then in my layman terms:
DDE enables two running applications to share the same data.
DDE is like OLE where OLE is now in the process of growing and will eventually eliminate the need for sharing the DDE.
The problem described above is easily corrected by placing the following command anywhere in your AUTOEXEC.BAT file and re-booting your PC. (Both Windows 3.1 and Windows 95 / NT)
SET SRDDE = aoxomoxoa
Setting the above environment variable changes the behavior of the DDEML library so that the problem described above disappears. After extensive testing, we have not been able to find any negative side effects from setting the above environment variable therefore we highly recommend adding it to your AUTOEXEC.BAT file, even if you never expect to encounter the problem described here.
Microsoft makes no mention of this bug in the DDEML library anywhere in their entire tech knowledge base. The solution above was obtained from a senior support rep at Microsoft who described the problem as an "undocumented feature" of the Windows DDEML library. Interestingly enough any program that does not use the DDEML library does not experience this "undocumented feature".
FOR USE ONLY IF THE ABOVE DOES NOT SOLVE THE PROBLEM
Steps to fix the annoying SYSTEM FILE ERROR message when booting and installing software.
1. Most important, BACKUP your registry.
WRPV3.ZIP is the Best and easiest Registry Backup/Restore I've Seen.
Go To: http://www.webdev.net/orca/system and Search WRP: Install and backup.
This is a well written batch file driven bakup and restore, so it writes
nothing to your system. Far better than Microsofts URU.
2. Make sure the file (or files) that it says
is older (DDEML.DLL) is
the same in the SYSTEM and SYSBACKUP directories.
3. Open the registry editor.
4. Search for the file (or files). You should
see it in the
"CheckVerDLLs" key.
5. Delete the key. (Not the whole CheckVerDLLs
key, just the key with
the file in it)
6. Keep searching for it anywhere else, and also delete those keys.
7. Reboot your computer.
If Windows doesn't start, reboot in DOS and change
directories to WRP
and restore.
1st, any or all of these files may be corrupted, so I always recommend that you rename the old one and extract new non-corrupted files to the directories shown;
RNAAPP.EXE Module Dependency List
ADVAPI32.DLL c:\windows\system\
GDI32.DLL c:\windows\system\
KERNEL32.DLL c:\windows\system\
MPR.DLL c:\windows\system\
MSPWL32.DLL c:\windows\system\
MSVCRT20.DLL c:\windows\system\
NETAPI32.DLL c:\windows\system\
NETBIOS.DLL c:\windows\system\
RASAPI32.DLL c:\windows\system\
RNAAPP.EXE c:\windows\system\
SECUR32.DLL c:\windows\system\
SVRAPI.DLL c:\windows\system\
TAPI32.DLL c:\windows\system\
UMDM32.DLL c:\windows\system\
USER32.DLL c:\windows\system\
Disable WINS resolution in My Computer>>Control Panel>>Network>>Configuration>>TCP/IP->
Dial-Up Adapter>>Properties>>WINS Configuration. Click OK, then OK again.
You may have to re-start your system to get it to work.
http://support.microsoft.com/support/kb/articles/q172/5/05.asp
1st, any or all of these files may be corrupted, so I always recommend that you rename the old one and extract new non-corrupted files to the directories shown;
RUNDLL32.EXE Module Dependency List
RUNDLL32.EXE c:\windows\
ADVAPI32.DLL c:\windows\system\
COMCTL32.DLL c:\windows\system\
GDI32.DLL c:\windows\system\
KERNEL32.DLL c:\windows\system\
SHELL32.DLL c:\windows\system\
USER32.DLL c:\windows\system\
If this does not solve the problem update your COMCTL32.DLL;
You're COMCTL32.DLL may be too old. Go to;
http://www.microsoft.com/msdn/downloads/files/40comupd.htm
Read all and download from this page:
http://www.microsoft.com/msdn/downloads/files/40Comupd.exe.
When you run 40Comupd.exe, that will extract,
install and register
latest COMCTL32.DLL for you.
DOCUMENT:Q149083 [win95x]
http://support.microsoft.com/support/kb/articles/q149/0/83.asp
The relevant part :
To resolve this situation, add the following line
to the [386Enh] section of the
System.ini file and then restart your computer:
MinSPs=4
Although there is no way to prevent Windows95 from detecting and installing drivers for some devices, you can disable certain devices that may be causing conflicts. The lack of a feature to remove an item from the list of detected devices (when you use Add/Remove Hardware) is quite irritating and confusing, but problems can usually be averted by following these steps:
1. Right-click on My Computer, and select Properties.
2. Click the Device Manager tab, and select the device you wish to
disable.
3. Click the Properties button, un-check Original Configration, and
click OK.
Then the BLUE screen>>> For People With UMAX Scanners....
"Vmm32.vxd missing or unable to load" is a problem caused by UMAX scanners!!
My UMAX software creates an incorrect line in the system.ini file. (The
site has a downloadable patch for this). I downloaded the patch,
reinstalled the scanner's software, installed the patch.
See: http://www.umax.com/graphsite/umaxen/frame.cfm?section=Support
2.
C:\WINDOWS\SYSTEM\VMM32.VXD missing/unable to load error
This site is devoted to this problem.
http://web.dreamsoft.com/jjcesari/vmm32vxd/home.htm
----------------------------------------------------------
Infinisource.com
This site is well documented and devoted to vmm32.vxd
http://www.infinisource.com/techfiles/vmm32.html
----------------------------------------------------------
VMM32.VXD: Missing/Unable to Load
Missing/Unable to Load. Press any key to continue.
http://support.microsoft.com/support/kb/articles/q191/8/74.asp
-----------------------------------------------------------------
Error Message: VMM32.VXD Is Required to Run Windows...
VMM32.VXD is required to run Windows. If this file is not in your PATH,
you may need to reinstall Windows.
http://support.microsoft.com/support/kb/articles/q194/6/79.asp