Kernel loadable modules in backtrace (with dependencies):
com.apple.filesystems.afpfs(3.8.2)@0x19816000
Kernel loadable modules in backtrace (with dependencies):
com.apple.filesystems.afpfs(3.8.2)@0x19816000
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOGraphicsFamily(1.2.6)@0x1a33f0 00
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOGraphicsFamily(1.2.6)@0x1a33f0 00
Kernel loadable modules in backtrace (with dependencies):
com.apple.filesystems.afpfs(3.8.2)@0x23055000
Kernel loadable modules in backtrace (with dependencies):
com.apple.filesystems.afpfs(3.8.2)@0x23055000
Now these lines tell me that two kernel modules are involved, com.apple.filesystems.afpfs and com.apple.iokit.IOGraphicsFamily. The first one is related to AppleTalk and the second probably to your video card. To eliminate these as possible problems you should turn off AppleTalk (System Preferences->Network->AppleTalk and uncheck Make AppleTalk Active) and you should try reinstalling your video card drivers.
However you didn't say if you have added anything to the computer, such as RAM. Very often a bad stick of RAM can cause the types of panics you are experiencing. I say this because a lot of the panics don't seem to involve kernel modules. Even those panics that did involve a kernel module could be caused by RAM problems. To see if this is the case try booting from the hardware diagnostic disk and run hardware tests. If nothing comes up then try shutting down and removing 1 stick of RAM (after market RAM first) and then starting up. See if your system is more stable without it. If it is then that RAM is probably bad, if not repeating this with another RAM stick.
Worst case, do a reinstall of your OS. Here is a PDF of the process.
That's very unusual, you have to have something corrupted. I admin around 40 Mac OS X 10.2 machines and haven't had a kernel panic in at least 6 months.
First of all, try running Disk Utility (found in/Applications/Utilities/). Click on your boot partition at the left and hit the button on the right "Repair Disk Permissions". Sometimes those get messed up and programs that need to run with certain permissions can't do so and crash. SecurityAgent is one of those. It's probably also a good idea to boot off of the System disks that came with the computer and do a Repair Disk with Disk Utility, just to be sure.
If you post the log and stuff like what OS version, type of computer, was any new hardware added to the system (including memory), etc. I'll see if anything jumps out as a problem. Like I have said, your situation is very unusual and it should be taken care of.
It isn't without bugs, and my system hangs every once in a while. Maybe once every 2-3 weeks.
That's odd, why is it hanging so much? I haven't had a true hang or crash with Mac OS X in about 6 months or so. It might be a bad driver or a corrupted NetInfo database. Take a look at/var/log/system.log and see what is the cause of those hangups. Often you can see what is the cause by the number of tries as the system attempts to do something like a NetInfo lookup. There are several ways to fix these problems, a quick Google should help you out with that.
Maybe that happened on an early version of 10.2x? I didn't use 10.2.x earlier than 10.2.5...
It used to happen with 10.1.x and earlier. Ever since Jaguar (10.2) I haven't seen this problem pop up. Apple has been pretty good about actually improving Mac OS X with every version. It actually gets faster with every revision too!
With the Mac office, it was ONLY me and I was doing nothing most of the day.
See the trick is to have a Mac office but LOOK busy. Run around a lot, shut down some machines and claim that you are applying fixes, keep frowning and shaking your head (thanks to George Castanza for that trick) because it looks like you have a lot on your mind, always have some papers in your hand. Then you can have the ease of Macs and still look like you are busy.
I run two labs of 20 iMacs in each and I haven't had to touch the things in months. If I didn't work hard at looking busy they'd realize they could probably replace me with a monkey and those machines would still run as well!
OO in C++ is horrible. Learn OO with Ruby, Python or Squeak and you shall see the light.
Or even move on to Objective-C, which is pretty much parallel to C++ in that it can use plain-vanilla C but Objective-C uses a Smalltalk-type messaging system for object calls. The cool thing is that the latest Objective-C compilers can also use C++ code so that you don't need to re-write old code.
Basically Objective-C is C with objects, but done in such a way that it doesn't feel like the object-oriented stuff is just bolted on. C++ always felt to me like it was too much of an afterthought, and a clunky implementation at that. With Objective-C everything seems to fit together much more logically. The NextStep/OpenStep/GNUStep/Cocoa libraries are great to work with also.
Yeah it's hot but we put a couple of big fans in them and make do, it's not too bad. See, it's a Boys & Girls Club in a poor inner city neighborhood and we barely have enough money for the buildings and the staff, let alone for air conditioning.
Actually, we're lucky that we had those iMacs donated to us. Those computers are perfect for us, really no administration or maintenance needed on them so we can afford to have computer labs. If we needed a full time support staff then there's no way we could have computer labs at all.
I've also seen heat-death claim a lot of iMac systems, so I'm somewhat leary of them on that
I don't know what kind of ambient temperatures those machines were running at but I have 2 labs with 20 iMacs each and have had no problems at all. Neither of these labs are air-conditioned and both have had ambient temperatures of 95 degrees Fahrenheit.
Here's a serial port for $12.99 and a parallel port for $9.99. So for $23 more you can get the ports you say are missing. As for a large footprint, it's the same size as a 17" monitor that you'd use for any other computer - except of course it's all-in-one, no space taken up by an additional computer case.
More expensive you say? Not when you figure in total costs of ownership of each type of system, you can read more about it here.
In the end it comes down to user preference. Don't count Macs out because of some lame myths that are floating around. Choose the operating system you feel comfortable with and that fits your needs.
We had a severe ice storm and most of blacksburg lacked power. but so did campus!
It's probably the same problem the North East had a few months ago. One set of power generating equipment goes out and several closely related systems do the same. This is because when one part of a grid goes down the demand suddenly shoots up in another part, overloading circuits. These circuits automatically shut down to avoid burning up. When enough gets shut down the power plants also shut down to avoid mucking up the situation further.
That power plant you are talking about was probably still able to generate but since the transmission system was mucked up it was not able to provide power. The thing is, if these systems were designed a little better and were better able to split up into smaller independent grids then we would have less problems when one of them goes down.
NSRangeException: [NSCFString substringWithRange:]: Range or index out of bounds</blockquote
Ok, to break this down:
NSRangeException - This is an exception raised by an error condition in Objective-C code, from the Next Step libraries (actually Cocoa, but it's descended from Next Step
NSCFString substringWithRange: - The exception is raised when messaging the NSCFString class through the substringWithRange method
Range or index out of bounds - either the number sent to the class was too large or it referenced a value beyond the end of the class. Most likely the string the program was attempting to substring was too large and instead of overflowing the program threw an exception.
The good thing is that Cocoa is largely protected from buffer exploits because it generally checks the bounds of arrays before dumping data into them. If something would overflow the array then it will most likely throw an exception rather than doing something bad. Thus, Cocoa programs are generally pretty secure - as long as you don't break the functionality by circumventing it and rolling your own standalone classes.
If you're mass-duplicating CDs, you're either going to use a Disk Duplicator (about $200-$300 now - put in a master, put in one or two blanks, repeat in 5 minutes - heck, they even have robot arms to mass-feed them!), a program that lets you make copies (shouldn't Apple's Disk Copy let you do this?), or have access to a plant and can make thousands on demand.
Well we were speaking in the context of using iTunes and burning directly from a playlist, not using other tools. Obviously there are other ways to make copies of the stuff you bought from the iTunes Music Store. This just highlights just how minimal Apple's DRM is, it's really just a nod towards copy protection. It's not meant to stop you from doing what you want with the music, it's meant to make the record companies feel warm and fuzzy about Apple's store.
Wait a second, this is the guy who copyrighted silence right? So how do you write 4 minutes and 33 seconds of silence? All rests? That just makes it even more funny.
However, a 5-second blank track would work, but it would probably infringe the Cage estate's copyright as an excerpt from his "4'33'".
Yeah that was a funny case. I gotta say that I support patents, copyrights, and trademarks for reasonable uses but this goes just a bit too far. Copyrighting a large chunk of silence is just yet another example of the blatant abuse of intellectual property laws. Laws that were originally meant to give a creator some control over his works have now been twisted to lock out people from creating new works and using old works in new and innovative ways.
OK, I'll get off my soapbox now. Wait - has that phrase been copyrighted? Ahh damn...
I never really understood the concept of "number of CD burns" restriction. Seems to me that if you could burn the audio tracks once to a CD, then you could just copy the copied CD, or rip the files to mp3 and do whatever you want with them.
Actually all you need to do is change the order of the songs in the playlist and you can then burn them another 10 times. I believe even adding a 1 second blank track to the end of the playlist would work also.
I think the point is that it is a tiny speed bump to trip up someone who is trying to mass duplicate a downloaded CD. No one who has a legitimate use for the CD is going to realistically need to burn it more than 10 times so most people won't be bothered by this limitation. However, someone mass duplicating the CD would have to fiddle with it every 10 tries and would not create a perfect copy after they moved stuff around.
So yeah it's just a nod towards DRM but it's enough to get the music companies to allow Apple to sell their stuff. Remember that Apple is the first to get a bunch of major labels to agree to selling individual tracks electronically. In order to do this there had to be some roadblocks to mass duplication.
Files *created* by iTunes when you rip your CDs are standard AAC files. However, files downloaded from the music store are NOT standard AAC files, and the DRM is most definitely NOT "volutarily enforced" by itunes. They are encrypted and keyed to the computer which you license with Apple.
There is no such thing as a standard AAC file. AAC (Advanced Audio Coding) is a codec, not a file format. The AAC files created by iTunes are actually.m4a files and the files that come from the iTunes Music Store are.m4p files. Basically the m4a and m4p files are Quicktime files that use AAC encoding to store music. The m4a data is unencrypted and the m4p data is encrypted.
Other players could definitely play the m4a files if they worked out the file format. Knowing Apple the file format is probably readily available to developers. The m4p files, by nature of the encryption, would require either cracking the encryption or partnering with Apple in order to play on a 3rd party music player.
I pulled those fans out and they looked like they could be replaced by standard, quieter fans. I took one from the last PC I'd built...
I noticed the apple supplied heatsink was BURNING hot...
I ditched that heatsink...and replaced it with a Zalman flower...The heatsink for the G4 attached differently, but it was easy enough to adapt the zalman with insulated wire tied underneath the CPU board...
the powermac booted, and stayed working far longer. For about three days, and from then on it wouldn't boot...
It turns out because I had MODIFIED the computer that my warranty was void. wtf? I added a superior cooling system to the machine, quietened it, IMPROVED it in every way, and they deny my claim?
OK, let me get this straight. You took a perfectly functioning computer for which the only problem was that it was loud. You replaced the fans on that computer without making sure that the replacements had the same airflow. The computer overheated so you got a completely different type of heatsink than the one that came with the computer. The heatsink didn't fit but you retrofitted it onto the processor. Then computer went completely belly-up. Face it, you didn't improve the computer in any sort of way, you made it worse and it malfunctioned.
Now none of these parts were approved by the manufacturer and I'm pretty sure that you are not a certified Apple technician, yet you still expect the store you bought it from to fix what you messed up. There is pretty much no company out there that would take back any product treated in this manner. If you retrofit stuff be prepared to pay for any mistakes you make, that's standard in any industry.
I'm sorry you had to learn this lesson the hard way but that's the way the world works. Don't blame Apple for your foolishness.
The funny thing is that people absolutely loved the cube. It didn't fail on its design or performance, it failed on its price point. It was just too expensive compared to biting getting a tower with the tower's better expansion options. If they could have sold the cube at 2/3 the price or so then it probably would have sold like crazy.
People just weren't willing to pay the price for miniaturization that came with the cube. It was halfway between a laptop and a tower and suffered the disadvantages of both - the high price of a laptop and the non-portability of a tower.
One good thing about the Apple//e was that here was no way that you could permanently mess it up short of physically destroying it. The Apple//e didn't maintain any data between power down and power up so if you screwed it up all you have to do is power down, wait 10 seconds and then power it back up. Yes you could screw up some diskettes and they would never work right again but the Apple//e didn't need a diskette to work.
So go ahead and mess up every Apple//e in school. I'm sure the administrator just powered them down and back up and they were fine. This is unlike the Commodore 64 which had a nasty bug where if you quickly toggled certain registers you could fry a chip on the motherboard and ruin the entire motherboard. I had a friend who ran a program which turned out to be a trojan horse of sorts and it did just this, toasting his Commodore.
Anyhow, here's the real spin here: Apple fucked up, and now they're going to pay.
How is that? They opened the iTunes Music Store (iTMS) as soon as they could, which meant just for Macs because that software was an easy write and done first. They have been extremely successful with iTMS for the Mac which has encouraged more artists to sell their songs through the store, building up the music catalog. Now there is news that Apple may have the Windows software finished early. A quote from the article:
And Apple, NEWSWEEK learned, quietly informed some music insiders that it's moved up the date for expanding its current Mac-only iTunes for the vast universe of Windows-based PCs to mid-October.
Now Dell on the other hand has been lagging in the music field. They only have an announcement of their plans and a promise that it will be out in time for Christmas. From the article:
Dell products that will be available for purchase in time for the holidays include a digital music player, online music service, multifunction LCD television and computer monitor, a home entertainment projector and a wireless handheld.
There are almost no details about all of these things. It doesn't say what artists will be available on the music service. It doesn't say the size of the player, it's features, what formats it supports, how large the hard drive, the price. It doesn't mention much about the multimedia application other than saying it will be an "important tool".
Frankly right now all this amounts to vaporware. Apple has products out for months or years that have proven themselves and made waves. People drool over the iPod and compare any new music service to iTMS. Dell's offerings, even if they come out in time and are amazing, are going to take time to build a user base. In the meantime Apple will have the lead and as long as Apple continues to innovate it should maintain a lead. At the very least the two might split the market down the middle, leaving a very nice chunk for each of them. Considering all this I would say that it is extremely unlikely that "Apple fucked up, and now they're going to pay".
Hmm, no problems with anything in the Microsoft Office suite. Word, Excel, and Powerpoint work just fine so far. It must be some odd combination of factors that causes problems.
Hmm, you probably could find out where that application is and remove it. It can't launch what's not there. When the thing runs control-click on it in the dock and select "Show in Finder", then drag it to the trash.
You might get away with just moving it or renaming it also, depending on how Mac OS X locates it.
Well, this has *an* update to ssh, I dunno if it's *the* update to ssh.
Yep, according to this technote it's *the* update to ssh:
Mac OS X 10.2.8
OpenSSH: Addresses CAN-2003-0693, CAN-2003-0695, and CAN-2003-0682 to fix buffer management errors in OpenSSH's sshd versions prior to 3.7.1
sendmail: Addresses CAN-2003-0694 and CAN-2003-0681 to fix a buffer overflow in address parsing, as well as a potential buffer overflow in ruleset parsing.
fb_realpath(): Fixes CAN-2003-0466 which is an off-by-one error in the fb_realpath() function that may allow attackers to execute arbitrary code.
arplookup(): Fixes CAN-2003-0804. The arplookup() function caches ARP requests for routes on a local link. On a local subnet only, it is possible for an attacker to send a sufficient number of spoofed ARP requests which will exhaust kernel memory, leading to a denial of service.
Slashdot Mirror
OK, some of the more relevant lines here are:
Kernel loadable modules in backtrace (with dependencies):
com.apple.filesystems.afpfs(3.8.2)@0x19816000
Kernel loadable modules in backtrace (with dependencies):
com.apple.filesystems.afpfs(3.8.2)@0x19816000
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOGraphicsFamily(1.2.6)@0x1a33f0 00
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOGraphicsFamily(1.2.6)@0x1a33f0 00
Kernel loadable modules in backtrace (with dependencies):
com.apple.filesystems.afpfs(3.8.2)@0x23055000
Kernel loadable modules in backtrace (with dependencies):
com.apple.filesystems.afpfs(3.8.2)@0x23055000
Now these lines tell me that two kernel modules are involved, com.apple.filesystems.afpfs and com.apple.iokit.IOGraphicsFamily. The first one is related to AppleTalk and the second probably to your video card. To eliminate these as possible problems you should turn off AppleTalk (System Preferences->Network->AppleTalk and uncheck Make AppleTalk Active) and you should try reinstalling your video card drivers.
However you didn't say if you have added anything to the computer, such as RAM. Very often a bad stick of RAM can cause the types of panics you are experiencing. I say this because a lot of the panics don't seem to involve kernel modules. Even those panics that did involve a kernel module could be caused by RAM problems. To see if this is the case try booting from the hardware diagnostic disk and run hardware tests. If nothing comes up then try shutting down and removing 1 stick of RAM (after market RAM first) and then starting up. See if your system is more stable without it. If it is then that RAM is probably bad, if not repeating this with another RAM stick.
Worst case, do a reinstall of your OS. Here is a PDF of the process.
I hope this helps you out!
That's very unusual, you have to have something corrupted. I admin around 40 Mac OS X 10.2 machines and haven't had a kernel panic in at least 6 months.
/Applications/Utilities/). Click on your boot partition at the left and hit the button on the right "Repair Disk Permissions". Sometimes those get messed up and programs that need to run with certain permissions can't do so and crash. SecurityAgent is one of those. It's probably also a good idea to boot off of the System disks that came with the computer and do a Repair Disk with Disk Utility, just to be sure.
First of all, try running Disk Utility (found in
Also take a look at these discussions to see if it relates to your problem:
Nvidea-related kernel panic
Keychain-related problems
Can you post the kernel panic log? Here's some info on how to find it:
Mac OS X: What Is a Kernal Panic?
Mac OS X: How to Log a Kernel Panic
If you post the log and stuff like what OS version, type of computer, was any new hardware added to the system (including memory), etc. I'll see if anything jumps out as a problem. Like I have said, your situation is very unusual and it should be taken care of.
That's odd, why is it hanging so much? I haven't had a true hang or crash with Mac OS X in about 6 months or so. It might be a bad driver or a corrupted NetInfo database. Take a look at
Good luck and welcome to the Mac!
Here's some info to help you:
Total cost of ownership article and links
A fairly balanced and well-thought-out comparison of Mac OS X and Windows XP
Apple's own site on switching from Windows to Mac OS X
Hope these help!
It used to happen with 10.1.x and earlier. Ever since Jaguar (10.2) I haven't seen this problem pop up. Apple has been pretty good about actually improving Mac OS X with every version. It actually gets faster with every revision too!
See the trick is to have a Mac office but LOOK busy. Run around a lot, shut down some machines and claim that you are applying fixes, keep frowning and shaking your head (thanks to George Castanza for that trick) because it looks like you have a lot on your mind, always have some papers in your hand. Then you can have the ease of Macs and still look like you are busy.
I run two labs of 20 iMacs in each and I haven't had to touch the things in months. If I didn't work hard at looking busy they'd realize they could probably replace me with a monkey and those machines would still run as well!
Or even move on to Objective-C, which is pretty much parallel to C++ in that it can use plain-vanilla C but Objective-C uses a Smalltalk-type messaging system for object calls. The cool thing is that the latest Objective-C compilers can also use C++ code so that you don't need to re-write old code.
Basically Objective-C is C with objects, but done in such a way that it doesn't feel like the object-oriented stuff is just bolted on. C++ always felt to me like it was too much of an afterthought, and a clunky implementation at that. With Objective-C everything seems to fit together much more logically. The NextStep/OpenStep/GNUStep/Cocoa libraries are great to work with also.
Yeah it's hot but we put a couple of big fans in them and make do, it's not too bad. See, it's a Boys & Girls Club in a poor inner city neighborhood and we barely have enough money for the buildings and the staff, let alone for air conditioning.
Actually, we're lucky that we had those iMacs donated to us. Those computers are perfect for us, really no administration or maintenance needed on them so we can afford to have computer labs. If we needed a full time support staff then there's no way we could have computer labs at all.
I don't know what kind of ambient temperatures those machines were running at but I have 2 labs with 20 iMacs each and have had no problems at all. Neither of these labs are air-conditioned and both have had ambient temperatures of 95 degrees Fahrenheit.
Here's a serial port for $12.99 and a parallel port for $9.99. So for $23 more you can get the ports you say are missing. As for a large footprint, it's the same size as a 17" monitor that you'd use for any other computer - except of course it's all-in-one, no space taken up by an additional computer case.
More expensive you say? Not when you figure in total costs of ownership of each type of system, you can read more about it here.
In the end it comes down to user preference. Don't count Macs out because of some lame myths that are floating around. Choose the operating system you feel comfortable with and that fits your needs.
It's probably the same problem the North East had a few months ago. One set of power generating equipment goes out and several closely related systems do the same. This is because when one part of a grid goes down the demand suddenly shoots up in another part, overloading circuits. These circuits automatically shut down to avoid burning up. When enough gets shut down the power plants also shut down to avoid mucking up the situation further.
That power plant you are talking about was probably still able to generate but since the transmission system was mucked up it was not able to provide power. The thing is, if these systems were designed a little better and were better able to split up into smaller independent grids then we would have less problems when one of them goes down.
Ok, to break this down:
NSRangeException - This is an exception raised by an error condition in Objective-C code, from the Next Step libraries (actually Cocoa, but it's descended from Next Step
NSCFString substringWithRange: - The exception is raised when messaging the NSCFString class through the substringWithRange method
Range or index out of bounds - either the number sent to the class was too large or it referenced a value beyond the end of the class. Most likely the string the program was attempting to substring was too large and instead of overflowing the program threw an exception.
The good thing is that Cocoa is largely protected from buffer exploits because it generally checks the bounds of arrays before dumping data into them. If something would overflow the array then it will most likely throw an exception rather than doing something bad. Thus, Cocoa programs are generally pretty secure - as long as you don't break the functionality by circumventing it and rolling your own standalone classes.
Well we were speaking in the context of using iTunes and burning directly from a playlist, not using other tools. Obviously there are other ways to make copies of the stuff you bought from the iTunes Music Store. This just highlights just how minimal Apple's DRM is, it's really just a nod towards copy protection. It's not meant to stop you from doing what you want with the music, it's meant to make the record companies feel warm and fuzzy about Apple's store.
Wait a second, this is the guy who copyrighted silence right? So how do you write 4 minutes and 33 seconds of silence? All rests? That just makes it even more funny.
Amazing, absolutely amazing.
Yeah that was a funny case. I gotta say that I support patents, copyrights, and trademarks for reasonable uses but this goes just a bit too far. Copyrighting a large chunk of silence is just yet another example of the blatant abuse of intellectual property laws. Laws that were originally meant to give a creator some control over his works have now been twisted to lock out people from creating new works and using old works in new and innovative ways.
OK, I'll get off my soapbox now. Wait - has that phrase been copyrighted? Ahh damn...
Actually all you need to do is change the order of the songs in the playlist and you can then burn them another 10 times. I believe even adding a 1 second blank track to the end of the playlist would work also.
I think the point is that it is a tiny speed bump to trip up someone who is trying to mass duplicate a downloaded CD. No one who has a legitimate use for the CD is going to realistically need to burn it more than 10 times so most people won't be bothered by this limitation. However, someone mass duplicating the CD would have to fiddle with it every 10 tries and would not create a perfect copy after they moved stuff around.
So yeah it's just a nod towards DRM but it's enough to get the music companies to allow Apple to sell their stuff. Remember that Apple is the first to get a bunch of major labels to agree to selling individual tracks electronically. In order to do this there had to be some roadblocks to mass duplication.
There is no such thing as a standard AAC file. AAC (Advanced Audio Coding) is a codec, not a file format. The AAC files created by iTunes are actually
Other players could definitely play the m4a files if they worked out the file format. Knowing Apple the file format is probably readily available to developers. The m4p files, by nature of the encryption, would require either cracking the encryption or partnering with Apple in order to play on a 3rd party music player.
Here are the notes for the MPEG-2 AAC Standard and the MPEG-4 AAC Standard
OK, let me get this straight. You took a perfectly functioning computer for which the only problem was that it was loud. You replaced the fans on that computer without making sure that the replacements had the same airflow. The computer overheated so you got a completely different type of heatsink than the one that came with the computer. The heatsink didn't fit but you retrofitted it onto the processor. Then computer went completely belly-up. Face it, you didn't improve the computer in any sort of way, you made it worse and it malfunctioned.
Now none of these parts were approved by the manufacturer and I'm pretty sure that you are not a certified Apple technician, yet you still expect the store you bought it from to fix what you messed up. There is pretty much no company out there that would take back any product treated in this manner. If you retrofit stuff be prepared to pay for any mistakes you make, that's standard in any industry.
I'm sorry you had to learn this lesson the hard way but that's the way the world works. Don't blame Apple for your foolishness.
The funny thing is that people absolutely loved the cube. It didn't fail on its design or performance, it failed on its price point. It was just too expensive compared to biting getting a tower with the tower's better expansion options. If they could have sold the cube at 2/3 the price or so then it probably would have sold like crazy.
People just weren't willing to pay the price for miniaturization that came with the cube. It was halfway between a laptop and a tower and suffered the disadvantages of both - the high price of a laptop and the non-portability of a tower.
One good thing about the Apple //e was that here was no way that you could permanently mess it up short of physically destroying it. The Apple //e didn't maintain any data between power down and power up so if you screwed it up all you have to do is power down, wait 10 seconds and then power it back up. Yes you could screw up some diskettes and they would never work right again but the Apple //e didn't need a diskette to work.
//e in school. I'm sure the administrator just powered them down and back up and they were fine. This is unlike the Commodore 64 which had a nasty bug where if you quickly toggled certain registers you could fry a chip on the motherboard and ruin the entire motherboard. I had a friend who ran a program which turned out to be a trojan horse of sorts and it did just this, toasting his Commodore.
So go ahead and mess up every Apple
How is that? They opened the iTunes Music Store (iTMS) as soon as they could, which meant just for Macs because that software was an easy write and done first. They have been extremely successful with iTMS for the Mac which has encouraged more artists to sell their songs through the store, building up the music catalog. Now there is news that Apple may have the Windows software finished early. A quote from the article:
Now Dell on the other hand has been lagging in the music field. They only have an announcement of their plans and a promise that it will be out in time for Christmas. From the article:
There are almost no details about all of these things. It doesn't say what artists will be available on the music service. It doesn't say the size of the player, it's features, what formats it supports, how large the hard drive, the price. It doesn't mention much about the multimedia application other than saying it will be an "important tool".
Frankly right now all this amounts to vaporware. Apple has products out for months or years that have proven themselves and made waves. People drool over the iPod and compare any new music service to iTMS. Dell's offerings, even if they come out in time and are amazing, are going to take time to build a user base. In the meantime Apple will have the lead and as long as Apple continues to innovate it should maintain a lead. At the very least the two might split the market down the middle, leaving a very nice chunk for each of them. Considering all this I would say that it is extremely unlikely that "Apple fucked up, and now they're going to pay".
Hmm, no problems with anything in the Microsoft Office suite. Word, Excel, and Powerpoint work just fine so far. It must be some odd combination of factors that causes problems.
Hmm, you probably could find out where that application is and remove it. It can't launch what's not there. When the thing runs control-click on it in the dock and select "Show in Finder", then drag it to the trash.
You might get away with just moving it or renaming it also, depending on how Mac OS X locates it.
Yep, according to this technote it's *the* update to ssh:
Just go to the NetResore/Carbon Copy Cloner web site that he had links for. They have full and detailed instructions on how to do it there.