Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Shortcut problem

0 views
Skip to first unread message

Matthew Kroll

unread,
May 22, 1998, 3:00:00 AM5/22/98
to

When Windows95/NT4 loads, the desktop shortcuts to my homemade
VB apps momentarily display the default VB project icon, then flash to
the correct image. Other shortcuts and programs on my desktop don't
suffer from this problem, only VB applications I've made. Suggestions
are welcome.

Matthew Kroll

René Whitworth

unread,
May 24, 1998, 3:00:00 AM5/24/98
to

I guess this depends on registry entries.
On my mashine some vb icons even show up as DOS programms, while other non
vb apps display in windows-not-registered icon.

--
Whitworth Software Solutions
René Whitworth
R_Whi...@bigfoot.com


Matthew Kroll schrieb in Nachricht <6k46tq$hh1$1...@marcie.fissiontech.com>...

Jim Bowman

unread,
May 27, 1998, 3:00:00 AM5/27/98
to René Whitworth

Rene',
I've never seen that. I'm wondering if you don't have a Windows problem.
-- JIM

René Whitworth

unread,
May 28, 1998, 3:00:00 AM5/28/98
to

Jim

As in the original news, this is meant at system startup just for a very
short time period.
I think it could be caused by loading and installing several jobs and apps
(just like virus protection), which are handled in advance.
Painting the desktop at startup is really not that important for the system
...

--
Whitworth Software Solutions
René Whitworth
R_Whi...@bigfoot.com


Jim Bowman schrieb in Nachricht <356BF4E0...@clandjop.com>...

John Wahl

unread,
May 28, 1998, 3:00:00 AM5/28/98
to

René Whitworth <R_Whi...@bigfoot.com> wrote in article
<OwxdP9h...@uppssnewspub04.moswest.msn.net>...
» Jim

»
» As in the original news, this is meant at system startup just for a very
» short time period.
» I think it could be caused by loading and installing several jobs and
apps
» (just like virus protection), which are handled in advance.
» Painting the desktop at startup is really not that important for the
system
» ...
»
» --
» Whitworth Software Solutions
» René Whitworth
» R_Whi...@bigfoot.com
»

Yes that would be correct. you have to remember you're dealing w/ non
executibles here. Interpretted Executibles are not the same as REAL apps,
although I'll praise VB all day, you still can't make an executible and
expect it to work on a machine w/o the virtual driver (msvb5 for 5, vb432,
etc..) The system picks up that it's a vb app on startup and gives it a vb
icon, until it can run the appropriate extracticon on the program later.
Have you ever noticed the resources area on vb app is "corrupt" by many
viewers? Because they're not standard EXEs. That's why this is happening.
It's just something you're going to have to live with.

Try running Quikview on a C++ built exe and see what's been exported or
imported from blah.dll then a vb app. You can't see what APIs the VB
program uses, because it isn't a real Executible (per-say).

Any Questions?

--
John J. Wahl -<wa...@zande.com>-
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
R.D. Zande & Associates, Inc.
Phone:(614) 486-4383 Fax:(614) 486-4387
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

0 new messages