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…

Hi, Let's say I have the following: code: NSProgressIndicator* progress; (assume it's initialized and visible etc) for (int i = 0; i < 5; ++i) { [progress setDoubleValue: …

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

Just got my new 2.0 GHz MacBook Pro and am absolutely delighted with it, except for one really annoying prolem: I cannot get it to print to my network printer via AppleTalk over th…

Most networked printers prefer TCP/IP connections over AppleTalk. AT has been "depricated" in standards terms-it's not the preferred interface and is not being supported for newer…

Yes, that works perfectly. Thanks! But I'm still at a loss to understand why it doesn't show up on the MacBoook Pro AppleTalk interface, when it did on my G4 Powerbook -- also runn…

Quote: Originally Posted by cms Just got my new 2.0 GHz MacBook Pro and am absolutely delighted with it, except for one really annoying prolem: I cannot get it to print to my ne…

Thanks for that but yes, I did know it already Tried deleting prefs, setting up a new user, all the usual suspects. No dice. I can't help it but even when a fix has been found and…

I'm starting to get the feeling that Tiger-Intel has some "differences" in the networking department. The AppleTalk issue is probably one of them. Remember, even Apple thinks of …

Hmmm...take your point BUT...If this is indeed the case, why can I see and access the printer via AppleTalk on my MacBook Pro on an ethernet connection? The AppleTalk access to net…

I am also having the same problem. I am unable to print over Appletalk using Airport but it works fine using the Ethernet port. Yes I made sure I had Appletalk enabled on the pro…

Jolly glad to know it's not just me. And particularly useful that you have recreated my exact same problem. Try the TCP/IP interface to see and use the printer over Aiport. It work…