Mailing List os2-wireless_users@2rosenthals.com Archived Message #1306 | ![]() ![]() |
|
---|
Lewis G Rosenthal wrote::-) No, I feel that I at least should own up to being misleading in my earlier statement implying VxWorks was "Windows-based." Interestingly enough, that FAQ mentions some relation to WIND, so perhaps that's where I misunderstood a "Windows" derivation. No matter; thanks for understanding.
On 09/07/06 07:56 pm, Sam Lewis thus wrote :
Lewis G Rosenthal wrote:
On 09/07/06 12:37 pm, Dunhill Satellite Systems thus wrote :
For me no *doze in my network ! (or it must be a paying client)
UsaSat/Surfbeam is a straight tcpip connection (also with static IP) and
runs on VxWorks.
(Which is Windows, after all...) ;-)
I thought VXworks was built on VRTX? I don't think there are any similarities between VRTX and Windoze. :)
I stand corrected; you are closer to the truth of the matter, my friend. My earlier impression came from some faulty data I read concerning the latest round of LinkSys boxes (WRT54G v5) based on VxWorks. Here's an interesting link: http://www.xs4all.nl/~borkhuis/vxworks/vxw_pt0.html#0.1.
Apologies for the (my) confusion.
I don't see where an apology is needed for anything. I'm learning quite a bit here. And I'll read the Faq you linked.
Firmware replacements and modifications. As VxWorks is proprietary, it's not very receptive to opensource firmware (which typically includes the OS as well as the code). In contrast, Linux-based devices typically have not only more RAM in them, but also have firmware which is more easily replaced.As VxWorks is just about as ornery to deal with (as it's proprietary, we don't have many available hacks for it
What do you mean by "hacks"?
Subscribe: Feed,
Digest,
Index. Unsubscribe Mail to ListMaster |