"Small administration fees" are normally charged when the update is distributed on some type of physical media. If I was getting PalmOS 3.5 on a CD, I'd pay for it. That would cover the cost of burning/stamping the CD's and shipping, along with the manpower they need for these processes.
But the fact is, PalmOS upgrades have in the past appeared on PalmOS software sites. Palm uses no more manpower or money in production for these updates than they normally do, and yet they want to charge now.
ok, please enlighten me, because I don't seem to understand...
Why exactly is it that the RPM's were built on a "nonstardard install"? Isn't the point of an RPM to be a package installed on a particular distribution? In other words, I downloaded the mandrake RPM's because I'm running mandrake on this machine. The RPM should be for use on a standard distribution.
Now, if this is BETA software, why would they put the package together in a nonstandard way? It seems to me that they're asking for problems. And it also seems they don't realize that those who try their RPM's aren't going to go through the trouble of using the final release if the RPM's didn't work. Wouldn't you agree?
I mean, I was using the thing 10 minutes and found 5 huge problems. If this was the latest Windows BETA everyone would jump on top of it, but because it's KDE it's somehow ok? Come on!
While I know compiling is always the best choice, in my case, it wasn't realistic. RPM's were the next best choice. Unfortunately, according to you, someone had the genius to make them in a "nonstandard" way. And well, that's their mistake.
I didn't like KDE two years ago, I should've known I'd have problems with it today.
ok, I looked at the KDE2 pages and thought it'd be cool to try out. After all, I haven't used KDE since version 1, and I thought it was about time I gave it another chance.
Let me get this straight... This is the 5th BETA, and the next release will be the official one, right? Folks, if that's true, I'm afraid the public is going to be disappointed. I mean, goodness!
I downloaded all the packages listed. Installed them all. Started up KDE and was prepared to be impressed...
Hmm, that bottom bar is a bit big. That's ok, just right click and change it to "Tiny". What's this? The Main Menu and the desktop chooser buttons suddenly become question mark documents? ok.. bug, I guess.
Well, I heard that Koffice was cool. I'll try that. Click KWord. Nothing happens. Click it again. Nothing happens. Same with KSpread and KPresenter. Hmm, don't tell me the install went wrong. I used the official BETA RPM's on their site. I know, I could've compiled, but I shouldn't have to.
Well, how about Konquerer at least? Hmm.. same thing as Koffice. One last try... Click the File Manager link in the menu. Comes up at least, with the name Konquerer in the header, but all I see is gray with a Help button in the menu.
Well, now I guess it's time to dust off the good ol' rpm -e.
btw, in case someone tries to tell me to compile it... ya, you sit through compiling it. If the RPM's weren't meant to work, they shouldn't have been on the site.
The Palm VII, IIRC, uses AAA batteries, and so it suffers from the same problem of leaving the serial port open. The versions that include a rechargeable lithium battery do charge on the cradle though.
I *thought* this would be a neat idea, but I think I figured out why there's no way that it'll ever work.
ok, it basically lets you dial "into" your palm and speak to it in order to retrieve information.
First of all, how many Palms are connected at this moment? As in, how many Palms have a modem attached which is attached to a phone line or wireless? Maybe leave it in the cradle and you call into your desktop? Nope, because leaving your Palm in the cradle automatically leaves the serial port open which wastes batteries.
And another thing... When would you use this? My guess would be in a situation where you didn't expect that you's need your Palm. And so what are the chances that you'd have actually set it up to receive your call in the first place?
I just don't think this will ever fly. To quote the Daily Show, these two go together like cookies and ass.
we have a hand-held radio that does basically the same thing. When you hit the transmit key, any monitor in the vicinity has it's picture jump around for an instant.
We haven't had any components fail yet, but I still think it may be dangerous. Anyone run into this before?
Well, all told, most cracks are easily fixed. That doesn't mean they weren't creative.
The Usenet thing is interesting, but the IRC thing was done first. Your version is simply improving on an existing crack, which is kinda kiddie-ish, IMO.
it's really quite beautiful. I mean, send out a program, have it connect to a channel, and send it instructions through the channel. That's just plain cool.
While I know cracking is a bad thing, I think some of these guys should get an award for creative thinking. And to see a *real* cracker break into a system with definite, calculated measures... it's just... wow.
Sorry, I know they shouldn't be given extra reason to do this stuff, but I stand impressed.
BeOS wasn't designed for the user to use a CLI. Hence, as a new user, I shouldn't have to. I don't know the file structure of BeOS, so a CLI doesn't make much difference to me anyway.
I'm losing interest in this. Maybe we can talk about it some other day.
I hate to say it, because you seem very honest, but that's the best you can give me?
I mean, you're a "be-fan" and I get an explanation that gives me no hope for the future of Be. Honestly, I mean no disrespect, but that's the whole reason the Be is going nowhere. I sincerely *don't* believe it to be the OS that people need. It's a niche right now, though I know no one in that niche, and I think it's destined for failure.
btw, ya it's hard to use. Those video drivers are a perfect example. In order to place them in the correct directory, I need to drag the file through eight million menus. While making everything graphical seems easier, you're just wasting time. It's easier to go to a prompt and type cp file/././file. And yes, I know Be has a terminal, but it wasn't designed for that type of operation.
Also, just navigating the menus is a pain. And using the file manager is an exercise in futility.
Granted, I used it a total of about a week. But if that OS is truly easy to use, I should have no problem with it. I shouldn't have to know little 'tricks'. I should be able to put my hand on the mouse, and make it work the way I want it to. It doesn't, and so I see no advantage to using BeOS over any other OS on the market.
Slashdot Mirror
Heh.
"Scriptkiddiot". I like that.
_______________
you may quote me
please.
phillip@ryals.com
_______________
you may quote me
I remember that! I don't remember the name though. Someone did it in PalmOS, but it wasn't as good as I remember.
_______________
you may quote me
Am I the only one left with a bad taste in the mouth after reading that article?
or maybe it's this coffee.
_______________
you may quote me
"Small administration fees" are normally charged when the update is distributed on some type of physical media. If I was getting PalmOS 3.5 on a CD, I'd pay for it. That would cover the cost of burning/stamping the CD's and shipping, along with the manpower they need for these processes.
But the fact is, PalmOS upgrades have in the past appeared on PalmOS software sites. Palm uses no more manpower or money in production for these updates than they normally do, and yet they want to charge now.
_______________
you may quote me
Hmm...
What I'd really be interested in is why a personal experience qualifies as flaimbait.
Oh well, maybe Meta Moderation will come to the rescue.
_______________
you may quote me
ok, please enlighten me, because I don't seem to understand...
Why exactly is it that the RPM's were built on a "nonstardard install"? Isn't the point of an RPM to be a package installed on a particular distribution? In other words, I downloaded the mandrake RPM's because I'm running mandrake on this machine. The RPM should be for use on a standard distribution.
Now, if this is BETA software, why would they put the package together in a nonstandard way? It seems to me that they're asking for problems. And it also seems they don't realize that those who try their RPM's aren't going to go through the trouble of using the final release if the RPM's didn't work. Wouldn't you agree?
I mean, I was using the thing 10 minutes and found 5 huge problems. If this was the latest Windows BETA everyone would jump on top of it, but because it's KDE it's somehow ok? Come on!
While I know compiling is always the best choice, in my case, it wasn't realistic. RPM's were the next best choice. Unfortunately, according to you, someone had the genius to make them in a "nonstandard" way. And well, that's their mistake.
I didn't like KDE two years ago, I should've known I'd have problems with it today.
_______________
you may quote me
ok, I looked at the KDE2 pages and thought it'd be cool to try out. After all, I haven't used KDE since version 1, and I thought it was about time I gave it another chance.
Let me get this straight... This is the 5th BETA, and the next release will be the official one, right? Folks, if that's true, I'm afraid the public is going to be disappointed. I mean, goodness!
I downloaded all the packages listed. Installed them all. Started up KDE and was prepared to be impressed...
Hmm, that bottom bar is a bit big. That's ok, just right click and change it to "Tiny". What's this? The Main Menu and the desktop chooser buttons suddenly become question mark documents? ok.. bug, I guess.
Well, I heard that Koffice was cool. I'll try that. Click KWord. Nothing happens. Click it again. Nothing happens. Same with KSpread and KPresenter. Hmm, don't tell me the install went wrong. I used the official BETA RPM's on their site. I know, I could've compiled, but I shouldn't have to.
Well, how about Konquerer at least? Hmm.. same thing as Koffice. One last try... Click the File Manager link in the menu. Comes up at least, with the name Konquerer in the header, but all I see is gray with a Help button in the menu.
Well, now I guess it's time to dust off the good ol' rpm -e.
btw, in case someone tries to tell me to compile it... ya, you sit through compiling it. If the RPM's weren't meant to work, they shouldn't have been on the site.
_______________
you may quote me
Cuz I'm Doug, and I'm outta heeeeaaar.
_______________
you may quote me
Good point.
The Palm VII, IIRC, uses AAA batteries, and so it suffers from the same problem of leaving the serial port open. The versions that include a rechargeable lithium battery do charge on the cradle though.
_______________
you may quote me
I *thought* this would be a neat idea, but I think I figured out why there's no way that it'll ever work.
ok, it basically lets you dial "into" your palm and speak to it in order to retrieve information.
First of all, how many Palms are connected at this moment? As in, how many Palms have a modem attached which is attached to a phone line or wireless? Maybe leave it in the cradle and you call into your desktop? Nope, because leaving your Palm in the cradle automatically leaves the serial port open which wastes batteries.
And another thing... When would you use this? My guess would be in a situation where you didn't expect that you's need your Palm. And so what are the chances that you'd have actually set it up to receive your call in the first place?
I just don't think this will ever fly. To quote the Daily Show, these two go together like cookies and ass.
_______________
you may quote me
Actually, this type of post is what's getting old.
Get a life. Well, one that doesn't require pointing out problems with Slashdot submissions.
_______________
you may quote me
we have a hand-held radio that does basically the same thing. When you hit the transmit key, any monitor in the vicinity has it's picture jump around for an instant.
We haven't had any components fail yet, but I still think it may be dangerous. Anyone run into this before?
Could the originals recieve commands through IRC? If not, then his is still a new idea.
Just because Linux users use VMWare to run windows?
yes.
Well, all told, most cracks are easily fixed. That doesn't mean they weren't creative.
The Usenet thing is interesting, but the IRC thing was done first. Your version is simply improving on an existing crack, which is kinda kiddie-ish, IMO.
it's really quite beautiful. I mean, send out a program, have it connect to a channel, and send it instructions through the channel. That's just plain cool.
While I know cracking is a bad thing, I think some of these guys should get an award for creative thinking. And to see a *real* cracker break into a system with definite, calculated measures... it's just... wow.
Sorry, I know they shouldn't be given extra reason to do this stuff, but I stand impressed.
800MHz Thunderbird with ATA/100 and a 28.8 modem?
um... what's wrong with this picture?
in which no other countries participate.
Um... Japan?
Sure, it's a kind of token game, but Dallas plays there every year now.
Where do you (whoever you are) get off moderating this as "flaimbait"?! Come on!
I've never used Amazon. And I couldn't be happier with that fact until now.
Your point is moot.
BeOS wasn't designed for the user to use a CLI. Hence, as a new user, I shouldn't have to. I don't know the file structure of BeOS, so a CLI doesn't make much difference to me anyway.
I'm losing interest in this. Maybe we can talk about it some other day.
yes yes, I know.
I've spent so long studying turbines, I guess I'm just tired of them.
I *would* like to advocate a new paradigm though. If I only knew which one. While turbines work, they really do let a lot of energy get wasted.
Apparently you haven't been listening.
I did that. And your magical BeOS did *not* automatically recognize it and use it.
And as ranessin already said, it's not configured in modules.conf. No wonder you're griping so much, you've never done it.
Hmm.
/././file. And yes, I know Be has a terminal, but it wasn't designed for that type of operation.
I hate to say it, because you seem very honest, but that's the best you can give me?
I mean, you're a "be-fan" and I get an explanation that gives me no hope for the future of Be. Honestly, I mean no disrespect, but that's the whole reason the Be is going nowhere. I sincerely *don't* believe it to be the OS that people need. It's a niche right now, though I know no one in that niche, and I think it's destined for failure.
btw, ya it's hard to use. Those video drivers are a perfect example. In order to place them in the correct directory, I need to drag the file through eight million menus. While making everything graphical seems easier, you're just wasting time. It's easier to go to a prompt and type cp file
Also, just navigating the menus is a pain. And using the file manager is an exercise in futility.
Granted, I used it a total of about a week. But if that OS is truly easy to use, I should have no problem with it. I shouldn't have to know little 'tricks'. I should be able to put my hand on the mouse, and make it work the way I want it to. It doesn't, and so I see no advantage to using BeOS over any other OS on the market.