Solved

making cardbus and legacy pcmcia work-dell lattitude cp 2/7/98

Posted on 1998-02-25
2
178 Views
Last Modified: 2013-12-16
my factory dell lattitude could boot with no problem using
3com 10/100 cardbus and megahertz legacy card installed-after I formatted the c drive and re-installed the dell images, it hangs on boot unless megahertz is removed-dell support says this has no fix !!! but it ships from dell in a fixed configuration !!! what does dell hardware engineers know that thier own tech support doesn't know. I had two machines from the factory and they worked flawlessly, but rebuilding them with dell software leaves them in a hanging
condition-dell won't give me the real answer-is there a vmm.vxd driver and a registry tweak required ??? one dell engineer did send me a vmm.vxd file and said drop it in the vmm32 directory, but when I do, it doesn't boot, it hangs saying vmm32.vxd is corrupt or missing...how does one install a vmm.vxd file so it works ??? it you can beat dell
tech support on this go for it-remember, they ship from the factory working fine, but call dell back and they say it should not work because cardbus isn't supported in win95
0
Comment
Question by:edzo
2 Comments
 

Author Comment

by:edzo
ID: 1754611
the original build was formatted out because Outlook 98 beta
ate my system, and the other sysytem we installed NT on...
we didn't (stupidly) burn the original image from dell onto
CDR, but the dell came with OSR2, OSR2 update, and 17 diskettes
worth of images to re-create the factory build...but they left
something out for sure...
0
 
LVL 9

Accepted Solution

by:
magigraf earned 200 total points
ID: 1754612
edzo....

Please read the following:

The information in this article applies to:

•Microsoft Windows 95 OEM Service Release version 2.1


SYMPTOMS

When you set up OEM Service Release version 2.1 (OSR2.1) over OEM Service Release 2 (OSR2) and restart your computer, you may receive an error message stating that the Vmm32.vxd file is missing or damaged, or you may not be able to boot Windows.


CAUSE

These errors can occur if either of the following conditions exists:

•The Vmm32.vxd file was not rebuilt properly or was damaged, resulting in an error message stating that "Vmm32.vxd is missing or corrupt." •The addition of Universal Serial Bus (USB) support is causing a conflict with the system and Windows 95 is unable to boot normally.


RESOLUTION

To resolve this issue, use the appropriate method:


Vmm32.vxd Missing or Damaged

If you receive an error message stating that the Vmm32.vxd file is missing or damaged, the rebuilding of the Vmm32.vxd file was unsuccessful, preventing Windows from booting properly and processing the RunOnce section of the registry.

You must uninstall OSR2.1 using the OSR2.1 real-mode uninstall tool (Rem.pss) on the installation disk. To use the uninstall tool, follow these steps:


1.Restart your computer.

2.Press the F8 key when you see the "Starting Windows 95" message, and then choose Safe Mode Command Prompt Only from the Startup menu.

3.Copy the Rem.pss file to the root folder of the boot drive as Remusb.bat (do not copy it to Rem.bat; "Rem" is a reserved command and it will not function).

4.Type "remusb" (without quotation marks) to restore the original files that were renamed with an .o20 extension.

5.To complete the uninstall process, restart your computer and use the Add/Remove Programs tool in Control Panel to remove the program "WDM/USB Supplement."

NOTE: This program may not be listed in the Add/Remove Programs tool. If it is not listed, skip this step.

6.Delete the Remusb.bat file from the root folder of the boot drive.



NOTE: The Rem.pss file has only been tested when the first reboot does not succeed. Failure to boot at any other time may not be resolved by the Rem.pss file process.

Windows 95 Cannot Boot Because of a Conflict

If Windows 95 cannot boot because of a conflict, use the following steps:

1.Restart your computer.

2.Press the F8 key when you see the "Starting Windows 95" message, and then choose Safe Mode from the Startup menu.

3.Rename the Detroit.bat file to Autoexec.bat. The Detroit.bat file is your original Autoexec.bat file that was renamed by OSR2.1 Setup.

4.Troubleshoot using standard Safe-mode troubleshooting.



For information about how to troubleshoot Windows using Safe mode, see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q156126
   TITLE     : Troubleshooting Windows 95 Using Safe Mode

hope this has helped
Regards
0

Featured Post

Save the day with this special offer from ATEN!

Save 30% on the CV211 using promo code EXPERTS30 now through April 30th. The ATEN CV211 connects a laptop directly to any server allowing you instant access to perform data maintenance and local operations, for quick troubleshooting, updating, service and repair.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

NTFS file system has been developed by Microsoft that is widely used by Windows NT operating system and its advanced versions. It is the mostly used over FAT file system as it provides superior features like reliability, security, storage, efficienc…
Learn how to PXE Boot both BIOS & UEFI machines with DHCP Policies and Custom Vendor Classes
In this video, we discuss why the need for additional vertical screen space has become more important in recent years, namely, due to the transition in the marketplace of 4x3 computer screens to 16x9 and 16x10 screens (so-called widescreen format). …
This Micro Tutorial will give you a basic overview of Windows DVD Burner through its features and interface. This will be demonstrated using Windows 7 operating system.

685 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question