ATIH 2012 Recue disk won't work with wireless keyboard

Yep, it would be a driver issue. ATI's linux boot environment doesn't have support for the driver(s) required by the wireless keyboard. I suspect that someone will advise you to use the Plus Pack in order to create a WinPE disk with driver support, or Mustang's bootable disks.

By the way, I forgot to mention that I also have the Plus Pack. Creating a WinPE disk, I would have to try, but is takes longer for WinPE to boot compared with Linux. With ATIH 2010, I also had an issue with a wired keyboard that time, a Microsoft keyboard.

Is there a way to add the (may be) missing driver to the Linux environment ? I remember that when you create with Linux, it asks for a command to execute, may be that would do it.

Another issue I have is that the Rescue Disk does not always 'see' other computers on the network.

Thanks tuttle.

Gilles Plante

Same Problem for me. After booting from downloaded image or created boot disk USB Keyboard and mouse stopping to work. Have already opened a Support incident but got no solution.

Have tried TIH2012 Build 6131 and 6154 and any provided option, with acpi, no acpi, BIOS USB Set to Legacy on and off, no chance.

Have an older 2010 Version and my USB mouse is working with this version, but still no Keyboard.

Issue starten with new Motherboard Intel DX79si - i think there are some drivers are missing in ISO Linux from bootable Disk.

World be nice if this issue could be sorted out as soon as possible.

Best and kind regards,
Roland

Greetings Everyone,

Thank you for taking the time to post your inquiries and requests at our Forum. Likewise, I appreciate your efforts Tuttle.

First of all, I would like to say that I understand the difficult situation you find yourselves in, and I personally apologise for the inconvenience this must have caused. However, I will be very glad to help provide useful information for a temporary workaround, only until our Development Team provides a fix for the incompatibility issue you face at hand. Therefore, I kindly ask for your patience, and hope that the workaround provided below will satisfy your needs in the meantime.

Gilles Plante, I'm afraid the Linux Kernel parameters will not be of help, as the only parameter you can specify, for a keyboard recognition during the boot process, addresses keyboards connected to a parallel port. Please see the list of parameters that are available from our Knowledge Base article, and the exhaustive list from this very article for reference.

Furthermore, Gilles Plante as you seem to have Acronis Disk Director Suite 10.0, a fix for a previous incompatibility issue with wireless USB kits (mouse and keyboard) was implemented for this product. Maybe you can provide us with a System Report to see as to why the issue persists with Acronis Disk Director Suite 10.0. Please see our Knowledge Base article on this fix. Roland Giehl, this very article states that the fix has been implemented for Acronis True Image Home 2010 as well, but I cannot ask of you to try and reproduce the issue and generate a System Report, as I presume you already have Acronis True Image Home 2012 installed. Normally, there should not be wireless keyboard and mouse incompatibilities with Acronis Disk Director 10.0 Suite and Acronis True Image Home 2010, as fixes for these products have already been implemented.

Roland Giehl, I understand that you contacted Acronis Customer Central, and have received support, and that your issue has not been resolved yet. May I ask if you have tried to add the specific driver for your wireless keyboard in the Windows Preinstallation Environment (WinPE)? You may very well provide me with your keyboard's model and manufacturer details so that I can find and download its corresponding driver for you.

As an initial step, please see the respective prerequisites to booting into the WinPE-based Acronis Rescue Media, from this Web-Help page or from this Knowledge Base article with simple, step-by-step instructions.

Presuming that you have Windows AIK and its related components downloaded and installed, and that you are ready with your WinPE-integrated Acronis Rescue Media, you may boot your computer with this media and add your specific keyboard drivers, that you should have ready, to enable the recognition of your keyboard devices. Please follow the steps on adding drivers in the WinPE environment provided in Microsoft's TechNet article and its respective sections.

Should you need help carrying out command-line instructions, please send me a PM and I will be very glad to help you out with this.

I apologise once again for the issues you are having, and hope that this workaround, and the request submission to fix this issue referred to our Development Team will be the resolution to your issue.

Please do not hesitate to contact me for additional help and questions that you may need answering.

Best,

Hi,

appreciate your reply. In regard to your solutions I must say I can't do so - because I need the "Plus Pack" to create WinPE Rescue Media. Thought you will understand that I'm not happy to invest money to solve a Vendor issue. Acronis Support (Case 01568337) had made the offer to provide the needed add-On for less - but I have not heard anything back.

Best
Roland

Hi Volkan,

thanks for your inputs. I don't know if the issue with the keyboard also occurs with Disk Director 10, I mainly use ATIH. I will give a try to WinPE when I will be back, I am away home for 5 weeks.

Hello Roland.
Normaly quit easy when you have a *.inf driver.

You have to use Microsoft WIAK to create your WinPe.
When you do that you can extend the image with the driver.

Take a look at the commandline tool 'dism.exe' and the parameter '/Add-Driver'.