Issue-#108 BlackBox Start up warnings

Post Reply
Ivan Denisov
Posts: 1700
Joined: Tue Sep 17, 2013 12:21 am
Location: Russia

Re: Issue-#108 BlackBox Start up warnings

Post by Ivan Denisov »

Josef Templ wrote:It seems that nobody is able to reproduce the error.
It seems that only you is not able to reproduce the error.
Top
Ivan Denisov
Posts: 1700
Joined: Tue Sep 17, 2013 12:21 am
Location: Russia

Re: Issue-#108 BlackBox Start up warnings

Post by Ivan Denisov »

Josef Templ wrote:I am not able to play Ivan's movie.
I used standard h264 coder. You can use VLC player.
http://www.videolan.org/vlc/
It will also install plugin for Firefox or Chrome for you can play h264 in the web directly.
Top
User avatar
Josef Templ
Posts: 2047
Joined: Tue Sep 17, 2013 6:50 am

Re: Issue-#108 BlackBox Start up warnings

Post by Josef Templ »

To be be precise, I am not really interested in this video.
I am interested in the error code.
Top
Ivan Denisov
Posts: 1700
Joined: Tue Sep 17, 2013 12:21 am
Location: Russia

Re: Issue-#108 BlackBox Start up warnings

Post by Ivan Denisov »

Josef Templ wrote:To be be precise, I am not really interested in this video.
I am interested in the error code.
Sarcasm is hard to understand in the board :)

The error code from LuoWe's ObxTest4 is 0.
Top
User avatar
DGDanforth
Posts: 1061
Joined: Tue Sep 17, 2013 1:16 am
Location: Palo Alto, California, USA
Contact:
Contact DGDanforth

Re: Issue-#108 BlackBox Start up warnings

Post by DGDanforth »

Ivan Denisov wrote:
Josef Templ wrote:I am not able to play Ivan's movie.
I used standard h264 coder. You can use VLC player.
http://www.videolan.org/vlc/
It will also install plugin for Firefox or Chrome for you can play h264 in the web directly.
I also could not play the movie but did download the VLC player and that works!
I like your method of moving the manifest to and from the desktop. Much more efficient than
my renaming process.
-Doug
Top
Ivan Denisov
Posts: 1700
Joined: Tue Sep 17, 2013 12:21 am
Location: Russia

Re: Issue-#108 BlackBox Start up warnings

Post by Ivan Denisov »

I prepared debug version of Kernel.
http://blackboxframework.org/unstable/i ... a1.491.zip

This test showing which libraries used by BlackBox:

Code: Select all

MODULE ToolsListUsedDllVersions;

	IMPORT WinApi, Log, Kernel, SYSTEM;
	
	PROCEDURE LogDllStack*;
	VAR item: Kernel.DllItem;
	BEGIN
		item := Kernel.verStack;
		WHILE item # NIL DO
			Log.String(item.name + " = " + item.version); Log.Ln;
			item := item.next
		END
	END LogDllStack;

END ToolsListUsedDllVersions.

Q^ ToolsListUsedDllVersions.LogDllStack

Code: Select all

Wine 1.6:
SHELL32.dll = 5.0.3900.6975
KERNEL32.dll = 5.01.2600.2180
USER32.dll = 5.01.2600.2180
OLE32.dll = 10.0.0.0
KERNEL32.dll = 5.01.2600.2180
USER32.dll = 5.01.2600.2180
OLE32.dll = 10.0.0.0
OLE32.dll = 10.0.0.0
COMCTL32.dll = 5.81
KERNEL32.dll = 5.01.2600.2180
GDI32.dll = 1.0
USER32.dll = 5.01.2600.2180
COMDLG32.dll = 4.0
KERNEL32.dll = 5.01.2600.2180
USER32.dll = 5.01.2600.2180
GDI32.dll = 1.0
COMDLG32.dll = 4.0
USER32.dll = 5.01.2600.2180
KERNEL32.dll = 5.01.2600.2180
KERNEL32.dll = 5.01.2600.2180
USER32.dll = 5.01.2600.2180
GDI32.dll = 1.0
OLE32.dll = 10.0.0.0
OLE32.dll = 10.0.0.0
USER32.dll = 5.01.2600.2180
KERNEL32.dll = 5.01.2600.2180
GDI32.dll = 1.0
USER32.dll = 5.01.2600.2180
KERNEL32.dll = 5.01.2600.2180
USER32.dll = 5.01.2600.2180
GDI32.dll = 1.0
ADVAPI32.dll = 5.1.2600.2180
KERNEL32.dll = 5.01.2600.2180
KERNEL32.dll = 5.01.2600.2180
USER32.dll = 5.01.2600.2180
GDI32.dll = 1.0
KERNEL32.dll = 5.01.2600.2180
SHELL32.dll = 5.0.3900.6975
GDI32.dll = 1.0
USER32.dll = 5.01.2600.2180

XP sp3 With Manifest
SHELL32.dll = 6.00.2900.5512 (xpsp.080413-2105)
KERNEL32.dll = 5.1.2600.5512 (xpsp.080413-2111)
USER32.dll = 5.1.2600.5512 (xpsp.080413-2105)
OLE32.dll = 5.1.2600.5512 (xpsp.080413-2108)
KERNEL32.dll = 5.1.2600.5512 (xpsp.080413-2111)
USER32.dll = 5.1.2600.5512 (xpsp.080413-2105)
OLE32.dll = 5.1.2600.5512 (xpsp.080413-2108)
OLE32.dll = 5.1.2600.5512 (xpsp.080413-2108)
COMCTL32.dll = 6.0 (xpsp.080413-2105)
KERNEL32.dll = 5.1.2600.5512 (xpsp.080413-2111)
GDI32.dll = 5.1.2600.5512 (xpsp.080413-2105)
USER32.dll = 5.1.2600.5512 (xpsp.080413-2105)
COMDLG32.dll = 6.00.2900.5512 (xpsp.080413-2105)
KERNEL32.dll = 5.1.2600.5512 (xpsp.080413-2111)
USER32.dll = 5.1.2600.5512 (xpsp.080413-2105)
GDI32.dll = 5.1.2600.5512 (xpsp.080413-2105)
COMDLG32.dll = 6.00.2900.5512 (xpsp.080413-2105)
USER32.dll = 5.1.2600.5512 (xpsp.080413-2105)
KERNEL32.dll = 5.1.2600.5512 (xpsp.080413-2111)
KERNEL32.dll = 5.1.2600.5512 (xpsp.080413-2111)
USER32.dll = 5.1.2600.5512 (xpsp.080413-2105)
GDI32.dll = 5.1.2600.5512 (xpsp.080413-2105)
OLE32.dll = 5.1.2600.5512 (xpsp.080413-2108)
OLE32.dll = 5.1.2600.5512 (xpsp.080413-2108)
USER32.dll = 5.1.2600.5512 (xpsp.080413-2105)
KERNEL32.dll = 5.1.2600.5512 (xpsp.080413-2111)
GDI32.dll = 5.1.2600.5512 (xpsp.080413-2105)
USER32.dll = 5.1.2600.5512 (xpsp.080413-2105)
KERNEL32.dll = 5.1.2600.5512 (xpsp.080413-2111)
USER32.dll = 5.1.2600.5512 (xpsp.080413-2105)
GDI32.dll = 5.1.2600.5512 (xpsp.080413-2105)
ADVAPI32.dll = 5.1.2600.5512 (xpsp.080413-2113)
KERNEL32.dll = 5.1.2600.5512 (xpsp.080413-2111)
KERNEL32.dll = 5.1.2600.5512 (xpsp.080413-2111)
USER32.dll = 5.1.2600.5512 (xpsp.080413-2105)
GDI32.dll = 5.1.2600.5512 (xpsp.080413-2105)
KERNEL32.dll = 5.1.2600.5512 (xpsp.080413-2111)
SHELL32.dll = 6.00.2900.5512 (xpsp.080413-2105)
GDI32.dll = 5.1.2600.5512 (xpsp.080413-2105)
USER32.dll = 5.1.2600.5512 (xpsp.080413-2105)

XP sp3 Without manifest:
OLE32.dll = 5.1.2600.5512 (xpsp.080413-2108)
KERNEL32.dll = 5.1.2600.5512 (xpsp.080413-2111)
USER32.dll = 5.1.2600.5512 (xpsp.080413-2105)
OLE32.dll = 5.1.2600.5512 (xpsp.080413-2108)
OLE32.dll = 5.1.2600.5512 (xpsp.080413-2108)
COMCTL32.dll = 5.82 (xpsp.080413-2105)
KERNEL32.dll = 5.1.2600.5512 (xpsp.080413-2111)
GDI32.dll = 5.1.2600.5512 (xpsp.080413-2105)
USER32.dll = 5.1.2600.5512 (xpsp.080413-2105)
COMDLG32.dll = 6.00.2900.5512 (xpsp.080413-2105)
KERNEL32.dll = 5.1.2600.5512 (xpsp.080413-2111)
USER32.dll = 5.1.2600.5512 (xpsp.080413-2105)
GDI32.dll = 5.1.2600.5512 (xpsp.080413-2105)
COMDLG32.dll = 6.00.2900.5512 (xpsp.080413-2105)
USER32.dll = 5.1.2600.5512 (xpsp.080413-2105)
KERNEL32.dll = 5.1.2600.5512 (xpsp.080413-2111)
KERNEL32.dll = 5.1.2600.5512 (xpsp.080413-2111)
USER32.dll = 5.1.2600.5512 (xpsp.080413-2105)
GDI32.dll = 5.1.2600.5512 (xpsp.080413-2105)
OLE32.dll = 5.1.2600.5512 (xpsp.080413-2108)
OLE32.dll = 5.1.2600.5512 (xpsp.080413-2108)
USER32.dll = 5.1.2600.5512 (xpsp.080413-2105)
KERNEL32.dll = 5.1.2600.5512 (xpsp.080413-2111)
GDI32.dll = 5.1.2600.5512 (xpsp.080413-2105)
USER32.dll = 5.1.2600.5512 (xpsp.080413-2105)
KERNEL32.dll = 5.1.2600.5512 (xpsp.080413-2111)
USER32.dll = 5.1.2600.5512 (xpsp.080413-2105)
GDI32.dll = 5.1.2600.5512 (xpsp.080413-2105)
ADVAPI32.dll = 5.1.2600.5512 (xpsp.080413-2113)
KERNEL32.dll = 5.1.2600.5512 (xpsp.080413-2111)
KERNEL32.dll = 5.1.2600.5512 (xpsp.080413-2111)
USER32.dll = 5.1.2600.5512 (xpsp.080413-2105)
GDI32.dll = 5.1.2600.5512 (xpsp.080413-2105)
KERNEL32.dll = 5.1.2600.5512 (xpsp.080413-2111)
SHELL32.dll = 6.00.2900.5512 (xpsp.080413-2105)
GDI32.dll = 5.1.2600.5512 (xpsp.080413-2105)
USER32.dll = 5.1.2600.5512 (xpsp.080413-2105)
Top
User avatar
DGDanforth
Posts: 1061
Joined: Tue Sep 17, 2013 1:16 am
Location: Palo Alto, California, USA
Contact:
Contact DGDanforth

Re: Issue-#108 BlackBox Start up warnings

Post by DGDanforth »

Ivan,
Excellent work!

I did something similar by downloading Listdlls.exe and noticed that ComCtl32.dll was loaded with or without the manifest BUT
your example shows that indeed the version is 6 with the manifest and 5.8 without it.

Now, we still do not know why Josef always gets a message box.
It must be that something in his environment is different from ours, but what?

-Doug
Top
User avatar
Josef Templ
Posts: 2047
Joined: Tue Sep 17, 2013 6:50 am

Re: Issue-#108 BlackBox Start up warnings

Post by Josef Templ »

There is a Windows tool named 'procmon.exe' that shows a lot of information about a process.
It is a bit tricky to configure the filter appropriately, though.
With procmon it should be possible to get a trace that shows where there are differences
between a successful load of ObxTest and a failure.

However the final fix looks like, it must be applied also to Kernel.DefaultTrapViewer.

- Josef
Top
User avatar
DGDanforth
Posts: 1061
Joined: Tue Sep 17, 2013 1:16 am
Location: Palo Alto, California, USA
Contact:
Contact DGDanforth

Re: Issue-#108 BlackBox Start up warnings

Post by DGDanforth »

I ran ProcMon.exe and then ran BlackBox master with Converters.ocf in my /USE directory
so it would fail and it did fail without a message box.

Looking back at ProcMon's output I was (firstly) amazed at the number of entries for BlackBox
and (secondly) how many of those entries were SUCCESS. There were also entries for
NAME NOT FOUND, some of which were querying the registry.

An interesting entry was the following:
NAME NOT FOUND
NAME NOT FOUND
It was looking for Converters in the directory Code of the Master directory.
Well that may be standard before it later looks for it in the /USE directory.
Don't know. Plowing through those entries takes quite a while.
-Doug
Top
User avatar
Josef Templ
Posts: 2047
Joined: Tue Sep 17, 2013 6:50 am

Re: Issue-#108 BlackBox Start up warnings

Post by Josef Templ »

Doug, I think you should focus on the simplest test case which shows the failure.
And that is luowy's ObxTest in http://forum.blackboxframework.org/view ... t=50#p3465.

- Josef
Top
Post Reply

Return to “Resolved (Bugs)”