Re: "Pwireless2 now in Quirky"

[jemimah]

Honestly I never had good luck with it on the command line either. That's why I use a configuration file in Pwireless2.

[darkcity]

Whats the difference between Pwireless2 and Frisbee? How come neither were included in Puppy 5.2?

[Béèm]

Nor Pwireless nor Frisbee were included in 5.2 because playdayz had decided so.
He stuck with Simple Network Setup and the classical network wizard.

[jemimah]

Not playdayz' fault. Frisbee is not ready yet, and I don't have the motivation to test Pwireless2 with LuPu.

[Béèm]

OK for Frisbee, but pwireless could have been included and playdayz didn't decide for it.
I did try the Frisbee I mentioned. It didn't work.
So I installed pwireless in 5.20.
It does work. Maybe good for you to know.

Apart from this, it doesn't solve my issue, but that's not the discussion here.

[jemimah]

I advised not to because I don't have a script that will make it work correctly with other network managers. If you read the pwireless2 thread you will see nothing but problems with pwireless2 trying to coexist with network wizard.

I've always intended pwireless2/frisbee to be the only network manager you need and haven't dedicated any time to making it play well with others.

[Béèm]

Jemimah, I appreciate that you always want to bring out a product that's quality. Indeed no need to get a sloppy product.

I started 5.2 with a new save file.
Didn't use SNS nor the NW wizard. So none of the two have generated config files.
Installed Pwireless2

Can there still be interaction then?
In this case, is your advice not to use Pwireless2 still valid then?

[jemimah]

Jemimah, I appreciate that you always want to bring out a product that's quality. Indeed no need to get a sloppy product.

I started 5.2 with a new save file.
Didn't use SNS nor the NW wizard. So none of the two have generated config files.
Installed Pwireless2

Can there still be interaction then?
In this case, is your advice not to use Pwireless2 still valid then?

That should work fine.

You may need to increase the sleep time in /etc/rc.d/rc.services if pwireless2 is starting before the driver for your NIC is done loading. I think that happens in LuPu a lot.

[Béèm]

Apparently I don't have timing problems.
But I still have my issue that quite some times an new page gives a 'address not found...........try again' panel.
Sometimes multiple pushing doesn't help and I see on the antenna a little cross, so no connection. However when I wait a while, without remaking the connection, all of a sudden it is established again and I can continue for a while.

I may have said it before, with Fluppy 10 and LightHouse 500G I don't have this problem.

I reported it in the Lucid thread several times now, but so far no reaction on it.

So Pwireless2 seems to be my easiest interim solution.