VC++ and XP ?

Actually, yes. This just started happening to me. I have no idea why.

"So crucify the ego, before it's far too late. To leave behind this place so negative and blind and cynical, and you will come to find that we are all one mind. Capable of all that's imagined and all conceivable."
- Tool
------------------------------


Edited by - wayfarerx on January 16, 2002 9:33:41 PM

I have VC++ 6.0 Standard and this happens all the time. It doesn''t matter how much time I wait after the last change to the file before saving it -- usually, it still gives me that error, and only once. After getting the error, the next time I save always works. It is definitely annoying and I would certainly like to know what is causing it. It''s possible the OS does some sort of automatic document-saving thing to allow you to restore documents you couldn''t save before the computer crashed or whatever.

~CGameProgrammer( );

this happen''d to me, but it also happened in Win2K. i have re-installed XP and it hasn''t happened since.

To the vast majority of mankind, nothing is more agreeable than to escape the need for mental exertion... To most people, nothing is more troublesome than the effort of thinking.

I''m only using Win2k, so this probably won''t help you, but then again, maybe.

The only file locking problem I''ve noticed during a build is when the executable was (or had recently been) running and the linker tried to save a new one over it.

Is it a problem with your source files, or the linker output ?

Source files.

"So crucify the ego, before it''s far too late. To leave behind this place so negative and blind and cynical, and you will come to find that we are all one mind. Capable of all that''s imagined and all conceivable."
- Tool
------------------------------

I''m guessing you''d have to disable something in Control Panel -> Administrative Tools -> Services. But I''m not sure. Hopefully there is some way to solve this problem.

~CGameProgrammer( );

I''ve had the problem too from time to time, but rebooting always seems to fix it.

Fruny, if they are having the same problem I am, it is with the source, not the linker output. I know that if you run your code from within MSVC and it doesn''t terminate properly, the next time you go to compile it will say something about the linker being unable to write the .exe file, since it''s still running in the background. But this is a different issue; like meZmo said, basically every other time you go to save the source file a dialog box pops up with that message. It''s really weird, and even more annoying.

Anthracks

Well that''s just strange. I''ve been using XP for nearly a year, and I''ve never experienced anything like this.

Ok. Can''t help you then. Good luck. ( But then again you''ve been using WinXP, so you accumulated lots''o'' bad karma )

Are you programming a Win32 application???

I used to call PostQuitMessage on the WM_DESTROY message... but in XP my apps stayed in the message loop and had to be terminated manually (thus stopping me from rebuilding the app).

Call PostQuitMessage on WM_CLOSE and all will be fine.

This has nothing to do with programming, MindHive. When using Visual C++, and you save a file (by clicking "Save" or pressing Ctrl+S, or simply compiling the program which saves automatically), half the time this makes an error saying you cannot save the file because it''s in use by another application.

~CGameProgrammer( );

And this isn''t dealing with the final executable that the linker creates, or the intermediate files (the .obj files, etc.), or anything like that. Just the files you create and edit.

~CGameProgrammer( );

I have been experiencing this problem for years whether it be with Win98SE, Win2K or WinXP (I have had it happen with all 3).

I honestly have no idea what is causing it and how to fix it, but I guess it is just one of those little things that I, and the rest of us, will have to live with. It _always_ works the second time for me.

Cray

It didn''t happen when I used Windows 98, then I got WinXP and it happens. It always works the second time, but it should work every time. It''s annoying having to save, click ''OK'', then save again.

~CGameProgrammer( );

I''ve used VC++ on Win NT 4 Workstation & Server with no prob, Win 2000 Pro & Server with no prob. The only time this has happened to me is on Win XP Home.

"So crucify the ego, before it''s far too late. To leave behind this place so negative and blind and cynical, and you will come to find that we are all one mind. Capable of all that''s imagined and all conceivable."
- Tool
------------------------------

quote:

---

Original post by Martee
Well that''s just strange. I''ve been using XP for nearly a year, and I''ve never experienced anything like this.

---

uhhhhmmm...its only been out a couple months.

And i never experienced this problem myself. I bought XP they day after it came out and installed VC the same day. It *might* be a security setting.

-----------------------------
The sad thing about artificial intelligence is that it lacks artifice and therefore intelligence.

a security setting.... that''s funny. especially, after every post has said that immediately after they press the save button again it works.

To the vast majority of mankind, nothing is more agreeable than to escape the need for mental exertion... To most people, nothing is more troublesome than the effort of thinking.

quote:

---

Original post by Promit
uhhhhmmm...its only been out a couple months.

---

The betas have been in MSDN for quite awhile now.



"So crucify the ego, before it''s far too late. To leave behind this place so negative and blind and cynical, and you will come to find that we are all one mind. Capable of all that''s imagined and all conceivable."
- Tool
------------------------------

It's good to get confirmed that this is an actual problem. Now if we could only find out why... I'm lost at this one..


Edited by - meZmo on January 17, 2002 2:51:28 PM