Skylake Thunderbolt 3 for Music Production

zipb · Jul 12, 2016

joevt said:
Zipb, post an ioreg file

There you go:

wildwillow · Jul 12, 2016

zipb said:
There you go:

Any chance you can make another copy with the version attached to Post#1 of the link and attach it. Using the same version of IORegistry Explorer makes it universal for all. If its not too much trouble. Thanks! [Guide] How to Make a Copy of IOReg | tonymacx86.com

joevt · Jul 12, 2016

wildwillow said:
There is an IOReg for thunderbolt 3 here Post#30 The system connection is via USB Type-C port to an Apple thunderbolt display. Motherboard-Z170-UD5-TH.

Yup, that looks as expected.

zipb said:
There you go:

This does not look as expected. Are you using an SSDT or DSDT that might be removing devices? Compare to a screen shot of Windows Device Manager (view by connection). There should be another XHC somewhere in there for the USB 3.1 Gen 2 functionality of the Thunderbolt 3 controllers. Can you plug a device into the USB-C ports?

zipb · Jul 12, 2016

wildwillow said:
Any chance you can make another copy with the version attached to Post#1 of the link and attach it. Using the same version of IORegistry Explorer makes it universal for all. If its not too much trouble. Thanks! [Guide] How to Make a Copy of IOReg | tonymacx86.com

Sure. Here it is:

zipb · Jul 12, 2016

This does not look as expected. Are you using an SSDT or DSDT that might be removing devices? Compare to a screen shot of Windows Device Manager (view by connection). There should be another XHC somewhere in there for the USB 3.1 Gen 2 functionality of the Thunderbolt 3 controllers. Can you plug a device into the USB-C ports?[/QUOTE]

I didn't see anything relating to USB3.1 or TB in Windows 10 in the device manager after I installed the driver and ran the updater. That made me suspicious in the first place. Not so easy to check again, I removed the Windows SSD after a disastrous effort to get multibooting going...

I use this SSDT:
/Volumes/EFI/EFI/CLOVER/ACPI/patched/SSDT-i7-6700K.aml

This is supposed to improve speed stepping and power management for overclocked systems like mine... If I remember well.

Thanks for the help, BTW. Appreciated!

joevt · Jul 13, 2016

zipb said:
I didn't see anything relating to USB3.1 or TB in Windows 10 in the device manager after I installed the driver and ran the updater. That made me suspicious in the first place. Not so easy to check again, I removed the Windows SSD after a disastrous effort to get multibooting going...

I use this SSDT:
/Volumes/EFI/EFI/CLOVER/ACPI/patched/SSDT-i7-6700K.aml

This is supposed to improve speed stepping and power management for overclocked systems like mine... If I remember well.

Thanks for the help, BTW. Appreciated!

The SSDT created by https://github.com/Piker-Alpha/ssdtPRGen.sh while SMBIOS is set to iMac17,1 is the only SSDT that I use. And anyway, that shouldn't affect Windows.

I think you need to have Windows before we can go any further. What issue did you have with multi booting? If your computer boots without the SSD, then it should boot with the SSD. Do you have any M.2 devices? Which slots, and what kind? Make sure the SSD is not connected to a SATA port that is affected by the M.2 devices. Use Mac OS X to mount each of the EFI partitions and note the locations of the boot files. Use commands like the following to show the EFI boot files:

Code:

diskutil list
/dev/disk0 (internal):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                         512.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                  Apple_HFS Empty1                  40.5 GB    disk0s2
   3:                  Apple_HFS ElCapitan               170.0 GB   disk0s3
   4:                 Apple_Boot Recovery HD             650.0 MB   disk0s4
   5:                  Apple_HFS MacGames                300.5 GB   disk0s5
/dev/disk1 (internal):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                         512.1 GB   disk1
   1:                        EFI EFI                     103.8 MB   disk1s1
   2:           Windows Recovery                         471.9 MB   disk1s2
   3:         Microsoft Reserved                         16.8 MB    disk1s3
   4:       Microsoft Basic Data Windows10               255.5 GB   disk1s4
   5:       Microsoft Basic Data Games                   256.1 GB   disk1s5
/dev/disk2 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *512.1 GB   disk2
   1:                        EFI EFI                     209.7 MB   disk2s1
   2:                  Apple_HFS SSD850                  511.8 GB   disk2s2
/dev/disk3 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *5.0 TB     disk3
   1:                        EFI EFI                     209.7 MB   disk3s1
   2:                  Apple_HFS ElCappy                 107.4 GB   disk3s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk3s3
   4:           Linux Filesystem                         100.0 GB   disk3s4
   5:                 Linux Swap                         65.5 GB    disk3s5

mount
/dev/disk0s3 on / (hfs, local, journaled)
devfs on /dev (devfs, local, nobrowse)
/dev/disk0s2 on /Volumes/Empty1 (hfs, local, journaled)
/dev/disk0s5 on /Volumes/MacGames (hfs, local, journaled)
/dev/disk3s2 on /Volumes/ElCappy (hfs, local, journaled)
/dev/disk2s2 on /Volumes/SSD850 (ntfs, local, read-only, noowners)
/dev/disk1s4 on /Volumes/Windows10 (ntfs, local, read-only, noowners)
/dev/disk1s5 on /Volumes/Games (ntfs, local, read-only, noowners)
map -hosts on /net (autofs, nosuid, automounted, nobrowse)
map auto_home on /home (autofs, automounted, nobrowse)
/dev/disk0s1 on /Volumes/EFI (msdos, asynchronous, local, noowners)

mkdir /Volumes/EFIdisk0
sudo mount_msdos /dev/disk0s1 /Volumes/EFIdisk0
find /Volumes/EFIdisk0 -name *.efi -exec md5 {} \;
MD5 (/Volumes/EFIdisk0/EFI/BOOT/BOOTX64.efi) = 1a59056b498b2774e0a7fc71374a8ba5
MD5 (/Volumes/EFIdisk0/EFI/BOOT/BOOTIA32.efi) = e9e70af4f254a91d512bffa1f65925e9
MD5 (/Volumes/EFIdisk0/EFI/CLOVER/CLOVERIA32.efi) = e9e70af4f254a91d512bffa1f65925e9
MD5 (/Volumes/EFIdisk0/EFI/CLOVER/CLOVERX64.efi) = 1a59056b498b2774e0a7fc71374a8ba5
MD5 (/Volumes/EFIdisk0/EFI/CLOVER/drivers32UEFI/FSInject-32.efi) = 3ad5b69ebb9597da420a2b2bf4a3326b
MD5 (/Volumes/EFIdisk0/EFI/CLOVER/drivers32UEFI/OsxFatBinaryDrv-32.efi) = 464a4414e8cc7fd6ed374acd81c4722e
MD5 (/Volumes/EFIdisk0/EFI/CLOVER/drivers32UEFI/VBoxHfs-32.efi) = 2ce1b2f9afecb07973b69c9ba941f470
MD5 (/Volumes/EFIdisk0/EFI/CLOVER/drivers64UEFI/FSInject-64.efi) = 450471c9e668a909c73a904b0c2ba37b
MD5 (/Volumes/EFIdisk0/EFI/CLOVER/drivers64UEFI/OsxAptioFix2Drv-64.efi) = d95e92873a711bffc82dd58bc9f79d1b
MD5 (/Volumes/EFIdisk0/EFI/CLOVER/drivers64UEFI/OsxFatBinaryDrv-64.efi) = 1eb9b8581e8ceaa8af2454eeddf37daf
MD5 (/Volumes/EFIdisk0/EFI/CLOVER/drivers64UEFI/VBoxHfs-64.efi) = 8627f6e9f77578454eedbf0298cd121d
MD5 (/Volumes/EFIdisk0/EFI/CLOVER/drivers64UEFI/EmuVariableUefi-64.efi) = 589e932bd95c306bde00abed43a5e95b
MD5 (/Volumes/EFIdisk0/EFI/CLOVER/drivers64UEFI/IsaSerialDxe-64.efi) = 0735d95130379fb508c7b139f55a739f
MD5 (/Volumes/EFIdisk0/EFI/CLOVER/drivers64UEFI/IsaBusDxe-64.efi) = c374d7a1ba86f74c2fd6c0e010550a98
MD5 (/Volumes/EFIdisk0/EFI/CLOVER/tools/bdmesg-32.efi) = 7e6b61f2e15d1e4bb9e7ff24ab7e1e2f
MD5 (/Volumes/EFIdisk0/EFI/CLOVER/tools/bdmesg.efi) = da17e157e2a8362aaf2163d0bc34160b
MD5 (/Volumes/EFIdisk0/EFI/CLOVER/tools/Shell32.efi) = 7fa0023638de5dcb2dbf5d2fb684073a
MD5 (/Volumes/EFIdisk0/EFI/CLOVER/tools/Shell64.efi) = d327f564b264976ca4d7765d8638320e
MD5 (/Volumes/EFIdisk0/EFI/CLOVER/tools/Shell64U.efi) = fed894fc7d9501ba5b96877101ec8eda

mkdir /Volumes/WindowsRecovery
sudo mount -t ntfs /dev/disk1s2 /Volumes/WindowsRecovery
find /Volumes/WindowsRecovery -name *.efi -exec md5 {} \;
find /Volumes/WindowsRecovery -type f
/Volumes/WindowsRecovery/Recovery/WindowsRE/boot.sdi
/Volumes/WindowsRecovery/Recovery/WindowsRE/ReAgent.xml
/Volumes/WindowsRecovery/Recovery/WindowsRE/Winre.wim
/Volumes/WindowsRecovery/System Volume Information/tracking.log

mkdir /Volumes/EFIdisk1
sudo mount_msdos /dev/disk1s1 /Volumes/EFIdisk1
find /Volumes/EFIdisk1 -name *.efi -exec md5 {} \;
MD5 (/Volumes/EFIdisk1/EFI/Microsoft/Boot/bootmgr.efi) = e5ce0ea9e43b188dadc15eec1e4cdcb6
MD5 (/Volumes/EFIdisk1/EFI/Microsoft/Boot/memtest.efi) = 69acf999e6cfdc6ce5c416f020341b07
MD5 (/Volumes/EFIdisk1/EFI/Microsoft/Boot/bootmgfw.efi) = 4c0946eb0d0bdb42144a42b77ec4b6cd
MD5 (/Volumes/EFIdisk1/EFI/Boot/bootx64.efi) = 4c0946eb0d0bdb42144a42b77ec4b6cd
MD5 (/Volumes/EFIdisk1/EFI/ubuntu/fwupx64.efi) = d73bbea8b6c047d2a706472f87d3ccdb
MD5 (/Volumes/EFIdisk1/EFI/ubuntu/grubx64.efi) = 6d0ef432d1373bab954f6ca3d34f070d
MD5 (/Volumes/EFIdisk1/EFI/ubuntu/shimx64.efi) = ded965934506efb38a6dcb9ac5b2b79e
MD5 (/Volumes/EFIdisk1/EFI/ubuntu/MokManager.efi) = ba8a7979ac57f1c0c307ef94d1020eb8

mkdir /Volumes/EFIdisk2
sudo mount_msdos /dev/disk2s1 /Volumes/EFIdisk2
find /Volumes/EFIdisk2 -name *.efi -exec md5 {} \;

mkdir /Volumes/EFIdisk3
sudo mount_msdos /dev/disk3s1 /Volumes/EFIdisk3
find /Volumes/EFIdisk3 -name *.efi -exec md5 {} \;
MD5 (/Volumes/EFIdisk3/EFI/APPLE/UPDATERS/SMC/SmcFlasher.efi) = 415ec2221990eb2c8c32b1ce1c9872bc
MD5 (/Volumes/EFIdisk3/EFI/BOOT/BOOTIA32.efi) = fa47427f38168e64c8ed886215bfa820
MD5 (/Volumes/EFIdisk3/EFI/BOOT/BOOTX64.efi) = 6debe730cc6ab2222d5663ff5edad7b4
MD5 (/Volumes/EFIdisk3/EFI/CLOVER/CLOVERIA32.efi) = fa47427f38168e64c8ed886215bfa820
MD5 (/Volumes/EFIdisk3/EFI/CLOVER/CLOVERX64.efi) = 6debe730cc6ab2222d5663ff5edad7b4
MD5 (/Volumes/EFIdisk3/EFI/CLOVER/drivers32UEFI/FSInject-32.efi) = adac5c9a2ba6041904f4079303400614
MD5 (/Volumes/EFIdisk3/EFI/CLOVER/drivers32UEFI/OsxFatBinaryDrv-32.efi) = 11d2c0ce2c5f724bed68b28a0473b2a7
MD5 (/Volumes/EFIdisk3/EFI/CLOVER/drivers32UEFI/VBoxHfs-32.efi) = 88bc72d3a34a52f47952b7d3ac63fed5
MD5 (/Volumes/EFIdisk3/EFI/CLOVER/drivers64UEFI/FSInject-64.efi) = 402245a45b03095e456ffbb4ea554934
MD5 (/Volumes/EFIdisk3/EFI/CLOVER/drivers64UEFI/OsxAptioFix2Drv-64.efi) = df75b129d25270a534e2ad0d75b58dfb
MD5 (/Volumes/EFIdisk3/EFI/CLOVER/drivers64UEFI/OsxFatBinaryDrv-64.efi) = 08c92eabd109e4a170ec2a0246b1bc19
MD5 (/Volumes/EFIdisk3/EFI/CLOVER/drivers64UEFI/VBoxHfs-64.efi) = 289205c58d9bcd7ee5c16699ad8daa04
MD5 (/Volumes/EFIdisk3/EFI/CLOVER/tools/bdmesg-32.efi) = b245c97dbdb379759230da23a7d38bb3
MD5 (/Volumes/EFIdisk3/EFI/CLOVER/tools/bdmesg.efi) = ff307433a82446403200ece77e783f2e
MD5 (/Volumes/EFIdisk3/EFI/CLOVER/tools/Shell32.efi) = 7fa0023638de5dcb2dbf5d2fb684073a
MD5 (/Volumes/EFIdisk3/EFI/CLOVER/tools/Shell64.efi) = d327f564b264976ca4d7765d8638320e
MD5 (/Volumes/EFIdisk3/EFI/CLOVER/tools/Shell64U.efi) = fed894fc7d9501ba5b96877101ec8eda

Notice that there's the default booter in the EFI partition at /EFI/BOOT/BOOTX64.efi which usually matches one of the OS specific booters such as /EFI/CLOVER/CLOVERX64.efi or /EFI/Microsoft/Boot/bootmgfw.efi

Clover should show you an option for /EFI/Microsoft/Boot/bootmgfw.efi

If your computer boots into Windows by skipping Clover, then you can use EasyUEFI to add a boot option for /EFI/CLOVER/CLOVERX64.efi, then move it to the top to make it the default. Make sure there's a boot option for Windows /EFI/Microsoft/Boot/bootmgfw.efi.

I've installed ubuntu 16.04 as well. Iin Mac OS X, make space for ubuntu partitions (either free space, or partition that you can remove), then in the ubuntu installer, add a partition for swap and a partition for the / path. The boot loader will be /EFI/ubuntu/grubx64.efi. I think you can do it without swap. It should be smart enough to put swap files in / somewhere.

I use iPartition in Mac OS X since DiskUtility in El Capitan is kind of crappy.

wimmy7986 · Jul 13, 2016

zipb said:
@wimmy7986: are your UAD devices working or not?

Nope unfortunately not.

joevt said:
That means you have two Thunderbolt audio devices? They appear to use the same driver com_uaudio_driver_UAD2Pcie2.

Does the Thunderbolt software in Windows show the devices attached? Did it ask you to give permission to connect the devices? Do these Thunderbolt audio devices have Windows drivers?

Remind me again what problems you're having? You have it working already on one Hackintosh (the source of the IORegistry screenshot) which had a Thunderbolt 1 port, but not a new Hackintosh with Thunderbolt 3? What does the IORegistry look like on the Hackintosh with the Thunderbolt 3 ports?

I do have two UAD Thunderbolt devices chained together. They work perfect on my Older Hackintosh with TH 1 and 2. They are NOT working on the new Hackintosh with TH3 + StarTech adapter. Unfortunately, these UAD devices are not supported in Windows either. I attached a screen shot of the device manager in Windows when the two are connected, and thats where the Billboard device showed up. Ive also attached an IORegistry file showing what my TH3 machine looks like when the UAD devices are connected.

Also, thanks for providing any info you can for this. It may be wishful thinking for me to ever get this working (until Apple comes out with TH3 support of course).

zipb · Jul 13, 2016

I temporarily removed my OSX software raid(2 disks as JBOD) and extra data ssd, and attached my Win10 SSD. I see this

iMac-van-Zip:~ zipsl$ diskutil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *512.1 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_HFS Werk512 511.8 GB disk0s2
/dev/disk1 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.1 GB disk1
1: EFI EFI 209.7 MB disk1s1
2: Apple_HFS El Cap 850 499.8 GB disk1s2
/dev/disk2 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *60.0 GB disk2
1: Windows_NTFS Door systeem gereser... 524.3 MB disk2s1
2: Windows_NTFS 59.5 GB disk2s2
i

Bear with me, I have very little knowledge about Windows 10. I don't understand why my GUID disk suddenly has a FDISK partition scheme, and I don't see any EFI partition on the Win disk.

I'll check if i can boot into Windows, I see 2 Win installs in Clover now. Don't know if I can boot from one of these.

Best,

Zip

zipb · Jul 13, 2016

I'll check if i can boot into Windows, I see 2 Win installs in Clover now. Don't know if I can boot from one of these.

Best,

Zip[/QUOTE]

No, I can't via Clover but I can get in by skipping clover and booting straight to Windows via the BIOS boot disk option. No mention off TB or USB3.1 in the Device Manager at all, anywhere.
I removed/reinstalled the driver and the firmware updater for good measure, without results.
I can see my FW card etc., but nothing TB related. I just checked the back of my rig, the 2 ports are really there(Ha!)
Am I supposed to install other Gigabyte/driver software too? Most of it looks like bloatware to me...

joevt · Jul 14, 2016

wimmy7986 said:
Nope unfortunately not.

I do have two UAD Thunderbolt devices chained together. They work perfect on my Older Hackintosh with TH 1 and 2. They are NOT working on the new Hackintosh with TH3 + StarTech adapter. Unfortunately, these UAD devices are not supported in Windows either. I attached a screen shot of the device manager in Windows when the two are connected, and thats where the Billboard device showed up. Ive also attached an IORegistry file showing what my TH3 machine looks like when the UAD devices are connected.

Also, thanks for providing any info you can for this. It may be wishful thinking for me to ever get this working (until Apple comes out with TH3 support of course).

Even if the devices are not supported in Windows, the PCIe devices should appear in the Device Manager without drivers. For Mac OS X, you have to have all the Thunderbolt stuff plugged in before you start the computer. For Windows, you can do the same, or hot plug the Thunderbolt stuff.

zipb said:
I temporarily removed my OSX software raid(2 disks as JBOD) and extra data ssd, and attached my Win10 SSD. I see this

Code:

iMac-van-Zip:~ zipsl$ diskutil list /dev/disk0 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *512.1 GB disk0 1: EFI EFI 209.7 MB disk0s1 2: Apple_HFS Werk512 511.8 GB disk0s2 /dev/disk1 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *500.1 GB disk1 1: EFI EFI 209.7 MB disk1s1 2: Apple_HFS El Cap 850 499.8 GB disk1s2 /dev/disk2 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: FDisk_partition_scheme *60.0 GB disk2 1: Windows_NTFS Door systeem gereser... 524.3 MB disk2s1 2: Windows_NTFS 59.5 GB disk2s2

Bear with me, I have very little knowledge about Windows 10. I don't understand why my GUID disk suddenly has a FDISK partition scheme, and I don't see any EFI partition on the Win disk.

I'll check if i can boot into Windows, I see 2 Win installs in Clover now. Don't know if I can boot from one of these.

When you paste output from the terminal in a post, don't forget to put it in between [ code ] and [ /code ] tags (no spaces) so that they are formatted correctly like I did in the above quote.

For fdisk type partition scheme (MBR) you can use this command to show the active partition and partition types. You can also use it on the GPT disks to see the protective EFI partition (which is a fake partition in the MBR (partition type EE) of the GPT disk which protects the disk starting from block 1 to the end of the disk) from old OS's that don't know what a GPT is.

Code:

sudo fdisk /dev/disk2

This command will show the bytes in the MBR. Usually these are mostly 00 for GPT disks. For MBR, they may have old BIOS boot code.

Code:

sudo dd if=/dev/disk2 count=1 | xxd

If the disk is on a Mac, and the Mac doesn't have UEFI, just older EFI, then Windows might boot using BootCamp, even on a GPT disk, where the MBR is a hybrid MBR which means it contains partitions that match some partitions of the GPT, and has BIOS boot code to boot the Windows partition.
This command shows only the GPT (your disk2 doesn't have a GPT, so try it on disk1):

Code:

sudo gpt -r show -l /dev/disk1

zipb said:
I'll check if i can boot into Windows, I see 2 Win installs in Clover now. Don't know if I can boot from one of these.

You can select each icon in Clover and press Space bar to get more information about the partition and what Clover is going to boot. You can press F10 to take a screenshot of the results which will be stored in the EFI partition. Press F1 for more help in Clover.

Clover should allow booting the MBR (BIOS compatibility mode) if that's how your Windows was installed. But you may want to convert your Windows 10 disk to GPT, and add the Windows EFI boot files. iPartition can convert a disk from MBR to GPT. There's also the gdisk command http://www.rodsbooks.com/gdisk/mbr2gpt.html which you can download and install in Mac OS X.

You may need a new Windows 10 installer. Download and run the Windows Media Creation Tool. It will download the Windows 10 and make a USB Flash disk Windows 10 installer. I think it will have commands to add missing Windows boot files. You could reinstall windows using the USB flash drive. Reformat the disk so it isn't MBR anymore. Maybe use Mac OS X to do that, to guarantee that the GPT disk will have a useful EFI partition in the right spot.

zipb said:
No, I can't via Clover but I can get in by skipping clover and booting straight to Windows via the BIOS boot disk option. No mention of TB or USB3.1 in the Device Manager at all, anywhere.
I removed/reinstalled the driver and the firmware updater for good measure, without results.
I can see my FW card etc., but nothing TB related. I just checked the back of my rig, the 2 ports are really there(Ha!)
Am I supposed to install other Gigabyte/driver software too? Most of it looks like bloatware to me...

The only think you need to install in Windows for Thunderbolt is the Thunderbolt software, and then after that is installed, you need to install the Thunderbolt firmware updater, and actually run the updater. After the firmware is updated, it will ask you to turn off the PC and unplug it for 30 seconds or something like that.

You might want a program like DriverGenius or DriverSupport to update all your Windows drivers. They cost money, but knowing your drivers are up to date is worth it.
http://www.driver-soft.com
http://www.driversupport.com

Here's some screen shots of my BIOS settings.

Here's some screenshots of the Thunderbolt settings in Windows:

Thunderbolt details and Attached devices (OWC Thunderbolt 2 dock):

Device Manager Thunderbolt 3 with OWC Thunderbolt 2 dock attached and with no devices attached:

Note: If the Startech Thunderbolt 3 to Thunderbolt 2 adapter is attached with no Thunderbolt 2 devices, then it does not appear in the Device Manager. This makes sense, if you consider that PCIe 2.0 devices can be inserted into PCIe 3.0 slots without a bridge chip in between them. I guess the Startech adapter just changes the shape of the port (probably more to it than that but that's the overall effect).

Search

Skylake Thunderbolt 3 for Music Production

zipb

Attachments

wildwillow

joevt

zipb

Attachments

zipb

joevt

wimmy7986

Attachments

zipb

zipb

joevt

Forum

Guides

Downloads