Tag Archives: Macintosh

The Server Project Begins

Posted on by
Comment

I [finally] get Mac OS X 1.4 Server and start to plan for installation and deployment.

If you’ve been following this bLog, you know that I recently purchased Mac OS X 10.4 Server from someone on eBay. I got the software at a smoking price — less than the Apple employee discount, in fact — and considered myself very fortunate. The only thing I can’t figure out is why it took the seller more than 10 days to send the software to me in a flat rate Priority Mail box.

The software arrived in good condition. The box looked a little worn, as if it had been handled by too many people or shuffled around from one shelf to another. But the seals were intact and the box appears to contain all the discs, documentation, and proof of purchase info — including the all-important serial number — that a legal copy of the software should. So I’m pretty confident that I did not buy used or pirated software.

Now that I have the software, I have no excuse to put off my big server project.

The goal, as I think I’ve mentioned elsewhere, is to install Mac OS X 10.4 server on my current Web server machine and use the following features:
– Web server (Apache) with PHP and MySQL for dynamic content
– E-mail server
– Mailing List server
– FTP server
– Streaming Video (QuickTime)
– Blog

I’ll also set up secure space on the server to back up my own personal documents, as well as Mike’s.

In addition to all that, the server will continue to run the same other services the server runs now:
– FileMaker Pro databases
– Webcam
– Steaming Audio (for KBSZ-AM)

All this on a Power Macintosh G4 running at 866 MHz. Seems pretty ambitious, but we’ll see how I can do. If all else fails, I’ll take my old G3/300 (beige, mind you) out of retirement and use that for the Webcam and FileMaker Pro databases.

I’ve made a list of steps that need to be done to get the project going. Here’s what I hope to accomplish today:

1) Adjust the upload address for all Webcams. Although the KBSZ-AM Webcam currently uploads to some GoDaddy hosting space I have, I think the wickenburg-az.com and Editor SpyCam Webcams both upload to my current server. I need them to upload someplace that won’t be affected by the change — probably that GoDaddy space — so I don’t lose Webcam service. I also need to adjust all Web page references to that new space.

2) Adjust the file locations for the ini files I use to display sunrise/sunset and upcoming event info on various Web sites. This information is generated each morning as a text file that is inserted in the appropriate locations on various Web pages. I need to change the source location for the ini files in the Web page HTML and then set up an AppleScript that automatically uses Fetch to move the files where I said they’ll be right after the files are created.

3) Set up hosting on the GoDaddy server for the Web sites I host on my server. This is temporary and will give me the time I need to make all the changes on the new server before moving the sites back. Some sites will move over without any major changes. Other sites, like wickenburg-az.com and aneclecticmind.com will undergo complete facelifts using new features available to me in Apache and the blogging software that comes with Mac OS X 10.4 Server. By moving them off my server to a place where they’ll continue to be served without interruption, I won’t be rushed to build the new sites. Some will be at GoDaddy for less than a month; others might be there for several months.

Since it’ll take up to 48 hours for the DNS info on the Web site move to propogate, I’ll have to wait a few days after I finish these steps to move onto the next step. Hopefully, while I’m waiting, the new RAM will arrive. I’d already ordered and installed 512 MB of RAM on the server and quickly discovered that the RAM was bad. When I get the new RAM, I’ll install it and send back the bad RAM. It should arrive today. If this RAM doesn’t work, I can only assume that they sold me the wrong kind of RAM.

When I’m sure that the sites are being served from GoDaddy’s servers, I can move on with the next steps in the project. I’ll write about those later on.

Stay tuned for progress reports, including problems I’m sure to encounter. And wish me luck!

On Blogging and Podcasting

Posted on by
Comment

Episode 7: On Blogging and Podcasting.

Everyone has a different idea of what blogging and podcasting is for. I thought I’d take a few bytes to explain my views. It’ll help readers and listeners understand what motivates me to share the information I share.

Transcript:

Hi, I’m Maria Langer. Welcome to Maria Speaks Episode 7: On Blogging and Podcasting.

Everyone has a different idea of what blogging and podcasting is for. I thought I’d take a few bytes to explain my views. It’ll help readers and listeners understand what motivates me to share the information I share.

My blogs and podcasts are separate and, in most cases, do not overlap. This entry is one exception; it’ll appear in both.

My blog, which is called Maria’s WebLog, contains over 270 entries written since October 2003. These entries cover a wide range of topics dealing with my everyday life and opinions about what I see going on around me.

I consider Maria’s WebLog to be an online journal. My main purpose is to share my experiences and views with readers. Part of it is to journalize my life so I can remember events in the future. The other part is to let my friends and family members know what’s going on in my life. I’m surprised when I meet someone and they tell me they’ve read my bLog. They’re welcome to read it, but they need to understand that I’m not writing it for them. I’m writing it primarily for me.

I don’t know how many people actually read my blog because it’s hosted on my .

Mac account and there isn’t any stat software for me to track it. But it appears that it is widely read by people all over the world. (If you’re reading it now, you might want to take this opportunity to use the Comments link to check in with your name and location, just for kicks.)

Some people read my blog entries and are offended by them. I think that’s pretty funny. There are so many things in this world that are far more offensive than anything I could write. But these people focus on a comment or observation or opinion I made in these blogs and use it as evidence that I’m some kind of evil person. Whatever. I think people like that need to get a life.

I made an entry the other day that left people wondering whether my entries were truth or fiction. What do you think?

One more thing about the bLog. I maintain it using iBlog software, which is a Macintosh-based blogging client. iBlog is a really cool little software package because it runs on my Mac and does not require access to the Internet to use. Instead, it keeps a database of all my blog entries as I write them. When I’m ready to publish, I connect to the Internet and click a button. This was really useful when I took my laptop to my place on Howard Mesa, which is off the grid. I’d just hit the coffee shop in Williams a few times a week and use their wireless access to update my blog and check my e-mail.

Maria Speaks is my podcast. For the folks reading this transcript in my bLog, here’s a brief definition. A podcast is an audio recording saved in a format that can be listened to on a computer or MP3 player, like an iPod. I call my podcast Maria Speaks because it’s me talking and I couldn’t think of a better name.

My idea of a podcast is that is should share useful information with listeners. After all, that’s why I subscribe to and listen to podcasts.

For example, I’m a big fan of NPR and now that I’m not tuned in all day, I like to listen to NPR stories as podcasts when I’m driving or flying.

I’ve tried a bunch of podcasts that I thought were a waste of my time. I don’t listen to them anymore. If there’s no value in what I’m listening to — if I can’t learn something or be entertained by something I can’t hear elsewhere — then what’s the purpose? There are too many podcasts full of talking heads that aren’t saying anything worth listening to. I don’t want my podcast to be like that.

So when it came time for me to do my own podcast, I had a choice. I could either vocalize my existing bLog entries by reading them — like I’m doing here — or I could create new content of interest to listeners. Since I don’t think my bLog entries are informative enough to attract listeners, I decided to go with new content.

I make my living writing about computers and there’s always some tip or trick I could share. So I decided to focus on computer-related topics, including tips and tricks for being more productive. I’m primarily a Macintosh user, so most of my podcast entries are about Mac computing, although I did publish a cross-platform episode about Microsoft Word yesterday. And because I’m not comfortable recording without a script, each episode has a transcript available online, complete with screen shots if necessary.

Please don’t get the idea that Maria Speaks will only be about using computers. I hope to come up with other interesting topics to enlighten listeners. I also encourage all listeners to visit the Maria Speaks home page and leave comments about what they’ve heard. Was the episode helpful? Not helpful? Boring? Interesting? What do you want to hear? All I ask is that you be gentle with me. Harsh comments don’t get results.

You can find links to the home pages for Maria’s WebLog and Maria Speaks on my Web site, www.aneclecticmind.com. Those pages include links for subscribing to the RSS feeds for both.

Well, as usual, I hope you found this episode interesting. You can read its transcript on Maria’s WebLog. Thanks for listening. Bye!

Clash of the Technologies

Posted on by
Comment

I teach an old computer new tricks.

I have a 20th Anniversary Mac. I bought it about six months after they were released and got a pretty good deal on it. It sits on a table in my living room, a piece of functional art. It runs System 7.6 — if anyone can remember that. The cool thing about this computer — other than the fact that both a floppy disk drive and CD ROM drive are built into the monitor — is that it has a Bose sound system. It also has a stereo receiver and, somehow, my cleaning lady has learned how to tune in Mexican music while she works.

Anyway, I bought an iPod Photo a few months back so I could write about it. I really don’t need an iPod Photo, but once you have something like that, you try to come up with ways to make it useful. I thought, wouldn’t it be nice if I could attach the iPod to the Mac, play music through those Bose speakers, and show photos onscreen?

Remember, the 20th Anniversary Mac is old technology. It dates back to ADB, Serial, and SCSI ports. There wasn’t any USB or Firewire in those days. But it does have an S-Video port and a microphone-in port. So I started experimenting.

The iPod Photo’s dock includes both an S-Video port and an audio line-out port. I didn’t have an S-video cable with the multi-pin connectors on both sides. But I did remember someone saying that an ADB cable’s pins are the same configuration as an S-video cable. So I took an old keyboard cable from the office, brought it home, and used it to connect the Mac to the dock. Then I took a standard RCA-type stereo cable and connected it from the line-out port on the top of the iPod to the Mac. (When I connected that cable from the dock to the Mac, I had no volume control and I still can’t figure out why.)

I fired up the two devices and set up a slide show. The iPod’s music immediately played through the Mac’s Bose speakers. It sounded really good at any volume. But to get the video to show up, I had to fire up an application that comes with the 20th Anniversary Mac. I think it’s called Apple Video Player. It enables me to use the built-in TV tuner (which doesn’t work here on the edge of nowhere) or to take video from an external source. It recognized the iPod Photo’s signal and displayed the images onscreen as a slide show. The only drawback: I had to set monitor resolution to 640 x 480 to get it to work right.

So now, when I have company, I can entertain them with music and a slide show, playing in the background while we chat.

Needless to say, I use the 20th Anniversary Mac a bit more often now.

Writing about Tiger

Posted on by
Comment

I begin work on my Mac OS X book revision.

I started working on my Tiger book this week.

So far, I have three of the 21 chapters done. I skipped Chapter 1, which is about installation and configuration. I always do that one last. Instead, I dove right into the Finder chapters: Finder Basics, File Management, Advanced Finder Techniques.

I added some new information to the File Management chapter about a new and undocumented feature called burnable folders. This was a challenge. Although I could figure out how to use this feature and write sufficiently about it, there wasn’t a single mention of it anywhere in online help or Apple’s Tiger Web pages.

What burns me up about this is that although I couldn’t find any official documentation about the feature, there was an article, with screen shots, on someone else’s Web site. Why does that burn me up? Because I had to sign a nondisclosure and swear up and down that I wouldn’t share anything about Tiger — especially screen shots — with anyone until the software was released. Technically, if my husband looks over my shoulder while I’m writing, I’d be in violation of this agreement. So that prevents me from giving my readers a sneak preview of the software and getting them all fired up for what’s to come. Yet someone else can publish articles on the Web, for the world to see, without getting in trouble. Does that sound fair?

Anyway, about burnable folders, to make matters worse, since I’m working with pre-release software, the feature isn’t perfected yet and is a bit buggy. Or perhaps it just set up conflicts with my screen shot software. In any case, my eMac was acting up and had to be restarted periodically. So it took me the better part of an afternoon to write two new pages and rewrite two others.

The Advanced Finder Techniques chapter was completely reworked. I pulled a lot of material out of this chapter to make a new chapter (Chapter 6) about customizing the Finder. This required complete renumbering of all figures throughout the chapter. A tedious task, but someone has to do it.

Next week, I continue writing with a brand new chapter about Apple’s new Spotlight and Smart Folders features. I hope to be able to knock that one off in two days.

If It Ain’t Broke…

Posted on by
Comment

I relearn something I’ve been telling people for years.

My production Mac, a dual processor G5, started acting up yesterday. It decided, out of the blue, that it would either restart or shut down whenever it felt like it. It seemed particularly fond of doing this right after I’d revised a page of my manuscript but before I’d saved that page to disk. At least that’s how it seemed. It got to the point that I stopped using it. I’d just let it run and start up programs, one-by-one, to see which of them would trigger the problem.

But I think I caused (and then resolved) this problem. I’d been playing with Nicecast (covered elsewhere in these blogs) and had discovered, by looking at the Console log, that some piece of software was unsuccessfully searching for a piece of hardware, in the background, while I worked. It wrote an entry to the log file once per second. That couldn’t be good. It must be using processor power. So I had to make it stop.

I began my witch hunt with a few messages to programming types like Dave Mark (author of a great C book) and the makers of Nicecast. They are obviously better with Google than I am, because they both came up with a Web page that pointed to my problem: a Canon scanner driver. It seems that when you install the driver for the LiDE scanner, two drivers are installed. One driver runs the scanner. The other driver spends all its time looking for a scanner that isn’t attached. Now what rocket scientist at Canon thought that up? So I attempted to delete the drivers, just to see if I could get the log messages to go away.

That’s where I screwed up. I somehow managed to drag a driver from its folder without disabling it. Every time I tried to drag it to the trash, I got a message saying that it couldn’t be dragged to the trash because it was open. I tried restarting my Mac. I tried renaming the file. The damn file couldn’t be deleted. In the old days of Mac computing, you’d occasionally get a folder like that. We called them “folders from hell.” This was a file from hell.

Eventually, I gave up and went back to work. And that’s when the computer started acting up. The first time it shut down, I’d stepped away from my desk to retrieve something from the printer. I thought I’d somehow used the shut down command. I mean, who expects their computer to just shut down by itself? But when it started doing it while I was working, I suspected a problem. It was a windy day and I thought that maybe the wind was causing power problems. Although the computer is attached to a UPS to prevent power problems from shutting it down, I thought the UPS might be dead. They don’t live forever, you know. Of course, nothing else was shutting down and not everything in my office is attached to a UPS.

After fiddling around with the UPS for a while, I started to suspect a hardware problem. Not what I needed. The G5 is less than two years old. None of my other Macs have had serious problems, and I’ve owned at least ten of them since 1989.

Then I started thinking about that file from hell. Perhaps it was triggering something really nasty in my computer, something that would bring everything down. I became determined to get rid of it.

I tried starting the computer with the Mac OS X 10.3 Panther install disc. I used Disk Utility to repair the disk (no problems) and permissions. Of course, there’s no access to the Finder when you start from that disc, so I couldn’t just drag the nasty file to the trash. When I restarted from my hard disk, the file still couldn’t be trashed. So I opened Activity Monitor, found the file’s process, and terminated it. Then I dragged it to the trash, emptied the trash, and restarted.

The computer behaved itself after that. I’d like to think that that was the problem and that I’d solved it.

So let’s review this: I find an error message in my Console log, which I really shouldn’t be looking at in the first place. I act on what I’ve seen and cause a problem that causes spurious restarting. I lose about three hours of work time causing and then resolving the problem. And now I can’t use my scanner until I reinstall the driver(s). The moral of this story: don’t look in the Console log. Or, better yet, the golden rule of computing: If it ain’t broke, don’t fix it.