Thread: VS2005 WinXP PROJECTS and VS2005 WinVista PROJECTS Problems........

hi,

I'm having trouble using VS2005 projects in windows vista, that were created on winXP Home.

The program that was created on winXP works perfectly, but when i open the same project the program runs, but when i do, for example, a delete user, the program crashes.

Does anyone have or had this experience?

Using:
- Windows Vista x64
- MS Visual Studio 2005 SP1

What do you mean 'delete a user'?, If you mean delete a user on the computer then it really depends on how you've done it.

hey!

That was just an example.

Ok. I'm creating a simple C program for school.
The program was created in VS2005 on a WinXP machine.

The program runs normaly on the winXP machine, were it was created. The program has several of options, since the creation of users, files, etc.

When i open the VS2005 project in my laptop, which is running vista x64, and when i compile, it doesn't give me any error or warning. So far, so good...

But when i run the program, either using VS2005 or the .exe file, and when i select "Delete User", the program crashes and closes :-S
All the rest is working...

Now, what is strange is that the code is all correct, and the same program runs smoothly in the winXP machine were it was created.

Can anyone help me now?

Could you should the code where you actually "Delete User"? What WinAPI functions you are using? Are yo checking all the return values? Probably you have not enough permissions (on Vista) to exacute some action - and as a result get the NULL pointer that you are using without check...

but as i said, this works in the winXP machine were it was created

yep!
done it long ago...

i even installed the most recent SP1, and nothing

fflush(stdin);

* Don't flush stdin, see the FAQ

gets(directoria);

* See the FAQ regarding gets(), use fgets instead.

strcpy( directoria, strlen_dir(directoria) );

* If 'strlen_dir()' returns the length of 'directoria'? Then this is incorrect, char * strcpy ( char * destination, const char * source );

There is a few more errors in the above, for one I see a 'free' but no malloc? Even if it is in one of your other functions like check_DIR or something, you don't check if it fails or not (yes malloc can fail)

your right zacs7!

i did what you said, i removed the free(aux); and it doesn't crash anymore, thanks alot!

but the strange thing is, that even with the free(aux); the program runs on the machine where it was created :S

> but the strange thing is, that even with the free(aux); the program runs on the machine where it was created
Unfortunately, you can never equate "working" with "bug free".

The next question is, was it really correct to not do "free(aux)", or is it just a case of if you don't do that, it just prevents it from crashing because it no longer exposes some other hidden problem in the code?

hi Salem

you're right...it stoped crashing but, it wasn't working well.
i had to use free but with another variable ( free(auxD); ) and use the malloc ( auxD=malloc(sizeof(nodir)); ).

Now its working nicely

Make sure you add some error checking this time...