G3 B&W with Tiger won't boot

hi
i got a used Power Mac g3 (350mhz, 512mb, 6gb, CD,)with Tiger installed, but during the boot process, it stops at the "Starting Mac OS X" It still shows the progress bar and it is still moving, but i think it must have errors and cannot progress. I am a noobie to Macs, but i have been arround Windows PCs and Linux for a long time....By the way i got Ubuntu PPC to boot nicely on it, so i think the problem must be software. I will gladly buy OS X Tiger, if that will fix the problem (reinstalling) But i want to make sure it is software before i buy any software.....thanks,
bones

upgrade the hard drive to a 60gb or 80gb, this should be no problem, right??
It is very important to determine whether you have a Rev 1 or Rev 2. The rev 1 "HeartBreaker" Blue & White generally does not respond well to a new hard drive that is any faster than the stock model. Rather than generating error messages, it gets so flaky and unreliable as to be unuseable.
This article show the "stacking bracket". If you have that, you almost certainly have a rev 2 [the reverse is NOT true.]
58193 -- Power Macintosh G3 (Blue and White): Additional Hard Drive Installation Options
This article discusses the definitive test for whether your is a Rev 2, reading the part number off the IDE/ATA chip, [646U2-402 for Rev 2}:
New Features of the latest [Rev 2] B&W G3

Similar Messages

Mac OS X Tiger won't boot, results to OS 9.

My PowerMac G4 currently holds two startup disks, OS 9, and OS X 10.4.11
However, after a recent update for iTunes and security, my machine got shut off manually and the next time I booted my mac is went directly to os 9. I tried restarting and holding down option to show available boot disks, and only os 9 showed up. However, now Os 9 struggles to boot with extensions on. But evennin os 9 it shows my os x disk and it is fully functionable. ( as in file browsing) can anyone tell me what is happening or what I can do?
Message was edited by: NickG9090

By abnormally shutting down the OS X partition has most likely gotten scrambled. You will have to reformat that volume and reinstall OS X.
Since OS 9 is working you may still be able to copy your personal files to an external drive so they won't be lost.

System file tampered with - Mac won't boot up. HELP!

Hi i have somehow managed to delete part of my system file and now when i try to start the computer it is fixed on the start up screen but the login box does not appear just a blue screen.
Is there anything i can do to overcome this problem? For example some way to reset my mac?
Any replies would be greatly appreciated

If you've deleted system files then you will need to reinstall OS X. If you are using Snow Leopard then the reinstall will not erase the drive. If you are using Leopard then you will need to do an Archive and Install to avoid erasing the drive:
How to Perform an Archive and Install
An Archive and Install will NOT erase your hard drive, but you must have sufficient free space for a second OS X installation which could be from 3-9 GBs depending upon the version of OS X and selected installation options. The free space requirement is over and above normal free space requirements which should be at least 6-10 GBs. Read all the linked references carefully before proceeding.
1. Be sure to use Disk Utility first to repair the disk before performing the Archive and Install.
Repairing the Hard Drive and Permissions
Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger, Leopard or Snow Leopard.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer. Now restart normally.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
2. Do not proceed with an Archive and Install if DU reports errors it cannot fix. In that case use Disk Warrior and/or TechTool Pro to repair the hard drive. If neither can repair the drive, then you will have to erase the drive and reinstall from scratch.
3. Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When you reach the screen to select a destination drive click once on the destination drive then click on the Option button. Select the Archive and Install option. You have an option to preserve users and network preferences. Only select this option if you are sure you have no corrupted files in your user accounts. Otherwise leave this option unchecked. Click on the OK button and continue with the OS X Installation.
4. Upon completion of the Archive and Install you will have a Previous System Folder in the root directory. You should retain the PSF until you are sure you do not need to manually transfer any items from the PSF to your newly installed system.
5. After moving any items you want to keep from the PSF you should delete it. You can back it up if you prefer, but you must delete it from the hard drive.
6. You can now download a Combo Updater directly from Apple's download site to update your new system to the desired version as well as install any security or other updates. You can also do this using Software Update.

Tiger won't boot from external firewire

Installed 10.4.3 DVD on clean external firewire (Extended/Journaled). Before I installed Tiger, I ran updates, and repaired permissions. Everything looked good to me.
I'm keeping Panther on main system drive for now - so from System Preferences>Startup Disk>the external tiger drive appears and I select it. Then I select restart and the promt confirms that the computer will restart with 10.4.3. Looks good so far.
After restart, I'm looking at the desktop, guess what? It's 10.3.9, not 10.4.3. How could that be?
Also, when I restart and hold down the Option key for Startup Manager options - the firewire drive does not appear as an option.
So Tiger appears in System Preferences>Startup Disc as an option, but the option doesn't actually work, and that drive does not appear at all in (Option key) startup manager.
I'm Indexing the firewire drive now (OMG is that slow or what!), but I'm not expecting this to make any difference. I'm stumped. What am I overlooking? Please advise.
Muchas Gracias

R MacCool,
"What if I manually drag and drop the 4 folders (from the Tiger DVD) onto a second internal SATA drive without partitioning the drive first? Will I be able to boot off an internal SATA drive like that? When I installed Tiger on the external firewire I see that 4 folders are there - I could drag them from that drive onto the second internal drive. Does that work?"
No, this does not work. MacOS X consists of more then 20,000 invisible files, most of them somehow connected and referencing each other.
MacOS X DOES boot from external firewire drives, both hard disks and DVD drives.
Why don't you just upgrade your current 10.3.9 to Tiger using this procedure: 10.4 Tiger Upgrade: Decision tree+Checklist?
"Why does Tiger seem to install correctly, then System Pref>Startup Disc recognizes it, but then after selecting 10.4.3 it restarts into 10.3.9?"
I am not a technician, but it could be that the firmware is the primary source for connectivity. After MacOS X has booted the internal firewire drivers might take over and "overrule" the firmware (this is why you can see it in the startup disk preference pane) but at boot-time it exclusively depends on the firmware. This theory might be completely wrong though.

G5 Tower (Tiger) won't boot from disk

When I try to boot from the Tiger install disk, it just ejects. I tried inserting the disk while the computer was running and it worked fine (meaning I was able to view the files), so I tried to run the install from there, and it ejected. So per some other posts I cleared the PMB and PRAM, to no avail. I then thought I would try a Leopard install disk, and it just ejects.
Can this be a bad optical drive, even though I can view the contents of the DVD?
Specs: PowerPC 1.6GHz, Tiger 10.4.11, 2.5GB RAM, 75GB Partition (Applepartitionscheme) with 18GB available.

The Leopard disk for sure is not retail - it came with my MacBook Pro. I'm pretty sure the Tiger disk is the disk I used to install the OS on that machine, but after several years and several moves I'm not 100% sure. Good to know it's not the optical drive, at least. Thanks.

Mac OS X Tiger won't boot up

I'm having trouble booting up Tiger. When I turn on my Mac the Apple symbol appears and the spinning ring. After about five minutes of this I get a "Do Not" symbol (a circle with a slash through it)
I was running classic 9.4, then installed 10.3 without a hitch, then upgraded to Tiger 10.4. Everything was running fine for about 2 hours. It was able to shut down and restart several times. Until I left in powered down over night.
What could the problem be and is there a solution

ipmcdesigns, welcome to Apple Discussions.
See Mac OS X: "Broken folder" icon, prohibitory sign, or kernel panic when computer starts
http://docs.info.apple.com/article.html?artnum=106805
May be a solution on one of these links.
Troubleshooting
The X Lab (Troubleshooting & Maintenance of OS X)
OS X Routine Maintenance & Generic Troubleshooting
Prevent Mac Disasters
Kernel Panic
Mac OS X Kernel Panic FAQ
Mac OS X Kernel Panic FAQ
Resolving Kernel Panics
 Cheers, Tom

Upgraded iMac from Panther to Tiger - Won't boot!

Hello,

Hello,
The PowerMac should be providing the donor drive (and the iMac's processor doing the work) when you do an install like this. You've probably ended up with a PowerMac customized version of Tiger on the iMac which won't work.
The other possibility is that the Intel version of the Tiger update was used which is also incompatible.
I'd advise trying the process again and make sure the PowerPC update is used:
http://www.apple.com/support/downloads/macosx10411comboupdateppc.html
mrtotes

17" C2D 2 gHz iMac w/fresh install of Tiger won't boot to desktop; takes me through setup, then instead of normal boot, it re-enters setup. (I don't have install disks)

Hi, I just bought an iMac from E-Bay, a pre-aluminum, 17" C2D 2.0 gHz machine. The seller told me that he wiped the hard drive and installed Tiger, with a borrowed disk, so I don't have install disks.
I booted up the computer and it took me through the initial setup process. Everything seemed slow, it took a couple of minutes to get to the setup intro screen. After going through setup, it looked like it was going to go for a normal boot, but it re-entered setup. I went through the process 3 times, and it wouldn't let me choose the same user name twice, so it seems to have created 3 user accounts. But I can't get it to boot to a normal Finder desktop. Safe mode is no-go. I reset the pram, no change. I plan on trying to boot using Linux Mint on an external USB, to see if the hardware is functioning.
Any suggestions or insights
Thanks!

You're not getting many hits here, try reposting at the Tiger site:
https://discussions.apple.com/community/mac_os/mac_os_x_v10.4_tiger

Pismo with Tiger won't go into target disk mode

I recently upgraded my Pismo to Tiger and can't seem to boot into firewire target disk mode. The computer restarts and gives me a terminal screen that reads: "can't OPEN DISK" and then goes on to say "Welcome to Open Firmware. To continue booting, type "mac-boot"..."
I tried zapping the pram, but that did nothing. Does anybody have any suggestions?

MacUser,
When booted in 10.4.8, select Target Disk Mode in the System Preferences > Startup Disk and see what happens.
If no success, try resetting Open Firmware (from Apple docs):
Boot into Open Firmware by holding down the 'Command-Option-O-F' keys from a cold start while the chime is being played. You will see a command-line screen...enter these commands:
1. At the Open Firmware prompt, type: reset-nvram
2. Press Return.
3. At the Open Firmware prompt, type: reset-all
4. Press Return.
Example:
0 > reset-nvram
Press Return
0 > reset-all
Press Return
The reset-all command should cause the computer to restart. If this occurs, you have successfully reset the Open Firmware settings.

Created zone with defaults won't boot completely (Solaris 10, Update 1)

If I create a zone with defaults, i.e. allowing the zone to inherit the typical package dirs, the resulting zone does not boot completely. When I attach to the zone via zlogin, the zone looks to be in an administrative state. It never boots to a point where one would typically enter in the initial configuration info, e.g. timezone and root password.
However if I create the zone after first removing the inherited dirs, the zone boots to a state where it subsequently can be confiured and fully booted.
Looks as if the SMF facilities are not fully initialized when the zone is configured to inherit its packages. This could be a red herring as I'm a newbie who's moved over from Linux and starting to understand SMF specifically and Solaris in general.
I did not have this problem with Solaris 10. I've just installed Solaris 10 Update 1; the problem seems specific to that installation. I reinstalled and the problem persists.

I snipped the output because there were some errors, which on retrospect seems to have been a silly decision. I repeated the process and captured the missing output:
# zoneadm -z foo install
Preparing to install zone <foo>.
Creating list of files to copy from the global zone.
Copying <5913> files to the zone.
Initializing zone product registry.
Determining zone package initialization order.
Preparing to initialize <942> packages on the zone.
Initialized <942> packages on zone.
Zone <foo> is initialized.
Installation of <1> packages was skipped.
Installation of these packages generated warnings: <SUNWxwfnt
SUNWxwplt SUNWxwcft SUNWjxmft SUNWxwpls SUNWpmowu
SUNWxilrl SUNWolrte SUNWi13rf SUNWi15rf SUNWi2rf SUNWi5rf
SUNWi7rf SUNWi9rf SUNWtxfnt SUNWdoc SUNWi1of SUNWi4rf
SUNWi8rf SUNW1251f SUNWarrf SUNWxwoft SUNWxwxst
SUNWkoi8f SUNWasu SUNWxrpcrt SUNWasac SUNWasdb
SUNWasut>
The file </zone/foo/root/var/sadm/system/logs/install_log> contains a log of the zone installation.The packages are related to App development and X11. I don't see any that might be related to SMF.
The logfile is too large to post at over 37K lines. However there seemed to be a pattern to the package failures. Hopefully these greps highlight the important messages:
# grep "partially failed" /zone/foo/root/var/sadm/system/logs/install_log
Installation of <SUNWxwfnt> on zone <foo> partially failed.
Installation of <SUNWxwplt> on zone <foo> partially failed.
Installation of <SUNWxwcft> on zone <foo> partially failed.
Installation of <SUNWjxmft> on zone <foo> partially failed.
Installation of <SUNWxwpls> on zone <foo> partially failed.
Installation of <SUNWpmowu> on zone <foo> partially failed.
Installation of <SUNWxilrl> on zone <foo> partially failed.
Installation of <SUNWolrte> on zone <foo> partially failed.
Installation of <SUNWi13rf> on zone <foo> partially failed.
Installation of <SUNWi15rf> on zone <foo> partially failed.
Installation of <SUNWi2rf> on zone <foo> partially failed.
Installation of <SUNWi5rf> on zone <foo> partially failed.
Installation of <SUNWi7rf> on zone <foo> partially failed.
Installation of <SUNWi9rf> on zone <foo> partially failed.
Installation of <SUNWtxfnt> on zone <foo> partially failed.
Installation of <SUNWdoc> on zone <foo> partially failed.
Installation of <SUNWi1of> on zone <foo> partially failed.
Installation of <SUNWi4rf> on zone <foo> partially failed.
Installation of <SUNWi8rf> on zone <foo> partially failed.
Installation of <SUNW1251f> on zone <foo> partially failed.
Installation of <SUNWarrf> on zone <foo> partially failed.
Installation of <SUNWxwoft> on zone <foo> partially failed.
Installation of <SUNWxwxst> on zone <foo> partially failed.
Installation of <SUNWkoi8f> on zone <foo> partially failed.
Installation of <SUNWasu> on zone <foo> partially failed.
Installation of <SUNWxrpcrt> on zone <foo> partially failed.
Installation of <SUNWasac> on zone <foo> partially failed.
Installation of <SUNWasdb> on zone <foo> partially failed.
Installation of <SUNWasut> on zone <foo> partially failed.and# grep "not installed" /zone/foo/root/var/sadm/system/logs/install_log
*** package <SPROmrdwf> was not installed:
*** package <SPROdwrfb> was not installed:
*** package <SPROlang> was not installed:
*** package <SPROlangx> was not installed:
*** package <SPROdwrfx> was not installed:
*** package <SPROsbld> was not installed:
*** package <SPROsbldx> was not installed:
*** package <SPROrdbkb> was not installed:
*** package <SPROrdbkx> was not installed:
*** package <SPROcc> was not installed:
*** package <SPROutool> was not installed:
*** package <SPROmrcc> was not installed:
*** package <SPROmrcom> was not installed:
*** package <SPROmr3m> was not installed:
*** package <SPROmrtcv> was not installed:
*** package <SPROm9xs> was not installed:
*** package <SPROsunms> was not installed:
*** package <SPROsmsx> was not installed:
*** package <SPROsmpx> was not installed:
*** package <SPROmrsbe> was not installed:
*** package <SPROsbe> was not installed:
*** package <SPROpnsn> was not installed:
*** package <SPROfd> was not installed:
*** package <SPROupdck> was not installed:
*** package <SPROcpl> was not installed:
*** package <SPROcplx> was not installed:
*** package <SPROcmpl> was not installed:
*** package <SPROtlbn7> was not installed:
*** package <SPROtll7> was not installed:
*** package <SPROtl7x> was not installed:
*** package <SPROtll7x> was not installed:
*** package <SPROscl> was not installed:
*** package <SPROsclx> was not installed:
*** package <SPROmrstd> was not installed:
*** package <SPROmrcpl> was not installed:
*** package <SPROstl4h> was not installed:
*** package <SPROstl4a> was not installed:
*** package <SPROstl4o> was not installed:
*** package <SPROstl4x> was not installed:
*** package <SPROstl4y> was not installed:
*** package <SPROftool> was not installed:
*** package <SPROl90> was not installed:
*** package <SPROl90x> was not installed:
*** package <SPROl90s> was not installed:
*** package <SPROl90sx> was not installed:
*** package <SPROf90> was not installed:
*** package <SPROmrftn> was not installed:
*** package <SPROgc> was not installed:
*** package <SPROlgc> was not installed:
*** package <SPROgcx> was not installed:
*** package <SPROlgcx> was not installed:
*** package <SPROdbx> was not installed:
*** package <SPROdbxx> was not installed:
*** package <SPROjdbx> was not installed:
*** package <SPROjdbxx> was not installed:
*** package <SPROmrdbx> was not installed:
*** package <SPROdemo> was not installed:
*** package <SPROdmake> was not installed:
*** package <SPROmrdmk> was not installed:
*** package <SPROtdemo> was not installed:
*** package <SPROmride> was not installed:
*** package <SPROdbxui> was not installed:
*** package <SPROsvc> was not installed:
*** package <SPROxdplg> was not installed:
*** package <SPROidext> was not installed:
*** package <SPROjnsnb> was not installed:
*** package <SPROjnsrt> was not installed:
*** package <SPROjnsup> was not installed:
*** package <SPROctags> was not installed:
*** package <SUNWnbide> was not installed:
*** package <SUNWnbcpp> was not installed:
*** package <SUJAnbcpp> was not installed:
*** package <SUZHnbcpp> was not installed:
*** package <SUNWexted> was not installed:
*** package <SUJAexted> was not installed:
*** package <SUZHexted> was not installed:
*** package <SPROnbreg> was not installed:
*** package <SPROfdxd> was not installed:
*** package <SPROmrxd> was not installed:
*** package <SPROgvim> was not installed:
*** package <SPROxmbin> was not installed:
*** package <SPROxmshr> was not installed:
*** package <SPROxmsrc> was not installed:
*** package <SPROmrxm> was not installed:
*** package <SPROprfan> was not installed:
*** package <SPROmrpan> was not installed:
*** package <SPROprfax> was not installed:
*** package <SPROprflb> was not installed:
*** package <SPROprflx> was not installed:
*** package <SPROprfgn> was not installed:
*** package <SPROmrpgn> was not installed:
*** package <SPROhtbas> was not installed:
*** package <SPROhttl7> was not installed:
*** package <SPROhtstd> was not installed:
*** package <SPROhtxd> was not installed:
*** package <SPROdwrfs> was not installed:
*** package <SPROrdbks> was not installed:
*** package <SPROctsrc> was not installed:
*** package <SPROplg> was not installed:
*** package <SPROpl> was not installed:
*** package <SPROplx> was not installed:
*** package <SPROpls> was not installed:
*** package <SPROplsx> was not installed:
*** package <SPROmrpl> was not installed:These messages seem to be inline with the general output captured from the zone install itself.
> What does "svcadm list -vc" give you when you started the zone ?
I took that as a typo, instead using "zoneadm?"
# zoneadm list -vc
ID NAME             STATUS         PATH
   0 global           running        /
   7 foo              running        /zone/fooThe zone is not on its own slice, however "/zone" is mounted as a loopback from /export/zone. I don't think that's a problem since the zone install seems to work if I don't inherit packages. Unless perhaps its a nesting level of lofs's.
FWIW,
# mount |grep zone
/zone on /export/zone read/write/setuid/devices/dev=1540000 on Fri Feb 24 16:10:55 2006
/zone/foo/root/dev on /zone/foo/dev read/write/setuid/devices/zonedevfs/dev=4640007 on Tue Feb 28 13:13:03 2006
/zone/foo/root/lib on /lib read only/setuid/nodevices/nosub/dev=dc0440 on Tue Feb 28 13:13:03 2006
/zone/foo/root/platform on /platform read only/setuid/nodevices/nosub/dev=dc0440 on Tue Feb 28 13:13:03 2006
/zone/foo/root/sbin on /sbin read only/setuid/nodevices/nosub/dev=dc0440 on Tue Feb 28 13:13:03 2006
/zone/foo/root/usr on /usr read only/setuid/nodevices/nosub/dev=dc0440 on Tue Feb 28 13:13:03 2006
/zone/foo/root/proc on proc read/write/setuid/nodevices/zone=foo/dev=4400007 on Tue Feb 28 13:13:06 2006
/zone/foo/root/system/contract on ctfs read/write/setuid/nodevices/zone=foo/dev=43c0008 on Tue Feb 28 13:13:06 2006
/zone/foo/root/etc/svc/volatile on swap read/write/setuid/nodevices/xattr/zone=foo/dev=448000e on Tue Feb 28 13:13:06 2006
/zone/foo/root/etc/mnttab on mnttab read/write/setuid/nodevices/zone=foo/dev=4440008 on Tue Feb 28 13:13:06 2006

17" iMac (Tiger) won't boot after latest software update

I downloaded the latest Tiger software update on my 17" Intel Core Duo iMac a couple of days ago and after I hit Restart I can't get past the grey Apple loading screen.
I've tried everything it tells me in the manual, pressing various combinations of keys as I turn the computer on, but to no avail. I also put Install Disk 1 in and tried to check hardware from that (pressing D) and tried pressing C too to boot from it, but nothing happens, just the grey apple loading screen. Of course, now the install disk is stuck in there too.
Any clues as to how I can sort this out? I'm still under AppleCare, so if worst comes to worst I'll call UK support and see what they can do, but thought I'd try everything I could at home first.
TIA.

Hello,
Try the Apple Hardware Test: http://support.apple.com/kb/HT1509
Carolyn

Firewire External HD with Clone won't boot

I just installed an OWC Mercury Elite-AL Pro 250GB external Firewire 400 HD to supplement storage on my eMac. I used the supplied Prosoft DataBackup 3 software (supplied with the OWC drive) to Clone my internal drive to the external drive, following instructions to make the Clone bootable.
The software indicated a successful backup, and Disk Utility shows the volume as "Bootable".
But, when I choose the external drive as the boot drive in the Startup prefs, it gets to the Apple Gray screen, and the little clock/fan thingy just spins and spins (I've waited as long as 10 minutes).
If I use the Option key on startup, the Startup Manager shows both drives as available (with the little "X" on the corner of both the internal and external drives), but choosing the external drive at this point doesn't work either.
Any suggestions as to what I may have done wrong, or what else I should try.
Thanks
PowerMac G4 Dual 1.25 & G4 17 Powerbook Mac OS X (10.4.9) 1.0 eMac, D-Link DSL Router & Switch, D-Link USB Hub

Download either Carbon Copy Cloner or SuperDuper. Both are good cloning programs and are both free to try (CCC all the time, SD is shareware). SD is a bit easier to get going and use, but CCC works fine and I use it because it is donationware. SD locks you out of certain functions in the free version.
Anyway... Try cloning your drive with one of those and see if you can then boot off it. If you can, then the software that came with the drive is either crud, or you just happened to get a bad clone that time. If the drive still doesn't boot, then that particular model may not fully be bootable compatible (it happens sometimes).
Patrick

Early 2008 with 8800 won't boot

When the machine is post chime.... I get horizontal blue lines that look like tire treads up and down the screen which makes me think video card. In verbose mode it stops in the same spot each time... the drive is reading I can hear it and then it just stops loading. I did FSCK -FY in single user mode and it modified things, ran it until it again until I got the disk was "okay" message. I get the blue lines regardless of the boot device, and no drive will boot all the way in. The funny thing is, this happened yesterday and after doing the FSCK -FY in single user mode everything booted fine, but after sleeping the machine last night it woke up not working, just blue lines on the screen. Things I've done:
Flashed the PRAM many times.
Unplugged everything and let it sit for 15+ seconds, then plugged in display and keyb to clear the SMB
Removed RAM and tried various combinations. No LED indicators to indicate RAM issues
Reseated all drives and the video card, as well as RAM obviously see above
I pulled the trigger on a new video card which will arive whenever it gets here in case it is the card. Got the ATI 5770 which supposedly works on the Early 2008 model. I had been planning on doing this for awhile as playing RIFT has had the video card fan revving constantly so it's been pushed hard, plus I do a lot of video editing. If anyone has any other ideas please let me know. The last shutdown condition = 3 whatever that means. Any other ideas would be apprecated. I'll post back otherwise when i get the new card and report.
Eric

Oh and I had forgot to mention, I'd tried more than one display, and both DVI ports on the 8800 with the same result, so the cause of the lines is not external.

Windows 200 PC with SP4 won't boot after install of iPod software from CD.

I installed the iPod software from the CD of my new iPod mini. It requested that I reboot the PC, which I did but it never rebooted. It hung and would not even boot in safe mode. After many attempts I booted to the boot console and when throught the install repair process. The PC will still not boot.
Is there any way to bring up the PC without having to rebuild it?
Has anyone found a way to get the PC back to it's original state, without a disk re-format?
Does Apple have a solution?
Any comments from Apple Support or their QA team would be of interest

Last know good does not work. I don't receive any error messages. I did the repair but PC still will not boot. The starting windows bar goes about three quarter of the way to the right and then it just stops. It does this regardless fo which boot mode I choose (ie. safe mode).
I do not have the iPod plugged in during this process.
Is there anything else I can do or that we can try from the console command mode?

MacBook pro with retina won't boot. Dark blue screen on start up. Any thoughts.

my MacBook pro will not boot up. I have no idea what happened to it. It is only a few months old. I have tried safe mode but that doesn't seem to work either.

FIxed

G3 B&W with Tiger won't boot

Similar Messages

Maybe you are looking for