Dual boot after upgrading to 10.4?

My parents use a summer 2001 slot loading iMac G3 that can boot either into OS 9.2 or OS X. I'd like to upgrade their computer to 10.4.
I know I'll need to add RAM and do the firmware upgrade first.
WIll their computer still be able to boot into 9.2 if they need to for some older software? Or will they lose the dual boot capability?

Hi
Yes, any Mac that has the ability to boot into OS 9 will retain that ability no matter how far you upgrade OS X.
Best,
Matt

Similar Messages

Can no longer dual boot after upgrade

Hi I used to run mac osx 10.7 dual booting with ubuntu 13.04. I used to press alt at startup to view the different partitions and select the appropriate OS. After upgrading to 10.9 I can no longer see the ubuntu partition when pressing alt. The disk is still there intact, but there is no way I can directly boot to it from startup. I tried creating another partition using disk utility and installing a fresh copy of linux and using the old linux partition as backup but whenever I select the ex-fat (or any other type for that matter) (for linux) I get:
File system resize support required, such as HFS+ with Journaling enabled.
I erased osx 10.9 and reset to factory settings back to 10.8 but the same problem continues.
I am not sure what to do to get dual booting working again. I do have an ubuntu backup on an external drive, but I would prefer not reformatting that partition.

I don't know why you couldn't repartition the disk using Disk Utility. You would have to provide more information about why you can't.
As for OPTION booting Ubuntu I'm not sure how that worked. Typically Ubuntu installs the GRUB bootloader/manager that provides a text menu from which you select which OS to start. GRUB replaces the OS X boot manager.

Problem with dual boot after upgrade to Mountain lion

Hello Every One,
I have a Macbook pro from 2009 which had dual boot option Windows 7 + Snow Leopard.
The windows 7 had 2 partitions (C; and D: an extended partition).
I upgraded the OS X to Mountain lion. after upgrade the system showed 3 options at boot time. Mac, Windows and a recovery partition.
when i boot to windows the D: drive is gone...I mean even though i can see the partition in partition software, windows 7 stopped showing D: in "My computer".
So i used testdisk utility to get the D: drive back and now when i boot to mountain Lion i am able to access both C:(BOOTCAMP) and D: drives.
but now the problem is during boot time my Mac Book pro doesn't show the windows option.
Can some suggest a means to boot into windows 7? Also what is the purpose of recovery partition that Mountain lion adds to the system? I mean is it going to hurt if i get rid of it so that i can go back to my old configuration of 3 primary partitions (1 for windows 7 ...C: bootcamp + MountainLion) + 1 extended partition for D:
any help would be appreciated?
Regards

Ragu79 wrote:
Also what is the purpose of recovery partition that Mountain lion adds to the system? I mean is it going to hurt if i get rid of it
Leave it: http://support.apple.com/kb/HT4718

Mac pro cannot boot after upgrade to 10.8.3

My Mac Pro cannot boot after upgrade to 10.8.3. Anything firmware I can reset or how should I do.
I am using a early 2008 Mac Pro

Can you boot into safe mode? http://support.apple.com/kb/ht1455
If not, how about Recovery? http://support.apple.com/kb/ht4718
If you can, run Disk Utlity and repair the disk. You can try rebooting normally, but I would just reinstall after quitting Disk Utility.

For Those Who Can't Boot After Upgrading To 10.5.6

For Those Who Can't Boot After Upgrading To 10.5.6
(and i am one of those)
how is Apple supposed to make them able to install future fixes and updates
once they finally acknowledge and address this horrible bug?
will they send free bootable CDs with the updates to 10.5.6?

What "Boot ROM version" do you have (check in the system profiler under "Hardware")? If it's not MBP31.0070.B07 or MBP21.00A5.B08, then you will need to update your MacBook Pro's firmware. To do this, you might need to connect an external display and mouse/keyboard, and then run the computer with the lid closed to bypass the laptop's monitor. Then apply the firmware patch and reboot the system. This might also be doable via "Screen Sharing" if you have that enabled and have another mac handy.
The firmware update is here: http://www.apple.com/downloads/macosx/apple/firmware_hardware/macbookproefifirmw areupdate151.html
Message was edited by: Topher Kessler

Windows 8.1 dual boot after image

Hey guys
I'm having a little weird thingy with my dual boot systems at work... I've been Google-ing a while, but can't find anything about it. Allow me to explain.
I have a classroom with 16 computers running Windows 7 Professional. Because a course of Windows 8.1 will start next month, I have to install a dual boot system in that classroom. So, like normally, I take one PC to my office, create an extra partition,
install Windows 8.1 on it, do the necessary configurations and place the Win 7 partition as default. No problems there.
After the install and configuration, I create an image of the Windows 8 partition, the system state and MBR. So actually, I have an image of all the available partitions, except the Win 7 partition. After creating an image, I'm going back to the classroom
and install it on the PC's. After putting the image of the partitions, one problem arrives and that's the MBR. But after a few commands (bootrec /fixmbr, bootrec /fixboot, bootrec /scanos, bootrec /rebuildbcd), that problem is solved.
So, everything is ready to rock! Or so I thought... Here's my real problem now. When you boot the PC, you get the new blue boot option of Win 8 where you can choose which OS to boot. Well, when I select the Win 7 partition as default, I get the old DOS screen
for that. Ok fine, not a big problem, but the problem goes deeper.
With Win 8.1 you have two ways of shutting down a PC: either via right mousse click on the start button followed with 'shut down', or use the charms bar. If I do it the way with the start button, the PC boots in the Win 7 OS by default (just as I want it to
be). BUT when I shutdown the PC via the charms bar, the PC skips the "select OS to boot" menu and immediately starts Win 8!
I hope my entire explanation is clear to understand... So, anyone advice?
NOTE: On the source PC (created with the DVD and pulled the image from) is this problem not happening.

Hi,
You can follow the steps below to check your default boot system:
Press Win+R, open Run, use msconfig
command to open System Configuration.
After that, switch to Boot tab. Then check which system was default.
Roger Lu
TechNet Community Support
Like I said in my original post, the Windows 7 was default. But thanks to Brandon, the problem is solved now.

Hangs during boot after upgrading to Kernel 2.6.39

I have just installed Arch on a new computer. It works fine until I upgrade to Kernel 2.6.39. After that it hangs on boot.
The end of /var/log/everything.log is posted below.
Jul 26 23:52:06 localhost kernel: [ 6.036766] [drm] nouveau 0000:04:00.0: Parsing VBIOS init table at offset 0x85F3
Jul 26 23:52:06 localhost kernel: [ 6.129046] adt7475 1-002e: ADT7473 device, revision 1
Jul 26 23:52:06 localhost kernel: [ 6.138997] [drm] nouveau 0000:04:00.0: Detected monitoring device: adt7473
Jul 26 23:52:06 localhost kernel: [ 6.139000] [drm] nouveau 0000:04:00.0: 1 available performance level(s)
Jul 26 23:52:06 localhost kernel: [ 6.139002] [drm] nouveau 0000:04:00.0: 0: memory 405MHz core 270MHz shader 540MHz
Jul 26 23:52:06 localhost kernel: [ 6.139233] [TTM] Zone kernel: Available graphics memory: 12371030 kiB.
Jul 26 23:52:06 localhost kernel: [ 6.139236] [TTM] Zone dma32: Available graphics memory: 2097152 kiB.
Jul 26 23:52:06 localhost kernel: [ 6.139238] [TTM] Initializing pool allocator.
Jul 26 23:52:06 localhost kernel: [ 6.139252] [drm] nouveau 0000:04:00.0: Detected 5376MiB VRAM
Jul 26 23:52:06 localhost kernel: [ 6.139260] mtrr: type mismatch for d0000000,8000000 old: write-back new: write-combining
Jul 26 23:52:06 localhost kernel: [ 6.150626] [drm] nouveau 0000:04:00.0: 512 MiB GART (aperture)
Jul 26 23:52:06 localhost kernel: [ 6.152371] [drm] nouveau 0000:04:00.0: failed to load fuc409d
Jul 26 23:52:06 localhost kernel: [ 6.176193] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
Jul 26 23:52:06 localhost kernel: [ 6.176195] [drm] No driver support for vblank timestamp query.
Jul 26 23:52:06 localhost kernel: [ 6.228800] No connectors reported connected with modes
Jul 26 23:52:06 localhost kernel: [ 6.228802] [drm] Cannot find any crtc or sizes - going 1024x768
Jul 26 23:52:06 localhost kernel: [ 6.231002] [drm] nouveau 0000:04:00.0: allocated 1024x768 fb: 0x8020000, bo ffff880608d97800
Jul 26 23:52:06 localhost kernel: [ 6.233786] Console: switching to colour frame buffer device 128x48
Jul 26 23:52:06 localhost kernel: [ 6.235094] fb0: nouveaufb frame buffer device
Jul 26 23:52:06 localhost kernel: [ 6.235094] drm: registered panic notifier
Jul 26 23:52:06 localhost kernel: [ 6.235098] [drm] Initialized nouveau 0.0.16 20090420 for 0000:04:00.0 on minor 0
Jul 26 23:52:06 localhost kernel: [ 6.255449] HDA Intel 0000:04:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
Jul 26 23:52:06 localhost kernel: [ 6.255451] hda_intel: Disable MSI for Nvidia chipset
Jul 26 23:52:06 localhost kernel: [ 6.255599] HDA Intel 0000:04:00.1: setting latency timer to 64
Jul 26 23:52:06 localhost kernel: [ 7.663482] EXT4-fs (sda3): re-mounted. Opts: (null)
Jul 26 23:52:06 localhost kernel: [ 7.807508] EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null)
Jul 26 23:52:06 localhost kernel: [ 7.851401] Adding 265068k swap on /dev/sda2. Priority:-1 extents:1 across:265068k
Jul 26 23:52:06 localhost kernel: [ 8.569682] r8169 0000:08:00.0: eth0: link down
Jul 26 23:52:06 localhost kernel: [ 8.569687] r8169 0000:08:00.0: eth0: link down
Jul 26 23:52:06 localhost dhcpcd[747]: eth0: waiting for carrier
Jul 26 23:52:08 localhost dhcpcd[747]: eth0: carrier acquired
Jul 26 23:52:08 localhost kernel: [ 10.301736] r8169 0000:08:00.0: eth0: link up
Jul 26 23:52:08 localhost dhcpcd[747]: eth0: broadcasting for a lease
Jul 26 23:52:12 localhost dhcpcd[747]: eth0: offered 131.181.53.42 from 131.181.127.32
Jul 26 23:52:13 localhost dhcpcd[747]: eth0: acknowledged 131.181.53.42 from 131.181.59.48
Jul 26 23:52:13 localhost dhcpcd[747]: eth0: checking for 131.181.53.42
Jul 26 23:52:18 localhost dhcpcd[747]: eth0: leased 131.181.53.42 for 43200 seconds
Jul 26 23:52:18 localhost dhcpcd[747]: forked to background, child pid 774
Jul 26 23:52:18 localhost crond[823]: /usr/sbin/crond 4.5 dillon's cron daemon, started with loglevel info
Jul 26 23:53:01 localhost crond[823]: FILE /etc/cron.d/prune-cronstamps USER root PID 835 job prune-cronstamps
Jul 26 23:53:01 localhost crond[823]: FILE /var/spool/cron/root USER root PID 836 job sys-hourly
Jul 26 23:53:01 localhost crond[823]: FILE /var/spool/cron/root USER root PID 837 job sys-daily
Jul 26 23:53:01 localhost crond[823]: FILE /var/spool/cron/root USER root PID 838 job sys-weekly
Any help fixing this would be greatly appreciated.

I have been trying to isolate the problem a little further. I re-installed (with just the base and sudo) and after upgrading pacman rebooted and it worked without fail. Then I installed libusb and libusb-compat which where required when I tried to upgrade just the kernel using
pacman -S kernel26
which initially failed because of the missing dependencies libusb and libusb-compat. I then re-booted and that worked without a problem.
I then upgraded to Kernel 2.6.39 using the above command and then it hung on rebooting. I saved the logs at each stage.
The additional logs in errors.log in the reboot that failed are as follows.
ul 26 16:28:39 O313 kernel: [ 5.120698] [drm] nouveau 0000:04:00.0: Pointer to BIT loadval table invalid
Jul 26 16:28:39 O313 kernel: [ 5.360508] [drm] nouveau 0000:04:00.0: failed to load fuc409d
Jul 26 16:28:39 O313 kernel: [ 5.808016] sd 20:0:0:0: [sdb] Assuming drive cache: write through
Jul 26 16:28:39 O313 kernel: [ 5.809960] sd 20:0:0:0: [sdb] Assuming drive cache: write through
Jul 26 16:28:39 O313 kernel: [ 5.812116] sd 20:0:0:0: [sdb] Assuming drive cache: write through
Jul 26 16:28:35 O313 udevd[369]: error: runtime directory '/run/udev' not writable, for now falling back to '/dev/.udev'
The end of kernel.log is as follows:
Sat Jul 9 14:57:41 CEST 2011
Jul 26 16:28:39 O313 kernel: [ 0.000000] Command line: root=/dev/disk/by-uuid/e4733c60-3e54-4001-a83e-415b690dfcb0 ro
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-provided physical RAM map:
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 0000000000100000 - 00000000cfed0000 (usable)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000cfed0000 - 00000000cfed1000 (ACPI NVS)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000cfed1000 - 00000000cfee0000 (ACPI data)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000cfee0000 - 00000000cff00000 (reserved)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000f0000000 - 00000000f4000000 (reserved)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 0000000100000000 - 0000000630000000 (usable)
Jul 26 16:28:39 O313 kernel: [ 0.000000] NX (Execute Disable) protection: active
Jul 26 16:28:39 O313 kernel: [ 0.000000] DMI 2.4 present.
Jul 26 16:28:39 O313 kernel: [ 0.000000] DMI: Gigabyte Technology Co., Ltd. X58A-UD5/X58A-UD5, BIOS FD 02/01/2011
Jul 26 16:28:39 O313 kernel: [ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
Jul 26 16:28:39 O313 kernel: [ 0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
Jul 26 16:28:39 O313 kernel: [ 0.000000] No AGP bridge found
Jul 26 16:28:39 O313 kernel: [ 0.000000] last_pfn = 0x630000 max_arch_pfn = 0x400000000
And this is the end of daemon.log
Jul 26 16:27:49 O313 init: Switching to runlevel: 6
Jul 26 16:27:50 O313 dhcpcd: received SIGTERM, stopping
Jul 26 16:27:50 O313 dhcpcd: eth0: removing interface
Jul 26 16:28:39 O313 2.352592] udevd[87]: starting version 171
Jul 26 16:28:39 O313 4.531007] udevd[370]: starting version 171
Jul 26 16:28:39 O313 dhcpcd: version 5.2.2 starting
Jul 26 16:28:39 O313 dhcpcd: eth0: waiting for carrier
Jul 26 16:28:35 O313 udevd[369]: error: runtime directory '/run/udev' not writable, for now falling back to '/dev/.udev'
Jul 26 16:28:39 O313 init: Entering runlevel: 3
Please let me know if any further information would be useful in tracking down this problem. Also ignore any timings in my initial post they were incorrect.
Last edited by TheStatsMan (2011-07-26 07:40:48)

Hanging on boot after upgrading server.app

After upgrading to 10.9 Server.App my boot hangs at "/etc/rc.server: line 14: /etc/rc.server.firewall: No such file or directory" and won't boot into safe mode either. Anyone know how I can fix this without restoring from a backup?

Cameron, thanks for your feedback.
I'm on a 2011 iMac, with a DIY Fusion Drive (I added a SSD inside). I always had slow startups. I thought it was the custom Fusion Drive's fault, but now I know it was not.
Now I can't boot at all, just after applying the most recent 10.9.2 security update. This is a software issue. The iMac was running Mountain Lion Server, then I upgraded to Mavericks but did not upgrade to Mavericks Server. However there were remains of the old 10.8 Server app.
As I said, yesterday I deleted all those remains (booting from an external drive). However I forgot the most obvious thing: open that **** /etc/rc.server file and comment out line 14.
This morning I booted the iMac again, in verbose mode. The message about /etc/rc.server was not there, at last, but fsck was launched and took a long time. I had to go to work, where I am now, and I don't know if fsck finished its work. I'll let you know...

Mac Mini stuck at boot after upgrading to Yosimite

Hi All,
I am using mac Mini late 2012 model with 4 gb ram. I have recently upgraded to OSX Yosimite.
But now I am facing issue with it.
My Mac stops at boot. With Apple logo, grey/white screen and progree bar with 0% progress.
If I keep it as it is for some time, Mac mini temperature rises and i feel the heat while touching the mac mini. And still progress bar show 0% progress.
But when I switch it off with the help of power button and restart it, it works fine.
This happen every now and then. I have only monitor, Bluetooth mouse, wired keyboard and LAN cable attached to it. (WIFI stops working after upgrading to OSX now there is no wifi icon in system preferences or in task bar )
I have tried clean install also. But no success.
Please suggest why it stops at 0% progress bar. This is working fine before upgrading.
Regards
Siddharth

Hi Adding screenshot of the same. It stuck at 0 %

Iphone4 randomly chrashes and bootes after upgrade to ios7.1

Hello,
after upgrading from ios7.0 to ios7.1 my Iphone 4 chrashes and then bootes. Sometimes it does not happen during the whole day. Then again it crashes 5- 10 times a day.
I tried a few strategies, incl complete reset. Even loaded Ios7.1 with 2 different PCs. No success. It seems also to happen quite randomly, at least I couild not identify any logic behind it. Very frustrating experience.
Does anyone have the same experience? Any idea what to do?
Thanks / Thomas

As Texas Mac Man wrote in another post, the problem was fixed by repeated shut down of the iPad till GC started to work properly.

Imac won't boot after upgrade to latest Yosemite

After Upgrading to latest Yosemite version - my Imac will not start - it just hangs there or eventually comes with Crash window tellling it will restart.
However the Imac does launch in safe mode - holding down the shift key -but then there is no sound - so that no good.
Can you solve this you will be the christmas hero in Danish land.
NB sofar I have tried
reset PRAM- reinstalled Yosemite - Verified Disk is ok.
iMac (27”, ultimo 2009) - 2,66 GHz Intel Core i5
Yosemite 10.10.1 (14B25)
Latest crash log
nonymous UUID: 273AE997-AFAA-D71B-8080-9D38EA80ADEB
Sat Dec 27 19:52:13 2014
*** Panic Report ***
panic(cpu 1 caller 0xffffff800d01e80a): Kernel trap at 0xffffff800d1338c3, type 13=general protection, registers:
CR0: 0x0000000080010033, CR2: 0x000000010689fb25, CR3: 0x0000000124a97000, CR4: 0x0000000000002660
RAX: 0xffffff801aaa5df8, RBX: 0x00bfbfbf00bfbfbf, RCX: 0x0000000009000000, RDX: 0xffffff800d6f42d0
RSP: 0xffffff80a69bb460, RBP: 0xffffff80a69bb4b0, RSI: 0xffffff80a69bb507, RDI: 0xffffff800d6f42d0
R8: 0xffffffffffffffe9, R9: 0x000000000000003a, R10: 0xffffff8077cf3008, R11: 0x0000000000000000
R12: 0xffffff80a69bb4f0, R13: 0x0000000000000017, R14: 0x0000000000000017, R15: 0x000000000000031b
RFL: 0x0000000000010206, RIP: 0xffffff800d1338c3, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x000000010689fb25, Error code: 0x0000000000000000, Fault CPU: 0x1
Backtrace (CPU 1), Frame : Return Address
0xffffff80a00bde10 : 0xffffff800cf3a811
0xffffff80a00bde90 : 0xffffff800d01e80a
0xffffff80a00be050 : 0xffffff800d03a443
0xffffff80a00be070 : 0xffffff800d1338c3
0xffffff80a69bb4b0 : 0xffffff800d331348
0xffffff80a69bb5a0 : 0xffffff800d331d55
0xffffff80a69bb740 : 0xffffff800d32aab9
0xffffff80a69bb7d0 : 0xffffff800d340ccf
0xffffff80a69bb9a0 : 0xffffff800d13f2f8
0xffffff80a69bba80 : 0xffffff800d13ea95
0xffffff80a69bbbb0 : 0xffffff800d152005
0xffffff80a69bbc00 : 0xffffff800d15fcc7
0xffffff80a69bbf20 : 0xffffff800d154f0a
0xffffff80a69bbf50 : 0xffffff800d44dcb2
0xffffff80a69bbfb0 : 0xffffff800d03ac46
BSD process name corresponding to current thread: WindowServer
Mac OS version:
14B25
Kernel version:
Darwin Kernel Version 14.0.0: Fri Sep 19 00:26:44 PDT 2014; root:xnu-2782.1.97~2/RELEASE_X86_64
Kernel UUID: 89E10306-BC78-3A3B-955C-7C4922577E61
Kernel slide: 0x000000000cc00000
Kernel text base: 0xffffff800ce00000
__HIB text base: 0xffffff800cd00000
System model name: iMac11,1 (Mac-F2268DAE)
System uptime in nanoseconds: 88678398319
last loaded kext at 88213280354: com.apple.driver.AudioAUUC 1.70 (addr 0xffffff7f8f484000, size 28672)
loaded kexts:
com.apple.driver.AudioAUUC 1.70
com.apple.driver.AppleHDAHardwareConfigDriver 267.0
com.apple.driver.AGPM 100.14.37
com.apple.driver.AppleTyMCEDriver 1.0.2d2

Hello snake-apps,
Welcome to Apple Support Communities.
The article below provides troubleshooting tips that’ll help resolve kernel panic issues, like the one that you’re seeing with your iMac after upgrading to OS X Yosemite.
OS X: When your computer spontaneously restarts or displays "Your computer restarted because of a problem." - Apple Support
Ciao,
-Jason

Windows hangs boot after upgrading any software

Hi,
My Windows 8 Pro x64 Dell XPS8500 machine developed a really weird problem. (The problem actually began a while back - first noticed maybe 4-6 month ago - but only now trying to fix it.) It re/boots fine so long as I don't try to install anything.
However, installing any software upgrades causes Windows to hang on boot. The software upgrades that I tried are Evernote, iTunes, Java VM, and all of them are triggering the same behavior. All this aforementioned software seeming doesn't have
anything in common. The only known upgrades that do not appear to trigger the issue are Firefox and Chrome (where upgrades happen more or less in passive fashion) There is no clear event that I can recall in the past that I can attribute this happening
to (i.e. I can't pin point to something like installing a driving and it failing immediately afterwards) - just one day a message popped up to upgrade iTunes, which I did, and then rebooted to experience the issue.
Here are the steps to describe what happens with a bit more detail and troubleshooting steps tried:
Manually launch upgrade of an existing software. (Tried Evernote, iTunes, Java VM)
Successfully go through the install/upgrade. Seems irrelevant if software asks for reboot or not. Machine works fine until rebooted.
Reboot the machine. Machine shuts down without any issues.
BIOS POST is successful, and Dell logo with jumping/circulating dots comes up.
There is a normal flurry of hard-disk activity for a few seconds, which after a few seconds reduces to none or sometimes/occasionally to very brief flashing a few seconds apart. This is where the problem is noticed. It can stay like that for
hours if not days (normal boot takes about 20-30 seconds).
Typically, if there is no hard-disk activity at all, pressing the power button causes one brief flash, followed by one more about 1-3 seconds later, and no change.
The only recourse is to force turn off by holding power button for few seconds.
Letting it try to boot again leads to the same behavior.
Repeating attempts to boot 3-4 times causes Automatic Recovery to kick in.
The only way to get the machine to boot again is to use Recovery to restore to a previous state. This sometimes requires to be done more than once and doesn't fix on the first try.
(Also, I enabled Win boot menu, and couple of times instead of waiting for Automatic Recovery to kick in, tried to use recovery through the menu - in that case it's more likely to require the procedure to be done more than once).
I tried to do a logged boot to capture log file in one of the cases where it boots - it appears to never produce \Windows\ntbtlog.txt file (possible I didn't do something right for this one, though I thought that file is never deleted and only grows)
Additional Info: SysRestore currently displays only two available points:
6/13/14 - Installed Evernote v. 5.4 - Type Install
6/9/14 - Automatic Restore Point - Type System
All other previous restore points (from having installed a few more updates and software in the 1.5 years I had the machine) are gone somewhere.
Choosing to revert to the second restore point (when selecting restore point from boot menu) as opposed to the first one and later booting successfully, for some reason the same restore points are listed again (so it doesn't seem to be truly reverting)
Nothing fruitful appears in the EventLog. The only critical messages that i see there are both from SCM and one reads "The Dell Digital Delivery Service service terminated unexpectedly. It has done this 1 time(s)." and the other "The
system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly." (which is expected). And there is a warn level entry about some Bluetooth device not being
able to enter power save mode. That's it for system event logs.
At this point I'm totally stuck trying to figure this one out, or even trying to figure out how to obtain information on where it gets stuck. This is worse than having a BSOD as with BSOD at least there is some info on what's happening. Here
I don't even see where it gets stuck or what's preventing from booting successfully.
Please help!!!

Here is the link to the SrtTrail.txt file:
http://1drv.ms/1sh7rCy
Again, let me clarify the situation as well as provide some additional information that I discovered since original post. Per original post - I can boot into the system up and until installer gets activated either by trying to uninstall or upgrade
existing software or install new one. At the time, the only way I could get the system to boot again was to let it fail boot twice and on the third attempt let it perform system restore from a restore point, and then it would boot again (with all the
installed/updated/uninstall changes wiped out)
Since then I discovered the following additional behavior points:
I managed to get it to accept couple of software upgrades by using roughly the following steps: let it fail boot twice. On the third attempt instead of choosing system restore I instead cancel or choose advanced options (depending on what it offers).
Typically it goes either through some system analysis or disk check for errors - wait and it doesn't find anything. When presented with a menu of other recovery options (like changing UEFI, command prompt, etc), I simply choose to exit and continue loading
windows. At this point it sometimes (I'd say 1 out of 3 times) manages to boot successfully, retaining all the changes (i.e. retaining software updates and the like). If it doesn't succeed booting, repeat until it does. Using these steps
I managed to update most of software so far, including windows update. But each time it's a struggle to get it to boot again.
Simply rebooting the system without any changes succeeds most of the time. However, today I noticed that a plain reboot (without any installer/uninstaller/update or any other system/soft/config changes) doesn't always succeed, requiring the same process
as in previous bullet point to get it to boot again.
I also noticed an additional behavior - my keyboard an mouse have some buttons that are illuminated (on dell keyboard those are media buttons, and on the dell mouse it is mouse sensitivity indicator). I noticed that when windows boot up, the keyboard and
mouse lights go out simultaneously. If they come back about a second or two later (with one flicker in between), then system boots up fine (the moment they come back, the system displays the logon screen with the seatle space needle). However,
if they don't come back, then the boot will hang there for ever. Is it possible that some driver sometimes succeeds to be loaded correctly, and sometimes fails to load causing Windows to perpetually wait for that driver to finish loading (which it never
does)? If that sounds like a possibility, how can I find out what is it that windows is doing when it starts to perpetually wait for whatever it is waiting for? Tell me what logs would help to understand that and how to capture those!
Also note that I run Avira Antivir antivirus (ever since I got this PC), and it doesn't flag anything suspicious on the system. I also ran MalwareBytes scan which found no suspects, as well as GMER rootkit scanner (which as far as i can tell, also
did not find anything suspicious).
There is another oddity that is going on with the system - may or may not be related, so mentioning just in case it is - which is that I'm using Dropbox, and it keeps creating "My Videos" folder on the Desktop, even though it is way outside of my dropbox
root. Deleting the folder doesn't help as the moment I right-click on the Desktop, it re-appears. It, oddly enough, also appears in C:\Users\{profile} folder right along side real "My Videos" folder. Looking properties of both in explore
shows in the property pages that one is located in C:\Users\{profile} and another in C:\Users\{profile}\Desktop (and again, yet both of those explore shows in C:\Users\{profile}). Like I said, not sure if these are related (I suspect not, but who knows),
so mentioning just in case.
Note that I'm trying to fix it without going through refresh or reset since the first one would cause the pain to reinstall of all the software on the system (without any indication that this would solve the issue), and the later option would just completely
wipe out everything off of the system, which is even more painful, and again would not guarantee solution (e.g. if it is a bad driver that would get reinstalled anyway after wipe. Yes, I technically do have backups, but those are more for drastic case if my
harddrive crashes, and wouldn't want to rely on those to voluntarily wipe the system due to odd behaviors - too painful and time-consuming. I'm looking for a solution to problem rather than just-start-from-the-beginning-because-it-is-easier approach.
Thanks, let me know how to get the troubleshooting info to get to root cause.

My Macbook Pro wont boot after upgrading to SSD, A ? Mark on Folder appears

Hello all,
I just put in a new SSD into my mid 2012, 13" macbook pro. This is the exact SSD http://www.tigerdirect.com/applications/searchtools/item-details.asp?EdpNo=77394 89&tab=7&SRCCODE=WEBLET03ORDER&cm_mmc=Email-_-WebletMain-_-WEBLET03ORDER-_-Deals &utm_source=EML&utm_medium=main&utm_campaign=WEBLET03ORDER&cm_lm=noahbragg@cedar ville.edu
I swapped out my optical drive and put in the SSD using this tutorial, http://www.ifixit.com/Guide/Installing+MacBook+Pro+13-Inch+Unibody+Mid+2012+Dual +Hard+Drive/13787 Everything seemed to go fine and i had no problems. But when I tried to start up the computer it stayed on a gray screen and a foler with a question mark on it, showed up blanking. I have looked all over for the internet for the answer, I have tried to reset the PRAM but it did nothing. I then tried to select what drive i wanted to boot from by holding the option key when i booted, but when the options came up, SSD or old harddrive did not come up as a way to boot up. There were some internet options to recover but they did not work.
The SSD has nothing on it at this point, but my plan was to boot up using the original HD and then clone it over to the SSD, but ovbiously i cant even find the HD to boot to. I have seen that people are having troubles with booting to their SSD because of the new mavericks update, but i am just trying to boot to my original HD at this point.
I also considered that maybe i possibly damaged the HD cables through static electricty, but when i searched more about it i learned that i should have heard snap or felt a jolt. None of these things happened when i installed the SSD. So i beleive that the hard drive or SSD are not broken in any way.
Does anyone have any ideas or suggestions on how i can fix this? Need my computer very badly! thanks in advance.

I also forgot to mention that after the first time i tried to boot, it went to the normal screen where it wanted me to put in my apple id password. but the loading wheel was just spinning the whole time. so i turned off the computer and tried again. thats when the question mark folder came up and kept coming up everytime after that.

Windows 7 no longer boots after upgrade from Lion to Mountain Lion

I got a late 2011 MacBook Pro, on which I installed Windows 7 with Boot Camp. After I upgraded from Lion to Mountain Lion, I can no longer boot Windows. If I keep the option button pressed during boot I only get the OS X and recovery options, and if I choose to boot Windows from the system preferences pane, I get a message that says that no bootable device was found. However, I'm sure that the partition is still there, because I can see it in finder and browse the files normally. How can I boot Windows again?

"Easier" in this case as an alternative is defined as repartitioning/reformatting your disk, and restoring from backups (which for most people also means starting from scratch with Boot Camp Assistant and Windows since most users aren't backing that environment up).
What you did is, in my opinion, easier and faster. But if you don't know what you're doing can lead to data loss. But then, by definition, blowing away your disk and starting over with a restored backup begins with data loss!

Z61t Doesn't boot after upgrading hard drive

I'm upgrading the hard drive on my girlfriend's Lenovo Z61t laptop and am running in to a strange problem.
The computer will not boot anymore! I cloned the old disk to the new one using acronis true image and when I insert the new disk into the laptop and boot it, after the system prompt there's a blinking dash at the top left corner of the screen.
http://forums.lenovo.com/lnv/board/message?board.id=Z_Series_Thinkpads&message.id=469&query.id=23938...
This user seemed to have experienced the same issue as me. Unfortunately, no reply to his post
Drive is detected in the BIOS, PC doctor reports no problem on both the short and extended test... And to top it off, if I insert the driver into my HP laptop windows will start loading as expected
Are lenovo laptop cursed?
Any help is appreciated!

I fixed the issue. I researched many many forums and found no help on any of them, and sorry-no help on this one either.
What solved the issue - and I hope this helps someone else who has the same problem:
1). Install new hard drive (with or without osx pre installed)
2). Remove all ram
3). Power on and wait 1 minute
4). Hold power button until it turns off
5). Install ram
6). Power back on
7). BOOM! It works again.

Dual boot after upgrading to 10.4?

Similar Messages

Maybe you are looking for