Quote: Originally Posted by ghporter Not right off or I'd have listed them. I've heard reports of D-Link and Netgear routers that insist on being routers no matter what, but I …

Quote: Originally Posted by mduell Could just be confused/uneducated end-users. Very true. I'd check out the manual for a prospective purchase online before I plunked down …

Quote: Originally Posted by mduell You don't need to connect the wifi ap directly to the cable modem. Just connect the APBS to a free port on your d-link, and disable nat/dhcp …

When you set up whatever access point you choose, you should always connect to it through a cable. While this may not be absolutely mandatory (some boxes do their configuration th…

Quote: Originally Posted by SimeyTheLimey Which is correct? The correct thing for you to have done is to have bought a refurbished AirPort Express, not a new AirPort Extreme…

Quote: Originally Posted by ghporter When you set up whatever access point you choose, you should always connect to it through a cable. While this may not be absolutely mandato…

Quote: Originally Posted by ghporter My recommendation is to set up your equipment in the second configuration, with the base station after the router, and then turn off the rou…

OK, here's what I'd do. For performance: modem ---> router (DHCP on) ---> LAN port - AEBS (DHCP off) For ease of use: modem ---> WAN port - AEBS (DHCP on) - LAN port -…

Quote: Originally Posted by f1000 Now that I've thought about it, wouldn't it be easier for Simey to hook things up using your first configuration? This should allow him to set …

Quote: Originally Posted by ghporter On the other hand, ONE modification to the AEBS through the Admin Utility would make it work seamlessly with everything else that's already …

Quote: Originally Posted by f1000 Will an AEBS in access point mode still function as a USB printer server? I believe so-it's not a router function. Quote: Originally Pos…

So far everything seems to work the way you guys suggested. I don't have my Macbook Pro yet, but I have tested it with a Dell notebook. The only thing I can't test is printing f…

You'll need to make sure you get the right printer driver for the Mac too; not all printer driver packages include a networking driver... Be careful in what you decide is "the rig…

I meant to give you an update on how things went. Right now I am sitting out in my back yard typing on my Macbook Pro, so everything has worked out well. First, everything hook…

Quote: Originally Posted by SimeyTheLimey Printing works OK with one hiccup. It seems I need to unplug and replug the USB cable from the printer into the base station. Once I …

Quote: Originally Posted by mduell Are you within the USB spec for cable length? 5m max per cable, 5 hubs/repeaters max per chain. I'm probably pushing the envelope. The p…

I think NSRunLoop is what you're looking for.

When you update the value of a progress indicator, it's marked as needing display the next time through the runloop (with setNeedsDisplay: YES). Your code, however, never returns …

Quote: Originally Posted by smeger When you update the value of a progress indicator, it's marked as needing display the next time through the runloop (with setNeedsDisplay: YES…

He already said that, for some reason, an NSTimer is really impractical for what he's doing. I'd think that indicates a problem with the program's structure, but y'know, whatever. …

Thanks for the responses. I was hoping to avoid pthreads as it's a bit overkill. As for some people who are unhappy with my design I can elaborate as to why it's uncomfortable to…

Couldn't you just pass those things in as the timer's userInfo object (e.g., in an NSDictionary)?

I don't think that would work. If I declared the array on the stack and then passed it into the user info of the timer wouldn't it already be popped off the stack by the time the …

Yeah, it would be off the stack; that's why I suggested an NSDictionary. Actually, the userInfo object is declared to be an id, so it should be an Objective-C object, anyway (it's …

Ahh, I didn't know the userinfo got retained by the timer. That's very interesting. Thanks for the info! gabe