Back when I bought my Mac it was a bit more of an experiment than anything. At the time I didn’t figure on needing to print so I didn’t arrange anyway for the Mac to access our printer. At the same time I really didn’t have a good setup for my laptop to access the printer either. The printer sat in my wife’s office and if we wanted to print, we had to bring the laptop to the printer, hook up the USB cable and then print.

Well, the Mac is now what I consider my primary computer and since it is a stationary box it makes a lot more sense to have the printer hooked up to the Mac and then share it. So now my current setup has the printer connected directly to the Mac and then shared to my XP laptop.

This is where the fun began. While Mac people like to talk about how easy OS X is and how easy it is to share your files or share your printers with other computers the brutal truth is OS X much prefers to share with other OS X machines, particularly in Leopard. This is evident in Apples choice to enable file sharing using Apple’s AFP by default rather than smb/cifs. In other words, enabling file sharing without visiting an options dialog will leave you scratching your head. Same thing applies to printing, though it is barely Apple’s fault here. The difference lies in the printing systems used in the OS X/Linux world and Windows.

OS X, like most Linux systems today, uses CUPS or Common Unix Printing System to provide print services for OS X. Windows does not and so it does not understand the drivers that CUPS uses for printing. So when I shared out my Photosmart 8150 and added it to my XP laptop my laptop requested the drivers for my printer. After providing the drivers and attempting to print a test page I was greeted with a whole lot of nothing. Why? Well it turns out that the Windows drivers will not talk to the OS X drivers properly and nothing happens.

Thankfully CUPS on OS X can be configured manually just like it can be under Linux by using the web interface. Here’s how.

Start by enabling printer sharing on OS X. Even though Windows can’t print to this printer you must enable printer sharing so that OS X opens up and starts the necessary ports and services.

Next, you must have your root account enabled. The easiest way to do this if you haven’t already is to open terminal and type ‘sudo su -‘ (no quotes) and press enter. Enter your password and press enter. Now set root’s password by typing ‘passwd’ and pressing enter. Follow the on screen prompts. If you don’t have a password set you can also use Directory Utility to enable the root account and then set a password. I don’t have experience using this method so YMMV.

Next, open up your favorite web browser and head to http://localhost:631 and click on the add printer button. Type in a name for your printer. For my setup I used Photosmart_for_Windows. Notice the underscores in place of spaces. Click continue

On the next screen you will select the device you wish to print to. In my case, I chose HP Photosmart series 8100 USB. Click continue.

On the next screen you might be asked to select which specific model you are using. You can simply click the Add Printer button without choosing anything.

On the next screen you will be asked what Make the printer is. Here, be sure to click raw and then click the Add Printer button again.

Next you’ll be asked about the Model and this time your only option will be Raw Queue. Click this option and click Add Printer. You will be asked for a username and password. Here you provide your root username and password. In my case it is root and ******.

You are now done with the OS X portion of the setup.

On the Windows computer go to Printers and Faxes in the control panel and click the Add a printer link on the left or Add Printer from the file menu.

Choose ‘A network printer…’ and click next

Click the third radio button for ‘Connect to a printer on the Internet….’ and enter in the following

http://<mac hostname>:631/printers/<printer name>

In my setup it is

http://macmini:631/printers/Photosmart_for_Windows

Click next

Window will pause for a while and then finally ask you for the printer drivers. Either choose the appropriate drivers from the list or use have disk and browse for them. Finish the add printer routine and do a test print.

Another nice new feature of Leopard is Spaces. For anyone who has used Linux at all you’ll recognize that Spaces is nothing more than virtual desktops. The problem with Spaces is that it isn’t enough like virtual desktops to really make me feel at home with it. A preferences panel add on called Warp fixes this.

http://www.ksuther.com/warp/

Using Warp I can now drag a window from once space to the next or go to the next space by pushing my mouse against an edge.

OS X is a funny system. So many things are very simple and yet there are some things that are more difficult than they need to be. Take for example mapping or mounting network shares. In Tiger (10.4) you could mount a share and it would show up in the sidebar. With Leopard (10.5) this isn’t so, you have to manually add it. This addition to the sidebar will stick until you reboot the system. This is a bit annoying. I like having direct access to the root of my share.

Fortunately OS X ships with automator and either I didn’t notice this in the previous version or it really is new but you can now call shell and apple scripts directly. I was already using automator to mount all of the shares I want mounted on login but I needed a way to get them into the sidebar. Click through to see my solution.
Continue reading

There is a bit of buzz on the internet right now about Apple’s announcement of OS X Snow Leopard which is to replace Leopard sometime next year. Word on the street is that it won’t be luring people in with hundreds of new features but Apple is instead concentrating on stability of the OS. This is amazing to me for a couple of reasons. One, Apple seems to be admitting that it is out of ideas! Two, when is the last time you’ve heard of a big software company just going back and streamlining their OS? This is fantastic because as I wrote before, I’m liking Leopard more now than I did when it was initially released but compared to Tiger it’s just not as polished. Boot times for instance could be improved as Leopard takes nearly 50% to twice as long to boot compared to Tiger.

Along with the Snow Leopard client comes Snow Leopard Server and here is my prediction. Apple hasn’t told us everything (as usual) and based on the direction Apple is taking the iPhone, I believe Snow Leopard is going to be Apples biggest attack on the business/enterprise market yet. They have already admitted that ZFS will be included in Snow Leopard and they are talking about better Exchange support. Virtualization is a huge topic lately and I won’t be the least bit surprised to hear Apple announce virtualization support in Snow Leopard Server and maybe even in the client version. My guess is for the support of any OS including OS X itself..

What are your thoughts? Leave them in the comments area!

Well by now it’s no secret to any of my friends that I’ve become a bit of an Apple fan but I’m not so much a fan that I can’t criticize what they do. I’m not that rabid yet.

So it was with trepidation that I gave Leopard a try, twice no less, before finally making the switch to it permanently. I wanted to be sure the kinks were worked out and that it would work as well as Tiger did. I had read about and had my own issues with Leopard on my mini including poor animations, apps failing to start and just a general clumsiness to it that just was not what OS X should be like. While I’m not convinced it is quite there yet, the latest update has brought it a long ways in my mind.

The latest update, 10.5.3, seems to fix a lot of the big issues I was running into with Leopard. The biggest issue was actually with some iLife apps like iMovie. Either through luck or an actual fix iMovie now runs on Leopard. In previous versions I couldn’t get iMovie to open fully and when it did working with video was problematic and importing video was terrible. While I have yet to import video since installing 10.5.3 I’m fairly confident it’ll work much better than it has in the past based on how well it runs otherwise.

By now you have probably heard about the digital tv switchover deadline in February of 2009. In case you haven’t, head on over to http://www.dtv.gov/ to get the long story. The short story is that analog TV signals will be turned off as of February 17, 2009. If you get your TV using an antenna, then there is something you need to do to get ready. You can either buy a new TV with an ATSC tuner in it already or you can purchase a government subsidized digital to analog converter box. To get your $40 coupon head over to https://www.dtv2009.gov/.

Last friday I received my coupon in the mail. The coupon comes in the form of a prepaid credit card and you can use it at any store that sells approved converter boxes. I took mine over to Best Buy and picked up their Insignia branded converter box. This box is fairly basic providing one digital input, one RF output and a composite video output but the box is proving to be quite up to the task. The composite output allows you to get stereo sound (surround sound in fact) from the device and an improved picture over the RF connection. It also offers just the current program and the next program on it’s very simple program guide.

Now you might be thinking there is nothing wrong with the current system and that just couldn’t be further from the truth. Even though your old analog TV isn’t digital, the picture will be virtually perfect and in some cases better than you’d get if you had dish or cable. Audio too will be improved and if you have a surround sound system then any show that uses surround sound will be available to you in surround sound as well.

While the analog to digital switch over is a bit of a hassle the quality improvement is very much worth it. If you have any old TVs that are still in good shape and you don’t want to buy a new one then I strongly recommend going the converter route.

A while back I saw a post on digg.com that talked about some new software that was currently in an invite only beta test called Dropbox. Dropbox allows you to synchronize folders between computers and if you watch the video over at their site I think you’ll be impressed.

But as I said, it’s invite only. So what is a guy to do right now? Well believe it or not Microsoft actually has something very similar and it too works with both Windows and Mac. Now if we’re to believe everything the the Dropbox video shows us, Foldershare isn’t quite as robust but it is free and and more importantly it is available now. Check it out at http://www.foldershare.com/

In my previous entry I mention my Super Smash Bros. Brawl testing and one of the other tests I wanted to do involved determining how much data is required to play a four way game. My home network setup is a bit involved yet I couldn’t find a way to route the Wii through a device that I could measure network usage with.

To make a long story short, I found that you can configure your Mac’s wireless to “create network” and unlike a Windows PC that would setup an adhoc network, the Mac will act like a normal wireless access point or wireless router. This was fantastic because the Wii will not join an adhoc network. With my Mac set to create a new network I was able to join my Wii to it and determine that a four way game in Brawl requires at least 10KB/s of network traffic in both directions.

Whenever I can I’ve been playing Super Smash Bros. Brawl. This game has sucked me in more than I ever thought it would. In fact, I even once thought the game looked too chaotic, something that I wouldn’t like.

Well one of Brawl’s major components is online play and all to often I find myself playing with someone and there is a lot of lag. While I wanted to blame Nintendo completely at first I thought I should at least verify that the issue isn’t on my end first.

I set out doing this by getting my Wii connected to the internet through my usual wireless setup and thing sending a ping request to it from my Linux box. My wireless router is less than five feet from my console and yet I’d see at minimum a 2ms delay. 2ms doesn’t seem like much until you ping my laptop and get .600 ms over the same wireless connection.

I kept pinging the Wii while playing a round of Brawl online and I found that at times, the delay *just on my network* would go as high as 111ms! Now, the Wii might be doing packet prioritization but I doubt it. Anyway, 111ms is quite a bit higher than I would typically get to any other web site I usually visit. The round trip time to yahoo.com is around 64ms. If I’m seeing typical times to Nintendo’s servers and then I add in that my Wii’s wireless is contributing between 2-30ms (take out m y worse case) it’s easy to see why some Brawl games suffer from a lot of lag.

To combat this issue, I picked up a LAN adapter from Best Buy. When using the lan adapter the delay still isn’t great, but it is at least rock solid at 2-3ms no matter what is going on. This is a huge improvement in my eyes and if a person is at all serious about online play with the Wii, a lan adapter is key.