G4 iBook works in Safe Mode, but not in regular mode (stuck on blue screen)

14" iBook G4 1.2GHz with 1 gig of RAM.
I recently had an issue with this machine in that the image on the screen would freeze but the cursor would be able to move around. This was narrowed down to an issue with the logic board. I wanted something a little more permanent than a shim, so I sent the board in to have it reballed.
After installing the maching back into my iBook, it seemed to work fine until I applied a software update to the machine.
It was then that I got to experience the first of many kernel panics.
Restarting at different times always brought me to the dialog box which states that the machine needed to be restarted in multiple languages.
Running the Apple Hardware Test off my install disks yielded this error code: 2ATI/2/4:113-xxxxx-125
I have no idea what that means. I do know that just before I got the results of the test, the screen changed to all kinds of colors. It was only for a few seconds and then the results (with the error code) were displayed.
Still, not sure what to do next, I tried resetting the PRAM. I also tried resetting the NVRAM.
I also tried booting up into Safe Mode which actually worked. There were no issues with the machine and everything seemed to be working fine.
When I tried to restart the machine in regular mode, I'm taken to the infamous blue screen and the machine just stays there. When I let the machine stay off overnight, it booted up normal, but after applying the software update, the machine was in kernel panic again.
I've tried running fsck, but nothing changes.
I'm still not sure why it seems to work in Safe Mode but not in regular mode.
I'd appreciate any suggestions or ideas.

Hi,
A couple of the things that are disabled in safe mode are AirPort and non Apple startup items. The easiest thing for you to test is the AirPort card. Shut down and remove the AE card under the keyboard. See if it starts. If it does your AE card is bad. If not, start in safe mode and go to System Preferences>Accounts>youraccount and disable all non Apple startup (LOgin) items by clicking on them and then the minus sign. Restart normally and see if it will start.
John

Similar Messages

Os 10.4 not booting... stuck at blue screen

As the topic suggests, my iMac G5 isn't booting properly, and is getting stuck after the grey apple screen,at a blue screen, with the mouse visible. It will start up in safe mode, but not in normal mode.
I've tried clearing the PRAM, resetting the SMU, I've succesfully completed a disc repair with no issues, and I've also done an erase/reinstall of the 10.4 OS.
Any thoughts or suggestions?

Welcome to Discussions - You may have a problem with corrupted preferences, try using Preferential Treatment and also, remove all log-in items from your start-up account.

BDC works in A-mode but not in N-mode. Why?

We recently upgraded from 4.6b to ERP6. I have a BDC that fails in ERP6 so I am trying to rework it. Something odd is happening. I find that some BDCs run through find in A-mode while you're stepping through them but not in N-mode when it's hands-off.
Here's the really odd thing. I have re-recorded a BDC against tran CO01 that creates a PP work order. I take the recording and product a function. I test the function with all of the default values intact accept for the new work order# and the function runs in A-mode. It FAILs in N-mode. It appears that ERP6 cannot run it's own BDC recordings.
I notice in A-mode that there are sometimes green info messages on the status line. What I'm wondering is if these are ok in A-mode because I can hit enter and move on vs. N-mode that perhaps gets stuck on them. I say that because I have seen BDCs fail and report in the MSGTAB information messages as though this is what caused the transaction to fail.
Is there some config setting in ERP6 that tells BDCs globally not to fail because of informational status messages?
Thank you.
Crew

Hi,
this may be an issue if you or the transaction is doing any updates on screens which may fail as call transaction by default updates in the asynchronous mode...
so try executing the call transaction in synchronous mode and then check if its giving you the same error message.
use
call transaction 'TCODE' using bdcdata mode 'N' update 'S'.
Regards,
Siddarth

My imac will not boot- it gets stuck on blue screen and will not go any further

Since the last update to Snow Leopard- My computer seems to perform fine, but when I restart the computer or shut it down and then turn it back on- it gets hung. SOmetimes I get the You need to restart screen. But, most times, it goes to the blue screen. The mouse shows up and the dissappears. It shows back up and the dissappears again. Then the system working spiral comes on and off every few seconds. But- it never gets to the sign in screen. ANyone know how to fix? What am I doing wrong?

Does your iMac fail to boot every time or only some of the time? Here are some things to try:
- Boot into "safe mode", which will run the equivalent of Disk Utility's "repair disk" operation.
- Boot from the system install disc that came with that Mac with the "D" key held down to run the diagnostics. Run them several times to see if any hardware problems are reported.
- If you can't identify the problem or fix it any other way, download and install the OS X 10.6.7 "combo" updater.
- If that still doesn't help, try reinstalling OS X 10.6 over the top of what's on the disk.

OSX Mountain Lion 10.8.4: imessage works fine in safe mode, but not in "normal" mode. Any hints?

My iMessages does not work in "normal" startup, but it works perfectly in safe mode.
Any hints?
I have the same problem on a MacBook Pro 17" and on a MacAir 13" mid 2011.
On my MacMini, iMessage work's fine.
I'm using same apple ID on all 3 devices.
Before update to 10.8.4, i had no problems.
FaceTime also stopped working after update to 10.8.4.
Thanks in Advance,
Lars O.

Please read this whole message before doing anything.
This procedure is a diagnostic test. It won’t solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
Third-party system modifications are a common cause of usability problems. By a “system modification,” I mean software that affects the operation of other software — potentially for the worse. The following procedure will help identify which such modifications you've installed. Don’t be alarmed by the complexity of these instructions — they’re easy to carry out and won’t change anything on your Mac.
These steps are to be taken while booted in “normal” mode, not in safe mode. If you’re now running in safe mode, reboot as usual before continuing.
Below are instructions to enter some UNIX shell commands. The commands are harmless, but they must be entered exactly as given in order to work. If you have doubts about the safety of the procedure suggested here, search this site for other discussions in which it’s been followed without any report of ill effects.
Some of the commands will line-wrap or scroll in your browser, but each one is really just a single line, all of which must be selected. You can accomplish this easily by triple-clicking anywhere in the line. The whole line will highlight, and you can then copy it. The headings “Step 1” and so on are not part of the commands.
Note: If you have more than one user account, Step 2 must be taken as an administrator. Ordinarily that would be the user created automatically when you booted the system for the first time. The other steps should be taken as the user who has the problem, if different. Most personal Macs have only one user, and in that case this paragraph doesn’t apply.
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
When you launch Terminal, a text window will open with a line already in it, ending either in a dollar sign (“$”) or a percent sign (“%”). If you get the percent sign, enter “sh” and press return. You should then get a new line ending in a dollar sign.
Step 1
Triple-click the line of text below on this page to select it:
kextstat -kl | awk '!/com\.apple/{printf "%s %s\n", $6, $7}' | open -f -a TextEdit
Copy the selected text to the Clipboard by pressing the key combination command-C. Then click anywhere in the Terminal window and paste (command-V). A TextEdit window will open with the output of the command. If the command produced no output, the window will be empty. Post the contents of the TextEdit window (not the Terminal window), if any — the text, please, not a screenshot. You can then close the TextEdit window. The title of the window doesn't matter, and you don't need to post that. No typing is involved in this step.
Step 2
Repeat with this line:
{ sudo launchctl list | sed 1d | awk '!/0x|com\.(apple|openssh|vix)|org\.(amav|apac|cups|isc|ntp|postf|x)/{print $3}'; sudo defaults read com.apple.loginwindow LoginHook; sudo crontab -l; } 2> /dev/null | open -f -a TextEdit
This time you'll be prompted for your login password, which you do have to type. Nothing will be displayed when you type it. Type it carefully and then press return. You may get a one-time warning to be careful. Heed that warning, but don't post it. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
Note: If you don’t have a login password, you’ll need to set one before taking this step. If that’s not possible, skip to the next step.
Step 3
{ launchctl list | sed 1d | awk '!/0x|com\.apple|org\.(x|openbsd)/{print $3}'; crontab -l 2> /dev/null; } | open -f -a TextEdit
Step 4
ls -A /e*/{la,mach}* {,/}L*/{Ad,Compon,Ex,Fram,In,Keyb,La,Mail/Bu,P*P,Priv,Qu,Scripti,Servi,Spo,Sta}* L*/Fonts .la* 2> /dev/null | open -f -a TextEdit
Important: If you formerly synchronized with a MobileMe account, your me.com email address may appear in the output of the above command. If so, anonymize it before posting.
Step 5
osascript -e 'tell application "System Events" to get name of every login item' | open -f -a TextEdit
Remember, steps 1-5 are all copy-and-paste — no typing, except your password. Also remember to post the output.
You can then quit Terminal.

BDC with call transaction VD02 works fin in A mode but not in N mode

Hi All,
I have BDC program developed in 4.6c using call transaction VD02 works fine with mode A but not with mode N.
Now we upgraded to ECC 6.0.Do I need to change anything?

No, you don't have to change anything for ECC. BTW, I wonder why VD02 is not working in the background for you?

Upload functin works in Edit mode but not in View mode

I am using the Oracle AS 10g PDK to integrate struts application into Portal. I found the upload function works fine in portlet edit mode, but it doesn't work in view mode (Go to the "The page cannot be found" and URL is "http://servername/portal/page"). Does anybody know the reason.

Hi there
Can you post a screen capture of what your Timeline looks like?
Odds are your Click Box is pausing in a weird place.
Cheers... Rick
Helpful and Handy Links
Begin learning Captivate 5 moments from now! $29.95
Captivate Wish Form/Bug Reporting Form
Adobe Certified Captivate Training
SorcererStone Blog
Captivate eBooks

Dll issue, works in release.exe but not in debug mode.

I have an issue with a dll that was previously working in both released and in debug mode. Now if I create a released .exe it functions. If I run it in debug mode the call to the dll function never returns. eventually whatever is occurring behind the scense prevents the released.exe from working also. I do not know if I accidenatally changed a setting in the cvi compiler that broke the code. Is there a way to default cvi2010 settings?

You can go back to the default ADE settings by renaming the following registry key to something else (anything other than "10.0", it doesn't matter what):
[HKEY_CURRENT_USER]\Software\National Instruments\CVI\10.0.
I think it's best to rename it, rather than delete it, so that you can go back to your current settings any time you choose to. Make sure CVI is not running when you rename the key.
After the rename, the first time you run CVI, it will prompt you if you want to copy the settings. Say no to that. At that point, CVI will create a new "10.0" key with the default settings in place.
Once you're done with your investigation, if you prefer to go back to the settings you had, you can delete the new 10.0 and rename the previous key back to "10.0".

Project runs Ok in debug mode but not in release mode

I have an application developed with VC++ 6.0 and measurement studio. The application controls SCXI-1161/1166 relay boards to connect the UUT. The application runs ok in debug mode, but in release mode the application can't drive the relay boards. I have tried to change optimizations mode, it didn't work. Who can tell me how to solve the problem? Thanks!

It sounds like you have an older version of our SWITCH driver which relies on our DAQ driver. I would recommend uninstalling the Traditional DAQ, DAQmx, and SWITCH drivers and then installing the newest version. At this point you have 2 options:
1) You can download Traditional DAQ 7.4, DAQmx 7.4, and NI-SWITCH 2.4 drivers bundled together here: ftp://ftp.ni.com/support/daq/pc/ni-daq/7.4/
2) You can install the latest version: NI-DAQmx 7.5 here: http://digital.ni.com/softlib.nsf/websearch/CF7ECCEA4C4CC7DE86257038004D88AE?opendocument&node=13206... This has support for all of our USB DAQ devices (if you're not using them then you may not want to worry about installing this now) and then install Traditional DAQ 7.4 here: http://digital.ni.com/softlib.nsf/websearch/C36A54ADDA3DC33D86257038004E55E6?opendocument&node=13206... and NI-SWITCH 2.4 here: http://digital.ni.com/softlib.nsf/websearch/9D6B8C7FD41BF3D08625702E0072E294?opendocument&node=13206...
This should solve your problem.

IMac not booting up - getting stuck on blue screen

Hello, first post here.
I have an iMac which I powered down last night and came this morning to boot it back up. Unfortunately it was having troubles booting up. It got stuck on the blue screen, kinda switching back and forth between two shades of blue and occasionally displaying the mouse and spinning load icon.
I tried restarting it, and curiously there was no startup sound. I tried unplugging the power cable and plugging it back in holding the power button and turned it on with the fan going full blast. I rebooted again, the fan was silent, but the startup sound finally chimed. I then proceeded to try the following:
•Reset the PRAM - no luck
•Tried booting in safe mode - stuck on gray screen with apple icon
•Tried booting into target mode - drive was recognized on my macbook fine
•Tried using disk utility on my macbook with the imac in target mode - repaired the disk, but still wouldn't boot
•Tried restarting it in single-user mode, worked, repaired the disk through that, rebooted and still no luck
•Couldn't boot into CD mode, I believe my DVD drive is broken
Whats interesting is that the hard drive isn't making the usual mechanism sound that I usually hear when its powering up (assuming that's what makes the sound)
So any help is much appreciated. I use this computer in my recording studio and have lots of data I wish not to loose, so any solutions needing a reinstallion/erasing the drive is fine, just keep in mind I need to do a good backup first.
Thanks

Hi J
Welcome to Apple Discussions
That sounds almost like a failed Leopard install:
http://support.apple.com/kb/TS1545?viewlocale=en_US
or it's Stuck in a "loop" at the login window after upgrading to Leopard: http://support.apple.com/kb/TS1413?viewlocale=en_US
Try an Archive & Install:
http://support.apple.com/kb/HT1710
or restore from your Time Machine Backup:
http://docs.info.apple.com/article.html?path=Mac/10.5/en/15638.html
Dennis

IMac does not boot up, gets stuck on blue screen with spinning wheel ...

... and tries to do something in a 10 second circle ... blue screen ... spinning wheel b/w on blue screen ... blue screen ... spinning wheel again ...
... with some hard disc work going on ...
i habe checked the disk with the disc utility, no errors.
any idea what I could do apart from reinstalling the os?
thanks for your help!
j.

Hi J
Welcome to Apple Discussions
That sounds almost like a failed Leopard install:
http://support.apple.com/kb/TS1545?viewlocale=en_US
or it's Stuck in a "loop" at the login window after upgrading to Leopard: http://support.apple.com/kb/TS1413?viewlocale=en_US
Try an Archive & Install:
http://support.apple.com/kb/HT1710
or restore from your Time Machine Backup:
http://docs.info.apple.com/article.html?path=Mac/10.5/en/15638.html
Dennis

Graphics Card works in Safe Boot but not Normal Boot

Specifics
350 G4 PCI Graphics Card Rage ATI 128
Envision 17" Monitor
Here's the deal
I use the machine as a Network Backup it has 4 250GB Hard drives in it.
Symptoms
No matter what PCI slot I use if I do a normal boot I get a dialog box that says "Input Not Supported"
If I boot in safe boot no problems!
The machine does Boot and it shows up on the network, just no video
Attempts
I have swapped the card to another machine (card works no problem)
Removed all other PCI cards from machine (no difference)
Created new user "troubleshooting" tried to boot in to troubleshooting's user account (Same message on screen "Input Not Supported")
Zapped P & V RAM
Replaced 3.6V Battery on mother board
Swapped Monitors (Same message on screen "Input Not Supported")
OK Any Suggestions?
Thanks in advance
Joseph
A Bunch Mac OS X (10.4.6) Photographer Made my own iTablet

So I got a clue and did a clean install, that did the trick!
I still have the question as to the how's and why's of what went wrong.
I imagine a corrupt file, but I would have guessed that making a new user, or an Archive and Install would have cleared that up.
Go figure
But yes it is working now!
And I say Thank God I was looseing a lot of time trying to figure it out!

I have a VI with menu barattached i want to remove the menu bar.I am able to remove the menu bar in run continuously mode.but not in normal mode how do i do it in normal mode

I have a VI with menu bar.I am able to remove menu bar in continuous mode by setting window appearence.But i want the menu bar to be removed at normal mode also.How do i do it

You can trun off the menu while the VI is running by going into the VI properties (right click on the VI icon and select 'Properties). Then from the Catagory selestion box, select Window Appearance, click the Customize button, then uncheck the Show Menu Bar check box and hit OK twice. That shold do it.
Note that this will only turn off the menu while the VI is running. The standard menu will always be showing when the VI is not running.
Ed
Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.

IP: input-ready query shows data in Load mode but not in Plan mode

Hello experts,
we're currently experiencing a very strange issue regarding an input-ready query which consists of a single lead column (read from the cube) and an input-ready plan column. The issue is as follows:
When the cube is in Load mode the lead column shows its data perfectly. However, when switching to Plan mode the data is not shown.
The cube is indexed by a BIA which may be part of the problem.
We're on BW 7.00 SP 21. I've read that this may be related to the OLAP cache, but haven't been able to find any notes relevant for 7.00 SP 21.
Thanks in advance for any suggestions.
Regards, Dirk

Hi Dirk,
I think that the problem comes from the cache used in the plan buffer query. Delete the cache via RSRCACHE. The query name is
IC/!!1IC if you have a query on an aggregation level on an InfoCube IC
MPRO/!!1MPRO if you have a query on an aggregation level on a multiprovider MPRO or directly on the multiprovider MPRO
You might search for note using 'cache' and component pattern BW-BEX-OT*, e.g. 1408959, 1528191, 1560036.
Regards,
Gregor

Script works in PowerShell ISE but not in regular PowerShell window

Hello all!
I've got another PS conundrum to ponder. I have the following script lines:
write-host"Check
for password complexity requirements:"-foregroundcolorblack-backgroundcolorwhite
write-host""
import-moduleactivedirectory
$PasswordPolicy=Get-ADObject$RootDSE.defaultNamingContext
-PropertypwdProperties
$PasswordPolicy|Select@{n="PolicyType";e={"Password"}},`
DistinguishedName,`
@{n
="Password complexity requirements";e={Switch($_.pwdProperties)
0{"Passwords
can be simple and the administrator account cannot be locked out"}
1{"Passwords
must be complex and the administrator account cannot be locked out"}
8{"Passwords
can be simple, and the administrator account can be locked out"}
9{"Passwords
must be complex, and the administrator account can be locked out"}
Default{$_.pwdProperties}}}}
|ft*-auto
When I run this code in ISE, it works great. It returns the value for the setting "1" which is what this GPO is set to.
But, when I run this same code in elevated PowerShell prompt, I get the following error:
Any help would be greatly appreciated.

Hi,
Are you creating $RootDSE before you use it?
Don't retire TechNet! -
(Don't give up yet - 13,085+ strong and growing)

G4 iBook works in Safe Mode, but not in regular mode (stuck on blue screen)

Similar Messages

Maybe you are looking for