I have offered these over at webDT.org (http://webdt.org) and they have been loving them
So to the Linux MCE gang.
As usual - WEBDT 366s for sale - Band new still in the box - $ 75.00 :o
or
Take two WEBDT 366s - Band new still in the box for only - $ 135.00
Either way I will through in 2 x 250Gb SATA Western Digital HDDs 3.5" - Brand new of course. for $35.00
SO
•one DT366 & two HDDs for $110.00
or
•Two DT366 & two HDDs for $170.00
Private Message me if you're interested.(http://public.bay.livefilestore.com/y1px8zapuhGOgRUim-I29Zoh8h2qvIMgJ1hxTgTpDbMMcAKq-z0zDS2J4XyPsu8FN2IRVIIGr0BZgVJLgGRCc1i7Q/DSC00569%20(800x450).jpg)
This is the Geode LX 800 model
512 of Flash
512 of Ram
Mini-PCI Intel Pro/Wireless 2200BG network card
Comes with....
(http://2onlgg.bay.livefilestore.com/y1pRsz3l6TmZp7LAMYB0Et87mK5PniMGnnrvyPQn3Xx1GkPCYjxYqrLFZMkjmCtgT0nKcYj4MTf9IoQDwe712SyKE6fRMkIb8ra/366.jpg?psid=1)
I have external batteries coming before the end of the year. PM me if you want your name on the list for one.
$40.00 each
How much is shipping to EU, and do you accept PayPal
How many of them do u have? Do you get them on a regular basis?
Does WebDT 366s support WPA/WPA2?
If so, does it out of the box or is it needed some hacking?
thanks and regards
Marco
been doing some research and unfortunately it seems like they do not. WPE only(what where they thinking..)
I think it is also mentioned in the specs that can be found somewhere in the big dark internet...
-johan
The Cisco Aironet 350 that is installed in those devices does not support WPA/WPA2.
-Thom
would be interested too, depending on EU shipping prices and payment options :)
-Coley.
Quote from: tschak909 on September 22, 2010, 04:20:52 AM
The Cisco Aironet 350 that is installed in those devices does not support WPA/WPA2.
-Thom
the card itself supports wpa with later firmware versions, but the linux driver does not. There is an experimental driver, but that does not work properly.
br Hari
Good Morning
I've not had a chance to check this out yet, but it appears that these WebDT 366s from tbowland may support WPA/WPA2 encryption. According to this (http://webdt.org/index.php?topic=421.0) and tbowland's original post in this thread, these WebDTs have an Intel 2200 Pro mini-pci card. According to this (http://www.thinkwiki.org/wiki/Intel_PRO/Wireless_2200BG_Mini-PCI_Adapter), this card is supported by the Linux ipw2200 driver. According to this (http://www.thinkwiki.org/wiki/Ipw2200), WPA and WPA2 work with ipw2200 drivers >= 1.0.2 using wpa_supplicant.
I just moved back into my house from a fire last fall, so it will be a looooooong time before I get a chance to look into this with any depth. I did buy 2 of these WebDTs from tbowland, so I will look into this in a couple months if nobody else has before then. Just thought I'd throw this nugget out there if somebody else is interested.
As a side note, not that it matters to me or likely to many others around here, these WebDTs from tbowland do not come with an operating system.
As a second side note, WebDT owners should check out the webdt.org (http://webdt.org) website. Some interesting reading there, including mods to upgrade the internal flash IDE chip to 4 GB. :o
A last side note, just in case anybody else is wondering why these say "Ambia (http://ambiahome.com/Default.aspx)" in the corner.
Bryce
[edited to add Ambia link, and clean up hyperlinks]
tbowland.. you have emails in your inbox (or spamfilter) from me.
Hello tbowland,
are there any devices left?
What are the shipping costs to Europe/Austria?
Regards
Johannes
A couple of notes to anyone looking at these right now:
The WebDT 366DT LX systems have a smaller internal drive than the WebDT 366GX (the device the current padorbiter installs onto). This means that padorbiter will not install onto these units.
I purchased 4 of these units and after a couple of weeks they arrived. 3 of the 4 units are working perfectly and I have shoe-horned padorbiter onto them with the wireless firmware and squeezeslaves on them as well. My squeezeslaves address themselves with leading zeros followed by the 2nd half of the webpads mac address to allow me to easily configure them on the core. There is decent battery life in the 3 working units. I can confirm the intel wireless g ipw2200 card is present. I have not tested wpa yet. They come with european 240v plugs on the cords, the power supplies are universal though so it's trivial to cut the ends and replace them.
Unfortunately one of my units arrived defective. My attempts have been completely unsuccessful installing any operating systems on this one unit. The install attempts have all failed part way through (they are successful on each of the other 3 webdts). I have sent an e-mail to tbowland and I am waiting to hear if he will replace this defective unit.
I'll post the resolution when I receive a response from tbowland.
J
I'm waiting for a response from tbowland, and it would seem many people are in the same situation:
PM could not be sent to 'tbowland' as their inbox is full!
tbowland, you need to delete some messages, or get back to us by e-mail...
I ran the bad unit through a bunch of tests and it ended up failing a MemTest86+. It has been put in the mail to be returned and he says he'll ship me a new one. I will admit that he hasn't been the most prompt of individuals to respond but he has been dealing with me and my problem.
I'm incredibly happy with these LX units vs my old GX. They are MUCH faster. With the increased processing capability and the 802.11g they easily run Orbiter and stream from .flac or .mp3 files to squeezeslave wonderfully.
It was not a simple 'plug n play' to get this up and running with the padorbiter distro. The drive size was the biggest issue to overcome. I tried resizing the image multiple times and never got the partition defined quite right. Had to do a fresh debian install to get a proper partition defined and imaged. Then the video was a bit of a pain as the vesa framebuffer causes white pulsing on the LX's screen. The framebuffer driver has to be set at boot and it works great in the console. Once booted the LX framebuffer doesn't wake-up from suspend properly under X, not sure why but it's not pretty, so I switched to the geode driver in X and it resumes just fine. The IPW2200 firmware had to be copied onto the webdt before the wireless would operate. The wireless card doesn't seem to wake up as quickly as the cisco card in the GX (at least that's the best I've come up with) and consequently Orbiter takes a bit before timing out and restarting. As a simple solution I kill Orbiter on resume, which restarts Orbiter in a couple seconds rather than 10 or 15. USB2.0 on the LX vs USB1.1 on the GX makes installing an image 5x faster. Took me a little over a week to figure out what to do and learn what I needed to do to make it happen.
If there is enough interest I will post an image of what I have, but that should be reserved for another thread.
J.
QuoteIf there is enough interest I will post an image of what I have, but that should be reserved for another thread.
J.
Interest! Interest! Interest!
I'll have to find somewhere to upload it to.
J.
Image: http://forum.linuxmce.org/index.php?topic=10914.0
edit. deleted my question after proper search ;)
-johan
ouch.. seems like I have one bad unit also.. upper most left led is constant lit when turning power on(in craddle or without) battery indicator is off course lit as well.
Strange.. almost like the cpu would be dead since I dont see anything happening with the screen and it does not even load the bios.
so
power on
blue led no1 constant lit.
nothing more..
- should have bought 4 =) (one as spare)
Is it still available? :) :) :)
Id like to know if any of these are still available also.
Thanks
QuoteId like to know if any of these are still available also.
Careful there. Adding in the two duds that were sold to me brings it to a total of 4 bad units sold in this thread already.
Bryce
guys, you get what you pay for.
Grab a good unit from lmcecompatible.com
-Thom
After my final experiences I wouldn't recommend buying from tbowland. The model itself is great though if you can find reliable stock.
J.
Quote from: phenigma on February 17, 2011, 12:52:27 AM
After my final experiences I wouldn't recommend buying from tbowland. The model itself is great though if you can find reliable stock.
J.
yeah i read a couple dead units but seems that you were able to ship it back and get a replacement right?
$350 each on lmcecompatible vs $75 is a pretty big difference and might be worth the risk as long as the guy will replace any duds that are sent out.
I did get mine replaced... It was at least 2 weeks after I had paid for the initial units before he shipped anything to me, and that happened because I contacted him. The defective unit I had arrived with a Windows installation on it that was BSoDing on boot with a licence violation error. I ultimately determined it had defective RAM. After I shipped my defective unit back to him he claimed to have copied an operating system onto the flash drive (which I was able to do quite well, it was failing memtest86 over a large chunk of RAM) and he was going to resell it. He then tried to give me a story about how much money he was losing and wanted me to pay for more shipping after I had received my replacement... This process was a pain and ultimately took 8-10wks to resolve.
I don't recommend purchasing from him.
I saw the price and gambled. The DX model he was selling is nice, it's 586 based and very responsive with a nice wireless NIC. GX units are 486 based and have wireless NICs that really only support WEP encryption (see Thom's & Hari's posts earlier in this thread). I figured I could get 4 (could actually have got 7) from this guy, with charge cradles, for less than the price of 1 from lmcecompatible (@USD$459.98+tx with a charge cradle) and if only 1 worked...
If I was to do it again I'd probably go for an Archos 7 Home Tablet and use an Android Touch Orbiter.
J.
phenigma,
a real orbiter (as the PadOrbiter running on the WebDTs) is much nicer than a Touch Orbiter.
My .02€
Fwiw, I bought two units from Ted. Neither unit will boot/recognize the USB port on it's side. Specifically, when I plug in a bootable USB drive and turn it on, neither unit will boot from the USB drive. They both go to a blue screen, then back to black and give the error "Attempting to boot a Hard Drive... Invalid system disk Replace the disk, and then press any key." Also, on one of the units, the first 2 of the 3 lights do not light up at first boot. I do have a third WebDT 366 (a GX, not purchased from Ted) that has no issues booting from my bootable USB drive, so I know that the USB drive is okay.
When I first contacted Ted about this, his reply was that I don't have a real problem, he could help me get something loaded, and he would send out another e-mail shortly with some info. After that, despite multiple e-mails from me, I never heard from him again.
Bryce
It could be that the purpose of your life is to serve as a warning to others. (http://www.despair.com/mis24x30prin.html)
Quote from: posde on February 18, 2011, 08:00:10 AM
phenigma,
a real orbiter (as the PadOrbiter running on the WebDTs) is much nicer than a Touch Orbiter.
My .02€
A very good point.
J.
Quote from: brake16 on February 18, 2011, 11:29:19 AM
Fwiw, I bought two units from Ted. Neither unit will boot/recognize the USB port on it's side. Specifically, when I plug in a bootable USB drive and turn it on, neither unit will boot from the USB drive. They both go to a blue screen, then back to black and give the error "Attempting to boot a Hard Drive... Invalid system disk Replace the disk, and then press any key." Also, on one of the units, the first 2 of the 3 lights do not light up at first boot. I do have a third WebDT 366 (a GX, not purchased from Ted) that has no issues booting from my bootable USB drive, so I know that the USB drive is okay.
Have you gone into the BIOS and set the boot order to boot from the USB? None of my units booted straight off the USB they were all set to boot from the internal flash HDD on arrival.
I also had one unit that the BIOS was set to output through some non-existent video device. Result was nothing but a black screen. I read a little on webdt.org and was able to hit the proper keys at the proper times to set BIOS back to defaults so it would show me a display again. After this I entered BIOS and configured it for USB boot, no problems since.
J.
phenigma, brake, and others thanks for the info.
Yeah doesnt sound like it would be worth the risk if there was no communication, etc. Doesnt seems like there are any available anyway so it doesnt matter but i appreciate the warning and the info.
Guys, you can get them from http://www.lmcecompatible.com/ and proceeds from that fund development.
-Thom
Quote from: posde on February 18, 2011, 08:00:10 AM
phenigma,
a real orbiter (as the PadOrbiter running on the WebDTs) is much nicer than a Touch Orbiter.
My .02€
I'm not knocking PadOrbiter...but I really dont think thats true in fact. The N800 Orbiter and PadOrbiter carry all of the baggage of the full Orbiter ie code complexity for no purpose, the need to update the Orbiter whenever new screens or other structural UI changes are made to the system they are attached to (which means that someone has to add support in source code for those screens to each orbiter implementation). There is no performance gain to speak of either.
Whereas with Touch Orbiters the only code that needs to be updated is proxy_orbiter if new screens etc are added - and you do that code change once for all Touch Orbiters and all systems that use them. So given reasonable hardware ie mid market Android device (some low cost Android devices are a little underpowered with the current Java based Android Touch Orbiter), pretty much any Arm based touch device, Any Atom based touch device and any iOS device then your experience will be good.
The battery life off the DT366 is pretty limited too... but thats purely a hardware limitation.
My .02€
All the best
Andrew
well, nevermind that no matter what is done, there is a hard limit to what Proxy Orbiter can render. No matter what, you're rendering single images, and sending whole images back in every single event.
This is one reason, I am currently doing the Java DCE port, to do a real Android based Orbiter, that uses native widgets.
-Thom
Quote from: totallymaxed on February 23, 2011, 02:28:24 AM
I'm not knocking PadOrbiter...but I really dont think thats true in fact. The N800 Orbiter and PadOrbiter carry all of the baggage of the full Orbiter ie code complexity for no purpose, the need to update the Orbiter whenever new screens or other structural UI changes are made to the system they are attached to (which means that someone has to add support in source code for those screens to each orbiter implementation). There is no performance gain to speak of either.
It is not that I am making this up. SWMBO yesterday told me "this other thingie is much nicer". I looked at her puzzled, until I realized she meant the WebDT being much nicer than the 7" android. I asked her why, and she said, it is much faster... This comes from a person who is absolutely, postively, without a doubt, NOT computer literate. ;)
Quote
Whereas with Touch Orbiters the only code that needs to be updated is proxy_orbiter if new screens etc are added - and you do that code change once for all Touch Orbiters and all systems that use them. So given reasonable hardware ie mid market Android device (some low cost Android devices are a little underpowered with the current Java based Android Touch Orbiter), pretty much any Arm based touch device, Any Atom based touch device and any iOS device then your experience will be good.
This is not relevant from the user perspective. They want the best experience they can get, and it seems, the user, does get a better experience from a native orbiter.
QuoteThe battery life off the DT366 is pretty limited too...
That is 100% accurate. Which is why we keep it at the charger most of the time. No idea, if newer batteries would help.
Quote from: posde on February 23, 2011, 08:19:39 AM
It is not that I am making this up. SWMBO yesterday told me "this other thingie is much nicer". I looked at her puzzled, until I realized she meant the WebDT being much nicer than the 7" android. I asked her why, and she said, it is much faster... This comes from a person who is absolutely, postively, without a doubt, NOT computer literate. ;)
I definitely agree with what your saying above if the 7" Android tablet your SWMBO was using was not a top-end device - the DT366 wins out (apart from on battery life thats is!). But if you do the same comparison with someone who has a high-end Android 7-10" tablet running Touch Orbiter then our experience with similar users is the reverse - performance is as good or better and on weight & battery life the Android device wins easily. So I guess what i am saying is that you need to compare Touch Orbiter on more comparable hardware.
For example if we put an iPad running Touch Orbiter into the mix then the iPad will beat everything currently - it is really fast and in all other areas from a non-technical users perspective it is close to ideal. Honestly we have customers who are totally won over by the iPad...it a big win for anyone who has a SWMBO honestly!
Quote
This is not relevant from the user perspective. They want the best experience they can get, and it seems, the user, does get a better experience from a native orbiter.
Again our experience is that if the physical device is equivalently 'nice' ie iPad or high-end other touch pad style device then Touch Orbiters deliver a fantastic user experience to the user. At the end of the day we sell what the SWMBO's of this world want...because they are very often the key to making a 'sale' to be frank!
Quote
That is 100% accurate. Which is why we keep it at the charger most of the time. No idea, if newer batteries would help.
Hmmm...they help a little but not really that much. The distributor of the DT's here in the UK says that they have always had complaints about buttery life...its the biggest complaint from their customers.
All the best
Andrew
We probably should split this topic and move it to user, but apart from that, one thing that really is a bother with the touch orbiter, is the fact, that sometime it does not update the screen correct, i.e. it never shows the TV remote after selecting TV. This works perfectly with the native (Pad)Orbiter.
If your customers are happy with their iPads, I am happy for them. I personally find 400-500EUR for a remote a bit pricey. But if people already have an iPad (or use it for other stuff as well), the price point might be more interesting.
Quote from: posde on February 23, 2011, 06:35:35 PM
We probably should split this topic and move it to user, but apart from that, one thing that really is a bother with the touch orbiter, is the fact, that sometime it does not update the screen correct, i.e. it never shows the TV remote after selecting TV. This works perfectly with the native (Pad)Orbiter.
If your customers are happy with their iPads, I am happy for them. I personally find 400-500EUR for a remote a bit pricey. But if people already have an iPad (or use it for other stuff as well), the price point might be more interesting.
We dont have the problem with the TV remote that you describe so thats not an issue and in general many of our customer have iPod's, iPhone's or iPad's already and so sticking with them is not an issue for them either. For those customers that have Android devices or would prefer a lower price point then they have that option too and as long as you dont choose a low-spec Android device performance is really excellent.
Splitting the topic seems a good idea but we've probably done the topic to 'death' now anyway :-)
All the best
Andrew
Quote from: phenigma on February 18, 2011, 01:52:06 AM
If I was to do it again I'd probably go for an Archos 7 Home Tablet and use an Android Touch Orbiter.
J.
phenigma
In your opinion how does the Archos 7 Home tablet compare to the Nokia n800??
I have the option right now to get either of them for about the same price. Looking at it the Archos looks like it would be better but looking through the wiki and the forums i dont see much mention of the Archos 7 Home tablet.
thx
The Archos 7 for now would run the Android proxy orbiters (two developers have written them, darrenmason and los93sol).
While the Nokia N800 would run the native Orbiter that was built for it. (http://diapub.com/~michael)
-Thom
As Thom says 2 different Orbiter software flavours, two very different devices, it really depends on how you want to use it.
The n800 kinda fits in your pocket, I find that Orbiter causes the batteries to drain pretty quickly, so it has to stay plugged in the majority of the time. It can be tough to hit some of the buttons without using the stylus. My n800 lives on my Dining Room table, it's very small and unobtrusive.
The Archos, I've only used one (an Archos 7 Internet Tablet) for about 5 minutes, I liked it for the most part. It ran Android (lots of apps), it was snappy and the screensize is bigger, which is better for 'coffee table' Orbiter use (flimsy built-in stand). I have not had a chance to try Orbiter or TouchOrbiter on an Archos itself. The Archos 7 Home Tablet is the same size with less speed/graphics capability than the Internet Tablet and would be more than enough to run Orbiter alone.
It comes down to what you want to do with your device and how you want to use it.
J.
as soon as there is a known meego build for Archos7, I will port PadOrbiter v2 to it.
-Thom
Thom and Phenigma thanks for the info.
I had taken a look at the 2 Android orbiters. I would probably more go for the simpler direct one that darrenmason did because right now i dont see myself needing to access stuff from outside my network and some of the other features that the other one has. But im still in the process of piecemailing my system together so once its up and im actually using it then that opinion might change. Would be interested in seeing how the PadOrbiter would look on the Archos7. Hopefully the meego build will come out soon.
Right now im only thinking of having the "couch orbiter" that i would use on the couch in the living room to control lighting and media but eventually i would like to put in some built in wall orbiters at the front and back door to control stuff.
The N800 GUI does look amazing but it is kinda small. It would work for the living room orbiter but would prob not work too well as a wall mounted orbiter. Ill probably lean more towards the n800 for now because i just found out the Archos tablet i was looking at is running Android1.6 instead of 2.1 like was advertised.
Thanks for the info guys. Im still trying to put all this together in my head on what i want and how i want my system to work.
edit: typos