We have a "simple" call to CreateFile:
flashfileHandle=CreateFile((LPCWSTR)working_path,FILE_READ_DATA|FILE_WRITE_DATA,0,NULL,OPEN_EXISTING,FILE_ATTRIBUTE_NORMAL,NULL);
which apparently had been working in Vista (32 bit) up to a few weeks ago. Now it is failing in our user's systems. It is still working properly in XP. Apparently this is related to some update that Microsoft did with an automatic update.
The return is either error 2(FILE NOT FOUND) or 123 (Invalid Name).
This code is in a "terminal module" compiled and linked under Visual studio 2005 SP1 with the test being done at command line level.
Using exactly the same name (working_path) in fopen_s works.
I have tried to set the administration rights to administrator and turning "user accounts->turn user account control on or off" off with no effect.
Eliminating FILE_WRITE_DATA does not help.
Any idea what has happened and how to fix it?
flashfileHandle=CreateFile((LPCWSTR)working_path,FILE_READ_DATA|FILE_WRITE_DATA,0,NULL,OPEN_EXISTING,FILE_ATTRIBUTE_NORMAL,NULL);
which apparently had been working in Vista (32 bit) up to a few weeks ago. Now it is failing in our user's systems. It is still working properly in XP. Apparently this is related to some update that Microsoft did with an automatic update.
The return is either error 2(FILE NOT FOUND) or 123 (Invalid Name).
This code is in a "terminal module" compiled and linked under Visual studio 2005 SP1 with the test being done at command line level.
Using exactly the same name (working_path) in fopen_s works.
I have tried to set the administration rights to administrator and turning "user accounts->turn user account control on or off" off with no effect.
Eliminating FILE_WRITE_DATA does not help.
Any idea what has happened and how to fix it?