October 20th, 2005

Enterprise Bridge

Renesas "C3300 (F) Cannot open internal file" error

One of my recent sources of agony has been this error message from the Renesas toolset I'm using to build a project at work:
C3300 (F) Cannot open internal file
The ch38 C compiler simply quit working for me one day, leaving me only that error. It doesn't tell me which file it can't open, just that it fails. After a week and a half of back-and-forth with Renesas tech support, I finally figured it out on my own. The makefile I'm using has no "clean:" recipe, and I wanted to make absolutely sure I was rebuilding from scratch. So I deleted the obj/Debug directory where it puts its built object files. I assumed the compiler was smart enough to recreate any directory it needed. Boy, was I wrong. 'mkdir Debug' saved the day.

(I'm logging this simply so it hits the search engines, so others can benefit.)
Enterprise Bridge

Windows startup configuration: msconfig

A while back, I remembered running across a utility, part of the stock Windows install, that let you configure all the different ways things can run at startup/login time. You used to do this by tiptoing through the registry, so things were scattered in several places, and it was easy to miss something. For the life of me, I couldn't remember what the hell that was, and searching Microsoft's own site was of course no help. (Chaff obscuring the wheat.)

The tool is called msconfig, and it lives in C:\WINDOWS\pchealth\helpctr\binaries
Enterprise Bridge

Thursday justice roundup

As deserved, the referee in last Friday's Helix-Mt. Miguel football game was suspended for the rest of the season for throwing a football at a player during a fight that broke out between opposing players during the fourth quarter. KUSI-TV's Prep Pigskin Report caught the melee on tape, I saw it on Friday night's broadcast. Kids fighting isn't a surprise, but to see a ref pick up a football and whip it at a kid walking away from him is a whole different thing.