I've moved to a new apartment, and would like to get my stereo cabinet connected to the network. Running cables to the third floor (where the equipment is) isn't reasonable, so I'm looking at wireless solutions.

I already have a (netgear) 802.11b access point on the second floor, that is used to connect to the network by my girlfriend's iMac (with airport card) and my laptop (with silver orinoco card). This is plugged into the net (cablemodem) via a linux firewall.

I have a linux PC, rio receiver, empeg, and tivo upstairs that I want to connect into the downstairs network. Can I just buy another access point and plug that into an ethernet hub? Will the AP bridge to the AP downstairs, while stlil allowing other 802.11b clients (the laptop and iMac) to connect?

Other suggestions? Thanks (tons) for your help...

-j

P.S. My original plan was to put both an ethernet card and a wireless card in the PC upstairs (and have it route between the two networks), but a bug in my bios irq routing seems to keep me from getting the orinoco card working with SMP....

sorry, but that won't work. the "residential" class access points do not support bridging between two units. i wish they did, as i would like to be able to do the same.

lucent sells a pricey "ethernet converter" that will bridge a single 10BaseT device (such as the empeg or tivo) onto the wireless lan. it will only handle a single device, though (unless that device happens to be a router, i guess). the price of the converter, plus the not-included wireless card, is a fair bit more than a second access point.

--dan.

Have you looked into HPNA devices?

___________
Tony Fabris

That's not true - the linksys residential wireless access point now bridging between two units.. (requires a firmware flash upgrade..)


(Linksys WAP11)

-mark

...Still (barely, pending 1.1 release) proud to have owned an Empeg since 00287

*Cheer* someone being sensible. Linksys do appear to be good people (especially linux-support-wise!)

Hugo
ps: Barely proud? 2.0 beta will be out in the near future, and it really is even better. We've got a bit blase about it because most people have been running alpha versions for the last 6 months, but it is nicer to use.

#define "most"

Maybe the cadre of alpha-testers and the employees can be blase about it, but the rest of us are sitting on the sidelines waiting (some patiently, some impatiently) for it.

But I think that "most" people are still running production code. Or did you really have an alpha-test group that consisted of (n>50)% of the deployed Empeg customer base?

...Hey I'm still an avid supporter:) but I have to tease you guys about the releases to keep you on your toes ;p
-m

...Still (barely, pending 1.1/2.0/TeAsE release) proud to have owned an Empeg since 00287

I've actually been running the 1.03 production code for quite a while now. The last 1.1 alpha that was sent to the testing team had one or two show-stoppers that prevented me from getting full enjoyment out of it. The 1.1 bug list is full enough right now that I don't need to go finding new bugs until the next code drop.

My point is... trust me, guys, be grateful it wasn't public yet. It'll be public when it's ready.

___________
Tony Fabris

GASP - you mean Empeg writes buggy first-gen code???? UNHEARD OF!
-m

...Still (barely, pending 1.1/2.0/TeAsE release) proud to have owned an Empeg since 00287

The last 1.1 alpha that was sent to the testing team had one or two show-stoppers that prevented me from getting full enjoyment out of it.

Aww, Tony, c'mon, that's an exaggeration, surely. I've only found one real show stopper in 1.1, and that's the {MESSAGE CENSORED BY THE NDA POLICE} and that one I can live with, albeit painfully, so long as the song has a quiet ending.

tanstaafl.

"There Ain't No Such Thing As A Free Lunch"

ooo, that's good to know.

anyone interested in a lightly-used lucent RG1?

--dan.

Greetings!

I seem to remember a message from Tony a while back that the early 1.1 alpha code obliterated the music partitions on occasion. While I am as eager as everyone else to get involved in the 2.0 beta, I can wait until things like that are fixed... Granted, that was minor compared to the bug you mentioned...

So, what is the feature in 2.0 that people are most looking forward to? My favorite announced features are:

1) Ability to insert next from a search into the current playlist (not just append / replace)
2) Emplode 2.0, with search and more - that really looks good!
3) Updated Visuals
4) New MP3 engine that handles VBR times better
5) Tightening of code under the hood / bonnet (not really a feature, but always a good thing)

Paul G.
SN# 090000587 (96GB Smoke)

In reply to:

---

So, what is the feature in 2.0 that people are most looking forward to? My favorite announced features are:

1. Ability to insert next from a search into the current playlist (not just append / replace)
   
2. Emplode 2.0, with search and more - that really looks good!
   
3. Updated Visuals
   
4. New MP3 engine that handles VBR times better
   
5. Tightening of code under the hood / bonnet (not really a feature, but always a good thing)
   

---

Mine are mostly the same, but in a different order:

1. RDS TA
   
2. New MP3 engine that handles VBR times better
   
3. Ability to insert next from a search into the current playlist (not just append / replace)
   
4. Bug fixes for emptool
   
5. Updated Visuals
   
6. Tightening of code under the hood / bonnet (not really a feature, but always a good thing)
   

--
Toby Speight - 040103385

RDS TA won't be in the first releases, there isn't really time. Lots of stuff is collected by the current rds code - AF lists, etc, but not actually acted upon. We'll try and get it in as the 2.0 betas move towards a final 2.0.

Hugo

I seem to remember a message from Tony a while back that the early 1.1 alpha code obliterated the music partitions on occasion.

Yeah, and I shouldn't have said anything about it, either. The only reason it got mentioned on the BBS was because I didn't think it was 1.1-related and I was looking for help to fix it.

Once the empeg folks got wind of it, they fixed it more or less instantly.

So, what is the feature in 2.0 that people are most looking forward to?

So far, my favorite features of The Software Formerly Known As 1.1 (and these were demo'ed at the Woodside meet so I know I can talk about them) are:

- "Insert" option added to search-by-title.
- Info:Transient.
- Weighted shuffles.


___________
Tony Fabris

In reply to:

---

sorry, but that won't work. the "residential" class access points do not support bridging between two units. i wish they did, as i would like to be able to do the same.

---

That's what I thought.

I did some more google searches and found that the orinoco card I had (the pccard and the pcmcia/pci adapter) doesn't work for lots of people in older ISA and PCI systems. I went to ebay, and got an old $20 ISA PCMCIA adapter shipped to me. Installed it that night, and everything works. The PC upstairs is routing between my upstairs network (for the
empeg, rio-receiver, tivo, etc.) and the wireless network (which connects it to the rest of the house and the internet.)

Pretty cool. Thanks, all, for the help (saving me from buying another AP that wouldn't solve the problem.)

-j

Jason,

Re-read my message:) the linksys access point DOES do what your'e trying to do.
-mark

...Still (barely, pending 1.1/2.0/TeAsE release) proud to have owned an Empeg since 00287