I've built a small application with shoes, running it on my Win 10 64 bit Laptop is not a problem at all, everything works fine. I tried to install shoes at my station (Win 10, 64 bit too), installation process is not a problem, command-line based stuff with the cshoes.exe (for example installing gems) works without any problem, but I cant start the shoes.exe at all, it appears in the task-manager, but there is no Gui and no Icon shown in the taskbar. When I try to start applications written with Shoes there is an empty windows popping up, but its just frozen and crashes as soon as its open. It is not a bundled app but a simple .rb file that I want to run with the installed shoes.exe. I tried it with compability mode for the shoes.exe, tried compability with win7 and win XP but it won't work. Did anyone experience this before and is there a solution for this?
Greetings, rtuz2th
Related
I've looked for someone with my same problem but it seems nobody had this drawback with Code::blocks. I've installed the 20.03 version and after the installation it works fine, also if i close and reopen C::B it works fine but if i restart my pc, then it won't open anymore. It stucks at the splash screen with the C::B title and version and nothing else appens. In the task manager i see that it use only 15.000/24.000kb of ram (over 70.000 when it works), I'm using windows 7-64 bit.
It's a problem if i have installed it in the secondary hdd? MinGW is in the same hdd.
I'm here for any other axplanation, thank you guys
I have a dell inspiron 5559 and i used to have a dual boot windows 10 and ubuntu 16.0.4.
After an update of windows 10 i got many problems like my graphic card driver didnt get auto-update and my cpu fan got some problem
After changing my fan windows would enter an automatic repair and before even starting it... it would jump into blue screen and enter a restart loop while my linux would work just fine
I tried installing or repairing windows but before the page for chosing language blue screen apears again and system jumps out of installation
I started a system diagnose and ram memmory test but there wasnt any error.
So i thought maybe its grub menu or linux's problem and i used rm rf root in ubuntu (that was a foolish mistake im really sad about this now) after that still i cant install or repair windows. and when i turn on my pc an error apears
//
Error: file '/boot/grub/i386-pc/normal.mod' not found.
Entering rescue mod...
Grub rescue>
//
I tried different windows dvd's for installation all had same problem. And i tried installing or trying ubuntu or kali live using an usb but various errors show up like bootmgr is missing or....
Can anyone help?
Sorry if my text had some english problems :)))
May be formatting the entire hard drive then install Windows or Ubuntu would work for you.
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
I am working on a Python project which uses wxPython and it works fine with python2.7 on windows 7, 32 bit. Now I am trying to install this project in Mac which has a Python 2.7.5, 64 bit. I installed WxPython Cocoa3.0 which is for 64 bit. The application crashes when I work on certain cases whereas it works fine for the rest. I have pasted the error which I got in the following link. Please help me with this problem.
https://raw.githubusercontent.com/lrajmohan/PyView/master/ExpSuite%20-%20Copy/ExpSuite/TMP/Error_mac
It's hard to exactly diagnose your problem without the code, but I've seen this issue before. A possible and well explained answer is here.
I had a similar problem recently, an application running on a 32-bit Mac moved to 64-bit and wx3.0 crashed out on certain mouse clicks (but not all). I fixed this with a CallAfter:
def OnClickEdit(self, event):
"""Edit clicked, show menu."""
def onclickedit():
menu = wx.Menu()
...
self.PopupMenu(menu)
menu.Destroy()
wx.CallAfter(onclickedit)
I'am learning some Gamedevelopment using Monogame.
I started a Windows OpenGL Project and everything works fine on my Win8 machine.
I have compiled the project and sent it to 2 People, both are using win7 x64 and one of them can't open the Game.
After that, I tested it on my other computer (also win7 x64) and I get the same problem, the game process starts, then the screen flashes (Aero seems to deactivate), then everything gets back to normal and the process of my game crashes without a message.
I'm sure, that there is no problem with my code, maybe some missing dlls but most of them are copied with the game
Lidgren.Network.dll
MonoGame.Framework.dll
OpenTK.dll
SDL.dll
Tao.Sdl.dll
Sincerely
CarnVanBeck
If it's taking down Windows Aero, it might be a graphics issue. Compare the graphical capability of the Win7 machine that can run it with the one(s) that can't. Does the working one have a graphics card? I seem to remember Monogame having odd behaviour with the Reach graphics profile.
Ok I fixed it using an OpenAL32 installer
I found the solution here
You have to install it, if your game doesn't work.
fixed it for me on my second computer.