Koderiter
asked on
Visual Stuido 6 pro linking taking a long time
I have been writing an application that is windows based with MFC on a AMD processor with win XP. I recently got a job with the company tha I'm writing the software for. I moved my code to a new machine of theirs. Which has an INTEL P4 processor and Win 2000. My project in Visual Studio 6.0 pro on my home machine AMD 1.8 mGhz 512 ram will compile and link pretty fast. Now here at work the LINKING portion is taking about 5 - 10 min.
Is there anything that I can do to help speed up the linking?
Does anybody know what is going on?
thanks,
RJ
Is there anything that I can do to help speed up the linking?
Does anybody know what is going on?
thanks,
RJ
are you compiling to a network drive??
b) did you compile locally(faster)
b) did you compile locally(faster)
ASKER
-I am compiling locally, no files are on the network.
-I did check the hard drive and it needed no defragmentation, but I still ran it. (no change with linking)
-no Virus scanning software is evan loaded.
-I did check the hard drive and it needed no defragmentation, but I still ran it. (no change with linking)
-no Virus scanning software is evan loaded.
ASKER
Has anybody had any problems with linking on an ITEL box vs AMD box?
I really would like any suggestions that you can think of.
I really would like any suggestions that you can think of.
i have a 1.3 GHZ intel and a 2.8 intel the difference is HUGE
So its probably the speed and not the make
So its probably the speed and not the make
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I have noticed that linking does not take very long in RELEASE mode as compaired to DEBUG mode. any thoghts there?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
-- Hard drive fragmented.
-- Virus scanner in real-time mode checking files on the fly
-- Some tools or source files on a network rather than on the build machine