I have been doing my development work on a Dell running Windows 8. I switched over to Windows 10 with Parallels on a 2013 MacBook Pro 2.8 GHz 16 GB RAM. Everything is super snappy. However, when I run my project without debugging, updates are very slow. I have this exact same project running on my Dell, and I don't have the problem. Parallels is running everything super fast.
For example, I change something in my html, and when I reload, it says waiting on localhost and that first get request takes about 30 seconds before loading the page. This happens after changing a single title in my view. I have been working on this problem for about a day and have tried many things.
What I've Tried
Reinstalling IIS and Deleting IIS folder in Documents
Changing my host file at \Windows\System32\drivers\etc\hosts "127.0.0.1 localhost"
Disabled IPv6
Restarting both Virtual Machine and Mac numerous times
De-enabling Browser Link
List item
Turning off Windows Defender and Firewalls
I have tried many other things, but that is what I can remember. I'm hoping someone has similar experience or can point me in the right direction.
*Side note - this project is a small-medium size web app that includes dev express controls. I did run a basic mvc project that is just a website, and it refreshed within a couple seconds when I changed the view.
Related
I have written a JavaFX app running on Windows 10 machine in the office which has problems showing (painting/rendering) certain embedded controls such as a Pane with PdfBox when I connect to it with Remote Desktop for Mac. It shows only a black screen in the app instead of the pdf document.
When I connect using RDP from my Windows 10 machine at home to my Windows 10 machine at work, the app works just fine (the pdf is shown in the app).
I have the same problems using AnyDesk and Teamviewer.
The app only shows PDFs properly using a connection from Windows 10 to Windows 10 with Microsoft RDP.
It might be a JavaFX issue. Similar issues are described here (although not 100% identical):
https://bugs.openjdk.java.net/browse/JDK-8239589
https://bugs.openjdk.java.net/browse/JDK-8229394
However, since I guess Microsoft Remote Desktop for Mac is using the same technology as the Windows Desktop client, I would have expected it to work fine.
I have a Mac Mini M1 running the latest OS (Monterey) at the time of writing this post. I am also using the latest Remote Desktop client for Mac.
This problem is not new and was also present in older releases.
I have tried to play around with screen resolutions, both on Host and Client but nothing good came out of those tests.
Disabled also hardware acceleration in Remote Desktop for Mac preferences but it didn't change anything.
The machine at the office has the following specs (which I cannot change nor update)
Edizione Windows 10 Pro
Versione 20H2
Data installazione: 10/09/2021
Build sistema operativo 19042.1415
Esperienza Windows Feature Experience Pack 120.2212.3920.0
Anyone else who has seen this problem and perhaps resolved it?
Could it be a bug in either PdfBox or Remote Desktop for Mac?
Except for the above issue, the Remote Desktop Client for Mac is working great (not lagging as TeamViewer or AnyDesk) and the user experience is phenomenal.
PS: While this might be considered a programming question (since I wrote the app with JavaFX) but it might be better to post on another forum? If yes, which one? On the other hand, many similar posts (look at the suggested thread on the right) have been upvoted despite not dealing with programming issues.
Thanks.
How do you use PDFBox? I ask because this is not a JavaFX component. If you use a SwingNode for that it might be interesting to try one of my two PDFViewer demos here and see whether the problem persists.
https://github.com/mipastgt/JFXToolsAndDemos#awtimage
The difference is in how I do the rendering and maybe that makes a difference for your use-case too. But of course this is just a wild guess and I can't promise anything.
This may already have a question somewhere, but I am at a loss as to how to debug IE11 on my Mac.
I currently run a full Win10 instance in a Virtual Box, but it is so bloated that it is nearly impossible to move nimbly between coding and debugging. IE dev-tools are also inaccessible using this method because it just cripples the VM, so I am flying blind with coding.
I have looked up tutorials as to how to run IE on a Mac direct using Wine/Remote Desktop, but these instructions are out of date or the supporting software does not work as intended. Also, Microsoft (being the evil empire that they are) discontinued support for debugging with Azure so that is another option off the table.
If there is anything that actually works without having to shell out $$$ please let me know as it is so painful currently to debug the worst browser that will never die.
From your description, I can see that you had already try to use the Windows 10 VM but it get hangs.
You can try to go to Windows Features on or off inside Control Panel-> Programs-> Programs and Features and try to turn off the features that you are not using may help to reduce the load.
It is possible that you are running your VM in a very less memory that downs the performance of the OS.
If possible for you than try to install a VM with some more memory.
Otherwise you can try to install Windows 7 in your VM and upgrade to IE 11 in that.
It can help you to solve your issue with the OS and you can debug the code on IE 11.
Below are some helpful references that may give you some additional information.
How to test your website with Internet Explorer on a Mac
How to Debug in IE on a Mac
When using my virtual machine, I'm trying to gain access to the Internet, but unable to get IE to start, when clicking the icon it doesn't react. I've done some research and a couple of hours troubleshooting, but no luck. It does appear to be a problem for some, but they don't have the exact same problem I do.
Here's what I've come across while troubleshooting:
1) OS is windows 8.1 32-bit, but my host machine is 64-bit, because of this there might be compatibility issues. Not much more on this though, no explanation on whether that is the problem at all.
2) My network settings could be wrong, but I'm attached to a bridged adapter, my IP's match for both VM and Host, and I can access the web when I use a web browser app (but the app that can't download anything, so I can't download google chrome or the necessary files I need to study).
3) Others say that the problem is Windows 8.1 itself. That VMs just don't work as they should like Windows 7.
I clicked to uninstall Windows explorer, but it seems it doesn't exist, and it doesn't have an icon on the home screen.
Could it be that the .iso I downloaded did not have IE included?
The original need for the VM was to test Docker containerisation for a report. Should I scrap the whole idea and try for Windows 7 64-bit instead? That's all I can do if I can't find a solution.
Any help would be appreciated. Thanks.
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.