This crack like all other does not work. I need some help! I have some insight on the issue now however. Ok I have learned what I believe to me by issue with the lo*der cr**ks on my Apple MacBook. All of them seem to use either NeoGrub or Grub4DOS and requires a MBR Patition Table. My MacBook is formatted as a GUID Partition Table (GPT). Does anyone have a solution to this? When booting using NeoGrub with the WoW7 lo*der this is the messages I see. Code: Booting GRLDR... Turning on gate A20... Success. Warning: Unrecognized partition table for drive 80. Please rebuild it using a Microsoft-compatable FDISK tool(err=4). Current C/H/S=266305/255/63 Starting cmain() ... Warning: Unrecognized partition table for drive 80. Please rebuild it using a Microsoft-compatable FDISK tool(err=4). Current C/H/S=266305/255/63 Does anyone have any ideas how to get this working with a GUID Partition Table (GPT) or even any of the Loaders working with a GPT?
WoW7 uses different approaches than vista loader. Try them both. Maybe one of them will work! I'll update grub at next wow version to make it more compatible (hopefully)!
I have tried every loader imaginably. WoW7, 7Loader, Chinese Loader, Cd-slic-ldr. None work on my GUID Partition Table (GPT) formated Apple MacBook.
Hope you find a way to make grub to boot your partition.....right configuration. I'm not familiar with grub and Mac-partitions
Just for the record, this can be and will be detected by Microsoft and patched. I dont recommend this method but the BIOS SLIC method will work as it cannot be patched by Microsoft.
ms Can it be patched detected even if updatesa re turned oiff?? I rarely use ms updates they always seem to screw something else up so wouldn`t miss them??
Still does not work even with this wow7 method. I do not really understand why using the same windows 7 x64 rtm iso has worked in other 2 machines, and still do not work in my HP Elitebook 2710p. What I can see is that slic table on read & write utility still shows 2.0 version. This just be the problem. It is like this methods cannot emulate SLIC 2.1 on this machine, but why? Do you have any idea? What I can see is that slic table on read & write utility still shows 2.0 version. This just be the problem. It is like this methods cannot emulate SLIC 2.1 on this machine, but why? 53 4C 49 43 76 01 00 00 01 AB 48 50 51 4F 45 4DSLICv.....HPQOEM 53 4C 49 43 2D 4D 50 43 01 00 00 00 48 50 20 20SLIC-MPC....HP 01 00 00 00 00 00 00 00 9C 00 00 00 06 02 00 00................ 00 24 00 00 52 53 41 31 00 04 00 00 01 00 01 00.$..RSA1........ 5B AB 60 56 BC 58 1E E8 C1 D2 A1 5C E5 4F BB FD[.`V.X.....\.O.. 1D A9 8C 94 B4 AE 08 11 DC 13 59 D3 7F F6 3E 87..........Y...>. 31 B9 95 74 10 DA 3B A4 5B B5 19 82 7C 39 D7 0D1..t..;.[...|9.. 7C 22 AC 1C 2A 84 E9 0A 88 6D FA B1 E2 D8 E8 21|"..*....m.....! 96 E1 2E 68 9A BF 44 45 3E 3C 8E 99 90 DE 37 38...h..DE><....78 57 0B 92 15 BC DE FF F2 07 7E B5 40 8C 51 3A [email protected]:. 02 48 F6 13 12 72 FB 42 78 E6 47 88 54 C7 B0 F0.H...r.Bx.G.T... 93 9E FB 04 B7 B8 B8 90 DE DB ED 32 E1 FB 54 A6...........2..T. 01 00 00 00 B6 00 00 00 00 00 02 00 48 50 51 4F............HPQO 45 4D 53 4C 49 43 2D 4D 50 43 57 49 4E 44 4F 57EMSLIC-MPCWINDOW 53 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00S .............. 00 00 00 00 00 00 30 A8 7E 10 1B 0F 13 DD 2E 2D......0.~......- 36 C2 AB 54 A7 8C 3A A0 2F C6 5B B3 B3 DD 93 EE6..T..:./.[..... 8E 39 A9 92 D0 5A 20 E1 2D F5 A2 1C 7A 3E 54 85.9...Z .-...z>T. 99 72 56 5F EC 6B 07 17 63 82 3E 79 02 50 40 C9.rV_.k..c.>y.P@. F1 D3 C5 58 39 A8 18 F1 56 91 EA 9C 54 1A E0 CE...X9...V...T... C9 16 F0 5D D1 90 B1 B0 9E 81 E6 BA 62 F1 3B 96...]........b.;. B0 7D D7 47 10 78 03 C9 28 52 E7 2D 4A F7 70 BB.}.G.x..(R.-J.p. 53 1F BE CD 4F 77 D1 2F A8 3D 5C 26 AF 80 42 25S...Ow./.=\&..B% EF 7A B2 67 BA 1C .z.g.. Signature"SLIC" Length0x00000176 (374) Revision0x01 (1) Checksum0xAB (171) OEM ID"HPQOEM" OEM Table ID"SLIC-MPC" OEM Revision0x00000001 (1) Creator ID"HP " Creator Revision0x00000001 (1) .........................
This message is primarily directed at Yen, but anyone else who is informed is encouraged to respond as well. I'm using a Mac, which comes with certain drawbacks with respect to SLIC tables, but also certain advantages. In my spare time I've been doing a lot of searching, trying to figure out how exactly it is that the SLIC table is loaded into memory. I've read that it's done through grub treating it as ACPI data, but I haven't been able to find any specifics, or source code to figure out how exactly it works. I'm using a Mac, and there exists a version of grub in svn that can be compiled as an EFI binary, and supports the loading of legacy operating systems as well. I think this would be the perfect solution for the Mac, since grub could be launched directly from the disk by "blessing" it, and the bootcode for the Windows partition could remain untouched. I just don't know how the SLIC table gets loaded. If you are able to help me in any way, I would be very appreciative, and if I can get something working with my fairly basic programming skills, the community would be as well. No guarantees that I can, of course.
@ sonyman I don't thinks it's grub that loads the SLIC into RAM. I think it's part of the (pre)boot process, reagardless of what OS/lo*der you are using. What exactly are you trying to do? Have a dual boot with win7 and macos? As I understand, the process goes like this: 1. During the (pre)boot process, the bios copies the slic table, among other stuff, to ram. When bios is done, it calls the mbr. 2. There are 2 grubs. One outside the floppy image (grldr) and one inside the image (grub.exe). The mbr is setup so that grldr is called first. grldr loads the floppy image, which is a Windows 98 "DOS mode" boot disk. 3. DOS is loaded and autoexec.bat is executed. It calls wow.exe, which patches the memory, and then calls grub.exe. 4. grub.exe now calls bootmgr and win7 takes over the machine. So, if you want to have a dual boot patched-win7 and unpatched-macos, you would edit the menu.lst *outside* the floppy image. Change it so that grldr would display a menu allowing you to choose to boot from macos or the floppy image, which will later call win7.
To Yen and others that might be able to help. We need to relay the symptom we are experiencing on Macs that sonyman is trying to help us with. Once we install a lo*der we experience a long delay in the boot process of Windows 7. During the initial boot we'll sit at a black screen with a blinking white cursor seen at the upper left corner of the screen. We'll be stuck at that screen for approximately 30 seconds before the boot process once again continues normally. We would like to get rid of this long boot delay. Your help is greatly appreciated by the Mac Community! Thank you!
help me! The download link from sendspace is blocked by my ISP, can anyone upload wow7 to any place other than sendspace via http ? thanks!