PPCGeeks Unified ROM Project: Project Updates - Page 3

psychotic · #21 (**permalink**) 03-21-2007, 05:07 AM

Quote:

Originally Posted by jamesus

[*]3/8/2007: Numerous people have indicated problems attempting to run Wireless Modem. One involves the "COM OPEN ERROR" problem (issues duplicating the error?). The other involves not being able to run Wireless Modem under certain circumstances, and needing a soft reset to re-enable it (referenced by JBabey here, and I've hit the problem myself as well, although I need to find out how to reproduce).[*]3/8/2007: Menneisyys wrote up an article expalining the change in the dial-up networking model changes in AKU 3.x.

Is the first section saying you are still working on a fix for the USB dial-up networking/modem problems?? Because the 2nd section describes a solution that only works with bluetooth. Is there a way to do this with USB? Sorry if you answered this above, I'm just slightly confused

**jamesus** · #22 (**permalink**) 03-21-2007, 11:23 AM

Quote:

Originally Posted by psychotic

Quote:

Originally Posted by jamesus

[*]3/8/2007: Numerous people have indicated problems attempting to run Wireless Modem. One involves the "COM OPEN ERROR" problem (issues duplicating the error?). The other involves not being able to run Wireless Modem under certain circumstances, and needing a soft reset to re-enable it (referenced by JBabey here, and I've hit the problem myself as well, although I need to find out how to reproduce).[*]3/8/2007: Menneisyys wrote up an article expalining the change in the dial-up networking model changes in AKU 3.x.

Is the first section saying you are still working on a fix for the USB dial-up networking/modem problems?? Because the 2nd section describes a solution that only works with bluetooth. Is there a way to do this with USB? Sorry if you answered this above, I'm just slightly confused

I don't use the 6700 as a modem, so I really haven't followed this problem as close as others. From what I know, you can use both USB and now Bluetooth PAN to connect.

MrHappy · #23 (**permalink**) 03-21-2007, 01:03 PM

That is correct. Both USB and BT work using the new Internet Sharing application. The old Wmodem is still included in some roms and from what I have read the USB "sometimes" works with that app... Your best bet is to just use Internet Sharing as it, at least for me, works much more consistantly... Plus, you dont need any modem drivers

boe · #24 (**permalink**) 03-23-2007, 11:14 AM

Wahoo - I see they have a new version in the FTP site - wonder what parts of the project remain.

**schettj** · #25 (**permalink**) 03-23-2007, 11:51 AM

This version (still in pre-release!) has some fixes for stuff found in the previous pre-release, but still has a few details to clean up, and I believe one major effort to check all the drivers being used (bluetooth being the most notible one, but pretty much I think the developers are wanting to check em all) to make sure we've got the best ones possible in the kitchen. The bluetooth PAN isn't integrated yet either - it's a diver too, so it's hoped that it will get integrated in during the great driver cleanup effort.

I've been running the previous version for a couple weeks (I flagged a few of the bugs that got fixed, managed to work around them so I've kept the prev version on to really give it a workout) and it is indeed getting very close to a solid release.

I'm still swamped in real life, but I hope to burn this one and run it thru its paces this weekend.

Sogarth has been doing a great job "driving" the kitchen development effort... hats off to him and the other developers!

**willysp** · #26 (**permalink**) 03-23-2007, 01:38 PM

Could you guys please consider releasing a kitchen, not ROM, version of RC2? I'd love to import my customizations and OEM's, cook it, and try it out.

Sounds like you've made good progress over the last 3 weeks, but also sounds like release is several more weeks away at this point.

Please?

I know you're not likely looking for more testers at this point, but if that would allow me to get a copy, I'd love to help.

TIA!

**schettj** · #27 (**permalink**) 03-23-2007, 02:03 PM

It's my understanding that the release happens once the testing and documentaion is done. We're still just trying to get to the point that the testing and documentation can start

On the up side, it looks like every single 'todo' fix that is possible to fix (ie, we can't really get BT DUN back, it's supposed to be gone in 3.x, and it looks like it really is gone from the bits anyone can find) is actually going to be fixed once it is released. That's a ton of progress from even the 'woo hoo it works kinda sorta except for these 10 major problems' state we started with from the Helmi_c 3.5 kitchen - and that was a pretty amazing bit of work even to just get there.

Hang in there, it will get there.

**willysp** · #28 (**permalink**) 03-23-2007, 02:36 PM

Thanks for the clarification!

The term 'Release Candidate' confuses me then. RC typically means internal testing basically complete, developers feel it's very close to being done, and want some real world testing prior to official release.

If formal internal QA/testing hasn't begun yet, then you're more at alpha or beta level wrt end users. Which is perfectly fine, of course. I appreciate all the 'free' work you guys are doing in your spare time and look forward to a quality release.

Thanks again for the update.

**jamesus** · #29 (**permalink**) 03-23-2007, 07:40 PM

Quote:

Originally Posted by willysp

Thanks for the clarification!

The term 'Release Candidate' confuses me then. RC typically means internal testing basically complete, developers feel it's very close to being done, and want some real world testing prior to official release.

If formal internal QA/testing hasn't begun yet, then you're more at alpha or beta level wrt end users. Which is perfectly fine, of course. I appreciate all the 'free' work you guys are doing in your spare time and look forward to a quality release.

Thanks again for the update.

You bring up a good point, but since the naming style has already been decided upon, I think they will stick to that. I'm sure there will be a new name once the kitchen is stable enough for the public.

Alwaysbelieve1 · #30 (**permalink**) 03-24-2007, 12:10 AM

Quote:

Originally Posted by schettj

This version (still in pre-release!) has some fixes for stuff found in the previous pre-release, but still has a few details to clean up, and I believe one major effort to check all the drivers being used (bluetooth being the most notible one, but pretty much I think the developers are wanting to check em all) to make sure we've got the best ones possible in the kitchen. The bluetooth PAN isn't integrated yet either - it's a diver too, so it's hoped that it will get integrated in during the great driver cleanup effort.

I've been running the previous version for a couple weeks (I flagged a few of the bugs that got fixed, managed to work around them so I've kept the prev version on to really give it a workout) and it is indeed getting very close to a solid release.

I'm still swamped in real life, but I hope to burn this one and run it thru its paces this weekend.

Sogarth has been doing a great job "driving" the kitchen development effort... hats off to him and the other developers!

Regarding BT Pan I made a OEM for it and it works perfectly with every flash. What is the difference to what u guys are doing to or with it?