Slashdot Mirror

Where have I seen something like this before...
oh yeah...
and that too...

Where have I seen something like this before...
oh yeah...
and that too...

http://www.sco.com/scosource/
What is this about? You can run a binary only version of Linux and you have to get a licence from sco? haha.. I wonder about my WRT54G from Linksys that just happens to be Linux based.
(I noticed I can program the most annoying things over and over while drunk and high)

http://www.sco.com/scosource/
What is this about? You can run a binary only version of Linux and you have to get a licence from sco? haha.. I wonder about my WRT54G from Linksys that just happens to be Linux based.
(I noticed I can program the most annoying things over and over while drunk and high)

Linksys 802.11g cards (and the new version of their 802.11b PCI card) don't work in linux. The chipset manufaturer, Broadcom, is holding back specifications on the card. If you want 802.11g in linux, the best solution is the D-Link card, or the Netgear one. Both use the Intersil Prism GT chipset. Intersil is very open about their design, and supports the development of open source drivers for Linux and other operating systems. Even if Broadcom were to open up, Intersil is more likely the company you would be wanting to give money to.

Still, drivers for the Broadcom chipset would be nice, so take a minute to sign the petition.

Linksys 802.11g cards (and the new version of their 802.11b PCI card) don't work in linux. The chipset manufaturer, Broadcom, is holding back specifications on the card. If you want 802.11g in linux, the best solution is the D-Link card, or the Netgear one. Both use the Intersil Prism GT chipset. Intersil is very open about their design, and supports the development of open source drivers for Linux and other operating systems. Even if Broadcom were to open up, Intersil is more likely the company you would be wanting to give money to.

Still, drivers for the Broadcom chipset would be nice, so take a minute to sign the petition.

Since the whichever shitbag monitors AskSlashdot submissions shot down my question, here goes:

I'm looking for a hardware audio/video streaming solution to push content to my home theater, but haven't had any luck finding anything using the popular search engines. Can anyone suggest a hardware solution that supports 802.11b, has both S-video as well as RCA jacks, and won't stick out like a sore thumb on my entertainment center? I'd prefer at least MP3, AVI and Mpeg support at the very least.

I've seen LinkSys' solution, but surely they're not the only ones with such a product on the market. Their price is right (about $170) but I've not had much luck with their wireless products.

Anyone care to recommend a good firewall or perhaps firewall/router box for a home/small business network.

Not personal/single machine jobs, but standalone units.

If you want a dedicated appliance, check out the various routers from Linksys and D-Link; they provide a nice, easy-to-use solution in one little box. While I haven't used any personally, I've helped many friends set up connection sharing and firewalling with them; both brands make good products. Also, they have features you might find useful: integrated switches, wireless access points, etc. They don't tend to be as featureful or customizable as Linux-based solutions like SmoothWall, but if you're willing to sacrifice those qualities for convenience, ease of use, and a support hotline, they can be good deals.

For various repairs I've had to do over the years, I've developed a nice toolkit that will handle anything I've seen so far.

* a firewire-ide bridge (here, look for firewire drivedock)
* an IDE cable
* a floppy cable
* a network cable
* several usb/serial/parallel cables
* a laptop with firewire and a cd burner, IE a Sony Viao or Apple iBook with windows or mac os and linux installed
* a hard drive full of cd images for various operating systems
* a hard drive full of windows updates/mac updates/updates for whichever UNIXy os you carry with you
* a phillips scredriver
* a slotted screwdriver
* a torx t9 and t8 screwdriver (for laptops)
* an external firewire drive to do backups
* a USB NIC (here's one)
* drivers for the aformentioned USB NIC.
* alternatively, a $10 PCI ne2000 NIC.
* a stack of cheap cds.
* a modem for your computer if it didn't come with one

I also use a Palm m515 with a serial cable and a program called pTelnet wich will act as a serial console program for Linux/BSD and non-free unix machines.

it might differ from the standard busybox, but does it differ from the busybox from the linksys code center http://www.linksys.com/support/gpl.asp? If the linksys binary matches the source code they have published I dont really see a problem.

. . . between this and a normal wireless bridge? Judging by the Linksys Prodcut Listing, you still have to buy an ethernet adaptor for the console. It *does* look cool, and perhaps it is easier to configure than the wireless bridges that are on the market now?

Um.... here is one!

And according to the weblog, the gpled code can be downloaded here

And it can all be downloaded from the web here

Linksys Wireless Router supports IPSec. It costs about $70. Not the cheapest, I guess, but certainly less than $400.

I agree.

I've had a linksys BEFW11S4 v1 for almost 3 years now.

I've never had a problem with it.
Linksys has always added great new featues to the firmware with upgrades.

I understand your pain with price.
I paid $300 dollars for mine and now they cost $99 most places.

"we have all those home Windows boxes connected direct to the Internet with no firewall/virus-detection"

we do? perhaps we need a cheap firewall or router.

and for god sakes pirate norton!

Have a look at the changelog for the firmware - it says "Linksys, A division of Cisco Systems, Inc."

Hmm... That wasn't me that replied. I sort of agree though. I didn't make that code up. Download the code, look at packet.c. If that code is trolling then blame Linksys, not me.

If you go to linksys.com and you hit "support" you end up here. You must be talking about the search box at the bottom of that page. Look right above it. See that penguin? Looks a little like Tux, doesn't he?

On a different topic, even if Linksys hasn't provided the 'correct' source code, as suggested by some, their acknowledgement of the GPL should at least mean open slather on reverse engineering any binary which has a hint of GPL to it.

On a different topic, even if Linksys hasn't provided the 'correct' source code, as suggested by some, their acknowledgement of the GPL should at least mean open slather on reverse engineering any binary which has a hint of GPL to it.

I have no problem at all with my Logitech wireless optical wheel mouse running through my Belkin 4-port switch.

Did you bother with the Linksys support site? Perhaps this is the problem you are having.

The Linksys product description says, "Because they donâ(TM)t use software, the ProConnect Compact KVM Switches are compatible with all major desktop and note-book computers." One might read into that statement that the switch is not altering the electrical signals and that the switch is compatible with all mice. Sadly, that appears not to be the case and although a known limitation they don't mention it in the description. I'd send it back and buy from a company that makes KVM switches that work properly.

Also note, their NAS disk storage devices (old EFG20, and newer EFG80) both use linux. No mention of this in the user guide, web site, or sales brochures. Use the link ftp://ftp.linksys.com/pub/network/efg80.zip to download the firmware.

found this on linksys site: linux_release.txt.

A bit more OT. Did you know that the Linksys WAP54G access point is based on Linux?. Somewhat strange, that there are no linux drivers for Broadcom 802.11g wireless NICs.

A bit more OT. Did you know that the Linksys WAP54G access point is based on Linux?. Somewhat strange, that there are no linux drivers for Broadcom 802.11g wireless NICs.

Microsoft has been adamant that the Xbox is and will remain a gaming platform. Period. The knee-jerk reaction to news of additional capabilities, such as voice and music, is "The Xboxes aren't selling as game consoles, so they're trying other applications in hopes of selling more boxes."

This doesn't make much sense when one considers that Microsoft loses money on every Xbox. The bill of materials is $400-$500, and they retail for $200. That difference can't be made up on volume. This business model is to lose money on the consoles but make it back (and then some) on the games, much like the razor/blade model. Games are high-margin products, especially those created in-house, and I would think that the Xbox business case is dependent upon preserving those margins. So pushing the Xbox as an enabler of low-margin services doesn't make much sense. Let's look at those mentioned...

Voice
Sure, Xbox Live voice quality is pretty good. Since Xbox Live requires broadband, it's not tough to obtain toll quality. But why would they want to? There are many reasons why voice over IP hasn't taken off (customers don't want to be tethered to their PCs, long distance is already cheap -- you'd better not be paying more than $0.05/minute for interstate calls), and to my knowledge Xbox Live doesn't have the billing capabilities required for voice services. The article states that Microsoft would move the chat capability to the Xbox Live dashboard, which implies the requirement of an Xbox Live subscription. It's unlikely that this feature would convince consumers to subscribe to Xbox Live. Microsoft would also need VOIP-PSTN gateways, so their customers can call people who don't use an Xbox. Telephone service is complicated. Maybe Microsoft would partner with a company such as Vonage, but they certainly aren't the easiest to work with.

Music
A neat capability, much like the QCast Tuner for the PlayStation 2. Consumers have shown little willingness to pay for this, however, as they're accustomed to free players. Service like Rhapsody and pressplay would undoubtedly benefit from freedom from the shackles of the PC, but their revenue shares are micenuts compared with Microsoft's costs. Given the current crop of LAN-to-stereo bridges, like the AudioTron and the SimpleFi, the Xbox does stand out, but this advantage may be gone in a few months when the likes of Linksys launch its low-cost device.

Movies
One of the reasons for Movielink's slow start is the simple fact that most consumers prefer to watch movies on their TVs, not their PCs. This problem is defeated with the Xbox in the mix, as it enables high-quality video output to the TV. Perhaps Microsoft plans to download the top 3-4 pay per view movies to the Xbox hard drive each night (Movielink movies are 500-600MB each, so they would easily fit on the 8-9GB Xbox HDD), so when the consumer chooses a popular movie playback begins immediately. The margins on this business are low, too. And Microsoft will compete with existing TV-based PPV and Video on Demand, which is slowly rolling out to cable systems. This makes a tough market even tougher.

Summary
Low margin + low penetration services will not lift the Xbox to profitability. Great games will. Strong Xbox Live games will give customers a reason to pay $9.95 a month for the service. Hopefully the EA/AOL exclusivity deal will end soon, so Xbox can benefit from good sports titles. Until the games improve, Microsoft is rearranging deck chairs on the Titanic. They have the cash to be patient, however.

Disclaimer: I work fo

Check out these two products:

Wireless Presentation Gateway

Wireless Presentation Player

Check out these two products:

Wireless Presentation Gateway

Wireless Presentation Player

If I want a Unix with spotty peripheral support and availability of applications, my choices are Linux and MacOS.

Spotty peripheral support? The only reason Windows has better peripheral support than either of those two is that hardware vendors supply drivers, and they supply drivers for the OS with a 90% installed base -- Windows.

But more and more peripherals are being supported under Linux and MacOS X. Some by reverse-engineering, but many hardware vendors are now stepping up to the plate and providing Linux and MacOS X drivers.

If you want to support Linux or MacOS X, then only buy hardware from those manufacturers that provide drivers. For instance, HP has open source (BSD license) drivers available for CUPS, LinkSys provides drivers for Linux (at least) for some of its products, etc.

If you don't like that OSes other than Windows have inadequate or missing driver support -- use your OS of choice and VOTE WITH YOUR WALLET and buy peripherals from vendors that provide Linux or MacOS X drivers, rather than whine and complain that Linux and MacOS X have spotty peripheral support. Or, better yet, get down and dirty and start reverse engineering products and coding your own open source drivers.

There is already networking over powerlines for inside your own house. I am not sure how this may or may not relate to delivery of internet service to one's home but this at least seems cool because a power outlet it the most prevalent outlet in most houses. I am not sure how well it works but I have been tempted to try it. Here is the link for the USB adapter and the Ethernet Bridge. Has anyone had any Real World experience with these?

There is already networking over powerlines for inside your own house. I am not sure how this may or may not relate to delivery of internet service to one's home but this at least seems cool because a power outlet it the most prevalent outlet in most houses. I am not sure how well it works but I have been tempted to try it. Here is the link for the USB adapter and the Ethernet Bridge. Has anyone had any Real World experience with these?

I had a Linksys WAP11 wireless access point with WPC11 cards at the office, and they were horribly unreliable no matter what I did. I was about to give up when I found a firmware update for the WAP on Linksys' support site. With that installed and all of the drivers updated to latest versions everything works like a charm.

I'd suggest looking to see if there are firmware updates for your wireless router. Depending on how long your retailer had it sitting in their warehouse you may not have the latest and greatest versions of everything.

The not-so-good news but more likely news is that Cisco will decide not to warranty Linksys products and will introduce new, Cisco-branded products at a much higher price.

Well, here's to hoping that Microsoft won't buy Logitech, and Sun won't try to acquire Matrox.

I have a Streamium MC-i200 in my garage (yeah, I spend a lot of time there). Here's the environment: Connected to the Ethernet port is a D-Link DWL-810 Ethernet-to-wireless bridge, which talks to a Netgear MR314 in my upstairs office. Also in the office is a media server, which is simply an old PC with a big hard drive. Finally, I have an old notebook that sits on my A/V tower downstairs, with a Y-cable from the stereo minijack out to an unused set of audio ins (MiniDisc, I believe). The notebook is perfect for playing Rhapsody through my main receiver.

With that out of the way, here's a quick review of the Streamium:
Good
- Ability to play MP3s from media server anywhere on your network.
- Limited Internet streaming capability. Rhapsody or something similar is needed.
- Really good sound, with decent bass thump.
- Remote control is handy when I'm working underneath the car and want to change tracks.

Bad
- Requires a special version of MusicMatch Jukebox on the "server" PC, even though I had already paid (yes, I paid) for the full version of MusicMatch. Now I have two versions on my music server. This server app must be running for the Streamium to find it and play music from the hard drive.
- Horrid navigation. My music is stored in folders, with an artist at the top level, and album folders underneath. It's a chore to page down through the alphabetized list of artists. So I play more Geoff Achison than I would like, and less of the Zombies.

Bottom Line
- While this is a good first step, $500 is far too much to pay (I evaluate this gear for my job). For that jack I'd buy a two-year-old notebook, PC speakers, and slap in a wireless card.
- Keep an eye out for a Digital Media Adapter from Linksys, which should be released soon. It, too, sits on your A/V tower, hooks into your receiver, and should have an out to the TV, so you can navigate playlists and such on the big screen.

BTW, the Wall Street Journal reviewed the Streamium last month. Yup, you gotta have a subscription.

Hope this helps.

-Ray

Linksys has a signal booster. It looks expensive and I've never used it, but it claims to be great.

Chapter 6: Using the Wireless Ethernet Bridge Web-based Utility

Overview

The Bridge is designed to function properly after configuration using the Setup Wizard [ed: Wintel Only].

If you go this route, you'll need a Wintel box, or at the very least Virtual PC to properly configure the bridge (for the first time -- its http admin works on the Mac after initial setup) -- even though Linksys claims otherwise.

Not having this linkys device, I'm interested to know what you tried to get it working--linksys does indeed claim that this will work, here. (Also linksys Knowledge Base KB10934380). Did you follow those steps, or no?

Finally, for those without easy access to Virtual PC--this kind of one-shot deal might be the kind of thing that you could go to your Apple Store for--they now have VPC running on some demo units, and aren't generally bad about letting one install software--it's all deleted every night anyways.

Its the linksys WET11

It's the WET-11 and it's a wireless bridge. Looks pretty neat. I believe SMC and Orinoco also make similar devices.

But I would still want it to be wireless.

I noticed this press release a few days ago, as well. Been doing some research since then.

You'll need a TiVo Series 2 to make this work. No word on whether 3rd party TiVo 2s will be supported (like the Sony unit).

Most everything below is an educated guess, so take with a grain of salt.

I'm assuming after looking at the unit's connectivity that you'll need to get a TiVo USB->Ethernet adapter. No word as to whether other parties' USB->Ethernet or USB->802.11x adapters will work as of yet.

I've already got a Linksys WET11 hooked up to my Playstation 2 network adapter, bridging to my wireless LAN (iMac with connection sharing on via Airport card), so adding a cheap hub at my receiver isn't a big deal on my end.

If you go this route, you'll need a Wintel box, or at the very least Virtual PC to properly configure the bridge (for the first time -- its http admin works on the Mac after initial setup) -- even though Linksys claims otherwise. Also, if you turn on encryption, keep in mind that you need to set up the Mac side to use the long-ass hex version of the password you pick (ie $AA2E43323B2300000) or the WET11 won't be able to get on. At the very least, lock your access point down to specific hardware addresses.

As far as bandwidth concerns -- let's see -- MP3s ripped at 192k -- vs the 11 megabit bandwidth on 802.11b. I'm not seeing a problem here. Hell, a direct uncompressed dump to AIFF or WAV from a CD will only come in at 150k/second (ie 1x CD-ROM). That's 1.5 megabits of bandwidth -- for uncompressed audio.

Back to the info -- this functionality seems to be part of a forthcoming firware upgrade for the series 2 models (which are currently shipping and on sale -- $199 for a 40 meg unit, $399 for an 80 with rebate).

It also seems that they're hinting that LAN functionality is going to be part of a new 'tiered' pricing structure -- the veiled hint being "part of our premium service".

At any rate, I'm in on this the moment it's available. I bought a Sony 200-CD jukebox about 5 years ago, and it's skipping horribly now and cleaning hasn't helped. I'm giddy at the thought of dropping it and just getting a 120-gig drive to take its place.

Here's to hoping that TiVo's media center (or whatever they call it) UI is decent, and it supports iTunes playlists and iTunes browsing by artist, album and genre.

I'd pay an extra $5 or so a month for that.

One last hint:

When ripping to iTunes, make sure your prefs are set to add track numbers to the filenames, otherwise your albums will play back in alpha order.

--dr00gy

How to set up a Series 2 TiVo with an Apple AirPort (802.11b) Wireless Network
Last Modified: January 9, 2003 @ 3:06 am

Background

When my DSL provider went out of business, I decided to go with cable modem instead of getting DSL with a different provider with the goal of getting rid of my landline phone altogether. With that change, the TiVo was the only thing I had that still needed a landline phone for. I use my cell phone (Treo 300, recommended) for just about everything anyway so if I could get the TiVo to get data over the internet via our home network, I could cancel my landline phone and save about $20 a month which more than justifies the cost of the TiVo, right? One problem - our network connections are all upstairs and the TiVo is downstairs. We do have a wireless network though... so I figured I'd give it a shot. I read up a bit on the tivocommunity.com message boards - basically, you connect a USB-to-Ethernet Adapter to the USB port on the TiVo, then connect a Wireless Ethernet Bridge to the USB-to_Ethernet Adapter. It took too many hours of tweaking and trial and error, but it finally works. I am quite pleased. I decided to write up the steps I took in hopes that it will help someone else who is trying to set up a similar configuration.

I have gotten a lot of mail asking why I didn't just get the Linksys WUSB11 USB-to-Wireless adapter or a similar product. Unfortunately, you cannot currently use a USB-to-Wireless adapter with a TiVo as there is no way to properly configure the adapter. You can read more on this at tivocommunity.com. Although to be honest - I did not try myself, I took other people's word for it. If you somehow make it work, please let me know - it would be a lot cheaper and more convenient.

My Network Configuration

I have a DSL/Cable modem attached to the uplink port of a hub. I have an AirPort Base Station (which is acting as my router/DHCP server) attached to the hub, along with my desktop computer. I have several laptops connected to the network wirelessly. Desktop Computer (TiVo with USB->Ethernet->Wireless)//DSL/cable modem -- hub -- AirPort Base Station -- Laptop A\Laptop B

Router: Apple AirPort Base Station serving DHCP
AirPort Network Name (SSID): Alex's AirPort (for this example)
WEP Security: none (for the sake of this example, however running a wireless network without encryption is not a good idea).

Required Hardware

• You need a PC (Virtual PC 5 worked for one reader) to run the WET11 setup program. Note to Mac Users: According to this article, you can configure the WET11 through a browser by connecting via ethernet, setting your computer's IP to 192.168.1.5 and sub 255.255.255.0, then going to http://192.168.1.225 in your browser. Thanks to Michael Dinsmore for the tip.
• A USB to Ethernet Adapter, I used a LinkSys USB100M.
• A Wireless Ethernet Bridge, I used a LinkSys WET11.

Configuring the WET11 to be a DHCP client

1. Unpack the WET11.
2. Set the switch on the back of the WET11 to quot;II (not X).
3. Plug the WET11 into your wired network. I plugged mine into my hub.
4. Launch the driver/setup program on a PC (or virtual PC) connected to the network (wired/wireless does not matter). Download Page | Zip file - or you can try accessing the WET11 from a browser using the default IP address (see the screenshot in the setup guide).
5. In the setup program - follow these teps:
   - select the WET11 and click Yes
   - enter the password (default is admin) and click OK
   - choose Infastructure mode (not Ad-Hoc) and click Next
   - enter the name of your AirPort network into the SSID field (Alex's AirPort), all other settings can be left as is, and click Next
   - choose Automatically obtain an IP address (DHCP)
   - enter your security settings, in our example we leave it disabled
   - review your new settings, click Yes to save the changes
6. Note: Your network may go a little screwy at this point until you disconnect the WET11 in the next step.
7. This is important: you must unplug the power from the WET11 for a few seconds then plug it back in again to save the new settings. The directions say to reset the WET11 - they DO NOT mean for you to hit the reset button on the back of the WET11, this undoes all the settings you just entered and restores the factory defaults.
8. Unplug the WET11 from the wired network.
9. Set the switch on the back of the WET11 to X (not II).
10. Now your WET11 is ready to go!

Let's test the WET11 to make sure it is working on the network.

1. Disconnect a computer from your network.
2. Connect the WET11 to this computer with an ethernet cable (RJ45).
3. Wait a few seconds and see if your computer is able to rejoin the network.
4. If you get back on the network, you're set to go, disconnect the WET11 from the computer. If not, try rebooting with the WET11 attached. If it still doesn't work after rebooting, hit the reset button on the back of the WET11 and go back through the WET11 setup steps.

Connecting the TiVo

Now we need to connect everything to the TiVo.

1. Unpack the USB100M.
2. Plug the USB100M into the top USB port on the TiVo.
3. Plug in the WET11 to a power outlet.
4. Attach the WET11 to the USB100M with an ethernet cable (RJ45).
5. Restart the TiVo: Main Menu > Messages and Setup > Restart or Reset System > Restart the Recorder.
6. Enter new dialing settings: Main Menu > Messages and Setup > Recorder & Phone Setup > Phone Connection > Change Dialing Options
7. Leave Dial-In Number as is.
8. Set Dial Prefix to ,#401 (comma - pound - four - zero - one).
9. Set Call Waiting Prefix to nothing, leave it blank or erase what you have there.
10. Set Tone/Pulse to Tone (I don't think this matters).
11. Set 'Phone Avail. Detection to Off (again, I don't think this matters).
12. Set Dial Tone Detection to On.
13. Select Use these dialing options (at the top of the screen).
14. Select Make Test Call.
15. Cross your fingers, close your eyes, make a wish...
16. Press the SELECT button...
17. It worked right? I sure hope so... if not, pull the USB100M adapter out of the top USB port and insert it into the bottom USB port, then Restart the TiVo again (step 5 above) and go through the steps again.

If you still can't get it working, unplug the WET11 from the TiVo and again verify that it is working when attached to a computer. To start over from scratch, you can hit the reset button on the back of the WET11 and go back through the WET11 setup steps.

I hope that this helps someone. If you know of another way to do this or have some related information, please let me know.

td colspan="2" valign="top

How to set up a Series 2 TiVo with an Apple AirPort (802.11b) Wireless Network
Last Modified: January 9, 2003 @ 3:06 am

Background

When my DSL provider went out of business, I decided to go with cable modem instead of getting DSL with a different provider with the goal of getting rid of my landline phone altogether. With that change, the TiVo was the only thing I had that still needed a landline phone for. I use my cell phone (Treo 300, recommended) for just about everything anyway so if I could get the TiVo to get data over the internet via our home network, I could cancel my landline phone and save about $20 a month which more than justifies the cost of the TiVo, right? One problem - our network connections are all upstairs and the TiVo is downstairs. We do have a wireless network though... so I figured I'd give it a shot. I read up a bit on the tivocommunity.com message boards - basically, you connect a USB-to-Ethernet Adapter to the USB port on the TiVo, then connect a Wireless Ethernet Bridge to the USB-to_Ethernet Adapter. It took too many hours of tweaking and trial and error, but it finally works. I am quite pleased. I decided to write up the steps I took in hopes that it will help someone else who is trying to set up a similar configuration.

I have gotten a lot of mail asking why I didn't just get the Linksys WUSB11 USB-to-Wireless adapter or a similar product. Unfortunately, you cannot currently use a USB-to-Wireless adapter with a TiVo as there is no way to properly configure the adapter. You can read more on this at tivocommunity.com. Although to be honest - I did not try myself, I took other people's word for it. If you somehow make it work, please let me know - it would be a lot cheaper and more convenient.

My Network Configuration

I have a DSL/Cable modem attached to the uplink port of a hub. I have an AirPort Base Station (which is acting as my router/DHCP server) attached to the hub, along with my desktop computer. I have several laptops connected to the network wirelessly. Desktop Computer (TiVo with USB->Ethernet->Wireless)//DSL/cable modem -- hub -- AirPort Base Station -- Laptop A\Laptop B

Router: Apple AirPort Base Station serving DHCP
AirPort Network Name (SSID): Alex's AirPort (for this example)
WEP Security: none (for the sake of this example, however running a wireless network without encryption is not a good idea).

Required Hardware

• You need a PC (Virtual PC 5 worked for one reader) to run the WET11 setup program. Note to Mac Users: According to this article, you can configure the WET11 through a browser by connecting via ethernet, setting your computer's IP to 192.168.1.5 and sub 255.255.255.0, then going to http://192.168.1.225 in your browser. Thanks to Michael Dinsmore for the tip.
• A USB to Ethernet Adapter, I used a LinkSys USB100M.
• A Wireless Ethernet Bridge, I used a LinkSys WET11.

Configuring the WET11 to be a DHCP client

1. Unpack the WET11.
2. Set the switch on the back of the WET11 to quot;II (not X).
3. Plug the WET11 into your wired network. I plugged mine into my hub.
4. Launch the driver/setup program on a PC (or virtual PC) connected to the network (wired/wireless does not matter). Download Page | Zip file - or you can try accessing the WET11 from a browser using the default IP address (see the screenshot in the setup guide).
5. In the setup program - follow these teps:
   - select the WET11 and click Yes
   - enter the password (default is admin) and click OK
   - choose Infastructure mode (not Ad-Hoc) and click Next
   - enter the name of your AirPort network into the SSID field (Alex's AirPort), all other settings can be left as is, and click Next
   - choose Automatically obtain an IP address (DHCP)
   - enter your security settings, in our example we leave it disabled
   - review your new settings, click Yes to save the changes
6. Note: Your network may go a little screwy at this point until you disconnect the WET11 in the next step.
7. This is important: you must unplug the power from the WET11 for a few seconds then plug it back in again to save the new settings. The directions say to reset the WET11 - they DO NOT mean for you to hit the reset button on the back of the WET11, this undoes all the settings you just entered and restores the factory defaults.
8. Unplug the WET11 from the wired network.
9. Set the switch on the back of the WET11 to X (not II).
10. Now your WET11 is ready to go!

Let's test the WET11 to make sure it is working on the network.

1. Disconnect a computer from your network.
2. Connect the WET11 to this computer with an ethernet cable (RJ45).
3. Wait a few seconds and see if your computer is able to rejoin the network.
4. If you get back on the network, you're set to go, disconnect the WET11 from the computer. If not, try rebooting with the WET11 attached. If it still doesn't work after rebooting, hit the reset button on the back of the WET11 and go back through the WET11 setup steps.

Connecting the TiVo

Now we need to connect everything to the TiVo.

1. Unpack the USB100M.
2. Plug the USB100M into the top USB port on the TiVo.
3. Plug in the WET11 to a power outlet.
4. Attach the WET11 to the USB100M with an ethernet cable (RJ45).
5. Restart the TiVo: Main Menu > Messages and Setup > Restart or Reset System > Restart the Recorder.
6. Enter new dialing settings: Main Menu > Messages and Setup > Recorder & Phone Setup > Phone Connection > Change Dialing Options
7. Leave Dial-In Number as is.
8. Set Dial Prefix to ,#401 (comma - pound - four - zero - one).
9. Set Call Waiting Prefix to nothing, leave it blank or erase what you have there.
10. Set Tone/Pulse to Tone (I don't think this matters).
11. Set 'Phone Avail. Detection to Off (again, I don't think this matters).
12. Set Dial Tone Detection to On.
13. Select Use these dialing options (at the top of the screen).
14. Select Make Test Call.
15. Cross your fingers, close your eyes, make a wish...
16. Press the SELECT button...
17. It worked right? I sure hope so... if not, pull the USB100M adapter out of the top USB port and insert it into the bottom USB port, then Restart the TiVo again (step 5 above) and go through the steps again.

If you still can't get it working, unplug the WET11 from the TiVo and again verify that it is working when attached to a computer. To start over from scratch, you can hit the reset button on the back of the WET11 and go back through the WET11 setup steps.

I hope that this helps someone. If you know of another way to do this or have some related information, please let me know.

td colspan="2" valign="top

How to set up a Series 2 TiVo with an Apple AirPort (802.11b) Wireless Network
Last Modified: January 9, 2003 @ 3:06 am

Background

When my DSL provider went out of business, I decided to go with cable modem instead of getting DSL with a different provider with the goal of getting rid of my landline phone altogether. With that change, the TiVo was the only thing I had that still needed a landline phone for. I use my cell phone (Treo 300, recommended) for just about everything anyway so if I could get the TiVo to get data over the internet via our home network, I could cancel my landline phone and save about $20 a month which more than justifies the cost of the TiVo, right? One problem - our network connections are all upstairs and the TiVo is downstairs. We do have a wireless network though... so I figured I'd give it a shot. I read up a bit on the tivocommunity.com message boards - basically, you connect a USB-to-Ethernet Adapter to the USB port on the TiVo, then connect a Wireless Ethernet Bridge to the USB-to_Ethernet Adapter. It took too many hours of tweaking and trial and error, but it finally works. I am quite pleased. I decided to write up the steps I took in hopes that it will help someone else who is trying to set up a similar configuration.

I have gotten a lot of mail asking why I didn't just get the Linksys WUSB11 USB-to-Wireless adapter or a similar product. Unfortunately, you cannot currently use a USB-to-Wireless adapter with a TiVo as there is no way to properly configure the adapter. You can read more on this at tivocommunity.com. Although to be honest - I did not try myself, I took other people's word for it. If you somehow make it work, please let me know - it would be a lot cheaper and more convenient.

My Network Configuration

I have a DSL/Cable modem attached to the uplink port of a hub. I have an AirPort Base Station (which is acting as my router/DHCP server) attached to the hub, along with my desktop computer. I have several laptops connected to the network wirelessly. Desktop Computer (TiVo with USB->Ethernet->Wireless)//DSL/cable modem -- hub -- AirPort Base Station -- Laptop A\Laptop B

Router: Apple AirPort Base Station serving DHCP
AirPort Network Name (SSID): Alex's AirPort (for this example)
WEP Security: none (for the sake of this example, however running a wireless network without encryption is not a good idea).

Required Hardware

• You need a PC (Virtual PC 5 worked for one reader) to run the WET11 setup program. Note to Mac Users: According to this article, you can configure the WET11 through a browser by connecting via ethernet, setting your computer's IP to 192.168.1.5 and sub 255.255.255.0, then going to http://192.168.1.225 in your browser. Thanks to Michael Dinsmore for the tip.
• A USB to Ethernet Adapter, I used a LinkSys USB100M.
• A Wireless Ethernet Bridge, I used a LinkSys WET11.

Configuring the WET11 to be a DHCP client

1. Unpack the WET11.
2. Set the switch on the back of the WET11 to quot;II (not X).
3. Plug the WET11 into your wired network. I plugged mine into my hub.
4. Launch the driver/setup program on a PC (or virtual PC) connected to the network (wired/wireless does not matter). Download Page | Zip file - or you can try accessing the WET11 from a browser using the default IP address (see the screenshot in the setup guide).
5. In the setup program - follow these teps:
   - select the WET11 and click Yes
   - enter the password (default is admin) and click OK
   - choose Infastructure mode (not Ad-Hoc) and click Next
   - enter the name of your AirPort network into the SSID field (Alex's AirPort), all other settings can be left as is, and click Next
   - choose Automatically obtain an IP address (DHCP)
   - enter your security settings, in our example we leave it disabled
   - review your new settings, click Yes to save the changes
6. Note: Your network may go a little screwy at this point until you disconnect the WET11 in the next step.
7. This is important: you must unplug the power from the WET11 for a few seconds then plug it back in again to save the new settings. The directions say to reset the WET11 - they DO NOT mean for you to hit the reset button on the back of the WET11, this undoes all the settings you just entered and restores the factory defaults.
8. Unplug the WET11 from the wired network.
9. Set the switch on the back of the WET11 to X (not II).
10. Now your WET11 is ready to go!

Let's test the WET11 to make sure it is working on the network.

1. Disconnect a computer from your network.
2. Connect the WET11 to this computer with an ethernet cable (RJ45).
3. Wait a few seconds and see if your computer is able to rejoin the network.
4. If you get back on the network, you're set to go, disconnect the WET11 from the computer. If not, try rebooting with the WET11 attached. If it still doesn't work after rebooting, hit the reset button on the back of the WET11 and go back through the WET11 setup steps.

Connecting the TiVo

Now we need to connect everything to the TiVo.

1. Unpack the USB100M.
2. Plug the USB100M into the top USB port on the TiVo.
3. Plug in the WET11 to a power outlet.
4. Attach the WET11 to the USB100M with an ethernet cable (RJ45).
5. Restart the TiVo: Main Menu > Messages and Setup > Restart or Reset System > Restart the Recorder.
6. Enter new dialing settings: Main Menu > Messages and Setup > Recorder & Phone Setup > Phone Connection > Change Dialing Options
7. Leave Dial-In Number as is.
8. Set Dial Prefix to ,#401 (comma - pound - four - zero - one).
9. Set Call Waiting Prefix to nothing, leave it blank or erase what you have there.
10. Set Tone/Pulse to Tone (I don't think this matters).
11. Set 'Phone Avail. Detection to Off (again, I don't think this matters).
12. Set Dial Tone Detection to On.
13. Select Use these dialing options (at the top of the screen).
14. Select Make Test Call.
15. Cross your fingers, close your eyes, make a wish...
16. Press the SELECT button...
17. It worked right? I sure hope so... if not, pull the USB100M adapter out of the top USB port and insert it into the bottom USB port, then Restart the TiVo again (step 5 above) and go through the steps again.

If you still can't get it working, unplug the WET11 from the TiVo and again verify that it is working when attached to a computer. To start over from scratch, you can hit the reset button on the back of the WET11 and go back through the WET11 setup steps.

I hope that this helps someone. If you know of another way to do this or have some related information, please let me know.

td colspan="2" valign="top

How to set up a Series 2 TiVo with an Apple AirPort (802.11b) Wireless Network
Last Modified: January 9, 2003 @ 3:06 am

Background

When my DSL provider went out of business, I decided to go with cable modem instead of getting DSL with a different provider with the goal of getting rid of my landline phone altogether. With that change, the TiVo was the only thing I had that still needed a landline phone for. I use my cell phone (Treo 300, recommended) for just about everything anyway so if I could get the TiVo to get data over the internet via our home network, I could cancel my landline phone and save about $20 a month which more than justifies the cost of the TiVo, right? One problem - our network connections are all upstairs and the TiVo is downstairs. We do have a wireless network though... so I figured I'd give it a shot. I read up a bit on the tivocommunity.com message boards - basically, you connect a USB-to-Ethernet Adapter to the USB port on the TiVo, then connect a Wireless Ethernet Bridge to the USB-to_Ethernet Adapter. It took too many hours of tweaking and trial and error, but it finally works. I am quite pleased. I decided to write up the steps I took in hopes that it will help someone else who is trying to set up a similar configuration.

I have gotten a lot of mail asking why I didn't just get the Linksys WUSB11 USB-to-Wireless adapter or a similar product. Unfortunately, you cannot currently use a USB-to-Wireless adapter with a TiVo as there is no way to properly configure the adapter. You can read more on this at tivocommunity.com. Although to be honest - I did not try myself, I took other people's word for it. If you somehow make it work, please let me know - it would be a lot cheaper and more convenient.

My Network Configuration

I have a DSL/Cable modem attached to the uplink port of a hub. I have an AirPort Base Station (which is acting as my router/DHCP server) attached to the hub, along with my desktop computer. I have several laptops connected to the network wirelessly. Desktop Computer (TiVo with USB->Ethernet->Wireless)//DSL/cable modem -- hub -- AirPort Base Station -- Laptop A\Laptop B

Router: Apple AirPort Base Station serving DHCP
AirPort Network Name (SSID): Alex's AirPort (for this example)
WEP Security: none (for the sake of this example, however running a wireless network without encryption is not a good idea).

Required Hardware

• You need a PC (Virtual PC 5 worked for one reader) to run the WET11 setup program. Note to Mac Users: According to this article, you can configure the WET11 through a browser by connecting via ethernet, setting your computer's IP to 192.168.1.5 and sub 255.255.255.0, then going to http://192.168.1.225 in your browser. Thanks to Michael Dinsmore for the tip.
• A USB to Ethernet Adapter, I used a LinkSys USB100M.
• A Wireless Ethernet Bridge, I used a LinkSys WET11.

Configuring the WET11 to be a DHCP client

1. Unpack the WET11.
2. Set the switch on the back of the WET11 to quot;II (not X).
3. Plug the WET11 into your wired network. I plugged mine into my hub.
4. Launch the driver/setup program on a PC (or virtual PC) connected to the network (wired/wireless does not matter). Download Page | Zip file - or you can try accessing the WET11 from a browser using the default IP address (see the screenshot in the setup guide).
5. In the setup program - follow these teps:
   - select the WET11 and click Yes
   - enter the password (default is admin) and click OK
   - choose Infastructure mode (not Ad-Hoc) and click Next
   - enter the name of your AirPort network into the SSID field (Alex's AirPort), all other settings can be left as is, and click Next
   - choose Automatically obtain an IP address (DHCP)
   - enter your security settings, in our example we leave it disabled
   - review your new settings, click Yes to save the changes
6. Note: Your network may go a little screwy at this point until you disconnect the WET11 in the next step.
7. This is important: you must unplug the power from the WET11 for a few seconds then plug it back in again to save the new settings. The directions say to reset the WET11 - they DO NOT mean for you to hit the reset button on the back of the WET11, this undoes all the settings you just entered and restores the factory defaults.
8. Unplug the WET11 from the wired network.
9. Set the switch on the back of the WET11 to X (not II).
10. Now your WET11 is ready to go!

Let's test the WET11 to make sure it is working on the network.

1. Disconnect a computer from your network.
2. Connect the WET11 to this computer with an ethernet cable (RJ45).
3. Wait a few seconds and see if your computer is able to rejoin the network.
4. If you get back on the network, you're set to go, disconnect the WET11 from the computer. If not, try rebooting with the WET11 attached. If it still doesn't work after rebooting, hit the reset button on the back of the WET11 and go back through the WET11 setup steps.

Connecting the TiVo

Now we need to connect everything to the TiVo.

1. Unpack the USB100M.
2. Plug the USB100M into the top USB port on the TiVo.
3. Plug in the WET11 to a power outlet.
4. Attach the WET11 to the USB100M with an ethernet cable (RJ45).
5. Restart the TiVo: Main Menu > Messages and Setup > Restart or Reset System > Restart the Recorder.
6. Enter new dialing settings: Main Menu > Messages and Setup > Recorder & Phone Setup > Phone Connection > Change Dialing Options
7. Leave Dial-In Number as is.
8. Set Dial Prefix to ,#401 (comma - pound - four - zero - one).
9. Set Call Waiting Prefix to nothing, leave it blank or erase what you have there.
10. Set Tone/Pulse to Tone (I don't think this matters).
11. Set 'Phone Avail. Detection to Off (again, I don't think this matters).
12. Set Dial Tone Detection to On.
13. Select Use these dialing options (at the top of the screen).
14. Select Make Test Call.
15. Cross your fingers, close your eyes, make a wish...
16. Press the SELECT button...
17. It worked right? I sure hope so... if not, pull the USB100M adapter out of the top USB port and insert it into the bottom USB port, then Restart the TiVo again (step 5 above) and go through the steps again.

If you still can't get it working, unplug the WET11 from the TiVo and again verify that it is working when attached to a computer. To start over from scratch, you can hit the reset button on the back of the WET11 and go back through the WET11 setup steps.

I hope that this helps someone. If you know of another way to do this or have some related information, please let me know.

td colspan="2" valign="top

How to set up a Series 2 TiVo with an Apple AirPort (802.11b) Wireless Network
Last Modified: January 9, 2003 @ 3:06 am

Background

When my DSL provider went out of business, I decided to go with cable modem instead of getting DSL with a different provider with the goal of getting rid of my landline phone altogether. With that change, the TiVo was the only thing I had that still needed a landline phone for. I use my cell phone (Treo 300, recommended) for just about everything anyway so if I could get the TiVo to get data over the internet via our home network, I could cancel my landline phone and save about $20 a month which more than justifies the cost of the TiVo, right? One problem - our network connections are all upstairs and the TiVo is downstairs. We do have a wireless network though... so I figured I'd give it a shot. I read up a bit on the tivocommunity.com message boards - basically, you connect a USB-to-Ethernet Adapter to the USB port on the TiVo, then connect a Wireless Ethernet Bridge to the USB-to_Ethernet Adapter. It took too many hours of tweaking and trial and error, but it finally works. I am quite pleased. I decided to write up the steps I took in hopes that it will help someone else who is trying to set up a similar configuration.

I have gotten a lot of mail asking why I didn't just get the Linksys WUSB11 USB-to-Wireless adapter or a similar product. Unfortunately, you cannot currently use a USB-to-Wireless adapter with a TiVo as there is no way to properly configure the adapter. You can read more on this at tivocommunity.com. Although to be honest - I did not try myself, I took other people's word for it. If you somehow make it work, please let me know - it would be a lot cheaper and more convenient.

My Network Configuration

I have a DSL/Cable modem attached to the uplink port of a hub. I have an AirPort Base Station (which is acting as my router/DHCP server) attached to the hub, along with my desktop computer. I have several laptops connected to the network wirelessly. Desktop Computer (TiVo with USB->Ethernet->Wireless)//DSL/cable modem -- hub -- AirPort Base Station -- Laptop A\Laptop B

Router: Apple AirPort Base Station serving DHCP
AirPort Network Name (SSID): Alex's AirPort (for this example)
WEP Security: none (for the sake of this example, however running a wireless network without encryption is not a good idea).

Required Hardware

• You need a PC (Virtual PC 5 worked for one reader) to run the WET11 setup program. Note to Mac Users: According to this article, you can configure the WET11 through a browser by connecting via ethernet, setting your computer's IP to 192.168.1.5 and sub 255.255.255.0, then going to http://192.168.1.225 in your browser. Thanks to Michael Dinsmore for the tip.
• A USB to Ethernet Adapter, I used a LinkSys USB100M.
• A Wireless Ethernet Bridge, I used a LinkSys WET11.

Configuring the WET11 to be a DHCP client

1. Unpack the WET11.
2. Set the switch on the back of the WET11 to quot;II (not X).
3. Plug the WET11 into your wired network. I plugged mine into my hub.
4. Launch the driver/setup program on a PC (or virtual PC) connected to the network (wired/wireless does not matter). Download Page | Zip file - or you can try accessing the WET11 from a browser using the default IP address (see the screenshot in the setup guide).
5. In the setup program - follow these teps:
   - select the WET11 and click Yes
   - enter the password (default is admin) and click OK
   - choose Infastructure mode (not Ad-Hoc) and click Next
   - enter the name of your AirPort network into the SSID field (Alex's AirPort), all other settings can be left as is, and click Next
   - choose Automatically obtain an IP address (DHCP)
   - enter your security settings, in our example we leave it disabled
   - review your new settings, click Yes to save the changes
6. Note: Your network may go a little screwy at this point until you disconnect the WET11 in the next step.
7. This is important: you must unplug the power from the WET11 for a few seconds then plug it back in again to save the new settings. The directions say to reset the WET11 - they DO NOT mean for you to hit the reset button on the back of the WET11, this undoes all the settings you just entered and restores the factory defaults.
8. Unplug the WET11 from the wired network.
9. Set the switch on the back of the WET11 to X (not II).
10. Now your WET11 is ready to go!

Let's test the WET11 to make sure it is working on the network.

1. Disconnect a computer from your network.
2. Connect the WET11 to this computer with an ethernet cable (RJ45).
3. Wait a few seconds and see if your computer is able to rejoin the network.
4. If you get back on the network, you're set to go, disconnect the WET11 from the computer. If not, try rebooting with the WET11 attached. If it still doesn't work after rebooting, hit the reset button on the back of the WET11 and go back through the WET11 setup steps.

Connecting the TiVo

Now we need to connect everything to the TiVo.

1. Unpack the USB100M.
2. Plug the USB100M into the top USB port on the TiVo.
3. Plug in the WET11 to a power outlet.
4. Attach the WET11 to the USB100M with an ethernet cable (RJ45).
5. Restart the TiVo: Main Menu > Messages and Setup > Restart or Reset System > Restart the Recorder.
6. Enter new dialing settings: Main Menu > Messages and Setup > Recorder & Phone Setup > Phone Connection > Change Dialing Options
7. Leave Dial-In Number as is.
8. Set Dial Prefix to ,#401 (comma - pound - four - zero - one).
9. Set Call Waiting Prefix to nothing, leave it blank or erase what you have there.
10. Set Tone/Pulse to Tone (I don't think this matters).
11. Set 'Phone Avail. Detection to Off (again, I don't think this matters).
12. Set Dial Tone Detection to On.
13. Select Use these dialing options (at the top of the screen).
14. Select Make Test Call.
15. Cross your fingers, close your eyes, make a wish...
16. Press the SELECT button...
17. It worked right? I sure hope so... if not, pull the USB100M adapter out of the top USB port and insert it into the bottom USB port, then Restart the TiVo again (step 5 above) and go through the steps again.

If you still can't get it working, unplug the WET11 from the TiVo and again verify that it is working when attached to a computer. To start over from scratch, you can hit the reset button on the back of the WET11 and go back through the WET11 setup steps.

I hope that this helps someone. If you know of another way to do this or have some related information, please let me know.

td colspan="2" valign="top

The Linksys EtherFast® Cable/DSL Voice Router is the perfect solution for connecting a small group of PCs to a high-speed broadband Internet connection or a 10/100 Ethernet backbone--and it features Voice Over IP telephone calls powered by Net2Phone. With the EtherFast® Cable/DSL Voice Router installed, no other special hardware is necessary for telephone calls. An ordinary telephone connects to the RJ-11 port (telephone jack) on the back of the EtherFast® Cable/DSL Voice Router, and calls are routed by Net2Phone's superior quality network to anywhere in the world--significantly reducing long distance charges.

It looks like the hardware people use the phrase "Network Attached Storage" for devices that are dedicated to serving files. LinkSys calls theirs EFG80 (such poetry), but you need a Windows PC to run setup. Sun has a whitepaper. A Google search on "Network Attached Storage" turn up mostly hardware turnkey solutions.