VMWare Notes: Difference between revisions

Line 11:

====Booting from a USB Flash Drive====

The first hint is that it doesn't seem to be available in BIOS mode, only UEFI.

~~The trick is to look for the little tiny Icon down at the bottom of the VMWare window that represents the USB Flash Drive, right click and select "Connect"~~

====Network Adapter Types====

Line 26:

Line 24:

<nowiki>*</nowiki> Cobbled: Go ahead. Do a search for: "virtualdev" "e1000" "e1000e" "vmxnet3" "rtl8139". NOTHING! Now if as of 2023, VMWare Workstation 17.5 supports all of those types, so shouldn't that be documented somewhere? According to VMWare: Nope.

==== If unable to add a new or USB connected Drive as a Physical Disk... ====

When plugging in a SATA drive via a USB adapter with the intent of adding at a Physical Disk to a virtual machine, if it isn't detected, close VMWare and then start it again. It should then 'see' the new drive. This is similar what occurs with Acronis products where software doesn't 'hear' or 'subscribe' to the events Windows makes available allowing software to be made aware of a disk drive change and allowing for 'rescanning' or automatic detection of new drives.

@@ Line 11: / Line 11: @@
 ====Booting from a USB Flash Drive====
 The first hint is that it doesn't seem to be available in BIOS mode, only UEFI.
-The trick is to look for the little tiny Icon down at the bottom of the VMWare window that represents the USB Flash Drive, right click and select "Connect"
 ====Network Adapter Types====
@@ Line 26: / Line 24: @@
 <nowiki>*</nowiki> Cobbled: Go ahead.  Do a search for: "virtualdev" "e1000" "e1000e" "vmxnet3" "rtl8139".  NOTHING!  Now if as of 2023, VMWare Workstation 17.5 supports all of those types, so shouldn't that be documented somewhere?  According to VMWare: Nope.
+==== If unable to add a new or USB connected Drive as a Physical Disk... ====
+When plugging in a SATA drive via a USB adapter with the intent of adding at a Physical Disk to a virtual machine, if it isn't detected, close VMWare and then start it again.  It should then 'see' the new drive.  This is similar what occurs with Acronis products where software doesn't 'hear' or 'subscribe' to the events Windows makes available allowing software to be made aware of a disk drive change and allowing for 'rescanning' or automatic detection of new drives.