From: Geoff Schaller on
I don't have any problems with the manifest files.

Here are my parameters:

upx %FULLFILE% -3 --compress-icons=0 (mdm compression)

upx %FULLFILE% -9 --compress-icons=0 (high compression)

Cheers,

Geoff


"Massimo Bighelli" <info(a)arcasistemi.it> wrote in message
news:493fa642$0$1093$4fafbaef(a)reader1.news.tin.it:

> Geoff,
>
> I always make one giant exe and I am happy with this approach
> BUT I stopped using UPX because of same strange problem compressing exe
> created with cctl6.man resource created.
> What version of UPX and what parameters do you use?
>
> TIA
>
> Massimo Bighelli
> ARCA Sistemi S.r.l.
>


__________ Information from ESET NOD32 Antivirus, version of virus
signature database 3681 (20081210) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com


From: Massimo Bighelli on

thx
I will try once more...



"Geoff Schaller" <geoffx(a)softxwareobjectives.com.au> ha scritto nel
messaggio news:ITN%k.1040$cu.954(a)news-server.bigpond.net.au...
>I don't have any problems with the manifest files.
>
> Here are my parameters:
>
> upx %FULLFILE% -3 --compress-icons=0 (mdm compression)
>
> upx %FULLFILE% -9 --compress-icons=0 (high compression)
>
> Cheers,
>
> Geoff
>
>
> "Massimo Bighelli" <info(a)arcasistemi.it> wrote in message
> news:493fa642$0$1093$4fafbaef(a)reader1.news.tin.it:
>
>> Geoff,
>>
>> I always make one giant exe and I am happy with this approach
>> BUT I stopped using UPX because of same strange problem compressing exe
>> created with cctl6.man resource created.
>> What version of UPX and what parameters do you use?
>>
>> TIA
>>
>> Massimo Bighelli
>> ARCA Sistemi S.r.l.
>>
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 3681 (20081210) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>

From: Dirk (Belgium) on
Paul D B

Starting the application takes about 2 seconds. After 2 seconds, the
login window is displayed. The login window is inside the EXE, which is
very small. If login is successful, then most of the DLL's are loaded.


Some customer works on Gigabit, some on 100 MBit. (We have found that
gigabit is not usefull for computers older then 3 a 4 year, because the
bottleneck is the computer, not the network).

I load them when I need them! Therefore, the first opening of the
childwindow is not taken in account for my speed comparision. Then it
takes just 1 (sometimes 2) second more.

Yes, it is the average I mean.

Yes, I have to redesign my app. The childwindow (with more then 7 tabs)
just have to load one tab, and when clicking on a tab, then the tab
have to be loaded when not loaded before.

Dirk

--

From: Dirk (Belgium) on
Phil Mermod wrote:

> Hi Dirk,
>
> In some customers' sites we had this kind of problem then we
> applied the following changes and this helped. Hope this will
> help yours too : http://support.microsoft.com/kb/296264
>
> Cheers,

I will look to it.

Dirk

--

From: Paul D B on
Hi Dirk,

Dirk (Belgium) wrote:
> Paul D B
>
> Starting the application takes about 2 seconds. After 2 seconds, the
> login window is displayed.

2 secs that's reasonable, especially if you are loading all DLL's at start
up and over a network.
So, this is the best proof that there is something wrong with your "big"
childwindow that takes 9 secs (locally) or 14 secs (remotely) to load!

The login window is inside the EXE, which
> is very small. If login is successful, then most of the DLL's are
> loaded.
>
>
> Some customer works on Gigabit, some on 100 MBit. (We have found that
> gigabit is not usefull for computers older then 3 a 4 year, because
> the bottleneck is the computer, not the network).

yes I can affirm this. I never benefited much from switching to Gigabit,
untill the day I replaced my computer.
However for applications that use a lot of bandwidth (such as using ordinary
DBF's on a shared network drive with Setfilters applied <g>), Gigabit will
always mean an improvement.


>
> I load them when I need them!

Fine, that's the approach I would take as well, but you said the opposite,
remember:
"DLL's are loaded with loadlibrary() on the start of the program, so
before opening the childwindow."

So it is quite difficult for us to give reasonable comments to your problem

Therefore, the first opening of the
> childwindow is not taken in account for my speed comparision. Then it
> takes just 1 (sometimes 2) second more.
>
> Yes, it is the average I mean.
>
> Yes, I have to redesign my app. The childwindow (with more then 7
> tabs) just have to load one tab, and when clicking on a tab, then the
> tab have to be loaded when not loaded before.

remember: VO28 is supporting this natively. Robert once explained us how to
use this. (Google for it).

But Dirk: what I would do, before going through the effort of redesigning,
is see if it is the data access that slows things down, or the
building/painting of a too complex window that is overloaded with controls.
It is quite easy to test:
- open the childwindow without opening the DBF's
- or if this is too hard to do, use copies of the DBF's that contains only a
few records
- and do the test with the data on the local drive, and again with the data
on the remote drive.


Paul

>
> Dirk



--
Paul