Unable to launch 64-bit delab on Win 7 machine

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Downloaded and installed 64-bit delab on Win 7 machine
2. Attempted to launch and no response
3.

What is the expected output? What do you see instead?
Program launch

What version of the product are you using? On what operating system?
The latest, but the same thing happened on the prior version.  I loaded it to a 
64-bit machine, Windows 7.

Please provide any additional information below.
It works on my 32-bit windows machine.

Original issue reported on code.google.com by sbre...@gmail.com on 3 Apr 2012 at 9:21

[GoogleCodeExporter]

I should have mentioned that I tried to reinstall more than once, and had the 
same problem.

Original comment by sbre...@gmail.com on 3 Apr 2012 at 9:21

[GoogleCodeExporter]

Can you provide some details on where you installed it? Did you choose the 
default location?

Can you try the following?

Copy the whole delaboratory directory to your local Users folders. Open a 
commandline and then cd over to the delaboratory directory in your Users folder 
and start delaboratory from there. Now, let us know what is the error message.

Thanks,
Partha

Original comment by parth...@gmail.com on 4 Apr 2012 at 10:59

[GoogleCodeExporter]

Thank you.

It was in the Programs directory.

I copied the folder from the Programs directory to my local user account 
(C:\Users\Owner) and cd'd over to the Delaboratory path 
(C:\Users\Owner\Delaboratory).  What should I put at the prompt to run it?  
I've typed in Delaboratory and Delaboratory.exe, but I do not get any response.

Thanks.

Steve

Original comment by sbre...@gmail.com on 4 Apr 2012 at 12:52

[GoogleCodeExporter]

first tell me what's in the directory. Type
dir in that directory. 

And yes, you would type delaboratory.exe at the commandline.

Original comment by parth...@gmail.com on 4 Apr 2012 at 10:33

[GoogleCodeExporter]

C:\Users\Owner\Delaboratory>dir
 Volume in drive C is Gateway
 Volume Serial Number is CA23-64C0

 Directory of C:\Users\Owner\Delaboratory

04/04/2012  08:48 AM    <DIR>          .
04/04/2012  08:48 AM    <DIR>          ..
03/17/2012  11:42 PM           453,468 dcraw.exe
04/02/2012  08:36 PM           102,543 delab-uninst.exe
03/24/2012  06:03 PM        12,288,628 delaboratory-with-logs.exe
03/24/2012  06:03 PM         7,023,616 delaboratory.exe
04/02/2012  08:36 PM                64 Delaboratory.url
01/24/2012  09:40 PM            77,312 libgcc_s_sjlj-1.dll
03/25/2012  08:57 AM           280,614 libjasper-1.dll
01/24/2012  09:40 PM           200,192 libjpeg-8.dll
03/25/2012  09:01 AM           388,444 liblcms-1.dll
01/24/2012  09:40 PM           164,352 libpng15-15.dll
01/24/2012  09:40 PM           980,480 libstdc++-6.dll
01/24/2012  09:41 PM           363,008 libtiff-3.dll
01/24/2012  09:41 PM         1,657,875 libxml2-2.dll
01/24/2012  09:41 PM            87,571 zlib1.dll
              14 File(s)     24,068,167 bytes
               2 Dir(s)  1,121,637,199,872 bytes free

C:\Users\Owner\Delaboratory>

Original comment by sbre...@gmail.com on 4 Apr 2012 at 11:53

[GoogleCodeExporter]

This looks right. 

So when you type delaboratory.exe at the command line, you get no response at 
all? What happens when you type delaboratory-with-logs.exe? Do you get a log 
file create in this directory?

BTW, Are you up to date on all Windows 7 64-bit service packs?

Original comment by parth...@gmail.com on 5 Apr 2012 at 10:37

[GoogleCodeExporter]

I am up to date with the service packs.

I get no response at all when I type in delaboratory.exe.

When I get home tonight, I will give the alternative command and will let you 
know.  

Thank you.

Original comment by sbre...@gmail.com on 5 Apr 2012 at 2:57

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

By "no response" do you mean that application just quits and you are back in 
command line, or do you mean that application hangs and you are not able to 
enter another command? If application quits for some reason then - as Partha 
wrote - you should be able to run delaboratory-with-logs and file debug.log 
should appear with some logs.

Original comment by jacekpop...@gmail.com on 5 Apr 2012 at 3:50

[GoogleCodeExporter]

I will check when I am back at home, but I believe I am just back in the 
command line, as if nothing happened.  I remember entering the command, nothing 
happened, entering again, so I believe it was not hanging.

Thanks

Original comment by sbre...@gmail.com on 5 Apr 2012 at 7:03

[GoogleCodeExporter]

I tried both ways, and no dice:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Owner>cd delaboratory

C:\Users\Owner\Delaboratory>delaboratory.exe

C:\Users\Owner\Delaboratory>delaboratory-with-logs.exe

C:\Users\Owner\Delaboratory>

It does not hang.  There was no response at all.

Original comment by sbre...@gmail.com on 5 Apr 2012 at 11:55

[GoogleCodeExporter]

there was no file debug.log created.

Original comment by sbre...@gmail.com on 5 Apr 2012 at 11:56

[GoogleCodeExporter]

I don't know what to say since it does not make any sense to me. Do you see the 
application at all if you check the task manager? If you had gdb, I would ask 
you to run it through the debugger so that we can see what's happening.

In any case, maybe the next build will work for you? 

Original comment by parth...@gmail.com on 6 Apr 2012 at 1:02

[GoogleCodeExporter]

Does old build work? You can download multiple 64-bit versions from downloads 
section.

Original comment by jacekpop...@gmail.com on 6 Apr 2012 at 9:19

[GoogleCodeExporter]

I have downloaded a prior version or two before, and it did the same thing.  
I'll go back and give it another try.

Interesting that I don't have this problem on my 32-bit laptop.

Original comment by sbre...@gmail.com on 6 Apr 2012 at 11:48

[GoogleCodeExporter]

I tried an ealier .6, and .5.9.4 and .5.9.3.  Same response.

Original comment by sbre...@gmail.com on 6 Apr 2012 at 11:54

[GoogleCodeExporter]

So your problem is not related to current version of delaboratory at all, you 
have just something wrong with your 64-bit system because older versions were 
working for other people.

Original comment by jacekpop...@gmail.com on 6 Apr 2012 at 2:49

[GoogleCodeExporter]

Any thoughts as to what I might investigate to find out what is blocking it 
(antivirus software, for example)?  I don't have this problem with any other 
software package.  

Original comment by sbre...@gmail.com on 6 Apr 2012 at 4:36

[GoogleCodeExporter]

Don't know, maybe Partha has any hints. Please try any other application using 
wxWidgets. There are plenty of them available.

Original comment by jacekpop...@gmail.com on 6 Apr 2012 at 8:15

[GoogleCodeExporter]

Can you do a search for all the DLLs listed above? How many copies do you have 
these DLLs? Are any of them in your Windows systems's folder?

Original comment by parth...@gmail.com on 9 Apr 2012 at 2:42

[GoogleCodeExporter]

1) libjpeg-8.dll: in my delab, photivo and gimp folders.
2) liblcms-1.dll: in my delab and gimp folders
3) libpng15-15.dll: in delab and photivo folders
4) libstdc++-6.dll: delab and gimp plug-ins folders
5) libtiff-3.dll: delab, photivo,gimp, tools\DRC, tools\EAC, tools\sigmoidal 
folders
6) libxml2-2.dll: delaboratory and gimp folders
7) zlib1.dll: delaboratory, "Program Files (x86)\Calibre2\DLLS", photivo, 
various Nikon folders in Program Files (View NX2, etc.), "Program Files (x86), 
"C:\Program Files (x86)\Common Files\Apple\Apple Application Support", gimp, 
many other applications, but not in Windows system folder.

Original comment by sbre...@gmail.com on 10 Apr 2012 at 12:33

[GoogleCodeExporter]

These should not interfere, since Microsoft documentation claims that the DLL 
search path is system's folder and then the application start folder and then 
the path.

I suppose all the other apps you are displaying here are 64-bit and they work? 

DO you have another computer you can try this on? I am guessing 0.7 is not 
working for you then.

Original comment by parth...@gmail.com on 10 Apr 2012 at 10:48

[GoogleCodeExporter]

Photivo and Nikon ViewNX2 are64 bit, but GIMP is 32 bit (not sure why).  They 
work fine.  

I don't have another 64-bit machine to try this on unfortunately.

Just tried 0.7...no luck :(

Original comment by sbre...@gmail.com on 10 Apr 2012 at 11:48

[GoogleCodeExporter]

OK so there are two different machines and on both delaboratory 64-bit doesn't 
work, but photivo 64-bit works, right? Could you provide any more info how 
these machines can be different than others? CPU? Language? Other unstandard 
configuration?

Original comment by jacekpop...@gmail.com on 11 Apr 2012 at 7:45

[GoogleCodeExporter]

Jacek, He does not have another computer to try this on. 

I think we are out of luck here. I have no clue what is wrong that delaboratory 
will not work on his machine. I have not had any other complaints about the 
64-bit not even starting up. Without further information, Sorry, won't (can't 
?) fix.

Original comment by parth...@gmail.com on 12 Apr 2012 at 10:51

[GoogleCodeExporter]

We can add two simple apps to the build. The first app will do nothing except 
creating some log file, but will be linked with wxWidgets. The second app will 
also do nothing except log, but will not even link to wxWidgets. This way he 
could try both apps and see does it work at all. 

Original comment by jacekpop...@gmail.com on 12 Apr 2012 at 12:23

[GoogleCodeExporter]

Sbrenner, happy to work with you if you are interested. Would you be willing to 
work with us on Jacek's suggestion?

Original comment by parth...@gmail.com on 13 Apr 2012 at 12:06

[GoogleCodeExporter]

Partha - Sure, would be happy to.  Please let me know what you would like me to 
do.  Thanks!

Original comment by sbre...@gmail.com on 13 Apr 2012 at 1:47

[GoogleCodeExporter]

Two simple tests have been added to SVN. The first one is called test_wx and 
it's just a simple wxWidgets application, the secone one is called test_no_wx 
and it's just a main function. Both tests create log files with 3 lines of 
text. Please try to run them and see if logs are created.

Of course first Partha will need to prepare build for you. Please don't upload 
this build on project website, because current state of SVN code is not for 
production use ;)

Original comment by jacekpop...@gmail.com on 13 Apr 2012 at 10:34

[GoogleCodeExporter]

Thanks to Jacek for creating these tests. 

Sbrener, please download the attached files somewhere that's accessible to you 
and writeable by you. Then simply double-click and check for the logs that are 
created. Let us know what happens.

Original comment by parth...@gmail.com on 15 Apr 2012 at 6:13

Attachments:

• delaboratory-test.7z

[GoogleCodeExporter]

Ran the test_no_wx and test_wx.  Same result.  Looks like a dll is missing from 
computer.  libgcc_s_sjlj-1.dll.  Says to reinstall program, but that has not 
solved it yet.  

Should I look for the dll and add it to the Delaboratory folder?

Thank you for your help.

Original comment by sbre...@gmail.com on 17 Apr 2012 at 1:12

[GoogleCodeExporter]

The file test_no_wx is just a simple main function like "hello world", if it 
doesn't work then your system is incompatible with the way Partha compiles 
software. In short - your system is broken.

Original comment by jacekpop...@gmail.com on 17 Apr 2012 at 4:47

[GoogleCodeExporter]

Hi Sbrener,

Here is the missing DLL. Please unzip in the same location as the previous 
file. Please let us know if the program runs after that.

Original comment by parth...@gmail.com on 18 Apr 2012 at 10:39

Attachments:

• libgcc_s_sjlj-1.7z

[GoogleCodeExporter]

Thanks Partha.

I added it to the directory, and now it says a different dll is missing :(

libstdc++-6.dll.  

I have a feeling that this might not be the last one that is determined to be 
missing.

Original comment by sbre...@gmail.com on 18 Apr 2012 at 2:45

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

The question is why these files are missing on your system. Are there normally 
coming with Windows or are they part of the installation? I assume "gcc" can't 
come with Windows, so does it mean that installer doesn't work correctly on 
your system? Or maybe you have different settings and these files were 
installed in different directory?

Original comment by jacekpop...@gmail.com on 18 Apr 2012 at 7:03

[GoogleCodeExporter]

Sbrener, Can you copy the dll from the delaboratory download that you did 
previously - version 0.7 I mean? 

Jacek, no, they don't come with Windows and are part of the delaboratory builds 
or any Windows application built with gcc.

Original comment by parth...@gmail.com on 19 Apr 2012 at 12:01

[GoogleCodeExporter]

I did that and got the following when I ran test_no_wx

hello
this is just a test
we write to log file from main function

I got nothing when I ran test_wx, but I didn't get an error either.

Thanks.

Original comment by sbre...@gmail.com on 21 Apr 2012 at 1:48

[GoogleCodeExporter]

There should have been log files created when you ran those programs. Can you 
upload them?

Original comment by parth...@gmail.com on 21 Apr 2012 at 4:48

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

The only log file created was from text_no_wx

Original comment by sbre...@gmail.com on 21 Apr 2012 at 12:39

Attachments:

• test_no_wx.log

[GoogleCodeExporter]

It means that you were able to run simple main() function but not the code 
which uses wxWidgets. I think you should first find out why you were missing 
these dlls. Probably you still miss wx libraries, but anyway, why installation 
failed and even test_no_wx were not working?

Original comment by jacekpop...@gmail.com on 21 Apr 2012 at 2:43

[GoogleCodeExporter]

I'm not really sure how I would find out why the dlls were missing.  Is there 
some set of dlls that I could download to address this?

Original comment by sbre...@gmail.com on 23 Apr 2012 at 11:44

[GoogleCodeExporter]

You should not download dlls yourself, it works for everyone else.

Original comment by jacekpop...@gmail.com on 24 Apr 2012 at 8:38

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

This is interesting.  I wonder what is unique about Delaboratory as the 
inability to properly install a program does not seem to be a problem for any 
other application that I have installed.  I have yet to see such a problem 
outside of this context.

Original comment by sbre...@gmail.com on 25 Apr 2012 at 4:56

[GoogleCodeExporter]

Hi.  I decided to give another shot at loading delab.  I downloaded 0.7 for 
64-bit machine, and just like before after install absolutely nothing happened 
when I tried to launch.  I uninstalled, crestfallen as always.

For the heck of it, I downloaded the 32-bit installation, and shock of shocks 
(at least for me), the 32-bit version works on my machine.

I'm wondering what it is that allows the 32-bit version, but not the 64-bit 
version to work on a 64-bit machine....

Steve

Original comment by sbre...@gmail.com on 18 Jun 2012 at 12:31

[GoogleCodeExporter]

Well we can't do anything here, 64-bit version works for many people, we are 
not able to make any progress here.

Original comment by jacekpop...@gmail.com on 30 Jun 2012 at 10:37

• Changed state: WontFix

[GoogleCodeExporter]

That's fine.  Just reporting it because I find it interesting that the 32 bit 
version works.  At least I am still able to use it.  Regards.

Steve

Original comment by sbre...@gmail.com on 30 Jun 2012 at 7:27