I’m taking the RedHat RHA030 and 130 right now at ECU. The really cool thing about the class is that it’s all online. We use VMware Workstation 6 and connect to the classroom servers through a VPN connection. The biggest drawback to the class is that it’s all online. Weird how that works.

Any-who, one of our labs has us using mount and umount (did I mention that RHA030 is a basic GNU/Linux skills class with a RedHat flavor?) with a floppy drive. There are a couple of problems with this, however. One, there’s no virtual floppy disk on the virtual machine that’s been configured for class. Two, VMware Workstation 6 has this weird quirk (at least the version we have) that won’t allow you to create floppy images in the img format. It adds flp to the end of whatever you put want to name your file, and then gives this error that the file already exists, which doesn’t make a lot of sense since the Workstation just created the file and should know that.

So, here’s a (mostly) graphical tutorial that allows you to create your own floppy image and use it with VMware Workstation 6.

Step 1. Open VMware Workstation and select the virtual machine you want to add a virtual floppy drive to.

Step 2. Select “Edit Virtual Machine Settings” from that virtual machine’s “Commands” menu.

Step 3. From the “Virtual Machine Settings” dialog’s “Hardware” tab, click the “Add…” button

Step 4. On the “Hardware Wizard” dialog, select the “Floppy Drive” hardware type and then click the “Next” button.

Step 5. On the “Hardware Wizard” dialog, choose the “Create a blank floppy image” radio button and then click the “Next” button.

Step 6. On the “Hardware Wizard” dialog, click the “Bowse” button to choose a location for your floppy image.

Step 7. Type in the name of the image file you want to create. Notice I tried to input an “.img” extension which is one of the types listed in the file type select box. Don’t bother trying that because Workstation will automatically tack on a “.flp” extension regardless of what you input.

Step 8. Check your file’s path and then click “Finish”. What’s supposed to happen is, Workstation creates an image file with the name in the text box.

Step 9. What happens is Workstation adds the “.flp” extension, creates the image file, then gives you this Alert box stating: “Unable to create floppy image. File exists.” Idiotic really. Just click the “OK” button and proceed as follows.

Step 10. You’ll now see that your file name has been appended with the “.flp” extension and that and further “Finish” clicking will merely give you to opportunity to view the Alert box again. But don’t worry, because even though you’re getting error a strange and magical thing has happened. Click “Cancel” to proceed to the next step.

Step 11. Click “OK” on the “Virtual Machine Settings” dialog.

Step 12. Ok, this is less of a step than just a view of the results. Remember that “strange and magical” thing I mentioned? Well, as it turns out Workstation has added the floppy drive to your virtual hardware and created and added the floppy image to your floppy drive just fine even with those errors. Weird, weird, weird, but I’m not really complaining, now I can do my lab!

Hope this helps anyone still having problems with this.

Well, we’ll see. I’m not really all that impressed with the software yet. But it does put me one step closer to getting my drawings, home improvement projects and other… graphics (?) up for the long haul. I’m really looking for the ability to be able to handle access controls so that I can make private albums for family, but public viewing is good too. I’m just not comfortable with having my likeness on the web is all…

Had to do some batch processing in the GIMP today. I looked over the scripting tutorials on the GIMP website, but as a fast and dirty approach this wouldn’t work for me (went right over my head). It took some digging around Google to find an easy to follow, automated way of doing it. What I found was a handy little plug-in from David Hodson [poor fellow, missed out on being a MST3K (here and here) cast away by one letter] .

While not performing every task I needed (I was resizing some images and I wanted to not only re-size but also change DPI), it did speed things up enough to make it worth while having. It also has quite a few built in options for commonly repeated processing; like rotation, color adjustment and cropping.

From DBP’s webpage:

“DBP (David’s Batch Processor) is a simple batch processing plugin for the Gimp - it allows the user to automatically perform operations (such as resize) on a collection of image files. Its main advantage is that the user does not have to learn a scripting language. Like the Gimp itself, DBP relies on a graphical interface. The user creates a list of images, and sets up the processing required for each image. The results of the current settings can be displayed. Once the required sequence of operations has been set up, DBP performs the same processing on each image in turn. The images can be colour corrected, resized, cropped, and sharpened, then renamed and saved to a different file in a specified image format. All the steps (except loading and saving the image!) are optional; so the simplest use of DBP is just to convert a number of image files from one format to another.“

Has anyone out there ever found any easy methods for scripting with the GIMP (outside of actually taking the time to learn yet another script’s syntax)?