I've got a wierd problem going on, and we've been spending all day trying to figure this out with no luck. I've been running the eval version of Keil uVision 3.1 with an MCB2130 board running an LPC2138 for a while now successfully. We just got in some new MCB2300 boards running a LPC2378.
Today I opened up the new board, hooked it up to the ULINK and put power to them both. Fired up the same eval version of uVision that worked fine befor and opened up the included MCB2300 Blinky program, try to compile, and boom.... doesn't work. What appears to be happening is that ArmAsm.exe is crashing. At first I just got an error the first time -- "Startup.s: Error: A9932E:" followed by some random text (anywhere from part of my username followed by "\Application Data" to "(founded by Phillips)" to something OrCad directory structure on the other computer) -- but now it appears that any time the compiler tries to load, it crashes, and I get a windows error that the arm compiler tools crashed. Trying to run the exe's in the \Bin32, they all pop up in a command prompt and seem to have functioned except for ArmAsm.exe, which crashes.
Since then, I've tried running other projects that did work before for the MCB2130 board and others, with no luck. I've uninstalled and reinstalled all the Keil tools several times, trying various things like being sure not to open the 2300 project first. We've tried it on my coworkers machine, where he had successfully used the eval of uvision in the past, and it didn't compile the 2300 projects either, and won't work on the 2100s (unfortunately we didn't try those first, as opening the 2300 projects is the only change we can see...). We've also installed the software fresh on a laptop that's never had it on there, and it does the same thing.
Since both of our main machines exhibited the same thing independently after previously working, I would suspect maybe there was some change to windows, as everything else seems constant, but it crashed the same way on the laptop we installed it fresh on, which is not on the network getting updates, and won't have the same setup on.
Another of us is working successfully on the professional version, but we can't afford to break his, as he's working actively on code for projects, where ours is for experimentation.
We've been over the settings over and over again, and just don't see what could be causing it, and can't think of anything that could have changed.
Anybody have any experience with the compiler failing to load, or have any ideas?