I image my lab once a year. This ensures that I have the latest updates for every machine for all programs, but it also cleans out the old stuff from the previous year that builds up over time.  Apple makes imaging very simple by installing a NetBoot feature on all of their machines and including a NetBoot server installed with MacOS X Server.  In the past I used Bombich NetRestore, a free AppleScript based program that helped make NetBoot image sets and helped with deploying them.  Mike Bombich stopped making NetRestore and suggested everyone to try DeployStudio for imaging..so I did.  I must say that DeployStudio is an amazing program especially for a free program.  It’s also very simple to get running and fairly robust. In this post I’m going to go over image creation, setup, and deployment with DeployStudio (DS) and also go over some issues I encountered and how I fixed them.

Creating the NetBoot Set

The first step to any Mac NetBoot is the NetBoot set.  What the set is is a basic image file that includes all the tools your computer will need to read the image, copy the image, and even run checks on your computer even if you’re not imaging.  It’s a very basic MacOS install that resides on the server.  DS creates these images for both PPC and Intel machines in the same set, so any Mac can boot from the same set.  After installing DS on your server you can open the DS control panel and begin setting up your system AND create your  NetBoot set.  I will not be going over server setup in this post, I may save that for a later time.

The DeployStudio Control Panel

When you open the control panel you should launch the assistant (you can also find it in /Applications/Utilities).  When the assistant opens you select “Create a DeployStudio NetBoot set and continue.  If you’re running the assistant on a computer other than a server you will see this:

DeployStudio DHCP Setup

If you plan on using a server to do the deploying, you can skip this, if not, you’ll have to setup a DHCP server.  This depends on your setup, for my case I can skip this.  The next step allows you to name your set; set the name and unique identifier to whatever you wish, (unless you have multiple NetBoot sets). When you click continue you will tell the set where the computer should log in and look for the images and workflows.

My settings...

more settings...

The settings above are MY settings, yours will be different.  The login and password for mine are supplied by the LDAP server.  The final step is the actual save location and creation of the image.  Pretty self explanatory. It takes about 5-10 minutes.

Completed NetBoot .nbi file

After image creating is successful you’ll have a nice .nbi file in your save location.  This file is basically an image file that contains the bootable images for PPC and Intel as well as the basic MacOS system with some basic utilities like Disk Utility, Terminal and Startup Disk.  It’s roughly 2.5 GB and it should be placed on your server in the NetBootSP0 folder (It’s located in [Volume]/Library/NetBoot/).  Inside the NetBootSP0 folder will be other folders which DS created during install, these contain various other things for DS and also house your images.  I will go over image creation next.  This is where we will be able to test to see if your NetBoot Server and set are both working.

Creating Images with DeployStudio

Creating the images is an extremely simple task once you know what settings you need.  I will explain the setup with my current settings but attempt to go over most of the other ones.

To start the process, boot your mac and hold the ‘N’ key down during power on, this will perform a network boot (REMEMBER: Your computers must all be on the same subnet, this is the only way to do this without messing with a lot of things!)  If your computer boots to the DS screen you will see the DS Runtime Window.

This window shows all of your available jobs in DS.  There are a few default jobs that come with DS, we’ll make our own later for deploying.  For now we’re gong to select “Create a master from a volume.”  Click the Play button at the top and you will come to the heart of the Image creation.

My Image Settings from a PowerPC computer

This window is probably the hardest window we’ve seen so far.  First thing is to choose which drive you will make an image of from the dropdown menu.  I’ll start with my MacOS partition.  After selecting the correct partition I name the image something like 2011_09_02_Intel_lab and leave other settings alone.  The keywords are not very important unless you have a lot of images. I usually select Compressed for the type because it saves space and it gives a much faster restoration.    Access group is what you would have set in your initial DS setup that I did not cover.

Format is what kind of image you are making.  Since I’m doing a MacOS install the Format will be HFS+.  I normally select “Auto Detect” but if you want to have HFS+ Journaled, Case-sensitive or both you may want to change it because it will always auto-detect HFS+ without journalising.

Once my settings are correct I click the Play button at the top and the image making process begins.  This will take a lot of time depending on the size of the image being created,  a 100+GB image will take roughly 2 hours (sometimes more, sometimes less, depends on the machine and network) and it will then compress the image (my images get compressed to about 75GB from 128GB…compression rocks!).

Masters in the NetBootSP0 Folder

After image creation you will see the .dmg file in your NetBootSP0/Masters/HFS folder.  (Note: I just found out that new versions of DeployStudio won’t show your images in DS Admin unless you have .hfs in filename before the .dmg, it will automatically add them during image creation, but if you have old images, just add the .hfs right before the .dmg extension).

You can use this same process to create NTFS, FAT, and EXT4 images.  Follow the same steps but make sure you leave the Format as “Auto-Detect.”  After creating a NTFS image it might take some time to show up in DS admin, this is because some server-side tasks may need to be done, it will show up when that is complete.  NTFS imaging requires a little more setup in DS admin beforehand…again, I will not be covering that in this post.

Making Workflows to Deploy Images

DeployStudio comes with an administration program where you can manage images, workflows, packages, scripts, and see progress of NetBooted computers.  You can also set up all of your computers in it before hand (names, network settings, licenses, etc) and set up automation for all of your systems so if you want a computer to automatically format and re-image when you NetBoot it, you can do that (please don’t think that’s a great idea…just saying).  To start setting up workflows you’ll need to open DS Admin, it’s located in /Applications/Utilities.  Enter your server credentials and you’re presented with the DS server information.

The window that opens first is the current (or previous) activities.  In this window you can watch and control the computers that are currently working in DS.  ou can also see what jobs they were doing, and how far along they are.  This screen is very helpful when you have DS running on many machines.

I am going to explain how to setup a dual-boot Mac workflow.  The default jobs are very helpful at getting you started, I’m going to start from scratch.  To create and edit workflows we’re going to select “Workflows” from the left sidebar and begin setting up our job.  Click the “+” button at the bottom and you will be presented with a new blank job.  Then click on the little “+” button next to “Drop tasks here.”

Creating a new workflow

The first thing to do is to drop the “Partition a disk” task from the left side to the drop space.  Then you should select  “Mac OS X + Windows” from the Apply layout template dropdown menu.  Resize the partitions to suit your needs, make sure your images will be able to fit on the partitions you make for your drive.  I normally do 75% Mac OS/25% Windows, I also normally Automate this process, your mileage my vary.

The next step is to drag the “Restore a disk image” job from the left and drop it after the partitioning job.  Your MacOS image should ALWAYS be first of else it will not work.  Select “Enter value…” from the Target volume section, then select the “MacOSX” option from the menu.  Set your Image to HFS and select the appropriate image from the menu (the one you created earlier).  Now, for the options you can read from the image below how to set those.  If you’re imaging Mac OS 10.7 Lion you should check “Restore system recovery partitions” but I don’t need this.

My HFS Settings

You may also notice Multicast settings, you can set this up if you’re brave, I don’t need it so it’s ignored.  Your HFS partition is complete, now on to Windows.

Drag the “Restore a disk image” job from the left and drop it after the first restoring task.  Select “Enter value…” from the Target volume section, then select the “WINDOWS” option from the menu.  Set your Image to NTFS and select an appropriate image from the menu again.  Settings for Windows is relatively the same as HFS with some exceptions;  you should check “Expand restored NTFS partition” and uncheck “Set as default startup volume” unless you want to have Windows as your default.  You’ll also notice that all of these tasks are automated, this is so you can boot the computer, select the job, and walk away without intervention.

DS NTFS Settings

Now, you can add more jobs to the workflow such as AD binding, or software updates, but this setup is the basic setup for a dual-boot deploy.  Now just rename the job by clicking the name in the top with the other jobs and rename it, you can also add a short description of the job.  Your workflow is now complete! Now it’s on to the easiest task…deployment!

Deployment

I say this is the easiest part because it really is.  If you have everything set up properly, you should have no issues.

To deploy the image to the computers, boot the machines again pressing the ‘N’ key, when the machine boots to DS you can select the newly created Workflow and press the play button.  If you automated everything, that’s it..it will partition your drive and load the images to those partitions.  After the job is complete your computers will either tell you it was successful (or failed…more on that below) or they will reboot.  If the task was successful, GREAT!  Reboot the machines, they will run the final scripts in MacOS then reboot again…MacOS is done.  You only have one more thing to do and that’s configure Windows.  I won’t go into this because it’s going to be different for everyone, but you will have to activate windows and any other programs that require it because Windows will not keep the activation after imaging.

Issues?

Now, not everyone will be so luck to have a successful run…if you run into any issues visit the DS forums, they are very helpful and pretty speedy.  I had one issue that just drove me nuts.  When I ran my deployment script the MacOS partition would go fine but once Windows hit it would fail…everytime.  DeployStudio keeps logs for every computer on the server, so I took a look and noticed the following errors:

[Thu Sep  1 14:41:15] dyld: unknown required load command 0×80000022
[Thu Sep  1 14:41:16] -> invalid starting block value () defined in MBR for partition /dev/disk0s3.
[Thu Sep  1 14:41:16]    Check your partition map. You need to define at least one DOS/FAT partition in order to get the MBR automatically in sync with GPT.
[Thu Sep  1 14:41:20] -> Restore action completed.
[Thu Sep  1 14:41:20] Restoration failure (elapsed time: 0.24 minutes)

I posted in the DS forums (topic link) and in a matter of hours the admin of the forums posted a solution:

Sounds like the custom fdisk command fails on 10.7 DSS netboot sets. You may try to remove the one located in your netboot folder at /Applications/Utilities/DeployStudio\ Admin.app/Contents/Frameworks/DSCore.framework/Resources/Tools/fdisk.

So I tried this and BOOM, successful.  It’s great when a developer helps with products so quickly…and I’ve only usually seen this with free or open source projects.  So if you’re having issues, the forums are key.

I hope this post helps people out with Mac imaging and deployment.  If you have any other questions or issues feel free to ask in the comments.  If this post helped you or think it will help others please feel free to repost and share away!

I installed CM7 when it was at RC1 for the DROID (still buggy, but still good for everyday use) and I originally flashed my phone by doing a factory reset of the device (removes everything) and then installing the ROM. This gave me an endless boot screen.  What I had to do to fix this was not only do a factory reset, but wipe the cache partition AND the Dalvik cache partition.  This was easy with the ClockworkMod and it was also nearly 100% risk free since I had a complete Nandroid backup.  After wiping the two it booted successfully!

I noticed that in Android 2.3 Google will restore all of your previously purchased and downloaded apps if you want it to automatically on a new device (only the app itself, not the data..like game save data).  This is great, but I already decided to use MyBackup Root for this, mainly because I wanted to have my stuff there with all of the data.  So i just told the phone not to download everything and I’ll just restore everything from my backup.  What this left me with was broken installed apps with no way to update them because the Market links were all hosed.  This sucked, now what was I supposed to do?  I decided to flash again and allow Google to push the apps to my phone.  This process took some time but everything was downloaded for the most part; unfortunately, I didn’t have my app data, so all of my game data and all of my settings were gone…I check MyBackup and sure enough I was able to restore data only!  I did that and bingo, everything worked again with all of my old data!  A few apps needed to be reinstalled or needed their data wiped (Google maps and Facebook I think) but for the most part everything worked just as it was supposed to.

Choose which to restore? Yay!

So now that I had my apps on my phone, I was nearing happiness with my hacked DROID.  I say nearing because I was still having many issues with other things.  I won’t go into every little one but I will talk about the two that almost made me decide to go back to stock.

LED Notifications

The one thing I love about Android phones is the LED notifications.  A simple little LED in the corner of my phone blinks different colors for certain things (texts, emails, etc) so I don’t need to turn the screen on, or unlock my phone to see what I missed or see what that beep was from…I can just look at the color of the LED.  Funny thing happened after installing, it stopped working.  I would look down and nothing would be blinking but when I unlocked my phone I’d notice an e-mail that I missed!  What was going on here?  I looked in the settings and found that CM has basically rewritten the notification system and you can customize colors and blink rate from it if you so desired, but instead it broke the damn thing.  This wouldn’t fly with me, I was about to go back to stock because one of my favorite features was broken…then I found the forums.  I searched the issue on the forums and found a lot of people with the same issue, on different phones even!  Reading through many of the posts they all usually came around to the same solution, un-check everything in the LED settings then check them again then hit “Reset all LED notifications” and reboot. And it worked!  I had my LED back and working and now it was even better because I can change the settings for every program and even change the colors and blink rate for them, pretty neat.

Change color and rate for LED notifications

Missing Messages

Now that my LED notifications worked I was happy that I could look down and see if I missed any emails or (more importantly) text messages…but strangely I felt that I was receiving less messages.  I went an entire day without a text message, which is very odd for me actually.  I looked at my phone, no blinking LED, I unlocked the phone, no notification in the menu, I opened the messaging app and boom, new texts, some as old as a day!  What the hell was going on with this?  I’m missing text messages now?  This used to happen with my EnV Touch, never my DROID!  I tried resetting my notifications for the app, and it would work for a while after I opened the app.  I figured, okay, it’s fixed, but then it would stop later on in the day.  I was getting very frustrated with this now and was again thinking about going back to stock.  I hit the forums again and found one post about the issue with one simple solution:

The solution! Check that box!

Once I checked that, never missed another message.  It locks the message app in the memory so it’s always running.  Sure it uses up memory, but my messages are more important to me than the amount of apps I can run at one time.

Side note: But why does the DROID do this with CM7?  The DROID has 256MB RAM, this was a lot when the phone came out and with 2.1 it was fine.  Once 2.2 was released memory was becoming a problem for the phone.  The phone had trouble even keeping the Home app in memory; if you ran a program that was memory hungry and went back to the home screen you’d have to wait for it to redraw because Android’s memory management would kill it.  So in CM7 you can see the two check boxes for home and messaging, this stoped the redrawing(relaunching) and the missing messages…but it took some memory away of course which means you can only do so much multitasking before apps start getting killed.  Android 2.3.3 uses more memory, and the DROID just doesn’t have that much…so CM7 also allows asset purging to free up RAM as well as compucache (memory compression).  These use a little CPU but allow you to multitask fairly well;  it’s nowhere near as good as other newer phones, but it works.

There were some other small odds and ends that I had fixed by tweaking settings and installing updates but I thought that these two were really the most damming for me.  I managed to fix them with help from other nerds at the CyanogenMod Forums who were running into similar issues and there are some I managed to fix by trial and error.  Now, he ROM still has it’s occasional reboots and hiccups (not very often) and they usually happen with two programs; Google Maps and the Camera app, but these crashes happen less and less with each update.

CM7 is now out of RC and was released as Gold…but not for the DROID yet.  It still is very much a work in progress, but the progress is going very quickly, and I really like the direction it’s heading.  They’ve managed to give DROID users Android 2.3 even after Motorola decided it “wouldn’t work” on the phone.  Well, it is working (for the most part) and I’m fairly happy with it.  It has really allowed me to use my phone a bit longer than I was expecting.  I’m probably going to wait until August to upgrade my phone instead of going for the Thunderbolt, but time may change that.  What I do know is that my phone still works well and I will get more time out of it because of the ROMS.

So when Froyo (Android 2.2) came out the DROID got it down the line and that’s when the DROID started to show it’s age; extremely slow…a big drop in performance.  So I decided to root it to get a little more millage out of it before my upgrade.  Mind you, I was waiting for the Thunderbolt to come out to replace it…but decided against upgrading for the time…another story I suppose.  I decided to use SuperOneClick to root my phone, and damn it was simple.  Literally one click and it was done…but what can I do with this root?  Well, first thing was overclocking to see if I can get some more speed.  I overclocked it to 800MHz and really didn’t notice much of a difference besides the fact that I could now have a wireless hot-spot…oh and I could take screen shots now (why doesn’t Android have this functionality built in? Seriously!).

Hey look, I need to ROOT to take a screen shot!

So I decided to take it a step further.  My buddy was telling me about CyanogenMod and how he loved it on his MyTouch and basically brought life back into it.  So I said “Why the hell not?”  Not only does it add a lot of functionality, it will give me Android 2.3.3 (Gingerbread)…something the original DROIDs won’t ever see normally.  I backed-up my apps and text messages phone using MyBackup Root then flashed my recovery ROM to ClockworkMod which allows me to install firmware from the SD card and allows me to backup my entire phone to an image just in case anything goes wrong.  After the backup with MyBackup Root I rebooted into recovery mode and backed-up the entire phone using the Nandroid backup (in the recovery) then started to flash CyanogenMod 7 on my phone..this meant I had to do a complete wipe of the phone which is always scary but with the backup I should be cool!

Wiped the phone, flashed the ROM, and booted the phone. It worked! I had the Release Candidate (at the time it was RC1) of CyanogenMod 7 on my phone!

I had some issues with CM7 at first and some issues with getting my apps back (which I’ll talk about in Part 2) but after some initial bumps I was up running as smooth as I could be on a release candidate.  I had some reboots and some programs would crash but reinstalling them from scratch helped for the most part.

After a few updates it became more and more stable.  I am now running RC4 with a new ultra-low voltage kernel (which allows me to overclock to 1GHz and uses less battery power than the stock kernel). which gives me good battery life, pretty good performance, and all around a pretty good experience.

Android 2.3.3 and 1.1GHz!

So if you’re looking to get some more time from your old DROID this seems like a great way to do it.  It’s not up there with the new phones, but it does give your device a nice little jolt until you decide to retire it.

In Part 2 I’ll talk about installing all of the apps from backup and troubleshooting the many issues I had with memory issues and how they were resolved.

Today Motorola responded to all of the eFuse nonsense with something that makes the situation a bit better.

Motorola’s primary focus is the security of our end users and protection of their data, while also meeting carrier, partner and legal requirements. The Droid X and a majority of Android consumer devices on the market today have a secured bootloader. In reference specifically to eFuse, the technology is not loaded with the purpose of preventing a consumer device from functioning, but rather ensuring for the user that the device only runs on updated and tested versions of software. If a device attempts to boot with unapproved software, it will go into recovery mode, and can re-boot once approved software is re-installed. Checking for a valid software configuration is a common practice within the industry to protect the user against potential malicious software threats. Motorola has been a long time advocate of open platforms and provides a number of resources to developers to foster the ecosystem including tools and access to devices via MOTODEV at http://developer.motorola.com.

This is very good compared to bricking the phone.  At least the phone can be recovered by the user instead of having to ship it to Motorola for a repair(not sure of the complete details and how warranty would work).  I’m also happy to see that Moto responded so quickly to the public.  However, this still does not sit well with me as Android was developed with developers and tinkering in mind.  If I want to mess around with my device, why can’t I?

(Thanks to Tom for pointing this out for me)

According to a source at My Droid World (and Motorola themselves), the Droid X has an eFuse chip installed in the device. The long and short of it is that Motorola has installed this eFuse in the new Droid X which checks the phone for the proper kernel, boot-loader, and ROM and if the proper software is not found it will automatically “trip a fuse” to corrupt the phone’s boot-loader forcing you to get it repaired and will most likely void your warranty. Oh and did I mention that the phone can ONLY be repaired by Motorola, so the Verizon Store won’t help you (well, they’ll ship it to them for you) and you’ll most likely end up pay for a new phone.

Why is Motorola doing this to their phones? According to the Motorola blog:

We understand there is a community of developers interested in going beyond Android application development and experimenting with Android system development and re-flashing phones. For these developers, we highly recommend obtaining either a Google ADP1 developer phone or a Nexus One, both of which are intended for these purposes. At this time, Motorola Android-based handsets are intended for use by consumers and Android application developers, and we have currently chosen not to go into the business of providing fully unlocked developer phones.

Now if I read that correctly, Motorola just told people to buy an HTC device (the Nexus One or a Google ADP1 dev phone) and not their product because their “Android-based handsets are intended for use by consumers and Android application developers.” So, the DROID was a fluke? Well…

When we do deviate from our normal practice, such as we did with the DROID, there is a specific business reason for doing so. We understand this can result in some confusion, and apologize for any frustration.

You’re joking, right? You deviated on the DROID for a “business reason” and now that everyone loves your Android-based phones, you’re going to change it? How stupid does that sound?

First, if you’re going to say you have a reason you could at least tell the people what that reason was even if it’s most likely about money. Secondly, why would you want to change something that has worked already? You know the whole “no fix if no broke” thing? The DROID was probably the best smartphone released last year because of it’s features and it’s openness. Taking one of those key selling points away is really going to piss people off. Also, not only is it frustrating, it’s just a punch right in the face of all the people who praised your phone for it’s openness.

What happens when (like the MyTouch 3g and G1, etc) the developers stop caring about a phone so much that they don’t release a new version of Android for it, when their phones are still capable of running them? Or if Motorola decides not to update the SenseUI on the phone and you’re stuck with whatever they stop with? Well, of course you’re supposed to buy another phone from them, but it probably won’t be a Moto phone if the eFuse is still there. But there are a lot of people want to get all they can from their device (I mean, you did pay $200+ for it!). So they’ll end up going the route of rooting a phone and installing a modded Android install and continue to be happy with your device. Does it change that fact that it’s still a Motorola brand phone? No, it just shows that your hardware still kicks ass 2 years after it was released instead of going to the bottom of the old electronics drawer or whatever.

I realize not everyone cares about modding their phones, hell it’s most likely a larger portion than the people who do care, but the issue is that Motorola is making it okay for a company to brick YOUR phone if they don’t like what you do to it. You know, the phone YOU paid for with YOUR money (which Motorola took of course!). A lot of people buy devices based on how much the company lets you tinker with the device after you buy it.

I’m almost positive that the phone will still be hacked, but this is going to cause a big backlash in the Android community against Motorola (and probably Verizon even though they most likely have nothing to do with it). A lot of Android folk are very pro-open-source and while the software is still “open” the hardware will strike you down if you try to change it.

While I won’t tell people not to buy a Moto phone again I will say that the Droid X will probably be a bad choice if you’re going to alter the base software or if you want the phone to last a long time.

The lab is primarily used for video editing and 2D/3D graphic design. These are three very expensive fields when it comes to software. For video editing we use Final Cut Studio 2. We have a lab license which allows us to run 5 copies at any single time; this license costs us a one-time upgrade fee of around $2000. Of course we had to have Final Cut Studio before that so you need to factor that cost into it also. I’m not sure how much it was originally, but I’m guessing between 2 and 5k. Now, we don’t pay a yearly fee or anything, it’s installed, and it works. No fuss. Is there anything else out there we could use, something free? Maybe cheaper?

In short, no.

There really is nothing like Final Cut Pro out on the market. (And don’t tell me Adobe Premiere Pro because I’ll just have to punch you in the face) Avid is around, it’s been around, it will probably always be around; but it’s not FCP. Avid is a whiny little pain in the ass that doesn’t work if it doesn’t get it’s way, not to mention it’s about $2000/license. No thanks. So FCP is something we’re stuck with it looks like, no big loss. (I know there are open source editors out there, but they’re just not as good and intuitive as FCP is at all, so don’t bring that up.) With respect to Adobe, we do have 1 license of After Effects. It hardly gets used, but it’s really a good program from what I’m told.

Next is 2D graphic design. This one is a bit simpler. We use Adobe Creative Suite 3 (no, we didn’t upgrade to CS4) which comes with Photoshop, InDesign, Illustrator, Dreamweaver, Flash, and Acrobat Pro. We’ll ignore Flash for now because we really can’t use anything else that I know of. Photoshop is the standard graphics/photo editing software, the weapon of choice for graphic designers if you will. Without this piece of software your digital media lab (or in this case, my lab) is a laughing stock of the DM world. However, there are freebies out there, although they might not be as good they sure as hell will do the job well. GiMP and GiMPShop are around and have been for a long time. This Linux counterpart to Photoshop gives users who cannot afford the price tag from Adobe the ability to make beautiful graphics like the pros. It’s tools are almost 100% similar, and it’s interface can also be with the help of GiMPShop. I would show screen shots comparing the two, but I can’t seem to get GiMPShop to run on my laptop. (BTW, the two run with X11, not natively.)

InDesign and Illustrator are programs I am not so sure about replacing, I’ve never tried alternatives to them. I know there are a few out there though. Inkscape is one that looks like a promising Illustrator replacement, it’s free too! For InDesign we have Quark of course; although Quark is rapidly getting replaced my InDesign, and one called Scribus, another open source replacement. I’ve never used any of these so I cannot speak for them, but if you’re looking, try them out!

Dreamweaver is for web-development. It’s more of a helper for most new developers. It’s gotten a lot better over the years, but it’s still nothing that cannot be replaced by good ol’ hand coding with TextMate or whatever editor you prefer. These are all wonderful, some are free, some are not. However, for true web editing I have to give props to Coda by Panic. I’ve mentioned before that I love this program. I do. I really think this is probably one of the best code/web/css editing programs on the market, ever. It’s beautiful, and it’s functional. It’s also $99. Does this bother me? No. Each penny of that $99 is worth it. If you’re just doing web stuff, don’t go near Dreamweaver, get Coda, as a matter of fact, get multiple copies of Coda to give to friends. That’s how much I love it.

Look at this beautiful CSS editor! I can also edit the code of the CSS and ANY OTHER CODE WITH CODE HINTING!

Now we come to 3D graphics. Our choice program in the lab is Autodesk Maya 2008 Unlimited. Maya is the “industry standard” for 3D graphics, right with 3D Studio Max; both of which are now owned by Autodesk…weird huh? Maya comes with so much stuff that it’s very hard to find a comparable program. Some difficulties come up with licensing (you need to be running a license server if you have a set number of licenses, and you need to make sre you get Unlimited or Complete. The difference is just what kind of fluids or fur you get, whatever. I like Maya to a certain extent. it’s powerful and fairly easy, but it’s licensing is annoying, and it costs a good amount for upkeep. We need to constantly upgrade if we want the bugs to go away (because lord knows you don’t want to keep fixing your software after the first service pack which we paid a few thousand dollars for in the first place) and if we want service for the license we bought, that’s also more money.

Maya's starting interface.

To replace Maya many people opt for Blender; Maya’s open-source cousin from the Dutch. Blender is completely free, and it does a lot of the things Maya does. It really is an excellent replacement for Maya; however, it’s got a steeper learning curve than Maya. While Maya may still be considered difficult to grasp anyway, Bender is like a nightmare to some 3D artists I’ve known. So if you can learn Blender (which by the way has all documentation online free as all good programs should) you will probably be very happy with the results.

A random screenshot from Blender 2.4 from Wikipedia.

Besides these main programs I have taken liberties to find free versions of other programs for my lab machines as replacements to troublesome or other non-free programs. Adobe Acrobat 9 has a nasty issue with network users on Mac OS, it crashes…all the time. I’ve taken Acrobat off and replaced it with a PDF plugin for Safari and Firefox. If someone wants to use Acrobat Pro, which is VERY rare here, then they can ask me to install it for them, for now Preview works just as well. AppFresh is a free program that checks all of your programs for updates and allows you to install them at once. very handy for updating the lab machines. And I can’t forget my favorite free buddies Carbon Copy Cloner and DeployStudio, without these FREE tools I would have be dead trying to deploy the lab and backup systems.

So, if you’re on a tight budget and you’re looking for cheaper alternatives, try out some of these. They might end up being better for you in the long run. If you have any other programs to suggest, drop a comment, I’d love to try some new programs out. Just remember, sometimes you don’t get what you pay for.

A few months ago Windows 7 build 7000 came out, I signed up for the beta and downloaded it.  I figured I’d give it a shot.  I had been using Windows XP on my MacBook Pro for a bit and I wasn’t really into Vista much so I decided, what the hell.  I installed the 32-bit version on my computer (I know my laptop is 64-bit but there’s a weird issue with installing 64-bit windows on this version of the MBP, can be fixed but didn’t know at the time) and began using it.

The first thing I noticed was the look and feel of the OS.  It’s very aesthetically pleasing; much nicer than XP and a small step up from Vista.  I noticed that the taskbar at the bottom was now like the dock in OS X, programs show up there when running (icon only) and you can “pin” the icon there permanently for later use; also, if you mouse over the icon you get a small snapshot of the window or program running, clever.  Windows 7 ups the graphics a bit in some visual effects which drastically challenges your graphics card at times, but of course the effects can be disabled; however, I only noticed this issue with it when attempting to run Windows 7 in Parallels (note to self, don’t try again).

Another thing I noticed about 7 is that it’s fairly speedy and responsive.  After installing my MBP drivers on the system the computer runs very nicely; no hiccups, no glitches, no lockups, very solid.  I began testing some small duties on it after a bit: typing, searching, surfing, etc.  I have yet to install and heavy programs like Premiere Pro or Photoshop yet, but that’s only because I don’t need to…I use Mac OS for that.  The main use of my Windows install is for Steam.  I installed steam and Left 4 Dead (among other games) and the games play fine.  I have had only one lockup playing Left 4 Dead and I don’t think t was a Windows issue.  The game loads FAST so I have no complaints about that.

I’ve also been using the latest Windows Media Player on it; another program which I used to avoid at all times.  The new WMP is pretty nice; it plays what I want it to play, and it looks better.  I even like how it organizes your music when loaded up with album art.

One surprising thing I was very happy to find was when I was repairing my girlfriend’s Sansa View media player.  In Windows XP you can load it up like a regular drive, or using windows media player, it only gives the option to open or play, thats really about it.  I was shocked to see that when I plugged the player into Windows 7 it gave me a window with the correct product, the ability to update the firmware, sync pics music and videos, play, etc.  This made me very happy to see it had built in Sansa support (and if it didn’t at first it downloaded it from the internet!).  It made it so much easier to fix the player and organize the music on the player.

Now Windows 7 isn’t completely without it’s problems.  While the interface is beautiful it does do some work on your graphics card at times.  I have an ATI Radeon x1600 with 256MB video memory in my MBP, the graphics did hang sometimes (not too much) but it was definitely doing something.  It might also be about the drivers, ATI has released some Windows 7 beta drivers, but again they are only beta.  Another thing I noticed was that I couldn’t install some programs; MacDrive and Symantec EndPoint Protection.  This is possibly the case in Vista also, but it did kinda suck that it wouldn’t install them.  The system also still complains a lot about security issues which gets annoying after a bit, but you can decrease the sensitivity of the annoyances to a certain extent.

So, the good definitely outweighs the bad here and I’m looking forward to seeing Windows 7 when it’s complete.  I believe that if this beta is this good, then Windows 7 has a damn good change of being “the next XP.” Overall, I’m very happy with Windows 7 and I’m very happy to see a Microsoft OS that functions well and is easy on the eyes.

Note: I am running Windows 7 build 7000, I have not installed 7100 or RC1.  I may have to update if anything changes with later builds, but for now I’ll leave it at this.

If you’re any sort of tech with multiple computer that need to be imaged every so often you know how much of a hassle it can be.  If you have a NetBoot system running it’s a breeze; however, this ease usually comes at a cost (money cost that is).  Mike Bombich, founder of Bombich software has created some useful Mac applications over the years. One is Carbon Copy Cloner, a program which I use all the time and find to be one of the fastest, easiest, and safest methods of cloning any drive (to either another drive or a disk image).

The other program which I use very often is NetRestore and NetRetore Helper.  NetRestore and it’s helper are VERY easy-to-use GUI interfaces to create a MacOS netBoot image and netRestore image for deployment over multiple machines.  My lab has 10 Macs in it which don’t get updated all at once sometimes, and at the end of each semester the computers all have a lot of left over student files and different versions of some software running.  NetRestore makes it very simple for me to make a clean, updated image of a lab machine, then just boot from the network from the other machines and it takes care of the rest. It’s usually 100% automated, and completes all computers in about 2-3 hours.

What makes these pieces of software better than say, Norton Ghost or SuperDuper! or whatever? They’re 100% free to use.  Yep, no charge at all.  No catch, no signing up for anything, no logging into the site to download, NOTHING.  The only thing you’d have to deal with is an advertisement on CCC’s progress screen.  Very small price to pay for this software.

So, why am I writing about NetRestore now?  Well, because I like it and I would definitely reccommend it to anyone who needs to deploy multiple Macs.  But I am writing now because NetRestore has reached it’s end of life. On November 17, 2008 Mike Bombich posted a letter on his site explaining the reasons for ending NetRestore.  It’s very funny when I am sad to see a program go away, but it’s sad to see such a good program go away.  I also find it ironic that of all the software I have never paid for, I have actually donated money to Mike Bombich for all of his hard work for his free programs. That’s how much I like this software.

Even though NetRestore has reached EOL, I will still be using it on all of my lab machines until it stops working on them.  Thanks Mike for all of your hard work, and I’ll continue using CCC for all of my cloning needs:-)

Visit Bombich.com for more info on CCC or NetRestore

Just a short note: In his letter, Mike Bombich reccommends a site called DeployStudio,  I have yet to use this to deploy the lab, but the program does seem promising and nice.  I’ll use it someday and maybe give a review.  Until then, Bombich’s NetRestore will be king.