That's what I'm wondering...

....I've been hunting high and low (well mostly Google-ing!) for anything
that might give us some clues as to how long the USB device is likely to take
to be "installed" into the System.

I don't know the source code of the application at all, but from what I've
seen of it so far it looks like it might try to copy the files across once
(and only once) and fairly early on in it's initialisation.

I guess I'm relieved that you haven't come back saying "Ah, you need an
Explorer shell because X, Y and Z will be missing if you don't". There isn't
anything *that* special about the Explorer shell/.exe is there?!?!

Cheers
-- Martin


"Sean Liming (MVP)" wrote:

>
> The USB flash disk when first inserted may take a few second to be mounted
> in the system. Does you application account for that time?
>
> Regards,
>
> Sean Liming
> www.sjjmicro.com / www.seanliming.com
> Book Author - XP Embedded Advanced, XP Embedded Supplemental Toolkit
>
> "Martin Dowie" <MartinDowie@discussions.microsoft.com> wrote in message
> news:C45C7C46-D5EE-48AE-B97E-C9534C1F73C5@microsoft.com...
> > We have a custom shell that litrally does nothing (just a Win32 app that
> > returns 0).
> >
> > Using Scheduled Tasks we start our actual application "When I log on".
> > This
> > seemed to be fine - ethernet/display/keyboard/mouse/opengl all working [we
> > had tried making the application the shell but it always just raised a
> > memory
> > access violation error].
> >
> > When we power up with a USB Memory Stick inserted (if present our app
> > should
> > read data files from it, not from the local hard disk). We can see the
> > light
> > on the stick flash (app accessing it) but the app fails to use the files
> > on
> > it.
> >
> > If we close the app and re-run it (via opening an Explorer window, then
> > double-clicking on the app's .exe file), the app reads and uses the
> > USB-based
> > files, as required!
> >
> > Does anyone have any idea what could be happening???
> >
> > TIA, Martin
> >
>