top of page



Recover Disc 2.0 Serial Number

Download File >>>

If you are unable to locate your copy of Rhino, we may be able to help find your license key code if you registered your product. If you bypassed registration, we will not have any record. We did not trace product serial numbers upon shipment, so your order number will not help us.

Please immediately drop us a line at with your product serial number and a brief description of what has happened, and we will get in touch with you right away to start the recovery process. In any case, it may best to step away from your device and wait for instruction.

You can choose to order a copy of your download software on a DVD. This ensures that you always have a copy of your software at hand! Your Backup Copy on a DVD will be sent by post within 7 business days. The serial number from your initial purchase is needed for installation. You will need to call for an activation code.

If your product requires a serial number or unlock code, you can usually find it in the Order Confirmation email that was sent to you when you submitted the order. If you do not have your Order Confirmation email, you can use the Account Login to look up your order and get your serial number or unlock code.

Second, please note that serial numbers, registration numbers, unlock codes, and passwords are case-sensitive. Make sure you are entering your code in upper case characters. If you still have problems, contact IMSI Customer Service at

The nominal method used within scsi_id command to obtain this information is to use the output from scsi INQUIRY command to fetch VPD (vital product data) information from either page 83 (device identification) or, if that is not available, page 80 (unit serial number). In the case of vmdk based virtual disks provided to the RHEL guest, these pages are not be available until the `disk.UUID` feature is enabled within the hypervisor. So the root cause when blank output is generated from `scsi_id` for virtual disks is the lack of appropriate VPD information being provided from the hypervisor. To correct this, enable the disk.UUID feature within the VMware hypervisor by following the [steps outlined above](#STEPS).

The scsi_id code does a standard INQUIRY (A) command. This is followed by an INQUIRY of page 00 (B) which returns all available pages supported by this device. The returned list of pages includes page 80, where the serial number is located as well as page 83 where the WWID is located. Then and INQUIRY of page 80 (C) is performed, and finally INQUIRY of page 83 (D). All those complete successfully, and the WWID retrieved from the device is displayed (E) and scsi_id exits with status of 0. The WWID itself is "60060160dfc02c00ce7fabaf69999999", the "3" take leads that string is added by scsi_id to identify the source and type of scsi identifier being output. See "How are SCSI ID generated" for more information on prefix characters and how SCSI identifiers are created.

Here the INQUIRY of page 00 (B) response as seen in data[254]= is the same standard inquiry data as seen in the output of (A) instead of the list of pages happened with device sdb. This means this device does not support any inquiry pages at all and therefore scsi_id cannot retrieve a serial number or a WWID from the device -- the required inquiry pages that scsi_id needs are not supported by the hypervisor for these devices. No identifier is output and scsi_id exists with a status of 1. The storage configuration for this vm guest within the hypervisor needs to changed to correct this behavior such that it provides the data upon an INQUIRY IO sent to the device to retrieve pages 00, 80, and 83 is completed successfully with the expected and required data.

A utility called Game Key Revealer has been designed specifically for the sole purpose of reading and recovering game CD Keys and Serials for installed games on your computer. The creator also has another tool called SoftKey Revealer which concentrates on recover

  • グループについて


    bottom of page