[AMD] Installing Snow Leopard 10A432 on AMD System

[Rommel64]

Rapidshare downloads on the front page... most of them don't work anymore. Require a premium membership... can somebody please upload those elsewhere, like mediafire (?), or attached to a post in this thread...? That would be greatly appreciated. Thanks.

 

 

They all work, you just have to wait for an open slot it took me all day to get all of them. LOL

[sarkdog]

I don't have a dual layered dvd so my question is, can I use iDeneb or any other release but just install the base of it, without other kexts and stuff?

[Covernuo]

I can't get the cpuids，so i can't patch two of them...help

[Suneru]

please help me, error

 

all steps, dsdt.aml from dsdt pathergui , replace boot, amd_kernel -x32 -v -s -x... phenom 9500, amd 690v/sb600...

please help;

 

ps: chameleon rc2, chameleon rc3 all is even error...

[k2dragon]

 

Before we begin to install Snow leopard On AMD system we need to prepare some file :

 

1. Kernel : Because AMD cant boot with vanila kernel..

for me the most success kernel is mach_kernel.test7 from modbin.

test7 its because its kernel number 7 i have test from modbin (all other kernel get me a KP)

you can get the kernel : here

2. Chameleon rc 2.640 pkg... you can get it from their website or : here

3. boot file to replace chameleon 2 boot file : here

4. DSDT.aml for your system. Google it to find out how

you will need a cmos reset fix in your DSDT.aml, DSDT patch also can be use to make your HDA sound working with vanilla AppleHDA.kext

5. Some kext like:

 

dsmos.kext - required to decrypt encrypted binaries

NullCPUPowerManagement.kext - attaches in place of the real AppleIntelCPUPowerManagement which doesn't work right on PCs (kernel panic, cpu running hot)

OpenHaltRestart.kext - very simple kext that makes reboot and shutdown work on PCs

PlatformUUID.kext - sets the platform UUID so that you have a uniform UUID from the very start of the boot.. this UUID is used in your preferences files (among other things) and I think it is important for a clean install to have this right from the first boot.

 

you can get it here

 

and you will need a snow leopard 10A432 dmg

 

Next Step Installing Snow...

(install from a working leopard)

1. prepare an empty volume with disk utilities n get the uuid of the volume in this sample name it "snow''

 

Make sure that the new volume's root directory is owned by the root user.

chown 0:0 /Volumes/Snow

 

2. Mount the installer

a. if you have a GPT (GUUID Partition Table)

mount the snow leopard installation dmg/iso

open /Volumes/Mac\ OS\ X\ Install\ DVD/System/Installation/Packages/OSInstall.mpkg

 

b. if you have an MBR partition u need to edit the OSInstall.mpkg or you can download : here

u can restore the dmg/iso to an empty partition and change the Osinstall.mpkg its located on /Volume/"some volume name"/System/Installation/Packages/

run the Os install.mpkg

 

3. Install Snow leopard to targeted volume

4. Install Chameleon Rc 2.640 to targeted volume.

5. Replace the boot file

5. Place the new kernel in the root of volume

6. create an smbios.plist and place in to /Extra (in the targeted volume)

this is the dummy:

   <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>SMbiosvendor</key>
	<string>Apple Inc.</string>
	<key>SMbiosversion</key>
	<string>MP21.88Z.005C.B01.0608221120</string>
	<key>SMbiosdate</key>
	<string>04/01/2008</string>
	<key>SMboardmanufacturer</key>
	<string>Apple Computer, Inc.</string>
	<key>SMboardproduct</key>
	<string>Mac-F4208DC8</string>
	<key>SMfamily</key>
	<string>MacPro</string>
	<key>SMmanufacturer</key>
	<string>Apple Inc.</string>
	<key>SMproductname</key>
	<string>MacPro2,1</string>
	<key>SMserial</key>
	<string>W88033AKY51</string>
	<key>SMsystemversion</key>
	<string>1.0</string>
	<key>SMUUID</key>
	<string>00000000-0000-1000-8000-000000000000</string>
	<key>SMmemtype</key>
	<string>19</string>
	<key>SMmemspeed</key>
	<string>800</string>
	<key>SMmemmanufacter</key>
	<string>Apple Computer Inc.</string>
	<key>SMmemserial</key>
	<string>100000000</string>
	<key>SMmempart</key>
	<string>1</string>
<!--
	<key>SMexternalclock</key>
	<string></string>
	<key>SMmaximalclock</key>
	<string></string>
-->
</dict>
</plist>

change the UUID with volume UUID that u have before (point 1)

also place the UUID in the PlatformUUID.kext its located on PlatformUUID.kext/content/info.plist

 

7. Place dmos.kext, PlatformUUID.kext, Openhaltrestart.kext, NullCPUPowerManagement.kext in /Extra/Extensions/

8. Edit your /extra/com.apple.Boot.plist

this is just a sample with EfiString for my nVidia Geforce 9600 GT

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>Kernel</key>
	<string>mach_kernel.test7</string>
	<key>Kernel Flags</key>
	<string></string>
	<key>Timeout</key>
	<string>5</string>
	<key>device-properties</key>
	<string>6c0200000100000001000000600200000d00000002010c00d041030a01000000010106000010
0101060000007fff04000e0000004e00560050004d00000020000000010000000000000000000000
0
0000000000000000000000000000000220000005600520041004d002c0074006f00740061006c007
3
0069007a006500000008000000000000201c0000006400650076006900630065005f007400790070
0
0650000000f0000004e5644412c506172656e740e0000006e0061006d00650000000b00000064697
3
706c617922000000400030002c006400650076006900630065005f00740079007000650000000b00
0
000646973706c617922000000400031002c006400650076006900630065005f00740079007000650
0
00000b000000646973706c6179100000006d006f00640065006c0000001a0000006e566964696120
4
765466f726365203936303020475420000000400031002c0063006f006d007000610074006900620
0
6c00650000000e0000004e5644412c4e564d616314000000400030002c006e0061006d0065000000
1
20000004e5644412c446973706c61792d4114000000400031002c006e0061006d006500000012000
0
004e5644412c446973706c61792d4220000000400030002c0063006f006d00700061007400690062
0
06c00650000000e0000004e5644412c4e564d6163100000004e00560043004100500000001800000
0
04000000000003000c00000000000007000000001e00000072006f006d002d007200650076006900
7
30069006f006e0000002e0000006e5669646961204765466f7263652039363030204754204f70656
e
474c20456e67696e65205b4546495d</string>
</dict>
</plist>

9. Place your fixed DSDT.aml in the root of targeted volume

10. if you have other kext like voodooHDA or sumthing you can also install it (i use dsdt to get my sound working)

 

11. Reboot your PC and boot from targeted volume

 

Good Luck....

 

 

I am installing on my

AMD Athlon 64 X2 4800+ / 2.5 GHz

4GB

NVIDIA GeForce 6150 / nForce 430.

The EFI does not have my card. What should I do?

Also I am trying to install Snow Leopard on a USB Hard Drive, will it work?

Right now I am getting

>80000080

<00000002

000000C1

00000048

*<00064028

J

[thatoneguy]

First off, awesome guide Arya. I used a distro for my Leopard install, so I quite enjoyed tinkering with the innards of the OS rather than just checking boxes.

 

It installed fine on my system and I can boot into it. However, I have no PS/2 support for my mouse (my PS/2 keyboard works). I have tried the VoohooPS2Controller as well as a hacked version of the ApplePS2Controller and still nothing. Is there another kext that will take care of this or could I edit the dsdt.aml to get it working? I borrowed a USB mouse for the time being and even that is jittery and nigh uncontrollable.

Also, everything runs incredibly slow. The boot times are ridiculous and everything is choppy, the dock, genie effects, opening programs, etc. How can I fix this?

As a sidenote, I used dsdtse for dsdt.aml editing and booting with that file doesn't seem to do anything.

 

Thanks in advance for any and all help.

[WaPeR]

I can't find my videocard in EFIstudio, what i need to do in my PC to work with my Ati HD4670?

 

thanks!

[thatoneguy]

I borrowed a USB mouse for the time being and even that is jittery and nigh uncontrollable.

Also, everything runs incredibly slow. The boot times are ridiculous and everything is choppy, the dock, genie effects, opening programs, etc. How can I fix this?

Fixed.

The folks at Evosx86 said that you either want you EFI string in the com.apple.Boot.plist or in the DSDT.aml, but not in both places. I removed the EFI string and no more jittery mouse or choppy programs.

[asasyx]

Can it be installed without the earlier versions of os x. Next to windows or clean hdd?

[elwin00]

Can it be installed without the earlier versions of os x. Next to windows or clean hdd?

 

I wanted to ask the same thing. Is there a way to install 10.6 on AMD without having previous version already installed? Perhaps with working virtual machine..

[Zythyr]

@arya, thanks for the great guide, but I am a little confused about the installation process.

 

Before I ask my any question, let me give you my specs:

 

HP Pavilion DV6607nr

Processor: AMD Athlon 64 X2 Dual Core TK-53

Chipset: NVIDIA nForce 560 MCP67?

Graphics: NVIDIA GeForce 7150M/nForce 630M (0x053110de)

Conexant HD Audio (0x504514f1)

Wireless: Broadcom BCM4311 (0x431114e4)

Ethernet: nForce Adapter (0x054C10de)

 

I had a very difficult time installing Leopard due to my nForce 560 chipset. I had to use Leo4Allv4.1 with a special modified Extensions.mkext which finally allowed me to boot into Leopard.

 

For the Snow Leopard installation, I am confused about the Extensions. Do I have to have special kext like the AppleNForceATA.kext, to have my chipset work? Which other kext do I need? Should I just copy and paste the Extensions in my current Leopard installation into the Extensions folder when I install Snow Leopard?

 

I was suggested to use the Extensions uploaded by Krishna21 in his nForce 630i guide. Should I use his Extensions or should I use the Extensions from my current Leopard installation?

[verdant]

@arya, thanks for the great guide, but I am a little confused about the installation process.

 

Before I ask my any question, let me give you my specs:

 

HP Pavilion DV6607nr

Processor: AMD Athlon 64 X2 Dual Core TK-53

Chipset: NVIDIA nForce 560 MCP67?

Graphics: NVIDIA GeForce 7150M/nForce 630M (0x053110de)

Conexant HD Audio (0x504514f1)

Wireless: Broadcom BCM4311 (0x431114e4)

Ethernet: nForce Adapter (0x054C10de)

 

I had a very difficult time installing Leopard due to my nForce 560 chipset. I had to use Leo4Allv4.1 with a special modified Extensions.mkext which finally allowed me to boot into Leopard.

 

For the Snow Leopard installation, I am confused about the Extensions. Do I have to have special kext like the AppleNForceATA.kext, to have my chipset work? Which other kext do I need? Should I just copy and paste the Extensions in my current Leopard installation into the Extensions folder when I install Snow Leopard?

 

I was suggested to use the Extensions uploaded by Krishna21 in his nForce 630i guide. Should I use his Extensions or should I use the Extensions from my current Leopard installation?

 

In /Extra/Extensions/ you will need the following standard Snow Leopard kexts

 

fakesmc.V2.5.kext

NullCPUPowerManagement.kext

OpenHaltRestart.kext

PlatformUUID.kext (apparently not required if using Chameleon 2.0 RC4)

 

plus at least the Leopard MCP67 AppleNForceATA.kext and IOATAFamily kexts but try to keep the number of extra kexts to the minimum required for SL to run.........and boot using arch=i386 in com.apple.Boot.plist with the Chameleon 2.0 RC3 or RC4 bootloader installed...........

 

Initially, add only the MCP67 AppleNForceATA.kext and boot with -v to see what happens........and then add additional kexts based upon any boot-up error messages.........

[Zythyr]

In /Extra/Extensions/ you will need the following standard Snow Leopard kexts

 

fakesmc.V2.5.kext

NullCPUPowerManagement.kext

OpenHaltRestart.kext

PlatformUUID.kext (apparently not required if using Chameleon 2.0 RC4)

 

plus at least the Leopard MCP67 AppleNForceATA.kext and IOATAFamily kexts but try to keep the number of extra kexts to the minimum required for SL to run.........and boot using arch=i386 in com.apple.Boot.plist with the Chameleon 2.0 RC3 or RC4 bootloader installed...........

 

Initially, add only the MCP67 AppleNForceATA.kext and boot with -v to see what happens........and then add additional kexts based upon any boot-up error messages.........

 

I followed arya's guide, and got kernel panic. I used a DSDT Patcher, found in Hardknox's guide, but the build failed, so I forced complied it. After finding no luck with arya's guide, I used Hardknox's guide, and still had no luck. I got the same kernel panic (see below).

 

 

So I noticed the kernel panic said something about IOFirewireFamily.kext and IOPCIFamily.kext. So what I did was, replaced those kext with the one from my leopard install so see if i get lucky. No luck, I got another kernel panic, this time saying those kext are outdated and something about dependencies with other kext. (see below)

 

 

Also, one thing I am confused about is that different guides (arya, krishna, hardknox) say to put the kext into diffrent locations. For example arya says to put the kext in Extra/Extensions while hardknox says to put them in System/Library/Extensions. Which location is the correct one?

[verdant]

I followed arya's guide, and got kernel panic. I used a DSDT Patcher, found in Hardknox's guide, but the build failed, so I forced complied it. After finding no luck with arya's guide, I used Hardknox's guide, and still had no luck. I got the same kernel panic (see below).

 

 

So I noticed the kernel panic said something about IOFirewireFamily.kext and IOPCIFamily.kext. So what I did was, replaced those kext with the one from my leopard install so see if i get lucky. No luck, I got another kernel panic, this time saying those kext are outdated and something about dependencies with other kext. (see below)

 

 

Also, one thing I am confused about is that different guides (arya, krishna, hardknox) say to put the kext into diffrent locations. For example arya says to put the kext in Extra/Extensions while hardknox says to put them in System/Library/Extensions. Which location is the correct one?

 

Your error messages are due to the fact that the kernel cannot be located........the Kernel key string entry in com.apple.Boot.plist should point to the kernel you wish to boot into:

 

<key>Kernel</key>
<string>mach_kernel</string>
<key>Kernel Flags</key>
<string>arch=i386</string>

 

so check that you have the correct kernel entry......

 

Ideally, non-Apple, non-vanilla kexts should go in /Extra/Extensions/ to keep the vanilla installaion untouched for non-problematic OS X system updating but sometimes a non-vanilla kext will only load when in /System/Library/Extensions/.......however, you can always create a symbolic link in /S/L/E to the kext(s) in /E/E/ if necessary......

[Zythyr]

Your error messages are due to the fact that the kernel cannot be located........the Kernel key string entry in com.apple.Boot.plist should point to the kernel you wish to boot into:

 

<key>Kernel</key>
<string>mach_kernel</string>
<key>Kernel Flags</key>
<string>arch=i386</string>

 

so check that you have the correct kernel entry......

 

Ideally, non-Apple, non-vanilla kexts should go in /Extra/Extensions/ to keep the vanilla installaion untouched for non-problematic OS X system updating but sometimes a non-vanilla kext will only load when in /System/Library/Extensions/.......however, you can always create a symbolic link in /S/L/E to the kext(s) in /E/E/ if necessary......

 

I have it set to mach_kernel.test7 since we are using a modified kernel. If I set it to mach_kernel, it just keeps restarting my computer ever time i try to access Snow install.

 

Do I have to change any permission settings or anything for the mach_kernel.test7 file?

[verdant]

I have it set to mach_kernel.test7 since we are using a modified kernel. If I set it to mach_kernel, it just keeps restarting my computer ever time i try to access Snow install.

 

Do I have to change any permission settings or anything for the mach_kernel.test7 file?

 

Try re-setting the kernel ownership and permissions:

 

sudo chown root:wheel /mach_kernel.test7
sudo chmod 644 /mach_kernel.test7
exit

[Zythyr]

Try re-setting the kernel ownership and permissions:

 

sudo chown root:wheel /mach_kernel.test7
sudo chmod 644 /mach_kernel.test7
exit

 

Nope didn't work. Same kernel panic message.

[verdant]

Nope didn't work. Same kernel panic message.

 

Have you tried the other AMD compatible non-vanilla kernels?

[Zythyr]

Have you tried the other AMD compatible non-vanilla kernels?

 

Tried Legacy kernel 10.6.2, 10.6.3, and 10.6.4. All give kernel panic which are similar stating something about those IOFirewireFamily.kext and IOPCIFamily.kext.

 

How do you know that the kernel is not being loaded? It keeps saying something about Firewire, couldn't that be the issue instead?

 

Which other Snow Leopard AMD kernels can i try?

[verdant]

Tried Legacy kernel 10.6.2, 10.6.3, and 10.6.4. All give kernel panic which are similar stating something about those IOFirewireFamily.kext and IOPCIFamily.kext.

 

How do you know that the kernel is not being loaded? It keeps saying something about Firewire, couldn't that be the issue instead?

 

Which other Snow Leopard AMD kernels can i try?

 

The kernel is loading when it has a major KP; hence:

Mac OS version:

Not yet set

 

Disable Firewire in BIOS to see if it is the issue; was it an issue when installing/booting Leopard? You may need to consider trying Slice's IOPCIFamily.kext

[Zythyr]

The kernel is loading when it has a major KP; hence:

 

 

Disable Firewire in BIOS to see if it is the issue; was it an issue when installing/booting Leopard? You may need to consider trying Slice's IOPCIFamily.kext

 

My BIOS doesn't have the option to disable Firewire. I tried booting with Slice's IOPCIFamily.kext, but still same issue.

 

Is there a way to modify a kext to just disregard the firewire since I can't manually disable using BIOS?

[verdant]

My BIOS doesn't have the option to disable Firewire. I tried booting with Slice's IOPCIFamily.kext, but still same issue.

 

Is there a way to modify a kext to just disregard the firewire since I can't manually disable using BIOS?

 

You could rename each of the following Firewire kexts from "kext name" to "kext name".kext.orig

 

AppleFWAudio.kext

IOFireWireFamily.kext

IOFireWireSerialBusProtocolTransport.kext

IOFireWireAVC.kext

IOFireWireIP.kext

 

and any other FireWire kexts via Terminal.......

 

cd /System/Library/Extensions/
sudo mv "kext name" to "kext name".kext.orig

[Zythyr]

You could rename each of the following Firewire kexts from "kext name" to "kext name".kext.orig

 

AppleFWAudio.kext

IOFireWireFamily.kext

IOFireWireSerialBusProtocolTransport.kext

IOFireWireAVC.kext

IOFireWireIP.kext

 

and any other FireWire kexts via Terminal.......

 

cd /System/Library/Extensions/
 sudo mv "kext name" to "kext name".kext.orig

 

Great News!!! Got successfully booted into Snow Leopard by disabling all the Firewire kext. I also had to use "idlehalt=0" bootflag or else it kept giving me Still waiting for root device message. I only added the AppleNForceATA.kext from my Leopard install and didn't use the IOATAFamily.kext.

 

Few issues/questions

 

1) So I am guessing now I have to use Marvin's AMD Utilities to patch the CPUIDs? I don't really understand how to use this tool. To what location am I suppose to patch it to?

 

2) After doing some reserach, I didn't find any solution to my GeForce 7150M graphics card. I tried using the guide, How to create nVida EFI String, and added the efi string to my com.apple.Boot.plist. But after doing so, I wasn't able to boot into my Snow Leopard install. I also tried to create the EFI string using OSX86 Tools. (Note I didn't use the tool to patch the com.appleBoot.plist since this tool is only for Leopard and not Snow). The efi string created using osx86 tools also prevented me from booting into Snow.

 

All I am trying to do is get better resolution. I added the following to my com.apple.Boot.plist file:

<key>Graphics Mode</key>

<string>1280x800x32</string>

 

But it didn't work . It didn't increase the resolution.

 

3) No battery manager, (I don't see any info about battery in my Snow) not sure what to do here. Am I suppose to install a battery manager package from a Leopard distro? (Fixed by installing VoodooBattery.kext)

 

4) I thought in Mac OS X, battery is suppose to last a lot longer than Windows. But I noticed battery is drained within 10-20 mins. Why such poor battery performance?

 

5) I don't think patching the DSDT thing worked correctly. I use the DSDT Patcher from hardknox's guide, but it couldn't complie, so I forced complied it. I also trying compling it using a diffrent tool, but it doesn't complie. Now everytime i go back to Windows, my clock is reset

 

6) Just to make sure, all I need to do is the regular software update provided by apple right? I don't need any special hacked version to update to 10.6.4?

[verdant]

Great News!!! Got successfully booted into Snow Leopard by disabling all the Firewire kext. I also had to use "idlehalt=0" bootflag or else it kept giving me Still waiting for root device message. I only added the AppleNForceATA.kext from my Leopard install and didn't use the IOATAFamily.kext.

 

Few issues/questions

 

1) So I am guessing now I have to use Marvin's AMD Utilities to patch the CPUIDs? I don't really understand how to use this tool. To what location am I suppose to patch it to?

 

See http://www.insanelymac.com/forum/index.php?showtopic=67917

 

2) After doing some reserach, I didn't find any solution to my GeForce 7150M graphics card. I tried using the guide, How to create nVida EFI String, and added the efi string to my com.apple.Boot.plist. But after doing so, I wasn't able to boot into my Snow Leopard install. I also tried to create the EFI string using OSX86 Tools. (Note I didn't use the tool to patch the com.appleBoot.plist since this tool is only for Leopard and not Snow). The efi string created using osx86 tools also prevented me from booting into Snow.

 

All I am trying to do is get better resolution. I added the following to my com.apple.Boot.plist file:

<key>Graphics Mode</key>

<string>1280x800x32</string>

 

But it didn't work . It didn't increase the resolution.

 

All GeForce models with X050, X100 and X150 and X200 are integrated to the chipset and are not supported by OS X for Core Image and Quartz Extreme........also, I am not aware of a solution to the 7150M resolution changing issue as of now......

 

3) No battery manager, (I don't see any info about battery in my Snow) not sure what to do here. Am I suppose to install a battery manager package from a Leopard distro? (Fixed by installing VoodooBattery.kext)

 

4) I thought in Mac OS X, battery is suppose to last a lot longer than Windows. But I noticed battery is drained within 10-20 mins. Why such poor battery performance?

 

Poor power management......try VoodooPower 1.2.3

http://www.insanelymac.com/forum/index.php?showtopic=143898

 

5) I don't think patching the DSDT thing worked correctly. I use the DSDT Patcher from hardknox's guide, but it couldn't complie, so I forced complied it. I also trying compling it using a diffrent tool, but it doesn't complie. Now everytime i go back to Windows, my clock is reset

See my blog entry on time difference resolution options........zip up your DSDT.aml and post it......I will take a look........

 

6) Just to make sure, all I need to do is the regular software update provided by apple right? I don't need any special hacked version to update to 10.6.4?

Download and run the 10.6.4 Combo Update in Safe Mode.......

[Zythyr]

I used DSDTSE App to extract my dsdt.aml. I was unable to complie it, so I have uploaded my dsdt.dsl file. Also, I have uploaded the logs from the DSDT Patcher from Hardknox's guide, which I used in order to patch my Snow install.

 

As for Marvin's AMD Utilities, I selected "Create Patcher Package" but I keep getting kernel panic halfway through the process. I am going to try using Marvin's AMD Util, from my Leopard install to see if I get kernel panic or not.

Ignore my post about trouble with Marvin's AMD Util. I just went back to Snow, and patched the binaries without doing the simulation mode. What changes am I suppose to notice now once my cpuids are patched?

 

Also, VoodooPower 1.2.3, is for Leopard only. But I am guessing Snow Leopard supported version is coming out soon. Meanwhile I'll give 1.2.3 a try to see if it works.

 

 

--------===== Edit ===== --------

 

I downloaded 10.6.4 combo update and booted into safe mode. Near the end of the installation of update (1 min remaining), I got a kernel panic. The same kernel panic I got earlier regarding the kext related to firewire. I booted into Leopard and noticed that the update reinstalled those firewire related kext. So what I did was, renamed them to Name.kext.bak and try to boot back into Snow. Despite disabling those firewire kext, I am not getting the same kernel panic related to those firewire kext.

 

Am I not able to boot into Snow, despite disabling the firewire kext, because the update was left unfinished and now when boot into Snow, it automatically loads those kext from another temp location created by the combo update?

 

Does update always install a fresh copy of kext or did it install it because those firewire related kext weren't present?

 

 

dsdt_files.zip