Open Firmware displayed on Desktop

Hi all,
I was wondering has anyone come across a problem where open firmware is displayed on the desktop. It happened when the computer was being shutting down. The computer all of a sudden displayed the open firmware screen over the desktop, the prompt was displayed but it wasn't possible to type anything in. The computer is a 1.8Ghz G5, 10.3.9. All the fans started running and the mac was left over night. The fans were still running the nextday and it was shutdown. I had a look in the System Profiler and the only thing that I could see that was relevant was this error
localhost loginwindow[179]: sendQuitEventToApp (iCalAlarmScheduler): AESendWithMach returned error -1712
Nov 6 13:41:30 localhost kernel: AFPSleepWakeHandler: waking up
Nov 6 13:41:30 localhost mDNSResponder[138]: mDNSResponder Waking at 8751262
Nov 6 17:33:40 localhost loginwindow[179]: sendQuitEventToApp (iCalAlarmScheduler): AESendWithMach returned error -1712
Nov 6 17:33:41 localhost loginwindow[179]: halting
Nov 6 17:33:42 localhost shutdown: halt by machine_3:
Nov 6 17:33:44 localhost syslogd: exiting on signal 15
Nov 7 09:47:37 localhost syslogd: restart
Does anyone know what this error means?
Fiachra.

Fiachra:
I think it was possible to run "repair disk" while booted from the hd a couple of osx versions back.
You cannot repair the volume from which you are booted. That is why you need to boot from the install disk, or another volume, e.g. while booted from a Firewire external boot volume, or from another mac while in Firewire Target Disk Mode. You can do a certain amount of Disk Repair by Starting up in the Safe Mode.
I have read verious oppinions about which way was best to run "repair permissions" so I tough the jury was out on that one.
While you can Repair Disk Permissions while booted from the install disk doing it from the Utilities Folder on the boot disk is preferable because it examines and repairs the latest permissions on the boot volume. At least that is the rationale I have seen, which seems to make sense to me.
On the other topic, I use Tech Tool Pro regularly and I try to do it at a time when I am not using the computer for anything else so I don't have to worry about how long it is taking. Many users prefer for Disk Warrior for directory repairs, although I find TTP to be as efficient, and it does the other things as well.
Good luck.
cornelius.

Similar Messages

I have a text window open that displays every move I make on the desktop and I can't get rid of it. Help!

My grandson was playing with my mouse and keyboard and did something so that now I have a text window open that displays every move I make on the desktop and I can't get rid of it. Help! The window continuously tells me where I am, etc.

Go to System Preferences > Universal Access > Seeing Tab > Turn VoiceOver off.
Or CMD FN F5
Captfred

G5 Boots to Open firmware on Startup every time.

I have a 2004 model Dual 1.8GHz 2.2Gbs RAM. The problem is that it keeps booting into Open Firmware. Once it gets to Open Firmware and i can mac-boot and start up off the Tiger disc, but I can't get it to find an external firewire OS. I don't have a hard drive in there at the moment but that should not effect this issue, Although I can see the firewire 800 in disk utilities but not on the Firewire 400. And still no Start up folder when i go to startup disk 800 or 400. If I put a hard drive in which i will when the new one arrives I believe i will be able to start up with it but I still think that it might boot into Open Firmware again. (I think a bus is bad maybe the Firewire bus if it is can't I bypass it somehow? so that is won't boot into Open Firmware.
Note: everything passes Hardware Test
I have Reset PRAM and NVRAM Rest all

(Sorry this is in here twice - I'm pretty experienced with Macs and PCs but a little new at message boards - pls forgive)
Had the same problem. I took mine into a "Mac Genius" at the retail store and he thought he had fixed it by rebuilding the directory. It booted and shut down perfectly while in the store. When I got home it was went right back to booting into open firmware.
I figured out by accident that the reason it was booting fine in the store was because he was using a cheap SVGA monitor on the DVI output - not the ADB connector I use with my older Apple monitor. Note that Apple has phased these type of connectors out. It gave me a great excuse to upgrade my monitor to a 20" cinema display and everything is working great (can't believe how I've deprived myself all these years).
If you have an older monitor that uses an ADB connector, try a different monitor that uses the DVI output on your video card. Even a DVI-VGA adapter (one probably came with your computer) with a VGA monitor is sufficient for testing. If your computer boots up, it's either the older monitor, or the ADB output on the video card that is bad. There is no easy way to know where the actual problem resides (the Geniuses couldn't tell me - they have no monitors in the store with ADB connectors), but I can tell you that my computer is working fine now. I do know that the ADB connector ran power, USB and video all together and that seems to be the reason they quit using them. The newer desktops have only 2 DVI outputs (instead of 1 ADB + 1 DVI), while the new monitors run power, USB and video separately.
Hope that helps,
Jeff

Strange boot bug; open firmware not working

Hi!
I have a powerbook Alu 15", 1.5Ghz. It runs OS X 10.4.2 with the latest security update. My problem started last Saturday.
The problem is that my pb will not restart nor boot on its own. The computer makes its usual chime, the hard-disk starts to spin for a few second, and then stops suddenly before anything is displayed on the screen (the display does not even light-up). If I press the option key after or before the chime, and keep it pressed, or the shift key, or the c key, or the t key, or the command-option-p-r key combination, or even the command-option-o-f key combination, the behavior is exactly the same: the disk starts to spin for a few second after the chime, and suddenly halts. The computer appears to shutdown on its own before the boot can even start.
Here is the strange part: the computer boots normally if I press the command key (this key on its own is not suppose to do anything). It also works if I press the command-s or command-v key combination. No other key combination seem to work.
Except for this strange boot behavior, the computer works flawlessly. I did not have any kernel panic for at least a year, the computer did not crash recently, everything works fine except for one small detail on which I will come back at the end.
I've tried to fix the problem by the following actions:
1) Clean install of Tiger with a new partitioning of the disk; I even zeroed the entire disk. This did not change anything so the problem is probably not OS related.
2) Reset of the PMU with the four finger salute: shift-control-option-power combination. No effect except that I lost the date/time information. Hence the reset worked.
3) Tried to reset the PRAM, but the command-option-p-r key combination does not seem to work.
4) Tried to load the open firmware with command-option-o-f, but this does not work either.
5) Memory seems ok. I have 1x256M of Apple RAM + 1x1G of RAM bought from OWC. I've had the OWC RAM for about a year without any problem. Anyway, I removed the 1G module and tried to boot on the 256M Apple module alone. Exact same behavior. Then I removed the Apple module and put back the 1G module. Exact same boot behavior. So the problem is not with my RAM, unless both modules have simultaneously developed a malfunction.
6) Tried to run the Apple hardware tests. However, for my machine, these tests come on the install DVD, in a special hidden volume. To boot on this special volume, one needs to boot with the option key depressed, and to select the boot volume from the open firmware interface. But this does not work on my machine, the computer seems to shut down before this interface can be activated!
So this problem is very strange. I can live with having to press the command key for booting my machine, but I would sure like to know what is going on here. Is the problem hardware related? Perhaps, but as I said, the machine works flawlessly except for the strange boot behavior.
Is the problem related to firmware? I think that this is the most probable option. What do you think? Maybe, the firmware got slightly corrupted? Maybe a bit got flipped in the flash memory? Is this possible? I guess so. But, what can I do? Should I contact my friendly local repairman?! I have to admit that this option scares me a little bit for such a strange problem. I would need an Apple engineer with boot related experience/expertise!
Now, here is a little bit of further information. I don't know if its related, but it is also very strange. I work with a dual screen configuration. Usually, I connect my screen and then I wake up the computer. Last week, I noticed that if I connect my second screen live, the system detects it automatically. I guess this is new to Tiger? Anyway, the strange behavior is that the computer then asks me if I want to sleep, restart or shutdown my pb, as if I had pressed the power button. But I did not press this button when I connected the dvi connector >:-o
Many thank

Hi Scott!
Almost every time the PowerBook woke after sleep, I got the 'Are you sure you want to shut down your computer now...' message.
I get this message upon wake only rarely, but every time I plug or unplug a display live.
The strange behaviour was tolerable, so I've lived with it for several months. But then when checking out the PowerBook discussions, I read about the failing lower RAM slot problems, and just out of interest, checked out my System Profiler....
Ok, so the good news is that my pb may continue to work for several months
My lower RAM slot appears to be ok for now.
Interestingly, I'm sure that the start-up problems began when I started using my PowerBook with a 23" Apple Cinema Display (a pink hued one, but that's another on-going saga) - and you too have mentioned that you use an external display, so I wonder if that's part of the cause of our start-up problems.
Yes, I've noticed the 'Are you sure you want to shut down your computer now...' message just a few days before noticing the strange boot problem (not sure if the machine booted in between). I use ViewSonic displays (one at home and one at the office), and several different projectors in different class rooms. From what I read, it is plausible that there is a link between this problem and the dvi port. Could it be that the boot sequence of mb is affected by a hardware problem on the dvi port? But not when a press the command key?!
Anyway, my machine is no longer under warranty, so I intend to live with the problem for as long as possible...
But I've been doing more regular backups since then.
Best wishes to you and your (almost) new machine!
Marc.

Beige G3 boot from **** problem; open firmware issues; bad motherboard?

Dear all,
I'm having huge boot/startup problems with my beige G3 that had been happily running OSX 10.3.9, but for purposes of this discussion we can (mostly) revert to OS 9. Originally, the machine was a G3 @300; was upgraded more than a year ago to a ZIF G4 @500.
To make a long story short, it won't boot from any hard drives, will not boot from any OS X CD, and will only occasionally boot from a 9.x startup CD (whether Apple or Norton Utilities). I think it's an open firmware issue, possibly caused by a bad motherboard (rev. 2).
All this started happening after I used techtool pro, but I think that's coincidence (even though I acknowledge that, for cops and computer users, there are no coincidences.) Also, as discussed below, I'm having the same problems with an HD that wasn't even in the computer when all these things began.
Here are some of the things I've done.
--repeatedly reset PRAM, both with key combinations and removing battery. The only time it will boot from a 9.x CD is after resetting PRAM.
--removed all add-on PCI cards.
--removed additional VRAM
--removed all memory cards and tried replacing one at a time.
--disconnected both existing hard drives and replaced with an older OS 9.x hard drive (approx 60 mb) that I'd used before. Also tried different ribbon cables.
--unplugged floppy drive
--disconnected PCI ATA disk controller that I'd been using for running a large (1.8 gb) hard drive.
--regarding open firmware: readenv usually shows totally normal default AND installed settings. Using reset-all works fine -- at least it makes the machine reboot, but doesn't solve the problem. reset-nvram does NOT work -- says it's an "unknown word."
--using startup keys like holding down the option key, or shift key, or X key or cmd-option plus two others I can't remember, has no effect. Again, after I've tried any kind of reboot, the ONLY way to get the C-key at startup to boot the CD is by resetting the pram (key combination). Otherwise, the usual result of these experiments is a dark screen on startup -- nothing at all (and the LCD monitor tells me "no input.")
--regarding OSX: sometimes (and I emphasize sometimes) I can get the machine to start booting from an OSX 10.2 CD, but it won't complete the process. Sometimes I get a "prohibited" (as in no-parking, no-smoking) icon; sometimes it will start booting (grey screen, OS X Apple icon), then crash (horizontal grey and white jagged bars); sometimes it will show the OS 9 start icon (the tiny smiling Mac SE), but not boot at all.
--when I get the mac successfully booted with an OS 9.x CD (again, this works sometimes, but not always), the old hard drive with two partitions does show on the desktop and can be accessed. Using either disk repair or Norton Utilities shows the 9.2 system partition on the hard drive to be fine. But if I go to the startup disk control panel, confidently set the 9.2 partition as my startup disk, then reboot, there's no change. It won't boot and I'm back at square one.
--even when I do get successfully booted with 9.x, the machine will still occasionally crash for no reason -- ie when I'm moving a Window.
--the only thing I haven't done is slowed down the processor. It's a ZIF G4 bought more than a year ago from XLR8 your Mac. I'm running at the default 500 mhz, and it's never given me any trouble.
So I think it's a bad motherboard or ROM. Thoughts?
Thanks.

The beige Mac is now operating happily again. My original tentative diagnosis remains the same (although still tentative): corrupted PRAM from bad battery, compounded by bad cables that wrote corrupted data to hard drives, and also (possibly) allowing Tech Tool Pro (a utility that I now regard with deep suspicion) to create a "virtual" startup partition.
A few things I've learned along the way that hopefully may be useful:
--remember that the Ex Post Facto utility can be used to help OS X startup, not just installation. This applies to hard drives, emergency CDs, installation CDs, etc. If you can boot into any working hard drive partition (OS 9 or a backup OS 10), then run Ex Post Facto (same program runs on either OS 9 or X -- don't ask me how) and tell it what system you want to start up from. Also, the utility has sometimes told me that the startup extensions on the disc that I wanted to boot up from were bad, and offered to fix them (which works).
--at least on my Mac (beige, v. 2 motherboard), resetting the CUDA button, resetting the PRAM, resetting Open Firmware and "draining" the memory by unplugging the computer and disconnecting the battery for several hours ALL DO DIFFERENT THINGS.
Specifically, if I'm having trouble booting (from a hard drive or a CD), the FIRST thing I do is restart and resetting the PRAM on the fly -- holding down command, option, P and R at startup, and waiting for the chimes (preferably at least 3-4 times).
If I do that and DON'T hear the chimes, that's my cue for my SECOND action -- restarting into open firmware (command, option O and F keys on startup). That should bring up the black text on white background open firmware screen. View other posts or apple support for details, but if you do PRINTENV and see a bunch of weird gibberish after the default/installed lists, you know that it was messed up and you need to clear it through reset nvram and reset all commands. Be aware some of these commands do or do not work depending upon what version of Open Firmware you have.
After I've rebooted with Open Firmware, then on restart I should be able to reset the PRAM on the fly. If that works, then either let the machine run and see what happens, or hold down the C command and see if it will boot from the CD
Usually, if I've fixed everything as above, the machine will boot into whatever version of OS 9 it finds on a hard drive. That's fine with me -- at that point, use Ex Post Facto to reboot into your OS X. (Before I forget: I used the shareware startup CD creator program BootCD to make an emergency boot CD based on OS 10.2.8 (which theoretically will support a beige mac in native fashion) and Disk Warrior, the god of disk repair utilities. Even though the CD should boot just by holding down the C key on startup, it doesn't -- but if I use Ex Post Facto to boot it, no problems (although the process is very slow -- be patient). Then I can fix almost anything using Disk Warrior.)
If none of the above works, then I'll try resetting the CUDA (on my beige minitower, it's a very small black button inconveniently located between a PCI slot and the side of the computer housing). Hold it down for 15 seconds. That should REALLY clear the PRAM. I know this does something different from the previous steps because this is the only action (except the battery disconnect -- next) that clears the date and time from the memory.
If all else fails, I will unplug the computer and disconnect the battery, then push the CUDA button for 15 seconds and let the machine sit overnight.
One final finding -- I thought I'd fixed everything, but both my hard drives suddenly quit working, I discovered that during all this repeated connect/disconnect of things, one of the male pins inside one of the connectors on my Acard ATA PCI card had broken off. Not good. Fortunately, the card had a second connector, which works fine. And I did some extensive shaking of the computer to make sure (I hope) that the broken pin hadn't landed on a circuit board.
All this took more than two weeks, and the advice of this board was much appreciated. Now I'm on to my next adventure -- trying to figure out why a combo Firewire/USB PCI card won't mount an external drive on Firewire, but will on USB. I've tried two cards with same result -- but a Firewire-only card works just fine.)
Regards to all,
Graham

PowerBook G4 17" Boots into Open Firmware; Won't boot from HD or Disk

This PBG417 (1GHz/512MB/60GB) has an complex recent history directly related to this problem. It was thought to have a dead logic board, and was given to me for a very insignificant amount of money. I discovered today (at an Authorized Apple Repair center) it merely had a ribbon cable disconnected from the logic board which kept it from powering on, which, when rge cable was reconnected it did on the spot, fully booting (imagine my satisfaction). However, upon getting home, it booted into Open Firmware instead, and offedrs a choice of typing mac-boot or shut-down. Mac-boot takes it to the grey screen where the question mark/Finder guy blink and nothing happens. I put a grey PowerBook G4 17" system disk in, but not the one that shipped with it, hoping it would do. When I try to boot from disk, it goes to Open Firmware, I enter mac-boot, it goes to happy Finder with no question folder, but stays there with the optical drive occasionally making movememts and sounds. If you enter any command besides shut down or mac-boot, iot says unknown word; the command prompt itself is 0> .
I'm not sure the hard drive is seated correctly. When I got the computer, the drive was removed; I put it in an enclosure and installed Tiger on it and put it back in, but apart from connecting the ribbon cable, it just sat in its bay not fixed down. However, it booted correctly the first time it was successfully started.
Finally, the previous owner removed all 23 bottom case screws when he took out the drive and lost them; the Apple repair tech mustered up about 9 and put them in the crucial locations but it's still not screwed down everywhere, although the one time it booted correctly, it had no screws in it.
It seems the computer doesn't read the hard drive or the disk, but the hard drive mau be installed wrong and the disk, while for a 17" was not the one that shipped with this PowerBook 17". The computer is missing many case screws, bnutg booted properly only when there were none it place. I also tried resetting the PMU but am not sure I did reset it because the Apple article isn't clear about which models have which processes. I tied Target Disk Mode but it woujldn't mount/boot.
How can I get the disk out and how to make it boot to the desktop?

You can try to reset NVRAM here is KBase from apple site:
http://docs.info.apple.com/article.html?artnum=42642
and after that reset PRAM in your unit, here is the kbase:
http://docs.info.apple.com/article.html?artnum=2238
If needed you can also tried to reset PMU, here is the kbase:
http://docs.info.apple.com/article.html?artnum=14449
Make sure you choose the correct step for your unit.
If after all the steps your unit still booting up to open firmware then there is possibility that you have corrupt NVRAM which could not be fixed by doing reset except replacing logic board.
Good luck. Hope this help
Flippo

Monitor refresh rates and Open Firmware

Does anyone know if it's possible to change the default monitor refresh rate of an iMac in Open Firmware and how?
Thanks.

Thanks but I think the iMac G5 does have a refresh rate or something analogous to one, in this case I believe it is 60 hertz. I want to know how to change it in firmware because I believe it will solve an issue my display suffers from. See here:
Stephen Durnin, "Horizontal wavy lines when screen shows too many dark pixels", 06:00pm Sep 16, 2005 CDT

Need urgent help on Sawtooth stucked at Open Firmware screen

Hello.
I've got a G4 Graphite Sawtooth Powermac running a Newertech MaxPower 2.0MHZ processor upgrade for about 3 years. It is running Leopard (10.5.8) system.
I've also installed a Seritek 1S2 card with a 500GB Sata disk.
Some days ago I've started to notice that sometimes when I did Log Off or Shut down the Mac cleaned all the desktop icons but then nothing happens.
Also, it started to freeze sometimes doing some tasks like open apps or working on Photoshop.
Today the Mac refused to boot on the main system disk (I have a secondary 80GB disk with Tigger installed on it).
Then I ran TechTool Pro Disck scan and it gave me an error on scanning the main disk.
I've booted into the Tiger disk (a 80GB one) and think to myself if this could be something to do with the Seriteck card or driver, or something related to it...
I've loaded the Seritek install CD and click the install firmware of the Seriteck disk, then I've booted and... it stucked on Open Firmware forever.
It is on the welcome screen of the open firmware and I can't do anything.
It says" To continue booting, type "mac-boot" and press return", but I can't type anything because it looks freezed. My keyboard don't respond.
I've tryed the firmware boot (that one with the long beep pressing the programmer button) at no avail.
I'm desesperate. I'm a freelancer and I've goot importante work to deliver to clients and I can't get my Mac to to boot into the system.
At this point I just want to boot normally into Tiger, Leopard, whatever.
I just need to boot and recover my works.
See screenshot of Open Firmware screen here:
http://img19.imageshack.us/i/dscn3061q.jpg/
Can someone please help?
Thank you for your time,
Macjaime

I ran TechTool Pro Disk scan and it gave me an error on scanning the main disk.
If you did a "Surface Scan", and not a "Volume Structures Repair", it is telling you there is a Bad Block on the Hard Drive.
There are two cases: It could be temporary, or it could be permanent. There are two sub-cases of each: It could be important or it could be unimportant.
When you run the test, and it tells you the Surface Scan has detected an error, you are supposed to ask it figure out what file is involved, and write it down. Then you can decide whether to delete that file and replace it with a good copy.
Bad blocks may mean your drive will not be working properly in six months, if you continue to use it full time. It could also die this afternoon -- no one knows. If you can re-initialize with Zero all Data (one pass) the drive will substitute some of its stash of spare blocks for any that remain bad after the zeroing. But of course all your data will be lost, and it takes a few hours to complete.
Some readers suggest that a drive that has had spare blocks substituted may last a long time at light duty, such as making an occasional backup.
The only article that comes up with a search for "default catch" has to do with drives that are really wacked out. It suggests you back up everything and re-initialize the drive.

Why do some of the pdf files I try to open just display a black screen?

Why do some of the pdf files I try to open just display a black screen?

Please see my current settings below Chrome PDF Viewer is Disabled and Adobe Reader is Enabled already.
Plug-ins (11) Details
Adobe Flash Player - Version: 12.0.0.41
Shockwave Flash 12.0 r0
Name: Shockwave Flash
Description: Shockwave Flash 12.0 r0
Version: 12.0.0.41
Location: C:\Users\njdp\AppData\Local\Google\Chrome\Application\32.0.1700.72\PepperFlash\pepflashpl ayer.dll
Type: PPAPI (out-of-process)
Disable
MIME types: MIME type Description File extensions
application/x-shockwave-flash Shockwave Flash .swf
application/futuresplash FutureSplash Player .spl
Disable  Always allowed?
Widevine Content Decryption Module - Version: 1.4.1.376
Enables Widevine licenses for playback of HTML audio/video content.
Name: Widevine Content Decryption Module
Description: Enables Widevine licenses for playback of HTML audio/video content.
Version: 1.4.1.376
Location: C:\Users\njdp\AppData\Local\Google\Chrome\User Data\WidevineCDM\1.4.1.376\_platform_specific\win_x86\widevinecdmadapter.dll
Type: PPAPI (out-of-process)
Disable
MIME types: MIME type Description File extensions
application/x-ppapi-widevine-cdm Widevine Content Decryption Module .
Disable  Always allowed?
Chrome Remote Desktop Viewer
This plugin allows you to securely access other computers that have been shared with you. To use this plugin you must first install the Chrome Remote Desktop webapp.
Name: Chrome Remote Desktop Viewer
Description: This plugin allows you to securely access other computers that have been shared with you. To use this plugin you must first install the Chrome Remote Desktop webapp.
Version:
Location: internal-remoting-viewer
Type: PPAPI (out-of-process)
Disable
MIME types: MIME type Description File extensions
application/vnd.chromium.remoting-viewer .
Disable  Always allowed?
Microsoft Office (2 files) - Version: 14.0.4730.1010
Office Authorization plug-in for NPAPI browsers
Name: Microsoft Office 2010
Description: Office Authorization plug-in for NPAPI browsers
Version: 14.0.4730.1010
Location: C:\PROGRA2\MICROS1\Office14\NPAUTHZ.DLL
Type: NPAPI
Disable
MIME types: MIME type Description File extensions
application/x-msoffice14 14.0.4730.1010 .*
Name: Microsoft Office 2010
Description: The plug-in allows you to open and edit files using Microsoft Office applications
Version: 14.0.4761.1000
Location: C:\PROGRA2\MICROS1\Office14\NPSPWRAP.DLL
Type: NPAPI
Disable
MIME types: MIME type Description File extensions
application/x-sharepoint SharePoint Plug-in for Firefox
Disable  Always allowed?
Native Client
Name: Native Client
Version:
Location: C:\Users\njdp\AppData\Local\Google\Chrome\Application\32.0.1700.72\ppGoogleNaClPluginChro me.dll
Type: PPAPI (in-process)
Disable
MIME types: MIME type Description File extensions
application/x-nacl Native Client Executable .
application/x-pnacl Portable Native Client Executable .
Disable  Always allowed?
Chrome PDF Viewer (Disabled)
Name: Chrome PDF Viewer
Version:
Location: C:\Users\njdp\AppData\Local\Google\Chrome\Application\32.0.1700.72\pdf.dll
Type: PPAPI (in-process)
Enable
MIME types: MIME type Description File extensions
application/pdf Portable Document Format .pdf
application/x-google-chrome-print-preview-pdf Portable Document Format .pdf
Enable  Always allowed?
Adobe Reader - Version: 11.0.05.3
Adobe PDF Plug-In For Firefox and Netscape 11.0.05
Name: Adobe Acrobat
Description: Adobe PDF Plug-In For Firefox and Netscape 11.0.05
Version: 11.0.05.3
Location: C:\Program Files (x86)\Adobe\Reader 11.0\Reader\AIR\nppdf32.dll
Type: NPAPI
Disable
MIME types: MIME type Description File extensions
application/pdf Acrobat Portable Document Format .pdf
application/vnd.adobe.pdfxml Adobe PDF in XML Format .pdfxml
application/vnd.adobe.x-mars Adobe PDF in XML Format .mars
application/vnd.fdf Acrobat Forms Data Format .fdf
application/vnd.adobe.xfdf XML Version of Acrobat Forms Data Format .xfdf
application/vnd.adobe.xdp+xml Acrobat XML Data Package .xdp
application/vnd.adobe.xfd+xml Adobe FormFlow99 Data File .xfd
Disable  Always allowed?
Java(TM) (2 files) - Version: 10.45.2.18
NPRuntime Script Plug-in Library for Java(TM) Deploy
Name: Java Deployment Toolkit 7.0.450.18
Description: NPRuntime Script Plug-in Library for Java(TM) Deploy
Version: 10.45.2.18
Location: C:\Program Files (x86)\Java\jre7\bin\dtplugin\npDeployJava1.dll
Type: NPAPI
Disable
MIME types: MIME type Description File extensions
application/java-deployment-toolkit
Name: Java(TM) Platform SE 7 U45
Description: Next Generation Java Plug-in 10.45.2 for Mozilla browsers
Version: 10.45.2.18
Location: C:\Program Files (x86)\Java\jre7\bin\plugin2\npjp2.dll
Type: NPAPI
Disable
MIME types: MIME type Description File extensions
application/x-java-applet Java Applet
application/x-java-bean JavaBeans
application/x-java-vm
application/x-java-applet;version=1.1.1
application/x-java-bean;version=1.1.1
application/x-java-applet;version=1.1
application/x-java-bean;version=1.1
application/x-java-applet;version=1.2
application/x-java-bean;version=1.2
application/x-java-applet;version=1.1.3
application/x-java-bean;version=1.1.3
application/x-java-applet;version=1.1.2
application/x-java-bean;version=1.1.2
application/x-java-applet;version=1.3
application/x-java-bean;version=1.3
application/x-java-applet;version=1.2.2
application/x-java-bean;version=1.2.2
application/x-java-applet;version=1.2.1
application/x-java-bean;version=1.2.1
application/x-java-applet;version=1.3.1
application/x-java-bean;version=1.3.1
application/x-java-applet;version=1.4
application/x-java-bean;version=1.4
application/x-java-applet;version=1.4.1
application/x-java-bean;version=1.4.1
application/x-java-applet;version=1.4.2
application/x-java-bean;version=1.4.2
application/x-java-applet;version=1.5
application/x-java-bean;version=1.5
application/x-java-applet;version=1.6
application/x-java-bean;version=1.6
application/x-java-applet;version=1.7
application/x-java-bean;version=1.7
application/x-java-applet;jpi-version=1.7.0_45
application/x-java-bean;jpi-version=1.7.0_45
application/x-java-vm-npruntime
application/x-java-applet;deploy=10.45.2
application/x-java-applet;javafx=2.2.45
Disable  Always allowed?
Windows Live Photo Gallery - Version: 15.4.3508.1109_ship.wlx.w4m4 (ship)
NPWLPG
Name: Windows Live Photo Gallery
Description: NPWLPG
Version: 15.4.3508.1109_ship.wlx.w4m4 (ship)
Location: C:\Program Files (x86)\Windows Live\Photo Gallery\NPWLPG.dll
Type: NPAPI
Disable
MIME types: MIME type Description File extensions
application/x-wlpg3-detect Windows Live Photo Gallery .wlpg
application/x-wlpg-detect Windows Live Photo Gallery .wlpg
Disable  Always allowed?
Google Update - Version: 1.3.22.3
Name: Google Update
Version: 1.3.22.3
Location: C:\Users\njdp\AppData\Local\Google\Update\1.3.22.3\npGoogleUpdate3.dll
Type: NPAPI
Disable
MIME types: MIME type Description File extensions
application/x-vnd.google.update3webcontrol.3
application/x-vnd.google.oneclickctrl.9
Disable  Always allowed?
Silverlight - Version: 5.1.20913.0
Name: Silverlight Plug-In
Version: 5.1.20913.0
Location: c:\Program Files (x86)\Microsoft Silverlight\5.1.20913.0\npctrl.dll
Type: NPAPI
Disable
MIME types: MIME type Description File extensions
application/x-silverlight npctrl .scr
application/x-silverlight-2
Disable  Always allowed?

How to display a desktop file via a user event ?

Hello All,
Can anyone please suggest of a function module or any other method to display a desktop flat file through ABAP code on a user event.
Thank you.
Regards,
Gaurav.

Do you mean open a text file? Take a look at this sample. Point the parameter to some text file on your PC and click execute. It should fire NotePad
report zrich_0001
       no standard page heading
       line-size 300.
data:
           ifile_table type table of file_table,
           xfile_table type file_table,
            return type i..
parameters: p_file type file_table-filename
          default 'C:'.
at selection-screen on value-request for p_file.
clear ifile_table. refresh ifile_table.
call method cl_gui_frontend_services=>file_open_dialog
   exporting
      window_title       = 'Get File'
      multiselection     = space
   changing
      file_table         = ifile_table
      rc                 = return
   exceptions
      file_open_dialog_failed = 1
      cntl_error              = 2
      error_no_gui            = 3
      others                  = 4.
read table ifile_table into xfile_table index 1.
if sy-subrc = 0.
    p_file = xfile_table.
endif.
start-of-selection.
data: file type string.
file = p_file.
call method cl_gui_frontend_services=>execute
    exporting
      document            = file.
Please remember to award points for helpful answers. Thanks.
Regards,
Rich Heilman

Console Mode with third-party PCI card w/ open firmware bios,Open Boot Info

PPC macs used open firmware to boot, and their videocards contained forth code in their rom. There are even custom roms for PC video cards which contain code for the PPC mac open firmware.
Could such a card be initialized as the primary display device on an Ultra 5?
I'm betting I'm going to be answered with 'use a sun branded card'. I can't imagine the rom on these cards is so much different than that used on the PPC mac?
What exactly does Open Boot do to find a videocard? Are there any documents on this? I assume it finds some forth routine in the cards rom and runs that to initialize it and identify it's capabilities? Again, I would really appreciate some direction on where to look for docs.
I'm confused on the difference between openfirmware (apparently a spec), and open boot (sun's implementation? Are all implementations compatible with eachother?)
http://www.openbios.org/Welcome_to_OpenBIOS
"Open Firmware is found on many servers and workstations and there are several commercial implementations from SUN, Firmworks, CodeGen, Apple, IBM and others."
Additionaly, what is the sun4u architecture? sun4v architecture? Which workstations are which? System handbook doesn't seem to say under 'hardware specs'.
So, if all else fails and using a card with an openfirmware rom doesn't help me, how do I go about doing this myself?
I know how to work VGA console mode via the stardard vga registers, Is there a way to get open boot to do exactly what I tell it in terms of registers and addresses?
Can I get an uncompiled form of my Open Boot Prom for my Ultra 5?
All I'm really looking for is good docs/source on how Open Boot/ Open Firmware work, specificly conerning PCI video devices.
Thanks for any tips.

I haven't looked at anything beyond the OpenBoot level.
I've been neglecting this project for some time.
I just wanted to let anyone else in my situation know that the sun OpenBoot documentation was very helpfull in my sucessfully setting a mode with the card.
I don't know how the OS and later OpenWidows interact with the card, or with the information OpenBoot has about it, and it's current mode.
I hadn't really looked at any of that yet. Though this information will probably show up as soon as I bother to look for it, it'd be nice if some one recommends a specific doc, or has a short answer about the topic.
There happens to be an open source driver for my card, for XFree86 and Xorg, however, I've had enough of a challenge merely using OpenWindows.
/etc/X11/xorg.conf /etc/X11/XFree86.conf
Where are simmilar files for OpenWindows? Again, it's probably in some docs I haven't bothered to read yet.
Sparcy: Weird that the card has Fcode and OpenBoot doesn't add it's package to the device tree. I assume it treats it like a non Fcode PCI card? Does it recognize the contents of the PCI base address registers? Try proding it's PCI registers and see if they behave as expected.
If the card is actually working and you can read the expansion rom I don't see why the Fcode didn't work. Maybe it has a later incompatible Fcode revision? Open boot 4.x 5.x? sun4u as opposed to something else? Or maybe the Fcode was designed to lock the card to a certain type of system (I doubt that).
http://www.sunshack.org/data/bootroms.html
Newer versions of openboot, and new hardware series listed at that link. Where's a more complete list?
Oh well, I guess I should bother to read up on this more thoroughly and finish the job.
Let me know if you find out what the problem was, or if you try that MAC card. Thanks.

ATI X800 Launches open firmware at startup ?!?

I've just installed my new graphics card, and whenever I boot the machine, I get an unfamiliar beep, a longish pause with a black screen, and then the open firmware screen. From here, I'm prompted to type "mac-boot," and once I do, the machine seems to start up normally.
Is it supposed to do that? I'm pretty sure I've got the most up-to-date driver (the August 2005 update from ATI) and the most recent ATI Displays utility...
Any Ideas?
Thanks in advance...
PowerMac G5 Dual 2 Ghz (June 2004) Mac OS X (10.4.3) 3gb RAM, ATI x 800 XT Mac Edition

That figures (re:ATI tech support). I was surprised that I couldn't find any other posts about this problem on the web. I hadn't installed the card until after I'd already done the 10.4.4 upgrade, so I was guessing it was a new problem with 10.4.4, but I see you're still running 10.4.3. I don't hold out much hope for repair/replacement since we're seeing the exact same problem, on essentially the exact same computer (June '04 2x2 G5, 3.5 GB ram in mine, 3 in yours). I'll post back here if I learn anything new.
-Ed

Regarding Open Firmware. Serious issue regarding Load Base change.

Hello.
Okay, i have purchased a Mac Mini G4 quite some time ago, and i recently sold it to a friend.
This friend is trying to port MorphOS to the Mini for fun.
In doing this he wanted to change the load base setting in the Open Firmware.
At first he set it higher, den twice as high and now to:
0x1000000 and then: 0x2000000.
After this the Mini displayed some text about flashing ROM and then turned off. After this it would not turn on..
Holding down the power button gives the <CHORD> sound plus some squeeking sounds, but nothing else happens.. Nothing is initiated, not even USB.
In my head the only possible solution now is to reflash the OF ROM.
What I need from you guys is info on how to do this and what tools is required.
Also if you have any experience with bustet OF setups, how could they be fixed.
This is quite a major issue as the Mini is almost completely DEAD as it is now. It doesn't boot, it doesn't move the DVD drive.. It goes <CHORD> and then nothing.
Please, help :P
Mac Mini Mac OS X (10.4.7)
Mac Mini Mac OS X (10.4.7)

unfortunately i cannot open any windows, no. the color wheel spins for an indefinite period of time. any program i try to open essentially freezes. i also cannot successfully restart the computer via the apple menu, the only ways i can restart are if i use the power button directly or if i restart from the login screen. i can't open anything, really. it tries to open the programs and starts to but after a while seems to time out. it indicates that it's still trying but after a few minutes shows no progress. if my screensaver goes on and i wake my computer up again, it freezes on the screensaver and can't get out of it. i tried starting up from the tiger disk but that wasn't working either (when i start up from any disk that isn't my hard drive, my monitor resolution isn't recognized, so it won't display anything - so every time i've had to upgrade in the past i've borrowed another monitor for the process).

Starts in Open Firmware. No OS

Short story,
When I turn on the Pismo, I get open firmware. I beleive the Hard Drive was formatted, and maybe partitioned eternally through a PC program called Macdrive. I have the software Restore Disc, and the software Install Disc. Neither will boot. I have reset the Pram, and Nvram through open firmware. All i get is a blinking '?' on Boot. How can i install the OS 9 back on this Mac?
Long Story,
I was given two G3 Pismo's and told to wipe them clean, and donate them. They would not powerup, as they had been sitting a long time. I took the hard drives out, and cleaned them (deleted files that seemed private) with a PC program called Macdrive. I then learned to Unplug the Pram Battery and this would powerup the Mac, and then boot to OS 9.1. I can't remember, but I may have used Macdrive to Reformat and/or Repartition the Hard drive.
I then became hooked on Mac, and decided to keep one of them. Now when I power it up, I end up getting open firmware, and I cannot boot into OS 9.1 I'm not familiar with Mac Commands, so how can I boot from the Software CD?
Holding down C while powerup does not work.

slow horse,
Until the issue of why you are booting into OF is solved, installing a fresh OS on the HD will not help; the boot into OF occurs long before any software loads. A normal cold start will produce the startup chime, then the raster (gray screen), then either a flashing '?' (no bootable volume found) or it starts to load the OS. I don't know why you are getting into OF. If the powerbook worked normally before you removed the HD, remove it again (and leave it out), then see if you can start to a normal startup chime and get to the flashing '?'. If you can, then see if it will boot a CD. If this is a successful test, then something may be wrong with the HD and/or HD ribbon cable.
However, assuming you solve the OF issue, this article discusses the differences between the Restore CD and the System Install CD. You should be able to boot to either barring any hardware problem.
http://docs.info.apple.com/article.html?artnum=31204
If you cannot boot to the CDs, you can connect the Pismo to your iBook via FireWire Target Disk Mode:
http://docs.info.apple.com/article.html?artnum=58583
You of course can also remove the HD, place it in an external FireWire or USB HD case and install software from the iBook.
If you have access to a FireWire CDRW or DVD burner, you can in most cases boot to a CD or DVD when connecting to the Pismo's FireWire port. Use the option key startup in this case.
If you connect to an iBook, you will not be able to use your Powerbook G3 Software CDs; the installer on the Powerbook CD sees an iBook, not a Pismo. If connected via FireWire Target Disk Mode, the Pismo is seen as just another external HD, nothing else. Depending on which version iBook you have, you can follow one of two procedures, and both will work regardless of how you connect the Pismo's HD to the iBook.
1. If the Pismo's HD mounts on the iBook's desktop, use 9.x's Drive Setup to initialize the HD; this will also automatically update the HD driver. If using 10.x's Disk Utility to initialize the HD, make sure you check the option 'Install MacOS 9 HD Driver'; if you do not, your Pismo will not boot to 9.x. When initializing with 10.x, be SURE to select the topmost name in the list in the left column; this is the HD's model number...do not select the HD's user-given name.
2. If the iBook has 9.1 > 9.2.2 installed, you should be able to drag-copy the System Folder from the iBook to the Pismo's HD. Be sure the System Folder is "blessed" after dragging it over to the HD: Open the System Folder icon, double-click the System file (suitcase), then close all windows.
3. You can also use the iBook's System CDs to install software on the Pismo's HD. Depending on what version software came with the iBook:
http://docs.info.apple.com/article.html?artnum=42929
If the above instructions are not the correct version, please let me know exactly what OS came with the iBook.

IBook screen flickers in Target Disk Mode or in Open Firmware

When booting in Target Disk or Open Firmware the screen seems to shift to one side showing a duplicate of the displayed image. In addidtion to this on the right hand side of the screen roughly about 1" wide the image is completely distorted. I'm not sure but I think the problem only occurs when the Power Adapter is plugged in (Still testing).
Update: The problem occurs with or without the power supply connected. In addition to the above the screen distortion can sometimes be intermittent and does not always distort in the same position as described above.

When you can't boot from any method it usually signals that one of 2 things (maybe both) have failed:
Motherboard
Hard drive - Some hard drive failures lock up the ATA controller so badly that the Mac can't boot from any device.

Open Firmware displayed on Desktop

Similar Messages

Maybe you are looking for