SNESLink
New member
This morning I decided to bite the bullet and attempt to get NESmaker up and running on my laptop. One small snag: I run Kubuntu on my laptop. Kubuntu is not Windows, and as of the day I'm writing this post - NESmaker is a Windows-only application.
I am attempting to get NESmaker up and running through Wine, and I hope to keep this thread updated with my progress. So far, there's already been a huge leap made: the application launches and I can register my access code. Details below.
First, I'll point out that I don't run a beefy laptop. I have a 15" Dell Inspiron from around 2015. It has a quad core Intel i5-5200U CPU that clocks in at 2.2GHz, I've updated the storage to an SSD and the RAM to 16GB, but with only integrated graphics, I'm not really going to be knocking anyone's socks off. All of this is just to let you know that if I can get this to run, hopefully you can too.
I'm currently running Kubuntu 18.04 (an Ubuntu flavor preloaded with KDE and Plasma) and Wine 3.13.
When I first downloaded NESmaker 4.0.0, I could get it to launch in Wine but the moment I attempted to register my activation code: the application would crash. I would get an error in my command line claiming that DNA.dll could not be found. While doing research on this forum to find out if anyone else had been attempting the same thing as me: I found this post http://nesmakers.com/viewtopic.php?f=22&t=542#p3398. In there I found a replacement DNA.dll and a new EXE – NESmaker 4.0.1. Upon changing these files I was able to both launch and register my application.
I haven’t done a ton of testing yet, but I can save the default project as a new project.
However, I can’t create a new project or load the project I saved.
Here is the console error I get when I attempt to load my existing project:
I don't know a ton about what I'm looking at here, but I have a few ideas that I could try. The application loads at least, and that is certainly a major step forward.
I’ll keep testing as patches for the editor come out, and update if I make any breakthroughs.
I am attempting to get NESmaker up and running through Wine, and I hope to keep this thread updated with my progress. So far, there's already been a huge leap made: the application launches and I can register my access code. Details below.
First, I'll point out that I don't run a beefy laptop. I have a 15" Dell Inspiron from around 2015. It has a quad core Intel i5-5200U CPU that clocks in at 2.2GHz, I've updated the storage to an SSD and the RAM to 16GB, but with only integrated graphics, I'm not really going to be knocking anyone's socks off. All of this is just to let you know that if I can get this to run, hopefully you can too.
I'm currently running Kubuntu 18.04 (an Ubuntu flavor preloaded with KDE and Plasma) and Wine 3.13.
When I first downloaded NESmaker 4.0.0, I could get it to launch in Wine but the moment I attempted to register my activation code: the application would crash. I would get an error in my command line claiming that DNA.dll could not be found. While doing research on this forum to find out if anyone else had been attempting the same thing as me: I found this post http://nesmakers.com/viewtopic.php?f=22&t=542#p3398. In there I found a replacement DNA.dll and a new EXE – NESmaker 4.0.1. Upon changing these files I was able to both launch and register my application.
I haven’t done a ton of testing yet, but I can save the default project as a new project.
However, I can’t create a new project or load the project I saved.
Here is the console error I get when I attempt to load my existing project:
Code:
0009:fixme:wincodecs:JpegDecoder_Frame_CopyPalette (0x16aa54,0x164c30): stub
0009:err:gdi:alloc_gdi_handle out of GDI object handles, expect a crash
0009:err:gdi:alloc_gdi_handle out of GDI object handles, expect a crash
0009:err:gdi:alloc_gdi_handle out of GDI object handles, expect a crash
0009:err:gdi:alloc_gdi_handle out of GDI object handles, expect a crash
0009:err:gdi:alloc_gdi_handle out of GDI object handles, expect a crash
0009:err:gdi:alloc_gdi_handle out of GDI object handles, expect a crash
0009:err:gdi:alloc_gdi_handle out of GDI object handles, expect a crash
0009:err:gdi:alloc_gdi_handle out of GDI object handles, expect a crash
0009:err:gdi:alloc_gdi_handle out of GDI object handles, expect a crash
0009:err:gdi:alloc_gdi_handle out of GDI object handles, expect a crash
System.Exception: Generic Error [GDI+ status: GenericError]
at System.Drawing.GDIPlus.CheckStatus (System.Drawing.Status status) [0x00079] in <3110e6dfe53a465e917aa087708d1bb4>:0
at System.Drawing.Graphics.GetHdc () [0x00011] in <3110e6dfe53a465e917aa087708d1bb4>:0
at System.Windows.Forms.TextRenderer.MeasureTextInternal (System.Drawing.IDeviceContext dc, System.String text, System.Drawing.Font font, System.Drawing.Size proposedSize, System.Windows.Forms.TextFormatFlags flags, System.Boolean useMeasureString) [0x0001b] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0
at System.Windows.Forms.TextRenderer.MeasureText (System.String text, System.Drawing.Font font, System.Drawing.Size proposedSize, System.Windows.Forms.TextFormatFlags flags) [0x00005] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0
at System.Windows.Forms.MessageBox+MessageBoxForm.InitFormsSize () [0x0008f] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0
at System.Windows.Forms.MessageBox+MessageBoxForm.RunDialog () [0x0000f] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0
at (wrapper remoting-invoke-with-check) System.Windows.Forms.MessageBox+MessageBoxForm:RunDialog ()
at System.Windows.Forms.MessageBox.Show (System.String text) [0x0000e] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0
at MysticSearchesTool.MysticSearchToolMainDialog.loadToolStripMenuItem_Click (System.Object sender, System.EventArgs e) [0x001c0] in <eaca8c4272e2475e9ca34d414e26611f>:0
at System.Windows.Forms.ToolStripItem.OnClick (System.EventArgs e) [0x00019] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0
at System.Windows.Forms.ToolStripMenuItem.OnClick (System.EventArgs e) [0x00090] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0
at System.Windows.Forms.ToolStripMenuItem.HandleClick (System.Int32 mouse_clicks, System.EventArgs e) [0x00000] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0
at System.Windows.Forms.ToolStripItem.FireEvent (System.EventArgs e, System.Windows.Forms.ToolStripItemEventType met) [0x00054] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0
at (wrapper remoting-invoke-with-check) System.Windows.Forms.ToolStripItem:FireEvent (System.EventArgs,System.Windows.Forms.ToolStripItemEventType)
at System.Windows.Forms.ToolStrip.OnMouseUp (System.Windows.Forms.MouseEventArgs mea) [0x00048] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0
at System.Windows.Forms.ToolStripDropDown.OnMouseUp (System.Windows.Forms.MouseEventArgs mea) [0x00000] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0
at System.Windows.Forms.Control.WmLButtonUp (System.Windows.Forms.Message& m) [0x00078] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0
at System.Windows.Forms.Control.WndProc (System.Windows.Forms.Message& m) [0x001b4] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0
at System.Windows.Forms.ScrollableControl.WndProc (System.Windows.Forms.Message& m) [0x00000] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0
at System.Windows.Forms.ToolStrip.WndProc (System.Windows.Forms.Message& m) [0x00000] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0
at System.Windows.Forms.ToolStripDropDown.WndProc (System.Windows.Forms.Message& m) [0x00017] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0
at System.Windows.Forms.Control+ControlWindowTarget.OnMessage (System.Windows.Forms.Message& m) [0x00000] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0
at System.Windows.Forms.Control+ControlNativeWindow.WndProc (System.Windows.Forms.Message& m) [0x0000b] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0
at System.Windows.Forms.NativeWindow.WndProc (System.IntPtr hWnd, System.Windows.Forms.Msg msg, System.IntPtr wParam, System.IntPtr lParam) [0x00085] in <dfcf5e19b3744f6abc3507fe9dffa1dd>:0
I don't know a ton about what I'm looking at here, but I have a few ideas that I could try. The application loads at least, and that is certainly a major step forward.
I’ll keep testing as patches for the editor come out, and update if I make any breakthroughs.