[Rumor]

I just read about it, so I am not sure of any issues with it. Has anyone upgraded Bootcamp and installed 7?

What I am mostly curious about is if anyone has updated Bootcamp on an existing 7 partition? Has it caused problems?

[ghporter]

Here is the 32 bit Windows update for Boot Camp.

Here is the 64 bit Windows update for Boot Camp.

And the very important Windows 7 Installer update. Use this BEFORE upgrading a Boot Camp-Windows Vista installation to Win 7.

This looks very nice. I wonder when I'll get time to play with it enough to see how nice it really is.

[Cold Warrior]

No issues observed. I'm on a MBP 13", Windows 7 Pro x64.

Skype now recognizes the internal mic.

Unfortunately my backlit keyboard still won't turn completely off. This has always been an issue though.

[seanc]

Originally Posted by Cold Warrior 

No issues observed. I'm on a MBP 13", Windows 7 Pro x64.

Skype now recognizes the internal mic.

Unfortunately my backlit keyboard still won't turn completely off. This has always been an issue though.

I don't think mine has ever turned off through the iterations of Windows I've installed.

[Rumor]

I updated last night and haven't had any issues yet.

[Big Mac]

Originally Posted by seanc 

I don't think mine has ever turned off through the iterations of Windows I've installed.

Works fine on our Penyryn MBPs, and we've had 7 since the Release Candidate.

[turtle777]

K, guys, I'm confused.

I was able to install Win 7 Pro on my 24" iMac (2008).
I deleted my former Win Vista install, and started from scratch on a 40GB Bootcamp partition.

Everything boots up fine.

Then I tried to install Bootcamp 3.1. Well, doesn't work, I can't find a standalone installer. So I try to install Bootcamp 3.0 first. Trouble. Upon booting up, I get the BSOD, and Windows restores back to the last restore point before the Bootcamp 3.0 install.

Question:

a) Why do I even need Bootcamp 3.x if my Win 7 install works fine ?
b) How do I get around this BSOD ?

TIA,

-t

[Cold Warrior]

ghporter's post above links to the standalone BC 3.1 exe installers.

If Windows restores and you can log in, maybe the 3.1 exe will work. Maybe check out the Windows system logs to see if you can find the driver or issue that's causing the BSOD.

[turtle777]

Originally Posted by Cold Warrior 

ghporter's post above links to the standalone BC 3.1 exe installers.

If Windows restores and you can log in, maybe the 3.1 exe will work. Maybe check out the Windows system logs to see if you can find the driver or issue that's causing the BSOD.

Unfortunately, the link above only leads to the Updater.

It seems like there used to be a Standalone installer, which got pulled by Apple.

Man, this really sucks. I have wasted about 8 hours trying to get this sh!t fixed. F*cking Windows. F*cking Bootcamp.

-t

[Cold Warrior]

If you had a virgin Win7 install, you could try installing only the Apple Software Update app and some single network/wifi drivers, and SW Update then might grab 3.1 without wanting 3.0.

[turtle777]

Originally Posted by Cold Warrior 

If you had a virgin Win7 install, you could try installing only the Apple Software Update app and some single network/wifi drivers, and SW Update then might grab 3.1 without wanting 3.0.

Thanks. I have a virgin Win 7 install. I tried Apple Software Update. Problem is, I can't get Bootcamp 3.0 installed (Win 7 crashes at startup with BSOD), so there's nothing the updater could find, because BC 3.0 is not installed.

It's like a bad catch 22.

I tried installing BC 3.0, and then immediately BC 3.1 (w/o a reboot in between). No avail, same BSOD.

For some reason, most things work in Win 7 even w/o the BC install. Wireless works, audio works, keyboard works (except for special functions like volume control etc...).

Next I tried installing BC 2.0 from the OX 10.5 disc. Worked only after forcing it (ignoring compatibility warnings). Let's see if the reboots works, or screws things up even more.

Edit:

Win 7 with Bootcamp 2.0 works WTF ?
Now the keyboard special functions like volume works.

Apple Software Update does NOT deliver an update to BC 3.0, because you need to purchase OS X 10.6 to get BC 3.0
I'm going to create a new restore point and see if I can get BC 3.0 installed over 2.0 now.

Edit 2:

Installing BC 3.0 over 2.0 causes the same BSOD upon reboot.
Also, BC 3.1 can NOT be installed over 2.0. As I said before, there don't seem to be any standalone installers for 3.1.

WTF Apple

How hard can it be to make your darn BC installer work with the limited amount of different hardware that you supply.

-t

[Cold Warrior]

Apple - Support - Discussions - Windows waking up from Sleep mode while ...

Some people have had success resolving a BSOD in that thread by preventing the hfs driver from launching.

[turtle777]

Originally Posted by Cold Warrior 

Apple - Support - Discussions - Windows waking up from Sleep mode while ...

Some people have had success resolving a BSOD in that thread by preventing the hfs driver from launching.

Sure you got the right link ?
It doesn't mentioned BSOD of hfs at all

-t

[Cold Warrior]

Apple - Support - Discussions - Boot Camp 3.0 AppleHFS.sys Windows blue ...

whoops

[turtle777]

Thx. I'll give that a try.

I'm still puzzled why a Bootcamp 3 on virgin install of Win 7 on a stock iMac 24" fails.
Shouldn't that be the first thing that Apple would test ?

-t

[turtle777]

Well, Apple-damnit, renaming AppleHFS.sys and AppleMNT.sys fixes the BSOD problem.

I can use BootCamp 3.1 now.
The only thing that doesn't work, of course, is mounting and accessing my Apple-formatted volumes and drives. WTF ?

Clearly, Apple f*cked this up. I can't believe that after all those months of Win 7 being out they still have issues like this.

-t

[seanc]

I've not had a problem with the AppleHFS driver on my MacBook Pro. Have you got all of the Windows 7 updates installed?

I have to say the driver is nice, but does need some usability kinks working out.

[turtle777]

Originally Posted by seanc 

I've not had a problem with the AppleHFS driver on my MacBook Pro. Have you got all of the Windows 7 updates installed?

Yes, virgin Win 7 install, with all the updates via software update.

I don't understand how Apple fails to make their software work on a VIRGIN install.

I understand that they can't test for all kind of interaction with installed 3rd party drivers and software, or what happens when you upgrade from Vista / XP to WIn 7.
But failing to work on a virgin Win 7 install is inexcusable. There are no unknowns in this.

-t

[seanc]

If you look through your Event Log, we may be able to help determine WHY it was BSODing.

Event Viewer is in Control Panel/Administrative Tools. You want the System Log.

You'll be looking for something that references a bugcheck or unexpected restart, then click the copy to clipboard button and paste here.

[turtle777]

Thanks. Here's what I got.

the BSOD screen says IRQL_NOT_LESS_OR_EQUAL, but doesn't reference any more details.

The Event log has 1 critical and 2 Error entries.

Critical:

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Error:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x00000030, 0x00000002, 0x00000000, 0x82d57f69). A dump was saved in: C: \Windows\MEMORY.DMP. Report Id: 012410-26379-01.

The following boot-start or system-start driver(s) failed to load:
AppleHFS
AppleMNT

Debug log:

************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {30, 2, 0, 82d57f69}

Probably caused by : cng.sys ( cng!HashFirstUserModeCallerBlobs+7f )

Followup: MachineOwner
---------

0: kd> !analyze -v;r;kv;lmtn;.logclose;q
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000030, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 82d57f69, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from 82ba4718
Unable to read MiSystemVaType memory at 82b84160
00000030

CURRENT_IRQL: 2

FAULTING_IP:
nt!ExQuerySystemLockInformation+c5
82d57f69 668b4830 mov cx,word ptr [eax+30h]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: csrss.exe

TRAP_FRAME: 8cf970c0 -- (.trap 0xffffffff8cf970c0)
.trap 0xffffffff8cf970c0
ErrCode = 00000000
eax=00000000 ebx=81fc8a78 ecx=00000000 edx=00000000 esi=00000000 edi=82b76698
eip=82d57f69 esp=8cf97134 ebp=8cf97150 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!ExQuerySystemLockInformation+0xc5:
82d57f69 668b4830 mov cx,word ptr [eax+30h] ds:0023:00000030=????
.trap
Resetting default scope

-t

[imitchellg5]

Originally Posted by turtle777 

Yes, virgin Win 7 install, with all the updates via software update.

I don't understand how Apple fails to make their software work on a VIRGIN install.

I understand that they can't test for all kind of interaction with installed 3rd party drivers and software, or what happens when you upgrade from Vista / XP to WIn 7.
But failing to work on a virgin Win 7 install is inexcusable. There are no unknowns in this.

-t

I had no problems at all on my MacBook Pro. Smooth as an OS X install. Well as smooth as it'll ever be.

[seanc]

Well yep, that pretty much tells us what caused the issue, the Apple HFS driver - we'll have to wait for a driver update from Apple I think.