Hmmm, given the USB is in from the very start and that to get from 'switching
power on' to 'application starting' takes about 50 seconds...shouldn't the
USB drive not be available by the point the application tries to copy from it?

Can it really take /that/ long for the OS to spot / mount the disk?

There is a light that is flashing as if being accessed by the application (2
times, perhaps once for each file it is trying to read?)...

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
> >
>