NESICIDE = DLL HELL!

[8bitMicroGuy]

When I installed NESICIDE's dependencies and then NESICIDE, I got errors about DLLs.
First missing DLL was sdl.dll. I got it from a DLL downloading website.
Then I was bothered by mingwm10.dll, libgcc_s_dw2-1.dll, QtCore4.dll, QtGui4.dll.

Now as I got the DLLs, I got this big error:
"The procedure entry point _Z21qRegisterResourceDataiPKhS0_S0_ could not be located in the dynamic link library QtCore4.dll".
I've been trying to solve this by using different DLLs, but they'd give another error about another procedure entry point (I'm not going to search which DLL caused that because this is a pain in the!).

So which DLLs am I supposed to download?
Can someone upload working DLLs from NESICIDE for me to Dropbox? (Please please please please don't use the upload services with virusy ads and offers or sites that will give me a blank screen or say "I am error")

[rainwarrior]

Don't get DLLs from a DLL website. There are muliple versions of all DLLs (this is actually the point of having DLLs). There is no way to insure getting the correct one from such a site.

To get the correct versions of DLLs for NESICIDE, ask the author. The lack of included DLLs is something that needs to be solved by the person who made the software, not something you should attempt to cobble together on your own with incomplete information about what you need. Omission of needed DLLs from the NESICIDE package would have been a mistake and needs to be corrected by its author.

[lidnariq]

Right there on the nesicide download page:

"nesicide-dependencies-win32.msi
Qt libraries, SDL, QScintilla, and various other dependencies required for NESICIDE."

No-one to blame but yourself.

[8bitMicroGuy]

Right there on the nesicide download page:

"nesicide-dependencies-win32.msi
Qt libraries, SDL, QScintilla, and various other dependencies required for NESICIDE."

No-one to blame but yourself.

*facepalm* I already have installed this, don't you see?!

[8bitMicroGuy]

Update. I fixed it. What I did wrong is that I installed the dependencies BEFORE the main installation.
Then I removed the bad dlls and reinstalled everything and now it works

Please excuse me for the inconvenience.

P.S. During the second installation (repair) of the dependencies, I realized I hadn't installed them, but only downloaded them My bad... How embarrassing XD

[cpow]

Update. I fixed it. What I did wrong is that I installed the dependencies BEFORE the main installation.
Then I removed the bad dlls and reinstalled everything and now it works

Please excuse me for the inconvenience.

P.S. During the second installation (repair) of the dependencies, I realized I hadn't installed them, but only downloaded them My bad... How embarrassing XD

I just saw this thread and that was going to be my answer. I have updated the descriptions on the download page.

[tepples]

Is there a way you could have the installer automatically download and install the dependencies?

[cpow]

Is there a way you could have the installer automatically download and install the dependencies?

The only reason it's two packages is because it's too big as one package for my google site. I wonder if the same restriction applies to google drive?

I'd rather just put the whole bloody thing up in one package...but I haven't the time to be a website maintainer -- otherwise I'd have put it up on nesicide.com directly.

[tepples]

My idea was not that your main NESICIDE installer would bundle the dependencies. Instead, it would use the HTTP client in Windows to download the secondary installer for the dependencies from the Internet, run that installer, and then continue. It's like how the Java installer downloads the Ask toolbar, except not evil.

[tokumaru]

Is there a way you could have the installer automatically download and install the dependencies?

I hate when installers do that. Actually, I hate installers. Portable FTW.

[cpow]

Is there a way you could have the installer automatically download and install the dependencies?

I hate when installers do that. Actually, I hate installers. Portable FTW.

It is actually a "portable installation". It can be installed to a thumb drive and run from there completely.

[tokumaru]

It is actually a "portable installation".

These I hate less.

Just kidding, these are OK, the only problem is that you can't always tell it's a "portable installation" just from looking at the EXE.

[cpow]

It is actually a "portable installation".

These I hate less.

Just kidding, these are OK, the only problem is that you can't always tell it's a "portable installation" just from looking at the EXE.

I know. 50 shades of suckage. At one point I had named it nesicide-portable.msi or similar but that was when I had two separate installs. Since the only *difference* is where *you* choose to install it to, this became less...useful.

[Pokun]

Then it would be good if it says it's a self-extractable archive type of installer somewhere. I also hate non-portable installers BTW.

[cpow]

Then it would be good if it says it's a self-extractable archive type of installer somewhere. I also hate non-portable installers BTW.

That is not what it is, so it does not say that. It is an MSI, which is clearly indicated by extension. But it installs wherever you tell it to install to. If you tell it to install to F:, it'll put everything on F:. That is what *I* mean by "portable install". Ie. "I've installed this on something that I can put in my pocket..."

I'm not sure I understand all this "I hate non-portable installers..." An installer's an installer. If you don't want the software installed, don't install it. Hate something else...something worth hating...?