M
Martin Dowie
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
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