@JourneymanGeek It seems you are not here for now... please ping me when you come back. I have posted some more details in screenshots for now. It might be helpful if you can check them. Thanks :)
@AwalGarg Why is that bad? the 64 bit programs/OS use more memory, but even with 2GB I would select an 64 bit OS over a 32 bit OS. (If you had 512MB than things might be different)
I recently asked a question about a problem that I had, but this problem now automagically disappeared, without I have really done something. What should I do with the question now? Delete it, close it, self-answer it by saying that it disappeared without doing something or keep it as it is now?
@ProgramFOX Eh... it's pretty well-asked. Generally troubleshooting ones that "go away" should be closed, but this might actually be helpful. On the other hand, it's not really possible to answer (it'd be better off as a debugging blog post :P)
Would've been closed as too localised last year, but they got rid of that close reason :\
@ProgramFOX Incidentally, I believe networking drivers are the buggiest after graphics (@ÃŁŁǫǛȉЖΦΤїҪ) :P
I remember some weird combination of OpenVPN and VirtualBox and changing power state (sleep, hibernate, shut down) would cause a similar BSOD on my laptop
With my network card being mis-identified, then the tool for that SPECIFIC problem not working until I got fed up and left the system unplugged overnight?
I have an Asus P8Z77-V motherboard with a built in intel 82579V adaptor. For some odd reason its being detected as 82579LM. I'm running windows 8, and the system worked properly before. Its a known issue but the utility either crashes or tells me there's nothing to do. I've also tried the dos ve...
That answer would've been right, uhh... 15-20 years ago.
> .dll files are placed in the windows system32/syswow64 directory when installed, and they are common files for many applications
@ProgramFOX I just noticed you linked a bug report. You can self-answer with that. In fact, there's someone on the report page asking for a kernel dump and other information - it'd be great if you could provide those.
Some systems will have a light to show that power is available to it, but there's not way to verify by an indicator before the system is turned on that the hardware is A-OK
@jackopen No, there would be too much to test. That's why they have a POST system built in (Power On Self Test) before starting the OS, but that is only a quick check.
As well, every motherboard and CPU is different, so it'd be near impossible to tell if a single trace was destroyed or damaged, and have that same rule apply to every possible configuration
Hello, I am receiving the following error when trying to use mono:
[ERROR] FATAL UNHANDLED EXCEPTION: System.TypeInitializationException: An exception was thrown by the type initializer for System.Windows.Forms.XplatUI ---> System.ArgumentNullException: Could not open display (X-Server required. Check you DISPLAY environment variable)
I tried setting the $DISPLAY=:0.0 but that did not fix it.
@jackopen I know it's going to sound rude, please don't take it that way... Read the motherboard manual.
It's going to say how to put it in the case, where to screw it down, how to put in the CPU, memory, any cables or add in cards, better than me guessing
