From: BlueChip <cs_bluechip_at_webtribe.net>
Date: Wed, 17 Dec 2003 01:23:41 +0000

> > All tests have been performed with Rockbox release code v2.1
>If you can build it yourself, why use the 2.1 release code? We've fixed
>numerous minor quirks since, and chasing bugs already fixed is... well,
>boring.

Do you really need/want an answer to the above question?

> > # Cannot power on unit
> > Archos firmware v1.28/1.27d (nothing we can do)
>Hold down the ON button longer.

aready tried - does not fix the problem.

>This works for me.

Are you using a flashed unit?

> > # Cannot power off unit
>This is not a bug and has been discussed a lot here. This is by design.

Please direct me to this discussion - I'd like to read about why it
corrupts the screen etc.

> > # Build for: Recorder, 2MB, Sim, Win32
> >
> > --A--
> > 4 warnings during compile:
> > ../../apps/plugin.c:111: warning: initialization from incompatible
> pointer type
> > ../../apps/plugin.c:113: warning: initialization from incompatible
> pointer type
> > ../../apps/plugin.c:114: warning: initialization from incompatible
> pointer type
> > ../../apps/plugin.c:116: warning: initialization from incompatible
> pointer type
>
>These warnings showed up in the build table for months before we fixed them,
>*after* the 2.1 release...

I didn't realise that the official release of v2.1 had known bugs that
stopped a successful compile.
How ironic (qv. 1st question)

> > windres -i uisw32.rc -o /home/rockbox/rockbox-2.1/s/uisw32-res.o
> > uisw32.rc:11:20: afxres.h: No such file or directory
>
>No clue.

Some M$ file iirc

> > Screen display is corrupt in simulator.
>Hm. Why do you get problems with this when others have not seen them? I'm just
>curious so that fixing this with your proposal don't break it for others.

Can you name users that have seen this feature working correctly so that I
may discuss it with them?

I was going to name "roland" as a user who HAS seen the error (as well as
me), but he has beaten me to it.

> > Features missing from menu system.
>When you run the tools/configure it creates a define in the makefile for what
>target model you build for. In the source code, the firmware/export/config.h
>is included and that checks what model you build for and include the proper
>config-*.h header file, in which those defines are defined.

Yes, I thought that too - but it doesn't ...for either me or earHertz.
I wonder why it works for you?
Can/Will you supply more accurate information about your development
environment?

> > main_menu options Plugins and Firmware do not work that is, selecting those
> > options does nothing, it just leaves you on the main_menu screen this means
> > that plugins cannot be used or tested in the simulator
>
>No clue.

Which O.S. did you test it on?

> > If ANYBODY can point me at a bullet-proof set of instructions which will
> > explain to even me what I am supposed to do to submit I would be immenseley
> > greatful.
>
>Make a patch:
>
> http://rockbox.haxx.se/docs/patch.html

"diff -u oldfile newfile > patch
OR
diff -u olddir newdir > patch"

????? ...You don't know what type of bullets I use ;)

>Submit a patch:
>
> http://sourceforge.net/tracker/?group_id=44306&atid=439120
>
> It's been so long, I'm not sure I can even remember how to use
> > diff and pat properly ...I never did suss ADDING a new file with diff
>
>-N "treat absent files as empty"

bingo! diff file which includes objects, makefiles, .deps, .rocks, etc.
etc. etc.

Anyway, I am sure I can work it out one way or another.
As you said at the top, it is good to repeat other peoples work, it makes
you bored :)

> > ...and I never did suss CVS :(
>It's easy to learn!

So they tell me.
One day I'll find out how :)

Thanks for your feedback,

BC
Received on 2003-12-17