I've got a VM (CentOS 6.5 guest) running under VMWare Player. Whenever I switch it on, the message "SRAT: Hotplug area too small" appears. Searching on Google didn't reveal any help, except that it's most likely related to the size of virtual RAM allocated for the machine. (3GB, but it's that much for a reason.)
What does the message mean?
How to get rid of it?
Could I run into problems by ignoring it?
Thanks,
Jochen
I changed the following option in my *.vmx file: mem.hotadd = "FALSE"
By default it is set to "TRUE". I've not seen any issues changing it...
Related
So recently I get this error "XHR failed" while trying to download extension and I already try a lot of things changing the setting but still it cant work. So I decided to try difference wifi (mySchool) and network(mobile data) and I'm shocked it's working fine. So, I guess the problem is on my own wifi. How to deal with it? I've been stuck for 2 days 🙂.
I use the latest VS CODE version on Windows 11.
I try a lot of things to fix it and been through github and stackoverflow too from `proxy setting,firewall,DNS,restart router,restart laptop also i tried everything in this question too and all but
"XHR failed"
keeps appear and as I said before without changing any setting but only changing wifi it works fine. So, I hope there's a solution on my wifi.
this is the error msgs on therminal:
enter image description here
Updates:
I'm running the same project at home and school.
I'm using the same laptop at home and school
By "mobile data", I mean hotspot from my cell service (vs. Wifi).
The projects ONLY works for wifi at school and from my hotspot.
It does NOT work from my home wifi.
It fails not only for remote explorer, but the other ones too.
I can't try to reload the extension that I want to download. The error always occurs, not only on Remote Explorer.
The other problem is "can't connect to discord via RPC: Error: could not connect"
Your problem is the same as discussed in this thread:
Visual Studio Code "Error while fetching extensions. XHR failed"
Unfortunately, there are several DIFFERENT possible root causes, and several different workarounds and solutions discussed in the thread.
You said you "tried several things". Please Update your post and specify exactly WHAT you tried, and the results.
You said it "works" on certain networks, but fails on your (home? school? other?) network (whether or not the network is "wifi" or not probably doesn't matter). Please clarify exactly "what's different" between the networks (to the best of your knowledge).
Please specify the platform you're running VSCode on (windows? MacOS? Linux? Other?)
Try this (one of the responses in the SO thread I cited above):
https://stackoverflow.com/a/71456820/421195
press f1
search "user setting"
click enter
search on user setting "proxy"
click enter
look for "use the proxy support for extensions."
change "override" to on
Q1: You're running the same version of VS Code, on Windows, using the same project, at home and at school, correct?
<= Q: Are you using the same PC (e.g. carrying a laptop from home to school), or are you using different PCs at home and at school?
Q2. By "Mobile data" (vs. "wifi"); you mean you "hotspot" for your cell phone service, correct?
Q3. The project ALWAYS works for Wifi (either at home or school), but NEVER works for your Hotspot, correct?
Q4. You're always trying to run the Remote Explorer extension in VS code when the error occurs (it never happens with other VSCode activities), correct?
<= Q: Any problems in other areas of VSCode (e.g. your compiler)?
Q5. The exact error message is The editor could not be opened due to an unexpected error: XHR failed, correct?
<= Q: Always using Remote Explorer, correct? What exactly are you doing in Remote Explorer?
BE SURE TO TRY ALL THE TROUBLESHOOTING TIPS HERE
(including verifying "ssh" from the VSCode command line, using your "bad" network):
https://code.visualstudio.com/docs/remote/ssh
I found the solution for my problems. it solved by using vpn.
the problem was my wifi provider probably blocking the request on vs code, seems like there's something fishy about the DNS policy. Hope this can help too
I don't know if this is allowed here but can someone help me why am I getting this random blue screen? It say's whea uncorrectable error but I don't know which part of my PC is faulty. I noticed the BSOD appears when there is a heavy task like when I am coding in VSCode (running npm install, etc). I will attach here the minidump if someone can read it. If you need more information about my PC, let me know. Please I really need your help. I want to use this PC for programming. Thanks!
Latest Minidump File
This usually happens due to the high temperature in your pc, driver related issues or corrupted hardware. I recommend you try stopping overclocking for some time (if it is) and check if the problem persists. If not, then I think there could be a problem with your hardware itself. Try replacing the motherboard.
Bounty Update
I am leaving the question essentially the same, but I just want to point out at the beginning here that I'm most interested in help trying to get the socket between flash (Adobe Animate) and the native debugger working again, as I believe that is the issue I'm having. Or is it a socket between flash and Windows?
Original Question
I've apparently turned something off? Even when I write really bad code (like trying to call a function that isn't there or divide an integer into a fraction), the flash player boots, shows a background color and stops there. No messages in the output window or compiler errors window. If I fix my code, it all runs fine, but for about 30 minutes (ever since I started trying to work with bitmaps for a sprite sheet) I get no runtime errors no matter what kind of mistake I type in my code. Anyone know how to turn it back on?
I've checked my actionscript settings and I have both warning mode and strict mode checked on.
Could it be a socket issue? I admit I have little to no experience working with sockets and only a surface understanding of what that even means. I've added the socket tag. If someone can see that this is clearly nothing to do with sockets, by all means, I'll remove the tag.
UPDATE: 6/22/16
I just reinstalled Adobe Animate CC 2015.2 and no change. I'll try compiling it in flash builder when I get a chance to help pigeon hole the problem. (Edit 6/24: flash builder worked! But my trial version expired the next day so is no longer a viable option).
And I just tried something in the command prompt in Windows 10 as an administrator:
netsh winsock reset catalog
netsh int ip reset reset.log hit
which I found another user on flashdevelop.org used to fix a similar issue, but no change.
And I just tried debugging in Flash Builder. It worked fine (debugger caught bugs) but my trial version expired the next day.
update 6/24
I've tried launching debugger for AIR from within the Adobe Animate CC IDE and it works fine if there are no bugs; it fails to do anything visible (no Iphone emulator, no swf window) if I put a typo or error in the code.
I also just deleted winsock and winsock2, rebooted Windows, then reinstalled winsock and winsock2. No change.
update 6/25
Just tried a system restore in Windows to set all my files and settings and drivers etc. to the way it was a week and a half ago... Also completely uninstalled all Adobe products and reinstalled. No change. I can only imagine that wiping my hard drive and reinstalling Windows would do the trick, but come on, it hasn't come to that has it?
As VC.One suggested, I checked the compile error window (cannot believe I didn't check before! Maybe when I checked before there were no compile errors... Only runtime errors?) and the errors are showing up there. Does this mean that it's catching compile errors but just not runtime errors?
When you force/test a runtime error... make sure you check
Compiler Errors (ALT+F2) and also Output (F2). By Output I mean the window that shows traces (and runtime issues). One of those two should have some feedback for you.
A possible solution is to save a new Workspace. So with those windows for Compiler Errors and Output both open (or tabbed, I tab them next to my Timeline) go to Window (in top options like File/Edit/Debug etc) and choose Workspace, then into that you choose New Workspace. Give it a name in the pop-up and okay everything.
Flash should always load that current workspace (next time, go to Workspace option again, check that your specified workspace [by name] has a tick next to it...).
Possible pitfalls:
1 - Use the debug player
2 - Make sure there isn't somewhere a try/catch enclosing the portion of code that triggers the event that may lead to an error
3 - Socket issue: may be exported in debug mode but swf cannot connect to debugger (it waits in a blank state for 60 seconds I guess)
4 - Does it compile ok? If there are compilation errors you may get an SWF anyway but then it will not start
...
I seem to have a problem for one the servers that i am handling, i have reinstalled CentOS for nth times, and formated everything, edited the grub.conf time out = 0, but all still the same, the grub timer wont move, always stuck.
Did you end up finding a solution to this? I just had a server with this exact issue right after a fresh install of CentOS 6.x. Even though the system seemed to be keeping correct time, replacing the CMOS battery resolved the issue for me. This was either due to a faulty battery, or the CMOS settings getting reset when I replaced the battery.
Here are the sites that led me to that solution:
https://serverfault.com/questions/42877/grub-hangs-after-x-2-seconds
http://www.tomshardware.com/answers/id-1809044/centos-grub-countdown-stops.html
A user on one of those sites said that clearing the "System Event Log" fixed the issue for them. Here are some guides on accessing and clearing the SEL/BMC log:
http://download.intel.com/support/motherboards/server/s7000fc4ur/sb/sel_viewer_ug_e1246101.pdf
http://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-59226
The issue could also be related to Grub's recordfail logic. More info here:
https://askubuntu.com/questions/202309/cannot-get-grub-menu-to-timeout-or-go-away?newreg=dc178d813fbb4f0d803644799bb89c5e
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/872244
Try adding this to /etc/default/grub
GRUB_TIMEOUT=10
GRUB_RECORDFAIL_TIMEOUT=$GRUB_TIMEOUT
Then run sudo update-grub
Support for GRUB_RECORDFAIL_TIMEOUT was added in the middle of the 12.04 cycle, starting from version 1.99-21ubuntu3.3
Check the date/time setup of your server. After I changed the CMOS battery, server's (HP Proliant) clock was 4 days behind and had same issue, the problem was fixed after setting it up correctly.
Because my work will get lighter for the next month or so, I decided to mess around with OS's, just to see how they work. I found this website, and I'm trying to run the code he provided. I am following the instructions exactly (to the best of my ability), but when I go to try booting with QEMU, I get this text:
SeaBios (version-blahblah)
Booting from Hard Disk...
Boot failed: could not read the boot disk.
Booting from Floppy...
And it never actually boots. I am relatively new to Ubuntu, and hoping that somebody would be able to point me towards where I made a mistake. I hope this is enough information to diagnose my error, and thanks in advance!
EDIT: Alright, I tried another tutorial which took me through very similar steps (but with slightly different code), and I still had the same issue. I also booted MikeOS from the floppy image it comes with, and it worked fine.
EDIT 2: Aaaaah! I just realized that when I pressed Ctrl+C, the text that was supposed to appear appeared for just a moment, then went away, along with QEMU. What can I do to make the text appear sooner? I've tried moving the infinite loop to after the display command, but to no avail.
I want to start by saying that I didn't read the entire page you provided (as I don't have enough time). However, the error that you cannot boot from HDD, regardless of the OS, usually (always in my previous experiences) means that either the MBA (Master Boot Record) is messed up/incorrect or you don't have a partition with a boot flag on it.
When I have some time I'll look deeper into that page and see if i can find exactly what the problem could be.
Do you have the bytes 0x55, 0xAA at offset 510 of your MBR?