I save my old equipment just in case current stuff fails so I can at least have some service until replacement arrives. Although I'll bet that gem is several cycles back in the upgrade path.
Got three en104s with the bnc on the back of them on my desk right now--I use them as book ends. But I'm sure they still work.
There was a neat thread on the netgear forum where someone found a bug in then with a certain dhcp setup.
Yep, they still do. I even have two accton 8 port switches with bnc in service (actually have them connected via the BNC), similar to this one:The ones with BNC connectors - those are pretty old... but they likely still work
Do you have link to the netgear forum post?
It took a bit of digging, but here's the netgear link. Seems like DHCP IP address assignment makes for some weird issues:
It's interesting to watch a speedtest when connected to one of the 10base-t ports and see something like 6Mb when the connection is actually 30+.
Yeah, definitely a weird issue. I'm going to see if mine do it whenever I have time.That's odd - perhaps there's some latent functionality - but hubs shouldn't be concerned with IP layer, much less segment out MAC layer stuff... I can't see a hub having an issue, as long as it works, but if there is a switch in the middle, that might be something...
Hmm? 10BaseT PHY is 10Mbit, and half duplex at that - so 6MBps seems reasonable... The EN108 is a 10BaseT hub, so no surprise there
Then along came the treo 650 and I kept using it until gprs was turned off in the US.
Today's touch UI is overbloated with bad code and useless features. people dont really know how to code nowadays, its not a simple matter of just writing instructions as thats what you do in assembly. Writing code requires structuring, designing the program in the way of how it should run and be represented, in other words representing a task or algorithm in the most code efficient way.I'm soooo glad you shared this. I always loved the Palm (have one somewhere needing batteries as well), and always thought the ultimate phone would be a device married with this pda. Then along came the treo 650 and I kept using it until gprs was turned off in the US. I still have the 650 and it still powers on and works. And for UI it was light years ahead of todays 3-4 user operations to do something--everything was more intuitive and still efficient.
So cool that you've got that Palm. It's literally the great, great, great, great grandfather of the modern smartphone. Long live it!
Today's touch UI is overbloated with bad code and useless features.
I'm so glad to hear a designer say this. I feel like I'm screaming in a tornado because it doesn't seem like anyone realizes this--and that they deserve a lot better.Today's touch UI is overbloated with bad code and useless features. people dont really know how to code nowadays, its not a simple matter of just writing instructions as thats what you do in assembly. Writing code requires structuring, designing the program in the way of how it should run and be represented, in other words representing a task or algorithm in the most code efficient way.
battery life back than was great. Nowadays they dont seem to care about it anymore. Phones last time would last a week and so would some PDAs?
That's quite interesting. When I hook up a bt keyboard to my phone, I can navigate to almost all the same places using the arrow keys that would require a touch. I guess a lot of that is still in there. I wish they had more of it in there. Keyboard shortcuts? With the real keyboard I have on the phone, yes please!Believe it or not - Android was not initially designed for Touch UI - it was more like the classic Blackberry devices - as a mouse/keyboard type of device... TouchUI was grafted on after the fact when iOS was introduced on the iPhone... that's why the initial devices either had rollerball/touchpads or d-keys to navigate the UI back in the day...
I would love to see someone port the palm os to the android hardware platform. It might be a throwback, or it might be a revolution because of its simplicity--which ironically is how the modern smartphone started before it got so complicated.
Oh w wow! So let me rephrase then.Trust me - no you don't
At least not the Palm OS that was in the various Palm and licensed devices...
It was always pretty ugly under the hood, and later versions even more so - and the ARM port broke a lot of legacy stuff...
no memory protection, no real concept of multi-tasking, later versions did get a little bit better with application life cycle (and some of that DNA did make it into early versions of Android, e.g. the Binder API's that PalmSource inherited from BeOS for PalmOS Cobalt) - eventually that house of cards was bound to fall, and this is why Palm/HP moved to WebOS...
It's much like BBY moving from their Java based OS to the newer BB10 operating system based on QNX...
WebOS was kind of nice - certain aspects of the UI were pretty cool... unfortunately by the time the Palm Pre's hit the market, iOS and Android pretty much closed that door - same goes with BB10 on the RIM devices... some of the UI concepts have made it into various versions of Android and IOS (everything seems to be a remix these days).
WebOS is still around - powering smartTV's is the most common use, and of course, while RIM/Blackberry is perhaps on a deathwatch, QNX is still going strong in many industrial verticals and of course in automotive platforms - not just for the IVE, but also for the engine/transmission/channel computer complex...
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!