-->

Starting with Windows 10, Version 2004 (OS build 19041.488 or higher), two additional identifiers are available for NVMe storage disk drives which support the STOR_RICH_DEVICE_DESCRIPTION structure:

SCSIt*v(8)p(40)

Where:

R3 VMLiteUSB;VMLite USB;c: windows system32 Drivers VMLiteUSB.sys 2010-20 R3 WatAdminSvc;Windows Activation Technologies Service;c: windows system32 Wat WatAdminSvc.exe 2011-736 R3 WDCSAM;WD SCSI Pass Thru driver;c: windows system32 DRIVERS wdcsam64.sys 2009-4.

• t* is a device type code of variable length

• v(8) is an 8-character vendor identifier

• p(40) is a 40-character product identifier

Drivers Vmlite Scsi & Raid Devices Usb

SCSIt*v(8)p(40)r(8)

Where:

• SCSIAdapter Drivers Download. In our share libs contains the list of SCSIAdapter drivers available for download. To download the proper driver by vender name. If not found in our garage driver you need, please contact us, we will help you in time, and updates to our website.
• PC Matic Pro is a set of revolutionary technologies that is empowering customers and businesses to secure and optimize the performance of their devices. Learn More Free Tools.

• t* is a device type code of variable length

• v(8) is an 8-character vendor identifier

• p(40) is a 40-character product identifier

• r(8) is an 8-character revision level value

In versions of Windows prior to Windows 10, Version 2004 (OS build 19041.488 or higher), the device ID format for a small computer system interface (SCSI) device is as follows:

SCSIt*v(8)p(16)r(4)

Where:

• t* is a device type code of variable length

• v(8) is an 8-character vendor identifier

• p(16) is a 16-character product identifier

• r(4) is a 4-character revision level value

The bus enumerator determines the device type by indexing an internal string table, using a numerically encoded SCSI device type code, obtained by querying the device, as shown in the following table. The remaining components are just strings returned by the device, but with special characters (including space, comma, and any nonprinting graphic) replaced with an underscore.

The SCSI Port driver currently returns the following device type strings, the first nine of which correspond to standard SCSI type codes.

An example of a device ID for a disk drive would be as follows:

SCSIDiskSEAGATE_ST39102LW_______0004

There are four hardware IDs in addition to the device ID:

SCSIt*v(8)p(16)

SCSIt*v(8)

SCSIv(8)p(16)r(1)

V(8)p(16)r(1)

In the third and fourth of these additional identifiers, r(1) represents just the first character of the revision identifier. These hardware IDs are illustrated by the following examples:

SCSIDiskSEAGATE_ST39102LW_______

SCSIDiskSEAGATE_

SCSIDiskSEAGATE_ST39102LW_______0

SEAGATE_ST39102LW_______0

The SCSI Port driver supplies only one compatible ID, one of the variable-sized generic type codes from the previous table.

For example, the compatible ID for a disk drive is as follows:

GenDisk

The generic identifier is used in INF files for SCSI devices more than any other, because SCSI drivers are typically generic.

Be aware that the SCSI Port driver returns no generic name for sequential access and 'processor' devices.

Whilst Virtualbox can access virtual disks in .vdi, .vhd and .vmdk format, VMware player or workstation supports only .vhd- and .vmdk file format. From time to time people asking me, how to convert a Virtualbox .vdi file to a .vhd or VMware .vmdk.

There are a couple of web sites describing how to use Virtualbox VBoxManage.exe to convert a .vdi file to a .vhd disk. It requires invoking a command prompt window, navigate to Virtualbox install folder and enter a command like this:

vboxmanage clonehd d:androidandroid4.vdi
d:androidandroid4.vhd --format VHD

The two lines above are one command. The resulting file android.vhd can be used in VMware Player/Workstation.

Note: This approach comes with two problems. First of all, it’s complicated to fiddle with command prompt window and spelling the right paths. And second I prefer to use Virtualbox portable beside my VMware Workstation installation. If Virtualbox portable is used, VBoxManage.exe won’t work – some Class isn’t recognized. Therefore I was looking for an alternative way, and I found the approach drawn below.

A smarter way to convert .vdi files

Drivers Vmlite Scsi & Raid Devices Download

In this Q&A somebody mentioned, that Virtualbox comes with a tool that works well under Windows. And someone else mentioned a graphical tool will do the conversion. After a bit of experimenting, I found out, how to convert Virtualbox .vdi files in a comfortable manner. It requires Virtualbox or VMLite workstation.

1. Launch Oracle VM Virtualbox Manager (or VMLite workstation – also Virtualbox portable fits).
2. Press Ctrl+D or open the Machine menu and select Manager for virtual media (see above in background).
3. In virtual media manager select the .vdi file to be converted. After selecting a file, press Ctrl+C or click the Copy button.
4. In the conversion wizard’s dialog box confirm the media to copy and click Next.
   
5. Select the target disk output format and click Next.
   
6. If you selected .vmdk for a virtual machine file, the next dialog box allows you to set the parameter for the target file.
   
7. After confirming the disk type using the Next button, select the target folder and adjust the target file name.
   
8. Click the Next button and confirm the Copy button in the next dialog box.

Virtualbox copy wizard creates a new target disk and convert the source content to the required target disk format.

Afterward, the target folder contains the converted virtual disk, that may be associated to a VMware Workstation or Virtual PC VM (depending on output format).

Attention: Converting .vdi disks containing VMs with Linux or Android should be no major problem. Only Android may causes trouble, because the Linux kernel just supports IDE disk controller. A Windows guest OS in a converted VM raises serious trouble, because booting in the new environment forces Windows to install other drivers for the hardware environment found in the VM. Windows XP fails with blue screens, if the disk controller changes. Whilst Virtualbox uses SATA- or IDE-controller, VMware connects always a virtual disk via SCSI controller.

Change the disk controller type in VMware

In some cases it’s sufficient to change the type of disk controller for VMware player or workstation. This change must be done manually, editing VMware .vmx configuration file with a text editor. In most cases something like this will be present in the .vmx config file:

scsi0.present = „TRUE“
scsi0.virtualDev = „lsilogic“
scsi0:0.fileName = „I:VMsAndroid3.2Android-v4.vhd“

The command lines shown above must be changed to something like the commands below:

ide0:0.present = „TRUE“
ide0:0.fileName = „I:VMsAndroid3.2Android-v4.vhd“

After modifying the configuration settings, the VM can bee bootet, to see, if it went well.

Note: For Windows I prefer tools like VMLite`s MyOldPC or Paragon Go Virtual. These tools not only converting the disk formats. Both tools supporting driver injection in Windows guests, so booting the converted VM should be not a painful job – only Windows activation can be a “pain in the as” – if Microsoft decides to block the license key.