Oracle's Java version 7u25 and below have been disabled by Apple on OS X. Updating to the latest release will allow Java to be run on Mac OS X. » » » » » » » » » » » » » » » » » » » » » » See information about. Yes, see the instructions on the Apple website.

1. For Mac Work Version Get Pagedefrag Servetter

If you have JDK 7 or later versions installed on your system and you want to restore Apple Java 6, then those JDK versions need to be uninstalled first. See the instructions to.

Operating system requirements: For Java 7 and later versions, you will need an Intel-based Mac running Mac OS X version 10.7.3 (Lion) and above. Installing Java on a Mac is performed on a system wide basis, for all users, and administrator privileges are required. Java can not be installed on a per-user basis. Browser requirements: A 64-bit browser (Safari, for example) is required to run Oracle Java on Mac.

For Java versions 6 and below, Apple supplies their own version of Java. For Mac OS X 10.6 and below, use the feature (available on the Apple menu) to check that you have the most up-to-date version of Java 6 for your Mac. For issues related to Apple Java 6 on Mac, contact Apple Support. Oracle and Java.com only support Java 7 and later, and only on 64 bit systems. Mac OS X and Apple Java 6 End of Life Apple has posted notice that Mac OS X 10.11 (El Capitan) will be the last OS X release that supports Java 6, and as such, recommends developers whose applications depend on Java 6 to migrate their apps to a newer Java version provided by Oracle. » (apple.com). Chrome browser versions 42 and above.

Starting with Chrome version 42, Chrome has disabled the standard way in which browsers support plugins. You can download Java from java.com. Mac OS X 10.6 and below: Apple's Java comes pre-installed with your Mac OS. Mac OS X 10.7 (Lion) and above: Java is not pre-installed with Mac OS X versions 10.7 and above. To get the latest Java from Oracle, you will need Mac OS X 10.7.3 and above.

If you have Java 7 or later versions, you will see a Java icon under System Preferences. Java versions 6 and below are listed in the Java Preferences.app located in the Applications Utilities folder on your Mac. Mac OS X 10.7.3 and above: Under System Preferences click on the Java icon to access the Java Control Panel which will list your Java version. If you do not see a Java icon under System Preferences, Java 7 or later versions is not installed. When you install Oracle Java on your Mac (Lion and above), Java will be enabled by default.

If you are running a Java application in the browser, you will need to also check that. For earlier versions of Java, check the Apple Support site. See See See For Java versions 6 and below, Apple supplies their own version of Java.

Use the feature (available on the Apple menu) to check that you have the most up-to-date version of Apple's Java for your Mac. Users of Lion Mac OS X 10.7.1 and 10.7.2 should upgrade to 10.7.3 or later versions, so you can get the latest Java version from Oracle.

Oracle highly discourages users from using older versions of Java. Installing old and supported versions of Java on your system presents a serious security risk. Upgrading to the latest version of Java ensures that Java applications will run with the most up-to-date security and performance improvements on your system.

You can confirm that you have the latest version on the. If installing an older version of Java is absolutely required, you must first uninstall the current version. See the instructions on the. Apple disables the Java plug-in and Webstart applications when the Java update is done using Software Update. Also, if the Java plug-in detects that no applets have been run for an extended period of time it will again disable the Java plug-in. The Java Runtime depends on the availability of an Application programming interface (API).

Some of the API were added in Mac OS X 10.7.3. Apple has no plans to make those API available on older versions of the Mac OS. See During an auto-update, Mac OS X 10.9 (Mavericks) users might see the installation stall.

Download the latest Java from the. Installing a JRE from Oracle does not update java -version symlinks or add java to your path. For this functionality, you must install the full JDK. Provide us details on for reporting issues or providing feedback for Java. You might also be interested in:.

I get this question fairly often from customers. They may be complaining of a slow computer and as soon as they see the desktop they start clicking on the browser, when that doesn't load they click on two or three other apps and then stare at the screen for a few seconds and then say, 'See. This is what I am talking about. It will take a long time before I can get on the internet, and it use to not take this long.' After a minute or so they freak out when a bunch of windows start opening up and that is their second complaint.

After I tell them that their computer has not booted yet and they are rushing it, the final question comes, 'How do I know when my computer is booted?' I'm tired of telling them to look at the drive light and saying, 'OK, there see how the light quit working. Oh wait, there it goes again.

You need to wait a little longer. Ok now it stopped. Well, anyway, just don't try to get on the internet until the drive light stops flashing a lot.'

I thought I would nip these customers complaint in the bud by simply downloading a program that will display or beep or play music, when everything if fully loaded. But guess what? I can't find such a program. Does anyone know of any or even a small utility that I could utilize to say that indicates all the loading has finished? Hello AnselAdams, I agree with Stuart's suggestion of a startup batch file. You can time a users average profile logon time from bootup as well, because logon in addition to bootup creates a delay.

Once you know of this time, you can create a batch file that runs on startup and Echoes a message on the screen saying something like 'Please be patient while the log on process completes on this machine' and then use the sleep command to wait so many minutes, making sure the message does not disappear. Once everything has stablized, you can have another message echo saying 'The boot and/or log on process is now complete, please proceed, thanks for your patience' Also, in my opinion, this is also a user training issue, they just need to have some patience. You might also want to investigate if the bootup or logon process is taking too long, very simple remedies can make the logon and bootup much faster. Hope that helps.

Because of the multi-user multi-threading multiple processes nature of the OSes it's near impossible to do this definitively. There is a portion of the kernel where certain groups of services and processes have to be started before other groups, thus ensuring dependencies. So, something to say they've all 'started' is one thing, something to say not only have they started but they have done all their launch procedure housekeeping and loading and have settled in to their virtual memory and minimum active memory footprint, um. That's another reason why watching the hard disk activity light is a great / the best idea, because also the swapping to virtual memory pagefile.sys when all the juggling balls are most busy will be reflected by the light. User-training to have some patience. Agree with that.

User-training to look at the disk activity light, you bet. Estimating how much time, well that would be guessing, there are many variables that can change one boot to the next or over time, so you'll be fielding complaints when it's not right. Returning from hibernation there are some programs that will be tedious to restart nevertheless, such as browsers with continually active java/flash code/content, or a Live Messenger or the like, popular end-user apps like Limewire. Another really big one is anti-virus. Take AVG for instance, sometimes you'll see avgupd.exe or what have you taking tons of memory and tens upon tens of megabytes of disk activity until it has finished updating, depending on the size and nature of the update and cumulative update history. See for yourself, launch Task Manager, processes tab, View, Select Columns, and see VM size (changed name in Vista/7/2008, and button needing admin priviledge to view all user processes) and I/O read and write bytes. Perhaps a little program that runs for several minutes at logon, but have it be an equivalent of a disk activity light, flickering to the point of lit solid, coloured red, big, in their face.

Just elaborating on the first 2 suggestions. If you placed a text file in the User's Startup folder, it would probably be the last place to start.

It would start after. Drivers and Services Userinit.exe Winlogon.exe Explorer.exe (what your users are seeing.) HKLM.Run HKLM.RunOnce HKCU.Run HKCU.RunOnce All users startup User Startup. Theres tons more in terms of startup locations but these are the major ones.

The text file can simply say 'Please use your computer now.' I disagree, for the reasons given. Quick n easy things like a notepad in startup won't cut it because that's exactly the same as the desktop icons show up so then they start clicking away despite/paying no attention to the fact the system is bogged down still starting things. Which reminds me, a couple of other things to look for. The problem can be too full or too fragmented or too slow of a hard disk.

As bad sectors begin to occurr on a disk, and they will happen normally over time, the drive might be doing retries. If the s.m.a.r.t values approach certain internal thresholds the firmware logic of the hard disk might switch into read after write or verify after write mode, which will significantly slow down all drive performance, maybe 3X+ slower. The problem can also be not enough RAM, but even with tons of ram the virtual memory swapping to pagefile.sys happens slow if the hard disk is slow (unless you have so much memory you can turn it off alltogether) One mistake novice technicians make all the time is put in more ram BUT the resulting larger pagefile.sys and hiberfil.sys are then scattered all over the too full hard dive and thus severely fragmented. A severely fragmented pagefile.sys will adversely affect startup performance. Microsoft aquired the systernals company, that made a tool to defrag the pagefiles and other usually undefraggable files, use PageDefrag or use PerfectDisk or the like. Clearly I'm too far off on a tangent about startup performance and performance in general.

We can talk about the fact that the RAM requirements of WinXP have more than doubled over time because of all the hotfixes and service packs, as well as updated larger more secure browser versions and of course anti-viruses and anti-spyware that have grown ten-fold+ in size. People don't expect their car to get slower or need twice the gas with every oil change.

This is a common problem - and there's no 'simple' solution. On MOST systems there's something that always tends to be last - for example, if there's an HP printer on the system, the checkmark that appears on the HP Digital Imaging Monitor icon is usually the last thing to happen in the boot process. If you're using AVG (and not an HP printer), the AVG icon usually indicates you're ready. With Microsoft Security Essentials, it's when the icon turns green with a checkmark. But it's very much dependent on the actual system. The reason is simple: Windows is a multi-tasking OS, so it starts ALL of the startup items as soon as it encounters them. That's the reason, for example, that you'll often see a security warning that 'no antivirus is installed' or 'xxx antivirus program is not active' - and then it will disappear.

It's simple a race condition - and the Security Center check has finished loading before the antivirus program. In addition to being 'ready', systems that have everything set for automatic updates also need a few seconds (typically 15 to 30) for all of those utilities (antivirus; Windows Update; Adobe products; Java; etc.) to 'phone home' and check the update status. Using the system before these complete will also seem a bit sluggish.

The best solution is to educate the user that these things are all happening, and it simply needs time to complete. Many of the early events will cause an hourglass icon on the cursor - but some of the later events do not, so that's not a good indicator. I'd simply tell them to wait for 30 seconds after the appearance of one of the late-to-build icons appears (AVG, the HP checkmark, the MSE icon, etc.). Or perhaps just some specific length of time after the desktop appears (one minute is usually plenty). You COULD use a batch file as suggested earlier with a simple Wait timer followed by a popup message that says 'System is now ready' - but that would NOT be a 'real' indicator. Since what it would really mean is 'You've not waited long enough that the system SHOULD be ready':-) Better to simply educate your users as to WHY it takes a while after the desktop appears before the system is really ready to go. In addition to my comment above about using a Batch File to echo a banner to the user and sleeping the banner for some time, in addition to user training.

You can also have the batch file run as a part of user's logon batch file, especially if you are in an Active Directory envionment. Log on batch files are prioritized during the logon process and will show the 'Please be patient.' But like I said, the most important thing you can do, is user training. It might seem trivial, but if this is a big problem you face, you can include a step to tell new and existing users about to be patient when doing a new user orientation etc. If this is getting to be a serious problem, then you even investigate moving to faster hardware and minimizing the boot up and log on time by doing some troubleshooting and using tools such as msconfig etc to minimize unneeded services.

Belabering the point a little more, the bottleneck is rarely cpu, but for the occaisional badly written process. Your initial instinct about watch DISK activity is correct, NOT cpu usage.

Are there some processes that tie up 96% cpu at times, sure, but. Fellow experts will also have seen this, a check of the processes shows only a couple of 2% or 6% little blips AND YET the system is still bogged down starting all the programs. Happens all the time, startup included, why is my computer slow and busy, the cpu is at below 10%?? The answer is disk activity, check the disk activity and you'll see that THAT IS the usual bottleneck. Virtual memory swapping to pagefile.sys also is lots of disk activity but measures virtually no CPU cycles in task manager.

I'm also guessing that these systems you have the user issues with aren't ready to go in quick 30 seconds but more like many MINUTES, which is why it's a problem. And just because the AVG icon shows up, does NOT mean it's finished bogging down the system at boot time yet, incremental updates accumulate in disk space to go through each time, and when the larger AVG engine 'program' updates happen now and then those take even longer, in the BACKGROUND, making the system seem slower and less responsive. This is true of pretty much all anti-virus, they have to update, usually when you turn on after being off for awhile. Annother one is Windows Update itself. That too will sometimes be a process that bogs down a system shortly after booting. It generally has to go through many files on the drive checking to see if all the various security updates are in place, and after being off is often the time it needs to check it. RealPlayer is a notorious one.

It was a great app, we thank them for inventing streaming, utlater versions became badly behaved bloatware and make some top-10 listsof bad software to avoid, uninstall, go with RealAlternative. Not exactly on point to your question, I'll mention a somewhat related issue. Seems like if you have an external hard disk, then during the Windows boot process, you'll notice the widows flying logo, then a black screen, and it stays that way for an INORDINATELY long time while the disk activity light on the external drive flickers away like crazy, and then finally Windows continues to load. It's as if windows scans the ext drive contents for something, other installations of windows probably. It happens with different anti-viruses,adismost noticeable under XP and excruciatingly long if USB 1 instead of USB 2. You can avoid this delay entirely and greatly speed up booting if you remember to have turned off external drives, wait until windows desktop appears and THEN turn on the external drives. Thanks a lot all.

I see that the 'solution' is as puzzling to most of you as it was to me. That's a good point noxcho, but the likelihood of my customers even having the slightest vague reference to BIOS or CMOS, is remote. These are people that don't know when windows is booted and hardly have the concept that you run a browser to get on the internet. You know, you ask what browser are you using and they say, 'You mean Windows XP?' To: ocanadatechguy and garycase: In my past life I was a programmer (computer repairman now) and I recall using a function or command to wait for all processes to finish.

More or less it changed multitasking code into procedural code. I assume it would call Windows API. Of course this was in the current program. I'm wondering if there is a place in the API that I could call to perform that task. It actually doesn't do anything other than to wait for all processes to complete or stop. Most of you have experience with all types of people from the beginner to advanced.

Apr 17, 2018 - So, I have got this shiny new Macbook Pro and installed VirtualBox on it to run some Linux boxes. Here is what I got when trying to start one:. Oct 15, 2012 - Can't find ATK0100 driver, Can't open ACPI ATK0100 kernel mode driver, Must install ATK0100 driver.' After closing the errors the system. May 6, 2013 - Error:'Can't open ACPI ATK0100 kernel mode driver', could occur when. It is not suggested to download drivers/software's from third party. Atk0100 kernel driver for mac. Aug 23, 2006 - This package supports the following driver models:ATK0100 ACPI UTILITY.

My biggest accomplishment was teaching a 95 year old retired attorney how to find Supreme Court cases on the internet. The biggest problem was to have him click without moving the mouse. Everything else went smooth. So there are a lot of varieties of people problems and a down and dirty solution would be nice to have. I've spent the time teaching and explaining but sometimes it's like talking to a wall only to find at the next boot process the user is quickly clicking on every icon allowing a few seconds pause before going to the next as they stare at their desktop in disappointment. You all gave me good places to start but I wanted to place a few bugs in your ears hoping that something might click. Here's another one besides the 'process all processes' above.

I did find a program that claimed to give you the boot time your computer took. I didn't download or install it, but it gave me the impression that there is some hook to tell you when all is done. But after reading the experts on here, maybe that 'hook' doesn't exist and the programmer simply was making a judgment call that could be variable. In addition, I do know that some people check the date stamp on their pagefile.sys file to see when it was booted. I'll wait for a few more responses and see what you guys come up with.

I've often wished Windows had a setting that basically said 'don't show the desktop until you're REALLY done booting':-) But of course there isn't such a function - in fact, the emphasis is on exactly the opposite. The goal is to show the desktop as quickly as possible so the APPARENT boot time is kept reasonably small. I suppose you could create a simple batch file that (a) displayed a large window with a message that says 'Please wait for background programs to finish their boot processes'; (b) waited for a specified time (you could set this for each system.

Make it PLENTY long ); and (c) closes the message window and perhaps sends a message noting that the system is now ready (probably not really needed, since the disappearance of the 'Please wait' message would be a good enough indicator). Nobus: I got off on a different tangent and haven't got around to downloading the program but will tonight.

I really don't think there is one file that is updated last (my current tangent) except for WindowsUpdate.log in the win directory. And I think that it only works if you have MS updates turned on. Of course for now I'm focusing on XP. I wrote a short program to watch WindowsUpdate.log time stamp and at best, I would read it and check it ever 10 or 15 seconds looking for a time change, and then consider it booted.

However it would really occur mabye up to 30 seconds later. Also it written to (time stamp change) numerous times as it nears a final boot. Bottom line is that I more or less gave up on that concept for now. I would probably want to address the CPU usage programmatically and suspect it might be a bear to accomplish. At least for me. I really hate this guys since I have a lot of anxiety picking who to give the points to while at the same time not diluting the points to almost nothing.

EVERYONE and I mean everyone has given me great advice and things to ponder. Nobus has directed me to the place that helped the most, but that's not to say the rest of the post are not invaluable to me, not only on this question but answers many others. I will split this the best way I can and I apologize in advance if you think I shorted any of you as you all deserve points. I used nobus' idea of CPU usage.

I found source code in the language I'm least rusty in, Delphi 7/Pascal and modified it for my needs. The original source was written by WhiteShadow and I think modified by him from C or VB original. I made a good deal of sophisticated and convoluted code to test for a full boot that was a complete waste of time, and have just started to fall back to simple code that has two basic settings. A threshold level (such as less than 5% usage on all cores) and number of seconds the computer stays at this level. Once both are reached the app pops up a 'computer ready' screen. I haven't done enough testing to see if this will be universal on different computers, and nothing on different OS's. The problem is cores now.

For Mac Work Version Get Pagedefrag Servetter

Wouldn't you know they would change the rules? Anyway, it will now work on up to 6 cores. As a side note, I noticed on my dual core machine, when I compile, there are parts that has the second core at 100% while the first core is at 0%. And for an extended period of time. I do think the drive light would be best but with the tools that I have this CPU usage is very close and behaves much the same way. And like most of you mentioned, user training is the best. But my 'solution' (for lack of a better word) will be used as a tool for the most stubborn customers that just don't get it.

It reminds me of the customer that was in my face how it took him forever to send photos by email and everyone else he knows doesn't have a problem with sending photos and they know little about their computer. I spent enough time with him how to reduce the size and what program to use. He really didn't believe me. That other people were shrinking the size whether manually or automatically. After not seeing him for about a year he was praising the program I had him download and telling me how many different people he has taught how to reduce the size of some new giant megapixel camera produced photos for emailing. Again, thanks all for the help and enlightenment!

Thanks nobus, I wish I had more to test but here is where I got so far: That's the file called BootWatch.exe. Put it in a folder and place a shortcut to it in your Startup. It will display the percentage usage per core. At the same time it is checking for two things: 1) The floor threshold that we would consider to be Zero.

IOW, when the CPU activity is below 3 or 4, let's say, is effectively little processing. Or no processing to be in the way. 2) The number of seconds that it has remained below the threshold level. As far as item #1, it is the average of all cores. IOW, you can have a dual core running at 70% each, but for #1 that would be 70%. (I was using the total of all cores at first trials but I think this is better.) My default setting for #1 and #2 are, 7 and 14.

If you put an.ini file in the same folder as BootWatch.exe, you can change these settings. It's a standard ascii file but it must be named, BootWatch.ini. The upper/lower case is important for all of this and the contents. The contents inside the file should look like this: SamplingSettings NoActivityPercent=7 NoActivitySeconds=14 So you can change the numbers.

These are whole numbers and if you use a decimal point it will ignore the whole file, and go with default setting inside my program. First, my goal: My goal was NOT to make a definitive indicator of when the computer is booted, but just be a little more accurate than a simple timer.

Did I accomplish that goal? To be honest, I'm not sure. Probably not except maybe for the next step. The second part of the goal was to make it universal, so I wouldn't have to adjust it from one customers machine to the next. Although I have it setup to use the.ini settings, that really was just for my/our use for testing/fine tuning. At this point, I wouldn't say it is fine tuning but coarse tuning. It's pretty sensitive.

As ocanadatechguy said, the closest thing that we can come to is the disk drive activity light. I will talk more about that in the next post and what I have found. Obviously this is a no frills app; it doesn't write anything. I have only tested it on two dual core machines and one single core (standard cpu) laptop. All were XP flavors. I don't know how it will behave on other OS's.

I am using a 3rd party library which may not work with anything above XP. I just don't know. Also I don't have any error checking for cores above six. I assume the program with crash on a higher core count giving a nondescript error. From the Startup it usually loads and displays the activity in the middle of the boot. Once it gives you a message your computer is booted everything disappears (true close) so if you leave the room, you'll miss it. That's all I can think of for now and please anyone feel free to use it and test it.

Just don't expect it to be too useful. I would like to hear any insight you can give me, including if it works on Vista and Win7? As ocanadatechguy indicated the disk bottlenecks might make the above BootWatch of little use. The ideal situation is to watch the disk activity light and record it's behavior to detect the boot completion. I'm pretty sure the activity light is processed only through the bios and hardware. I came across a 'software solution' but it is more an emulation. It only works with.Net Framework (starting with ver 2.0).

My Delphi is one generation too old to incorporate the.Net Framework however I have Visual Studio that will do it, but I'm too rusty to reinvent the wheel with it. Regardless, during my tests, the software really bogs down the boot process, so it's a non issue at this point for me.

The way it works is this:.Net Framework has routines to monitor files or folders for changes. It can also monitor the entire hard drive or even multiple hard drives. I'm sure the app was buffered a lot as it wasn't as active as the hard drive light. The app places a green/red square in the taskbar. It might change every five or six seconds.

Not this on and off you see with the hard drive activity light. I found something interesting.

A file is written often, especially near the end of the boot process. It is c: windows system32 config Software. Typically there are about 5 or 6 writes in sequence, then a pause of about 5 to 10 seconds and then more writes to it. A brief search gives me the impression it is the changes to the registry and more or less used as a cache in the event the writes cause problems with the registry so it can be restored.

So typically the file size is small or almost nothing. I'm thinking about pulling the date and time stamp off that every few seconds until it is seldom written. I 'was' going to do that after the end of CPU activity, e.g., bump the threshold activity up on the BootWatch program, above, so it will fall through to the disk monitor (iow, watching the one single file changing). My thought are that this will narrow the target of the true boot conclusion. I am still a little puzzled that MS avoided this. It does make sense to make it difficult to follow a number that can be written down about 'boot time' and/or the nature of multitasking just doing things and not wasting the time to do a query how long it will take, but it still seems a 'procedural accomplishment point,' (for lack of better terms), could have been used.

I suspect the big problem is the bottle necks the DMA causes that the CPU is unaware of. If you haven't been following this thread this all came about because of customers not knowing when their computer was booted and generally these are people with very old and slow computers. Does anyone know about the Mac? Is it very clear when it is booted or are you in limbo until you are familiar with the particular machine. Way back in the old days (DOS), I remember extending an LED to above my monitor so I could watch the disk activity. Unfortunately neither CPU activity nor disk activity completely resolves the 'done booting' question. For that matter, it's not clear that multiple folks would even agree what constitutes the 'done' point:-) For example, I suspect Microsoft's position on 'done' booting is when (a) you're at the desktop; (b) all RunOnce and Run registry items have been executed; and everything in the Startup folder has been executed.

But you can't simply monitor these to determine the 'done' point, as many of these items don't run to conclusion, but simply load a process that's then resident throughout the OS session For example, I load several hardware monitoring utilities - for CPU temps; hard drive temps; CPU and network monitoring; etc. In addition, even after these are all done, there are many other processes that tend to do things shortly after a boot - the indexing service will kick off; any programs that are set to do automatic updates will check the web for available updates Windows; Adobe; HP utilities; security utilities (virus, spyware, etc.); etc. 'Done' in my view is simply the point when the system becomes 'normally' responsive. I suspect that a combination of low CPU activity (as measured by BootWatch) and a reasonable period of no disk activity is probably a reasonable indicator that the system has reached that point - but that combination could happen just as a major update for your security package 'kicks in'. Which could impact the system's responsiveness.

Rather than trying to programmatically measure this and send a 'Done' message, I'd simply educate your users that it's best to wait a few minutes after the desktop appears before using the system. And let them know that if they don't that it's normal for the system to be notably less responsive. In the FWIW category, I've found that for most configurations there's usually some specific icon that tends to regularly occur 'last' - you could also simply tell folks to watch for that specific icon; although this is still not a reliable 'done' measure. But it's easy to educate users to at least wait for that icon to appear On systems with HP printers, the checkmark on the HP monitor icon is usually last; on others the MSE or AVG icon is last; etc.

You should be able to run the exe at any time, and should get a display with horz bars of cpu activity. BTW, I downloaded it from here to be sure it works the same and it does for me. Let me know if you still can't get it to run by manually running it from the desktop.

For the last couple of months I've been moving my customers over to MSE and that seems to be a very good indicator when things are booted. Just a few seconds after the checkmark appear on the tray's icon. But I do educate my users that have problems not knowing when it's booted. What prompted my question are those 'few' customers that are instructed and it's still a mystery to them. I mainly deal with in-home pc users and not businesses.

Of course my corporate accounts don't have any problem understanding when a computer is booted and for that matter that they know the difference between Internet Explorer and XP. I don't want to beleaguer the ignorance of some customers other than to say it is real and some people just don't get it. My home customers are usually elderly or rich and it's not unusual for me to arrive to turn the on/off switch on the power strip that magically got turned off by their feet, or to replace an inkjet cartridge because their printer was 'broke.'