why does Win95 and CVI lockup?

[Farside]

Every time I make a modification to a c file, I save then Compile the code. I do not receive any compile or linking errors. I then select Debug Project, which goes through the build process. THe Running status then comes up within the window. However, the cursor locks up at this point where Windows95 does not respond to even a CTRL_ALT_DEL sequence. I then cycle the AC Power on/off switch, and run SCANDISK. Upon re-entering CVI I go directly to the Degub Project button. Upon reselection (No changes have occurred to the CVI code) the program successfully works. This lockup happens on changes as simple as going from printf ("Reading is: %d\n",var); to printf(" Reading is: %d\n",var);. (Here I only added a single space in front of the Read wi
thin a printf command. How can I avoid having to cycle power on my PC then running SCANDISK everytime I make a CVI code change?

[Shiner]

Are you running any other tools such as ClearCase (or other Source Code Control apps), or something like BlackIce (Firewall type apps).

Or accessing these files from a network drive ?

I have had similar problems with the above before.

[Farside]

The only application I am running is CVI. The PC does have McAfee AntiVirus SW running in the background though. The machine is an older 486 device that was once used on a network, but is now standalone. I'll Disable the AntiVirus AP, then try a reformat on the HDrive with a standalone config if it persists. Thanks for the Q's...