I have a number of SD-cards, with Windows IoT Core installed, which has been running in Raspberry Pi 3b for a time, sometimes weeks and sometimes months. They all have some kind of boot issue. Some wont boot at all, I can't even reach the Windows Debug Portal, so I assume that the installation of Windows IoT Core are totally broken. Some boot fine most of the time and sometimes fails with an error which reboots after a couple of seconds and often times manage to boot properly.
I have tried to follow this guide: https://learn.microsoft.com/en-us/windows/iot-core/manage-your-device/windowsdebugger#raspberry-pi-2-or-3-rpi2-or-rpi3 but when I try to run:
bcdedit /store c:\EFIESP\EFI\Microsoft\Boot\BCD -debug on
I get: An error occurred while attempting to access the specified entry. The system cannot find the file specified..
Blue Screens are also pretty common, when they happen the system does not reboot as far as I have seen.
I know that the devices are fine and working, and the SD-cards also seems to be fine, no broken partitions or similar.
How do I find out what went wrong?
Related
Hoping this is the right place to ask this. I'm trying to learn React Native and I'm using Expo as my medium for deployment, but I'm finding that I'm literally getting 20 minutes at a time before my browser fails to connect with the error code ERR_CONNECTION_FAILED. I've tried the following:
netsh winsock reset, then the related ipconfig commands for flushing DNS settings
Clearing browser caches
Updating drivers
I'm at my wits end as the only thing that completely solves it is restarting my laptop, which for obvious reasons isn't feasible every 20 minutes, so I'm hoping somebody can help.
I'm experiencing the same issue with Expo in this environment:
Windows 10, version 1909 (OS build 18363.476)
using WSL (Windows Subsystem for Linux) with Ubuntu 18.04 LTS
These links were useful to learn why this is happening:
https://github.com/expo/expo-cli/issues/99
https://github.com/microsoft/WSL/issues/2913
https://github.com/microsoft/WSL/issues/3951
In essence, this issue seems to be due to a problem with WSL. Per a post in the first link, I tried the alternative to restarting the computer and it worked - it made the ERR_CONNECTION_FAILED problems disappear...for 20 minutes. That alternative is as follows:
WIN+R -> services.msc
Find LxssManager
Right-click -> Restart
This restarts the WSL service which also means that the WSL instance that was running gets terminated. This is less than ideal, but at least a computer restart is avoided. The third link says this WSL problem is fixed in Windows Insider Build 18890.
I am now considering spinning up a VM to run Ubuntu instead of trying to use WSL for Expo projects.
I uninstalled the latest Windows updates, and the problem has not surfaced since.
I've built an Electron app using the Squirrel packager/update manager.
I've had no issues in building the bundle, targeting Windows 64bits only.
I installed it on my Macbook pro (on a windows 7 x64 dual boot) without trouble. I tested it also on a 64 bit Surface pro 3 (Win 10), and another Win 7 PC. Everything works fine.
I published the app and got a few hundred downloads :half the people that downloaded it has it working, and for the other half it just won't start. The process spawns, then dies a second after. I tried starting it in admin, the admin dialog box won't even show. I tried running it from command line
myapp.exe > out.txt
But out is empty. How can I debug this ?
I was having trouble getting the logs for a production build as well.
My solution was to use electron-log to let the production app write logs to disk while debugging the problem.
You can then access the logs on windows at:
%USERPROFILE%\AppData\Roaming\<app name>\log.log.
Add some logs in your app that will give you insights in where the app crashes.
Don't forget to remove electron-log when you're done debugging and don't need to write any logs to disk any more.
I solved it for many users by building directly on a windows 10 fresh install.
The builds I used before were built on a windows 7. Not sure if it was that, I also have been cleaning the node modules a little bit, so maybe one of the modules I removed was the issue. Anyways, I still do not know of to debug the built exe in this kind of situation. There must be a way to get a log or something when the process kills itself
Part 1 - Description of the problem
I have the DK2 and I am working on a VR project. This project uses FirefoxNightly. I've downloaded it and installed the WebVR Enabler Add-On
Got this from http://mozvr.com/downloads/
I have also downloaded and installed the latest SDK and Runtime for Windows from https://developer.oculus.com/downloads/
I am also getting this on the Oculus Configuration Utility (while the oculus is plugged in):
However, I have gone on another computer with windows.. installed everything just like on this windows computer and it clearly shows the Oculus Rift connected properly but the head tracking still not working.
EDIT: I just tried connecting the oculus rift to this "second" pc ( dell laptop ) and now it doesn't even recognize the oculus rift. Still no head tracking.
EDIT 2: I tried installing everything on a third PC without success. I'm getting "service unavailable" on the Oculus Configuration Utility
My display mode is set as shown in the image.
Part 2 - Questions
What am I doing wrong? Is there a step I forgot to do? The weird thing is, I have the same project running on Mac without having any problems. Yes, on windows I can see the screen through the oculus rift but head detection is just not present.
Part 3 - list of possible fixes that did not work
This reddit post talks about the firewall issue however I tried the oculus rift with the firewall disactivated without success.
This reddit post talks about a possible fix by reinstalling everything and updating certain drivers.. however I have followed this fix step by step without success.
This oculus forum post talks about the issue and one person proposes a fix that worked for him/her. I followed the fix without success.
Part 4 - System info
If you require specific translations let me know. It is in French.
Part 5 - List of things I have tried that have been thought of
I have reinstalled everything. SDK (is not even needed in fact), runtime, firefoxnightly, webvr add-on multiple times
I have rebooted my computer multiple times
I have tried the different Rift Display Mode
Basic demos from mozvr.com and other webvr based projects work fine but head tracking does not work.
My Oculus is not broken (maybe for windows), it works fine for the Mac.
I've tried using different HDMI cables and Different minUSB-USB cables without success.
Part 6 - Quotes from the forum
First post
This sounds like the same issue a lot of us are having with the 0.5
and 0.6 versions. It's not something wrong with the cables, but with
the Runtime itself. Direct-mode works flawlessly and in Extended mode
the rift still displays a picture, altho without any tracking etc from
the runtime. Hoping it'll be fixed in the next update.
I've seen head tracking break in Firefox Nightly sometimes but I can usually solve it by restarting the browser once or twice, assuming that the hardware and Oculus side of things is working correctly.
Today, most games made for the Oculus Rift are based on specific versions of the Oculus Rift. I found this GUI desktop application that seems to solve most of those problems.
The idea is to install all Oculus Rift Runtime versions and then use the GUI to switch between each version.
The link above is to a reddit post that talks about how to install the application and the different runtimes.
You must install the runtimes from oldest to newest otherwise you'll run into some difficulties, like I unfortunately did. If I'm not mistaken runtime version 0.8 is very buggy and I never really got it to work.
Good luck.
This is what I did to get the Oculus DK2 working on my Windows 10 Laptop:
Create a windows restore point before you start this.
Download oculus_runtime_rev_1_sdk_0.4.4_win.exe from the Oculus downloads page.
Run the installer. Do not restart your computer when prompted.
Go to C:\Program Files (x86)\Oculus\Service folder, right click on OVRServer_x86.exe and go to properties.
In the compatibility tab, check Windows 8 mode, and Run As Administrator.
Run OVRServer_x86.exe
That's it.
The Good News
You should now be able to run direct to rift games. The HELIX rollercoaster app works well. So does the 6000 Moons demo. Most others do not. Depending on the game, you may need to go to your windows display settings, and fiddle with the screen resolution and rotation of the Oculus display.
The Bad News
Your computer may not restart. When I did the above, and later restarted, the computer hung on the windows loading page. I had to go into advanced start mode and load a system restore point. Definitely not the best user experience, but at least I got something working.
I have been developing a Windows phone app on my lunch breaks at work and spare time at home. The project is stored in my Dropbox so it's the same on both pcs. At work when I debug/deploy to the device everything is fine and dandy. At home however I get the following.
Error : DEP6100 : The following unexpected error occurred during boostrapping stage 'Connecting to the device':
SmartDeviceException - Deployment failed because no Windows Phone was detected. Make sure a phone is connected and powered on.
Error : DEP6200 : Boostrapping 'Device' failed. Device cannot be found. Deployment failed because no Windows Phone was detected. Make sure a phone is connected and powered on.
Now in both cases I'm using the same version of the SDK and of VS on the same Microsoft account on the same phone on the same project. But it doesn't work.
I have reinstall the SDK twice now to no avail.
When I run the device registration I get the following message.
Unable to connect to a phone. Make sure the Windows Phone IP over USB transport service is running
I'm not sure what I'm doing wrong here, has anyone run into this before? Any ideas of a fix for the issue?
Update:
I have uninstalled 2013 r4 and installed 2015. I have done a hard reset on my phone. I have run Windows Update and I'm up to date. I have tried making brand new projects as some of the posts suggest, to no avail. Same issue occurs, except now my emulators get:
The following unexpected error occurred during bootstrapping stage 'Connecting to the device '184901A8-DC44-4CED-869E-DC7733D048D6'
I'm guessing the next step is reinstalling Windows, I think I'll just wait till Windows 10 comes out.
Possible Fixes:
1.Try reconnecting your phone.
2. try re registering your phone as developer device
3. try this fix
https://dev.windowsphone.com/en-US/OEM/docs/Phone_Testing/Configuring_IP_over_USB
Testing apps on windows phones can be frustrating. One common problem I get is the need to reinstall drivers for the phone. I think this may be your problem.
The other problem similar to this I've encountered, was when registering for windows phone not using the correct version on that pc for 8.0 or 8.1.
Aside from this, there is a list with links provided that may help you. Let us know how you get on.
This link Problems and fixes when registering a Windows Phone 8 device to deploy/debug applications covers the major issues, some mentioned by Akash.
The following is a summary of the points discussed in the above link:
Windows Phone IP Over USB Transport(IpOverUsbSvc) service is running
Phone name is already in use by this account
Too many phones have already been registered with your account
Device lockscreen has to be unlocked (and it is unlocked)
Can’t find any devices
Point 5 is also addressed in this answer https://stackoverflow.com/a/30303946/3956566.
Update after comment
The other thing that you may need to do is:
1. make sure you have all your updates in Windows.
2. Make sure you have all VS updates.
3. reinstall VS.
4. Reinstall any .net framework packages for VS.
The first two are the most likely things.
If worse comes to worse, to reinstall windows.
I have needed to do all of the above at one time or another to fix various issues. Painful, yes.
And don't forget to reboot your machine.
Let me know if this works. There MUST be a solution.
I know what you mean about the phone appearing in explorer, update anyway, won't hurt to reinstall them.
I have had basic tests for meteor on a Windows7 PC.
But there the application crashed too often.
Before this, I tested meteor on PC running Windows8. There, crashes happened much less often and generally they were recovered when I shutdown and rebooted the meteor.
Is Meteor unstable on windows7?
Or is there any way to avoid this?
The version packaged to the MSI installer that can be found on win.meteor.com is not official. If you want a more stable, try the virtualized option I've described on the site. I've been using that for a month without issues.
Please could you be specific about what problems you are seeing, for example, what do you mean by 'crash'.
You can certainly raise issues on SO, but if they appear to be specific to the windows port, please raise a ticket at: https://github.com/sdarnell/meteor
The only difference between Win7 and Win8 meteor, is that the installer sets the Win7 compatibility mode for the node.exe executable on Windows 8.
There are also relatively few differences between the windows port of meteor and the official linux/mac release. So there is a possibility that the issue is either environmental (e.g. you have different things installed on the two machines), or it may even be a core issue that just happens to appear more often Win7 due to timing issues (there was a case of this in 0.6.3).