@orgin

1) You got me wrong. I meant on the registration page for new users where they fill their infos (username, password, etc.). Theres on the bottom a field to enter the "displayed" security code probably for preventing automated regsitering bots.. i guess there should be a picture displayed with some characters in it, etc .. it isn't displayed here... and it isn't checked, i.e. without entering anything the registration succeeds..

2) well, i didn't thought i would mess up the systems if i'm not creating any categories... maybe i even don't want categories ... so for me it's a bug

3b) ok.. still maybe not obvious enough ;)
c) ok

4) Yes, but as far as i can tell that email is only used as Sender of the registration mail and stuff.. i would rather like to have seperate addresses for user notification and admin notification.. An RSS feed is nice, but it's not what i want to use if more than 1 admin is involved in the bounty project..

5) thx

6) PHP 5.2.3-1

BTW: You can find my testsite on http://amigabounty.stackswap.net/ if you want a testadmin account, just shout ;)

@orgin

Ok, now tried to create a category (the very first one) and got


Could that be caused by the fact that there is already a bounty in the database without any category?

BTW: using 0.11

@orgin

I just installed your engine and it went all fine... fantastic work Orgin! *thumbsup*

Although i found some glitches:

1) The security code on registering as new user is not displayed nor checked.. probably not yet implemented?

2) after submitting a new project and trying to view the suggested projects i got
Quote:
Which probably is a result of the non-existant categories and therefore the project is also without category id... see 3)

3) The category drop-down when registering a new project is a) useless if there aren't any categories yet and should b) get a text-field as friend to let user also suggest new categories.. and therefore c) it should maybe get a default entry "Suggested category:" or something.. at least each project should have a category and if it's just "nocategory".

4) What about email notification for admins if a new project was suggested? There should be the possibility to specify one general email address for notifications (which could e.g. be a mailing list) and for each admin a setting if he wants to receive notifications ... ok, the first one should suffice in most cases..

5) Some default contact page with basic contact form..

I'll keep you informed about my findings and suggestions so at least it's me who's interested in ;)

@orgin

ok.. just wrote him a mail offering my help with www.amigabounty.net .. i honestly think we finally need a central bounty site as there are more and more really good project suggestions.. of course, as much bullshit ;)

And it would be a real pitty if your system wouldn't be used!

let's see what he thinks about it.. i hope Troels and myself can work something out which will help all amigans..

BTW: i have some more suggestions for liquorice.. will write them in the liquorice thread..

@orgin

Quote:

WTF?

I though Troels/amigabounty.net would use you fantastic work at once? At least Troels once wrote in a mail to me, that you're working on a bounty system which they plan to use..

Or whats exactly the problem?

Of course, such things definitely belong to a bounty site! I would probably write far more drivers if i would get some bucks for ;)

@orgin

First, well done so far.. secondly, some suggestions questions:

1) Hows the donation amount and it's original value calculated? Amount = rounded_down(Original - PayPal-Fee) ?

2) I like the idea of a bounty pool... i.e. donars may subscribe to a monthly donation plan or do one-time donations to that pool and once a month the pool is distributed across the bounties.. maybe according to popularity of each bounty or something..

3) Maybe the bounties should get some sort of progress indication, where the assigned developer(s) can tell people how far the process progressed.. maybe a percentage fuel gauge with comments or something..

4) didn't check the source yet, but i hope the colors and stuff are easy to change.. at least for me the default colors (on the test site) aren't very nice..

--
Bye,
Cyborg.

Hello Orgin,

Thanks for the quick processing of my uploaded rtl81x9.device. Unfortunately i forgot to bump the version in the upload form. Could you please set it to 0.28 instead of 0.26?

Thanks.

@rwo

Well, it's an alpha version and so it hasn't to support everything from the start... additionally i wrote it for the cards i had around in first place ;)

8129 support shouldn't be a big problem... but i didn't find any docs for it on the realtek server, though AFAIK it only differs from 8139 in the PHY being external via MII.. have to check that when i find the time *sigh* .. do you have a 8129 card? I don't so i'd need someone to actually test it..

Regarding the supported versions: RTFM I stated in the readme that all 8139 chips should be supported. i couldn't test all though.. that's why i released this alpha version.

Hello folks,

After a long time I decided to publish the current alpha version of my OS4 native SANA2 ethernet device for Realtek 81x9 chips, which will show up shortly on Aminet/os4depot. Of course you should read the included Readme, but i'll repeat the most important points here, just to be sure.. besides that, this thread my serve as a first-support-thread if you have problems with the device or questions or whatever.

1) It's ALPHA! That means there will probably show up some problems. You've been warned.

2) It supports 8139 (100Mbit) and 8169 (1000Mbit) Realtek chips. For a bit more details, see the readme.

3) If you encounter any problems, please check your serial line or memory buffer (DumpDebugBuffer)! If i can't verify the problem ad hoc, please be prepared to test a special debug version with lots of debug output (which i'll then send to you).

Thanks for reading, testing, reporting! Have fun and a happy new year 2007

Edit: Removed one paragraph as i decided to open a thread on aw.net too.. no offense, but theres simply more traffic than here (yet) and i *need* more user input..

EDIT: I just read you already made it, well, then my post won't be of any interest for you anymore.. i'll still leave it here just in case someone else has similiar problems.



Quote:


Is your A1 directly connected to an ADSL "modem" or to an ADSL router with integrated "modem"?

In any case this smells like being just an MTU/MSS related problem. If you can, get the correct default MTU and/or MSS Settings from your provider and set your settings accordingly.

For Ethernet connections (i.e. your A1 is behind a router with local IP address) the MTU should be 1500 and the MSS 1460.

But for direct connections through an ADSL "modem" this values might be different. E.g. for British Telecom the recommended MTU is somewhat around 1458, but 1430 has been proven to be the better value. The MSS should always be MTU - 40 bytes. E.g. if your MTU is 1500, MSS should be 1460.. if MTU = 1430, MSS should be 1390.

The MTU is controlled in your interface file in Devs:NetWorks. Open it with an texteditor and add a line like:

mtu=1492

The mss is controlled by the tcp.mssdflt setting of roadshow, you can either change it during network runtime with RoadshowControl or via an env variable, e.g. create the file ENVARC:Roadshow/tcp/mssdflt with the MSS as content (e.g. 1460, if 1500 is your MTU) and restart the network or reboot.

Quote:

And you did!

The reporter was me and i verified you fixed it.