paulogorjao
Contributor
Contributor

Base System Device driver is missing

Jump to solution

Hello,

I have a VMWare fusion 5.0.3 Windows XP Virtual Machine, where the the Base System device driver is missing - showing a yellow icon, and causing the annoying New Found Hardware Wizzard to show at startup every time.

The Hardware IDs are:

PCI\VEN_15AD&DEV_0740&SUBSYS_074015AD&REV_10

PCI\VEN_15AD&DEV_0740&SUBSYS_074015AD

PCI\VEN_15AD&DEV_0740&CC_088000

PCI\VEN_15AD&DEV_0740&CC_0880

I tried to re-install several times the VMWare tools, no help. This VM was originally on a previous version of VMWare, that I copied to this PC after it was updated to Fusion 5.0.

The vmx file is attached.

Thanks in advance for your help.

Kind regards,

Paulo

0 Kudos
1 Solution

Accepted Solutions
WoodyZ
Immortal
Immortal

You need to completely uninstall, not repair install/update install, VMware Tools then reboot and install VMware Tools.  Have you done that yet?

View solution in original post

0 Kudos
13 Replies
WoodyZ
Immortal
Immortal

You need to completely uninstall, not repair install/update install, VMware Tools then reboot and install VMware Tools.  Have you done that yet?

0 Kudos
paulogorjao
Contributor
Contributor

Thank you - uninstall and do a complete install of the VMWare tools solved it.

0 Kudos
cparke2
Contributor
Contributor

I am encountering this same issue under Windows 98 with VMware v12.5.9.

 

Removing and re-installing tools did not help.  VMware Tools themselves are working properly, as is the operating system itself.  There also is a crash of the VmwareService.EXE when it is attempted to be restarted during the Repair Installation of VMware Tools, but not on the first time install after a clean removal as you instructed above.

 

Using Windows 'System Information' utility, it is the same problem device reported by the OP:

 

PCI System Peripheral
    Unknown
   This Device Has a Problem: Code=28 (0x1C)
    The drivers for this device are not installed correctly. To install the driver for this device, click the Driver tab, and then click Update Driver.
    Registry Key:                        	 HKEY_LOCAL_MACHINE\enum\PCI\VEN_15AD&DEV_0740&SUBSYS_074015AD&REV_10\BUS_00&DEV_07&FUNC_07
    Alloc resources:                    	 Logical Configuration 0
    IO Range:                              	 Base=x1080 End=x10BF Min=x0000 Max=xFFFF  Alias=xFF, Decode=x00
    Memory Address Range:      	 Base= xFEBFE000 End= xFEBFFFFF Min= x00000000 Max= xFFFFFFFF 
    HW Revision:                        	 016
    Driver:                                   	 Driver Not Installed

 

 

Windows simply does not find the appropriate driver for the device. Maybe you forgot to include it on the tools installation media for Windows 95/98/ME?  What is the driver file name/location, is there somewhere else I can get it from?

0 Kudos
wila
Immortal
Immortal

Hi,


@cparke2 wrote:

I am encountering this same issue under Windows 98 with VMware v12.5.9.

 

Removing and re-installing tools did not help. 


That statement misses an essential part.. and so we still don't know if you did that correctly.

Did you reboot the VM after uninstalling VMware Tools?

To clarify.
Yes, that reboot is essential as Windows marks files ready to delete on boot when you run the uninstall.
If you skip that reboot and immediately run the install after uninstalling, then at the of the install when it prompts you to reboot for the first time, your freshly installed drivers will be gone after the boot.

--
Wil

| Author of Vimalin. The virtual machine Backup app for VMware Fusion, VMware Workstation and Player |
| More info at vimalin.com | Twitter @wilva
0 Kudos
cparke2
Contributor
Contributor

Yes, I did reboot after uninstalling before re-installing.  The base driver still is not to be found on the system ...

0 Kudos
cparke2
Contributor
Contributor

I believe this KB article address the issue  - Windows device manager shows yellow exclamation for VMCI device (1023129) :

For Windows 98 and Windows 98SE, there is no support for the VMCI device in VMware Tools. One workaround is to disable the VMCI device using the Device Manager so that it is ignored by Windows, and diagnostic tools stop reporting errors. Another workaround is to downgrade the virtual machine to virtual hardware version 4.

 

0 Kudos
magoo22
Contributor
Contributor

I solved the problem as follows, without downgrading the hardware version of the VM (I currently use Fusion 12.1 on a Mac and use hardware version 19 for the Win98SE VM).

After shutting down the Win98SE VM, I opened the VM Bundle file of the VM using "Show Package Content" (in Mac OS)
(the bundle file contains the hard disk image, and many other files). 

Then I copied the .vmx file (it is a text file) which is inside (at the top level) and pasted it on a Windows PC (or another working VM), in order to edit it using Windows Notepad. In fact I was afraid of using Mac TextEdit, as it might change the line feeds / carriage returns at the end of each line of the text file to Unix style.

I changed the following line:

vmci0.present = "TRUE"

to:

vmci0.present = "FALSE"

then transferred the modified file back inside the VM Bundle (keeping the same name, after renaming the original file).

Then I rebooted the Win98SE VM and voilà ! The "PCI System Peripherals" item with the yellow exclamation mark disappeared and did not show up again, even after hitting the "REFRESH" button.

In fact, Win98SE is unable to handle the VCMI Device, so it makes no sense to keep it active.
The advantage of this solution is that it works with the latest HW version of the VM (version 19).

0 Kudos
wila
Immortal
Immortal

Hi Magoo22,

That certainly is interesting as it pinpoints where the problem is.

Beware though that VMware Tools nowadays expects VMCI to be enabled and functional.
See also: https://docs.vmware.com/en/VMware-Tools/11.3.0/com.vmware.vsphere.vmwaretools.doc/GUID-6994A5F9-B62B...

It's possible that things like Shared folders do not properly function (can you try?)

 

edit
Tip: You can edit the .vmx file much easier. In the library, with the VM shut down (not suspended), right click on the VM, hold down the "option"  key and "Show in Finder" changes into "Open config file in editor"

--
Wil

| Author of Vimalin. The virtual machine Backup app for VMware Fusion, VMware Workstation and Player |
| More info at vimalin.com | Twitter @wilva
0 Kudos
gringley
Hot Shot
Hot Shot

Ummm...the VMtools that works here is Version 7.7.0 build-378486.

VMtools 11.3 would not begin to install on Windows 98 SE I would think?

Yes this is some stock advice I see from googling.  Setting the USB controller to USB 1.1 also gets rid of a device as Win 98 SE does not know USB 2.0.  

0 Kudos
wila
Immortal
Immortal

Hi,


@gringley wrote:

Ummm...the VMtools that works here is Version 7.7.0 build-378486.

VMtools 11.3 would not begin to install on Windows 98 SE I would think?


All good points, you're probably right about it not being able to install the latest 11.3, I will try later on.
Disabling vmci might be the better solution, I'm just wondering out loud about any side effects (if any) of doing that.

--
Wil

| Author of Vimalin. The virtual machine Backup app for VMware Fusion, VMware Workstation and Player |
| More info at vimalin.com | Twitter @wilva
0 Kudos
gringley
Hot Shot
Hot Shot

I booted my Win 98 SE back up and could drag a text file from my Monterey 12.1 iMac to the guest in Fusion 12.2.1 and the startup sound still works so I am not seeing any issues?  I realize that one of the minor missing documentations in VMware is a recommended hardware level to operation system chart.  I settled on an approach where I looked at what VMware hardware version was current when the operating system was released.  For My Windows 98 SE guest I use VMware hardware version 9.  In my mind it would be counterproductive to present Version 19 hardware to such an old operating system?

0 Kudos
wila
Immortal
Immortal

Hi,

I'm on virtual hardware 6 and also VMware Tools 7.7.0.

Everything works then.. as expected.

It is interesting to know that it works on later virtual hardware versions as there's always a risk of VMware removing support for the earlier VH versions in an update later on.

--
Wil

| Author of Vimalin. The virtual machine Backup app for VMware Fusion, VMware Workstation and Player |
| More info at vimalin.com | Twitter @wilva
0 Kudos
magoo22
Contributor
Contributor

Hi Wil,

it's me again...

I did the test with the VMware Tools.
As you correctly imagined, Shared Folder does not work.

But this seems to be a general problem with Win98SE VM's.
In fact, I tried to revert back vmci0.present = "TRUE" in the .vmx file, reboot the VM and the problem persisted:

Screen Shot 2022-01-21 at 10.05.46.png


In addition, after the boot, I got an error message in Windows:

Screen Shot 2022-01-21 at 09.57.06.png

I have Fusion 12.2.1  and VMware Tools 7.7.0. This is the version of VMware Tools that were installed automatically on the Win98SE VM. The install went without any problems.

In my opinion and according to my tests, the "fix" that I presented before (i.e. setting vmci0.present = "FALSE" in the .vmx file) does not introduce any additional limitations. Setting that flag to "TRUE" will bring back the "PCI System Peripherals" device with a yellow exclamation mark in the Windows Device Manager, and this does not make things better, since there is no suitable driver for it. 

Maybe this is something that VMware should provide/fix in one of the next VMware Tools version?

And besides the missing "Shared Folder" feature (regardless of the setting of the vmci0.present flag!), all the other VMware Tools features work even with vmci0.present set to "FALSE":

  • drag 'n drop files in and out of the VM
  • release mouse pointer in and out of the VM window
  • dynamically resize the VM screen size
  • audio

USB also works, after changing USB version from 2.0 to 1.1 in the VM's USB settings (as suggested in other forum discussions). I also had to install an additional driver not natively provided by the Win98SE install CD to get USB working:

nusb33e.exe (which can be found in the internet).

Instead of using Shared Folders to get files in & out of the VM, I can now use a USB memory stick, or simply drag & drop the files over the VM's window. So that's not really a limitation.

Do you think that setting an older hardware version for the VM would enable Shared Folders on Win98SE ? Which one?
Would that change imply a lengthy rebuild/rescan of all Windows drivers on the first boot after the change?

And thanks for the tip on how to edit the .vmx file. Very useful. I wasn't aware of it!!

0 Kudos