reboot

Why do the bytes “0xea 0000 ffff” in a bootloader cause the computer to reboot?

由 会有一股神秘感。 提交于 2019-12-10 18:21:23
问题 I was researching boot loaders and I found this interesting piece of assembly: ;Sends us to the end of the memory ;causing reboot db 0x0ea dw 0x0000 dw 0xffff By the comment I know what it does; sends the computer to the end of memory, but what I can't figure out is how those numbers reboot the computer (x86_64 processor on 16-bit mode). 回答1: Those bytes correspond to jmp word 0xffff:0000 (you can see this by assembling with NASM and then disassembling the resulting binary), which happens to

bash/cygwin/$PATH: Do I really have to reboot to alter $PATH?

由 寵の児 提交于 2019-12-10 15:12:21
问题 I wanted to use the Python installed under cygwin rather than one installed under WinXP directly, so I edited ~/.bashrc and sourced it. Nothing changed. I tried other things, but nothing I did changed $PATH in any way. So I rebooted. Aha; now $PATH has changed to what I wanted. But, can anyone explain WHY this happened? When do changes to the environment (and its variables) made via cygwin (and bash) take effect only after a reboot? (Is this any way to run a railroad?) (This question is

Android widget update called twice after device boot

由 好久不见. 提交于 2019-12-10 11:02:58
问题 After device reboot I receive first APPWIDGET_ENABLED and then twice APPWIDGET_UPDATE. I spent quite some hours googling this without result. Is anybody experiencing the same? Have you found a way to avoid calling the update twice? Here's some code: <receiver android:name=".Widget" android:label="@string/app_name"> <intent-filter> <action android:name="android.appwidget.action.APPWIDGET_UPDATE" /> </intent-filter> <meta-data android:name="android.appwidget.provider" android:resource="@xml

Can't reboot device using runtime.exec

由 时光毁灭记忆、已成空白 提交于 2019-12-10 10:33:27
问题 For some reason I cannot reboot Android devices using Runtime.getRuntime().exec("/system/bin/reboot");. I have tried the following code on 3 devices now without luck. One was built from rowboat-android source. The other two are the Motorola Droid Pro (Rooted, stock) and the HTC Ledgent (Rooted, Cynogen Mod). All devices are running Android 2.2 Froyo. Does anyone know why? su works as well as the Super User application is visible. I should note various other shell commands do work, like netcfg

Get date/time of last reboot programmatically

由 风流意气都作罢 提交于 2019-12-10 07:37:24
问题 I would like to find the time of the last reboot programmatically in Linux. I am using C and C++ in my module. Is there an API? 回答1: There's no direct api, but you can read /proc/uptime "file" to learn how many seconds the system have been running, subtract that from the current time - and assume that's when the machine was rebooted. /proc/uptime This file contains two numbers: the uptime of the system (seconds), and the amount of time spent in idle process (seconds). 回答2: You could either

Why do some installers need to restart the computer before you run the program?

由 旧巷老猫 提交于 2019-12-10 03:47:05
问题 I'm fairly new to deploying desktop applications, so this is the first time I'm building an installer for my software. Currently, the first time I run my software after installing it, it crashes. After that, it runs fine. I'm still in the process of debugging this issue, but I've noticed that a reboot immediately after installing and before running the software seems to fix this crash. What are common reasons that some installers ask you to reboot before running the software? Also, why do

Does iOS start app in background after reboot if remote-notification defined in UIBackgroundModes and new push notification comes?

由 我们两清 提交于 2019-12-09 13:32:30
问题 I have an iOS7 app which registers for background mode remote-notification: <key>UIBackgroundModes</key> <array> <string>remote-notification</string> </array> It works fine before reboot and app gets this event while in background: -(void)application:(UIApplication *)application didReceiveRemoteNotification:(NSDictionary *)userInfo fetchCompletionHandler:(void (^)(UIBackgroundFetchResult))completionHandler But it looks like after reboot I don't get this event anymore until I start application

wcf certificate Keyset does not exist problem after reboot

由 孤人 提交于 2019-12-07 18:56:58
问题 There are two projects in one VS solution: client(wpf app) and а wcf service lib. I'm using Message security and a custom AspNetMembershipPrivider on th server side to validate username and pass. As i'm not using Windows security, I had to use certificate on server to establish secure chanell, and what i did: - opened my local IIS manager and added self-signed certificate named likemy dev machine. - checked that this certificate appeared in Certificates snap-in under Personal-Certificates -

Shortcut intent extras lost after restart?

由 早过忘川 提交于 2019-12-07 15:57:35
问题 My application listens to the android.intent.action.CREATE_SHORTCUT broadcast, in my code I am creating a shortcut which includes a String extra like this: Intent shortcutIntent = new Intent(Intent.ACTION_VIEW); shortcutIntent.setClassName("com.some.name","com.some.name.Activity"); shortcutIntent.putExtra("stringid", "some string value"); ShortcutIconResource iconResource = Intent.ShortcutIconResource.fromContext(ShortcutActivity.this,iconIdentifier); Intent intent = new Intent(); intent

Start intent after Reboot

由 ∥☆過路亽．° 提交于 2019-12-06 16:53:50
I have a GPS Service that gets GPS position every 60 seconds. It's working okay, but it doesn't do anything after phone reboot. I tried adding this in a BroadcastReceiver that is working after reboot but nothing happens. Any help would be great; I just need to load my Intents after reboot. //Start intents after reboot if (intent.getAction().equals("android.intent.action.BOOT_COMPLETED")) { context.startService(new Intent(context, DashboardActivity.class)); } GPSActivity.java public int onStartCommand(Intent intent, int flags, int startId) { //Toast.makeText(getBaseContext(), "Service Started",
订阅 reboot