We have a device with Windows 8 embedded OS. We need to install cypress USB drivers while updating our application and do it silently without any OS pop ups, as users won't have input device to accept the prompt dialog.
I have used PNPUtil.exe and DpInst.exe with /S /Q option combinations. Either installation does not happen or it happens with OS prompt.
I tried signing our drivers with code sign certificate still there OS prompt pops up.
I have also tried disabling EnableLUA option in the registry, but still issue exists.
I have used following to tools with all relevant flags, still we could not suppress the OS prompt.
pnputil.exe /S -i -a Drivers/win8/x86/
dpinst-x86.exe /S /PATH Drivers/win8/x86/
I would like to know :
Whether this is possible?
Does any installer framework support such installation?
Can creating a sub process and making it install the drivers in a programmatic way serve the purpose?
Can we modify the registry to suppress these prompts?
NOTE: if I could I would have left this as a comment.
For this scenario I've always used DISM. You can mount your image and install software, drivers or anything you like and then silently blast the image onto a machine. If reinstalling isn't an option please disregard.
https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/dism---deployment-image-servicing-and-management-technical-reference-for-windows
Related
I have installed Ubuntu 18.04 for windows subsystem for linux on windows 10, after enabling WSL in Powershell (instructions here: https://learn.microsoft.com/en-us/windows/wsl/install-win10).
I've done this before on a desktop but now I'm doing it on a laptop. I had no issues with the previous installation but this time around ubuntu will not launch. I get the ubuntu console popping up briefly before disappearing.
Also trying to run bash.exe from the command line fails silently (doesn't hang, just exits with no message), which may be related.
I'm struggling to figure this out as I have no idea where any error messages might be logged. Does anyone know how I can investigate further why this is happening?
Setup is a windows 10 Pro, os build 17134.376, everything up to date.
I'm struggling to figure this out as I have no idea where any error messages might be logged. Does anyone know how I can investigate further why this is happening?
Check with wslconfig.exe /l all registered distros, try to deregister the one you have problem with ( e.g. wslconfig.exe /u Ubuntu [^1]) and run the ubuntu.exe in your distro once again. Just a wild guess, it might be also a problem, if you have more than one copy of the linux distribution in you home directory.
[^1]: Warning: deregistering will delete all the associated files!
I have installed NetBSD 6.1.5 with full installation setting. However, when I run startx it says no screens could be found. So i tried "X -configure" and then "X -config ~/xconfig.conf.new" and I was brought to a very generic screen with a black x crosshair, but I was unable to exit this using the suggested ctrl+alt+backspace, so I had to force power off and check if my keyboard was recognized in the conf file generated, which it was. I have installed xdm, xterm, Xorg, and other X programs.
I am not familiar with setting up desktop environments from scratch. I am a newb who is used to Ubuntu esque installers doing that stuff for me.
Would someone be able to walk me though the installation or point me to a link which explains a step by step process?
What happens if you rename your xorg.conf.new to /etc/X11/xorg.conf? Does startx or xdm work then?
Are you running this inside a VirtualBox or other emulator?
I have NetBSD on a Thinkpad T420 which I occasionally boot into Windows, and I've setup VirtualBox to be able to run the same NetBSD install when I'm in Windows. The key difference in the xorg.conf file is in the Device section:
Section "Device"
Driver "vesa"
EndSection
Also I've found the free version of http://mobaxterm.mobatek.net/ very handy - I use it to ssh into the virtual NetBSD box and then run X apps and have them display on the Windows desktop.
Final note - you might want to look out for the NetBSD-7 RC1 which should be out 'Real Soon Now', as there are some very handy improvements, including better support for most modern display hardware :)
I found that running startx from any directory with a .xinitrc file gives strange behavior in amd64 6.1.5 and 6.1.4. Delete (or rename) any .xinitrc files and try
xinit /path/to/windowmanager
Please read Chapter 9 of NetBSD Guide:
http://www.netbsd.org/docs/guide/en/chap-x.html
Section 9.9 discusses installing various Desktop Managers/Environments.
It turns out that I could run "X -config xorg.conf.new" as root on host and then ssh using putty to manually launch windows.
http://zzsethzz.blogspot.de/2013/02/install-chromium-upgrade-it-to-chrome.html
According this tutorial, I should remove all HDDs I do not want to install chromium OS to during install. I wanted to try this guide on my imac using an external SSD for chromeos. Obviously, removing the HDD isn't an option. Will the chromiumOS installer format my mac drive too, if I don't remove it?
AS the writer of that tutorial I can hopefully help you. When you install Chromium OS to begin with you can specify where to install to if you know your unix commands well enough. and then from there you can update to Chrome OS once you have your external working for you.
To find out what your hard drive is when connected, open a terminal (you may need to use a developer terminal) and use the command "fdisk -l" This will list your hard drives. for example /dev/sda1 etc...
Your install command would be "Install /Dev/sda1" but replace the dev part with whatever your hard drive was listed as. If you need further help email me at admin#xiaorishu.co.uk
Possible?
I think to do this I need to upgrade the AIR runtime on the Fire to 3, but the version in the app store won't install. I can't create an AIR apk that is both captive runtime and debug that I know of, so the debug version of the app has to run on the AIR runtime installed. Since the Fire comes with 2.7, 3.x apps won't run in debug mode.
Has anyone managed to get AIR 3 running on a Fire without using captive runtime?
To update AIR on your KF you have to get root privileges. Also keep in mind that android build on KF doesn't have any copy command (it cut off). So the best way I found is to flash your KF with modified (pre-rooted) stock version and then install new air.
Get pre-rooted stock version (I took it here). IMPORTANT: it installs via TWRP, google how to install TWRP on KF.
Put downloaded .zip and air_runtime.apk (latest AIR version) in the root of KF.
Reboot in Recovery mode (TWRP should load)
Flash this version.
On your PC open cmd and run "adb shell" (make sure you see your device in list when run "adb devices" otherwise check drivers).
Run "su" (if you downloaded secure version).
In shell go to sdcard ("ls" to get list of files/folders and "cd folder_name" to get into) and run "install air_runtime.apk /system/app/air_runtime.apk" (I think you can just run "install /sdcard/folder_with_air/air_runtime.apk /system/app/air_runtime.apk").
(7a. If it tells you that can't install because of file already exist, run the following two commands: "mount -o remount rw /system" (mount 'system' with read/write rights) and "mv /system/app/air_runtime.apk /system/app/air_runtime.bak" (rename air_runtime.apk into air_runtime.bak). Then repeat step 7.)
In KF just run (install) air_runtime.apk (use any file explorer, e.g. download ES File Explorer from Amazon).
Check AIR version in Applications.
That's all. Looks a bit complex, but in real it takes about 4-5 mins for me to update AIR (BUT I have TWRP already installed).
Hope it helps.
UPD. After your Kindle updates itself (version 6.3.1 currently the latest) you'll lose you SU privileges. AIR also will be rolled back to 2.7. You can prevent KF auto-updates (search on xda how to do it) or flash actual pre-rooted version (it gives you several months without problems).
Is is possible to automate the installation of an OS using VMware or any other virtualization product?
One of our products consists of a customized version of CentOS that installs the OS and our application on a server. It's much like any CentOS/RHEL installation where you choose a mode that corresponds to different kickstart options, and then you choose your keyboard type. The rest of the installation is automatic.
What I'd like to have is an automated system that will create a new guest VM, boot it with the ISO image of our product, start the installation (including choosing the keyboard), wait for the reboot, and then launch a set of automated tests.
I know that there are plenty of ways to automate the creation of new VM guests from existing templates/images, and I know you can use the VIX API to interact with virtual machines, but the VIX API seems to require that VMware tools is already running (which won't be the case when you're booting from the CentOS install disk).
This answer (Automating VMWare or VirtualPC) indicates that you can script VMware to boot from an ISO that does an unattended installation, but I would really like to test the same process that our customers will be using.
Another option might be to use Xen's fully-virtualized mode and see if scripting it over the serial port will work.
TIA,
Jason
I have a very very similar question, it is on superuser:
https://superuser.com/questions/36047/moving-vmware-os-image-as-primary-os-on-a-system
You can also use VirtualBox instead of VMWare. The VirtualBox SDK allows you to directly control the keyboard, the mouse the serial port and the parallel port of the guest without the virtualbox guest tools installed.
Unfortunately it doesn't offer a text console interface but the serial port can be connected to a local pipe file and that can probably be worked with just as well.
This may not be exactly what you need:
I have done something similar with a Ubuntu-based install. We used preseeding (Debian's form of kickstart), to answer all the questions during the install - providing the preseed file and the installer via tftp.
In addition to the official Ubuntu mirror we added the apt-server with our own packages in the preseed file. We put a .deb version of vmware-tools on the apt-server and added it to the packages to be installed.
The .deb of vmware tools just contained the .tar.gz and a postinstall script that would extract it to /tmp and run the vmware install script (which has a switch to be run unnattended, so it does not ask any questions).
So after the reboot vmware-tools were up and running and we could use vix to script the rest (which was not very reliable).
If you should encounter problems with running vmware-config.pl during boot, you could make a custom package that just extracts the tools and an init script that installs them on first boot, disables itself and reboots.
Maybe you can use this strategy (replacing apt by yum, preseed by kickstart and tftp by a remastered iso). If you really need to test that your users choose a keyboard in the installer (which is not very different from kickstart) this would obviously not work for you..