I have an ASUS Chromebox and I need to put it into developer mode so that I can...develop on it. However, I can't seem to get into Recovery Mode so that I can reboot it in developer mode. I followed the instructions to put it in Recovery Mode as documented and the Chromebox appears to turn on, but nothing happens on the monitor. How do I fix this?
The ASUS Chromebox in Recovery Mode does not support all monitors. If your Chromebox appears to have booted in recovery mode (lights are on) but the screen is blank, try booting it with a different monitor. Once it has restarted in developer mode, you can plug it back into the first monitor and it will work again.
Chromium.org's wiki has this page --> http://www.chromium.org/chromium-os/developer-information-for-chrome-os-devices that includes the following steps to enter Developer mode on the Asus Chromebox.
Entering
To invoke Recovery mode, you insert a paper clip and press the RECOVERY BUTTON (just above the kensington lock) and press the Power button. Release the RECOVERY BUTTON after a second.
To enter Dev-mode you first invoke Recovery, and at the Recovery screen press Ctrl-D (there's no prompt - you have to know to do it). It will ask you to confirm by pressing the RECOVERY BUTTON again.
Dev-mode works the same as always: It will show the scary boot screen and you need to press Ctrl-D or wait 30 seconds to continue booting.
I've found this list of systems and how to enter developer mode very useful.
Related
Docker Desktop is running, but it is not showing up in the system tray (a bug I assume?). How can I shut it down? I see no way to do this via the UX. The only way I've seen to shut it down is via right-clicking the system try icon, but that's not showing up. I could play whack-a-service in Task Manager, but I'm hoping there's a better way.
Overall, I'm not at all impressed with the UX of Docker Desktop. The "modal as a full app element" decision is confusing at best (it took me a while to notice that "X" in the upper right), and the inability to do things like actually shut the service down is frustrating.
I have made sure that the mac does not sleep by adjusting the settings in the system preferences. Jenkins will start the test on a schedule, the browser comes up but the test fails because the page is blank.
The same test works with no problem if the mac is unlocked or the screen save is not up.
I cannot leave the mac unlocked because the test runs at night and its a security issue.
Has anyone encountered this issue? And have a solution. Please share.
Attaching some logs. This image will give an idea of what I am describing.
You can try to run tests on locked computer when:
you set your display never turn off, when you lock your computer
you made sure, that computer never goes in hibernate or sleeping mode
If it will not work you can use two more possibilities:
run your tests on headless browser. Here is a pretty good explanation how to do it.
run your tests on a remote screen via VNC or RDP
EDIT:
You can try not lock the screen, but instead start the screensaver, and require the screensaver to immediately require a password.
I have a centos 7 on a vm. I put some command lines on the rc.local to initialize always the system reboot. I think i did something wrong, because when i restart the system, it frozes and dont enter centos anymore.
The internet is not on, i have to manually connect it when the centos starts, so i can't login the machine through Putty or other ssh program in order to fix the rc.local
What should i do now?
I found out the answer in this video:
www.youtube.com/watch?v=rvPtrwidhwo
When your linux appears to load completely (but get stuck) press "esc" to see where in the list of processes it got stuck.
Restart the virtual machine, and by the time it enters the mode to choose with linux you will want to load (rescue mode or normal mode), press ctrl+e to enter on a configuration/modification screen. It will show commands in the prompt.
You have to add parameters shown on the video. Search for the work "quiet". After this word and before the word LANG, add "systemd.unit=rescue.target"
Press ctrl+x to save (it will restart the vm automatic).
You will enter the rescue mode, input the root password.
Disable or modify the rc.local on (vi /etc/rc.local) in order to regain control over linux.
Then type: shutdown -r.
Restart the vm and everything will work again.
I have created a VB NET application that is installed with a installer project (MSI). Installer works perfectly, app functions as designed.
On a Windows 2008 Server R2 (Standard), the first time I log in the application starts with the wrong icon/task bar group. It starts with the IBM Tivoli command line icon or GUI icon with those options in the group.
After I close my application and open it a second time, I have the correct icon and taskbar group.
If I log into the box and start a different application, then my application, I get the correct icon/group.
Things I have tried...
Uninstalling/reinstalling multiple times
Confirmed my application is advertised
Deleted the icon cache for my profile
More information (from continued trouble-shooting)...
If I set taskbar buttons to "Never Combine" I get the correct icon for my app, but not the correct group options (right click).
If I pin the IBM Tivoli command line to the taskbar, this problem goes away. My app starts with the correct icon/group every time.
If I pin my app to the taskbar, the problem also is resolved every time.
So this problem is only occuring when neither app is pinned to the taskbar.
Another update...
This issue occurs in multiple environments (same server configuration).
This issue does not occur with a user account that did not perform the install. Only the installing account gets the behavior.
Solution...
This had nothing to do with my application or IBM Tivoli, it is a bug in certain versions of Windows...
KB 2519550
This KB hung up the box on restart, but once I hard cycled it, the problem was resolved.
I have a Windows 7 Ent - 64bit system.
I am stuck in a loop, where the login screen is presented, i enter my network credentials, the welcome spinner is shown, the screen flickers like when resized, then the system goes to logging off screen and then finally goes back to the control alt delete screen.
I cannot get out of that loop for the life of me.
I contacted corp support, he came over and logged in using his login (admin level) and was able to get a desktop up.
The support people are not allowed to access the registry to correct or even look at my users settings, and my user IS NOT AN ADMIN on this machine.
Question is - is there a way to blow away my profile on this machine, or reset my registry branch to that of a new user or something???
i have bitlocker enabled on the drive - so using the emergency boot disks are almost rendered useless...
im stuck, and i dont know where to look....
any ideas would be wonderful
thanks
the admin level user logged in, and turned his back for a moment, and i was able to go in and reset the autologon registry entry...
rebooted,and all is well.
Disconnect Your USB Devices
If you like using all sorts of USB devices such as the mouse, keyboard, speakers, Bluetooth speakers, USB dongles, USB Wi-Fi adapters etc. However, these connected devices might cause the Windows 7 stuck on the welcome screen for a long time issue. Therefore, a common solution to the problem is to disconnect all externally connected devices from your PC.
Disconnect from the Internet
Sometimes Windows 10 gets stuck on the login screen because it's trying to connect to your wireless connection. If your Windows gets stuck on the welcome screen, you should make sure that you are not connected to the internet before proceeding to log in.
Run system checks
In some case, corrupt system files on your computer will cause this problem – stuck on welcome screen Windows 10/8/7. Therefore, to fix the Windows 10 freezes on startup problem, you can use CHKDSK to run some checks on your computer to see if it is the corrupted files that cause your startup problem.Restart Windows Update service
You can try restarting Windows Update service and then rename few files if you still get stuck on welcome screen Windows 10 issue.
Here are the steps:
Step 1. Open command prompt.
Step 2. Type net stop wuauserv in the run dialogue and press Enter.
Step 3. Type cd %systemroot% command and press Enter.
Step 4. Type ren SoftwareDistribution SD.old and press Enter.
Step 5. Type net start wuauserv and press Enter.
Step 6. Type exit and press Enter to close Command Prompt and restart your PC.
Step 7. Now, reboot your PC/laptop and check if the stuck on welcome screen has gone.
Restore Windows by using System Restore
System Restore is a useful feature that allows you to restore your operating system to a previous state and fixes any boot problems such as Windows 10 freezes on startup, Windows 7 hangs on welcome screen, etc.