Unsupported Model Error

[MarcGuay]

Am I the only one who finds IRC incredibly slow and painful?

Anyway, I would have asked there but it seems I don't have the patience.  So:  I'm trying to add the Sansa c100 as a build target as per the instructions on the PortingHowTo wiki page, and have come across an error I can't fumble my way past.  It looks as such:

Code: [Select]

Build bootloader file
unsupported model: c100

[saratoga]

Update scramble.c to support your target.

[MarcGuay]

Thanks.  Seems like Windows' search for "containing text" failed me once again...

[saratoga]

Use "grep -r" instead.  Took me about 5 seconds to figure out where that error came from.

[bluebrother]

Am I the only one who finds IRC incredibly slow and painful?

Don't use the web client -- that is a pain. But using a real IRC client works quite well -- from the number of people in the channel I assume for quite some

[GodEater]

Although if you *have* to use a web client (like some of us behind nasty restrictive firewalls), then www.mibbit.com is way better than the CGI::IRC thing we use as our direct link on the site.

The downside of it is you have to know a bit more about IRC to connect to the rockbox channel, since it doesn't automatically log you in there.

[MarcGuay]

Excellent, Mibbit is a definite improvement.  I tried mIRC before and it was brutally slow as well, maybe I just chose the wrong client from the pile.  Anyway, thanks a lot, maybe I'll stick my head in there more often.

[GodEater]

Out of interest, you said you found IRC "slow" - I'm curious to know "when compared with what?"

[MarcGuay]

Compared to a speed I find tolerable, I guess, which is based on the speed I'm used to when dealing with an up-to-date computer.  It was taking about 2 or 3 minutes just to log in, at which point I'd often get booted by a random error.  And then the time between sending a message and it actually appearing in the channel would deter me even more.

[AlexP]

Yeah, that's just the cgi client.  Mibbit is better, but a proper client (i.e. not in a browser) is instant (except for if you have network troubles of course

[pixelma]

Thanks.  Seems like Windows' search for "containing text" failed me once again...

The Windows explorer doesn't search the content of file (types) it doesn't know of, not in *.c files etc. as you found yourself. Stated above you could use the commandline grep in your development environment. But there are also standalone free grep tools (for Windows too), e.g. there's a free demo version of "baregrep" which I like to use for that. Just another way to search in the files, eases developing in case it feels more comfortable to you.

[bluebrother]

But there are also standalone free grep tools (for Windows too), e.g. there's a free demo version of "baregrep" which I like to use for that. Just another way to search in the files, eases developing in case it feels more comfortable to you.

If you like the command line and possibly the tools you usually find on linux systems try http://gnuwin32.sf.net

[MarcGuay]

The Windows explorer doesn't search the content of file (types) it doesn't know of, not in *.c files etc. as you found yourself.

Interesting, thanks for that bit of info.  I figured it was smart and useful like computers are supposed to be.  Big mistake?  The grep command is coming in very handy, though.