Hi guys

I'm trying to install Elementary OS on my Asus Laptop,(Specs Below) I have a 25 GB SSD and a 1TB HDD, I want to dual boot elementary and Windows 10. I want to ignore the SSD while doing this. When I launch the installer it doesn't give me the option to dual boot and when I open the custom version it doesn't recognize my partitions so I can't even do it that way. I was hoping you guys could offer some kind of a fix for this issue.

Thanks

Specs

Operating System
Windows 10 Pro 64-bit
CPU
Intel Core i7 4500U @ 1.80GHz 46 °C
Haswell ULT 22nm Technology
RAM
6.00GB Dual-Channel DDR3 @ 798MHz (11-11-11-28)
Motherboard
ASUSTeK COMPUTER INC. S551LN (SOCKET 0)
Graphics
Generic PnP Monitor (1366x768@60Hz)
Intel HD Graphics Family (ASUStek Computer Inc)
2047MB NVIDIA GeForce 840M (ASUStek Computer Inc) 45 °C
Storage
931GB Seagate ST1000LM024 HN-M101MBB (SATA) 30 °C
22GB SanDisk SSD U100 24GB (SSD)
Optical Drives
HL-DT-ST DVDRAM GUA0N
Audio
Realtek High Definition Audio

Motherboard
Manufacturer ASUSTeK COMPUTER INC.
Model S551LN (SOCKET 0)
Version 1.0
Chipset Vendor Intel
Chipset Model Haswell-ULT
Chipset Revision 09
Southbridge Vendor Intel
Southbridge Model ID9C43
Southbridge Revision 04
BIOS
Brand American Megatrends Inc.
Version S551LN.208
Date 3/28/2014
PCI Data

Hard drives
ST1000LM024 HN-M101MBB
Manufacturer Seagate
Heads 16
Cylinders 121,601
Tracks 31,008,255
Sectors 1,953,520,065
SATA type SATA-III 6.0Gb/s
Device type Fixed
ATA Standard ATA8-ACS
Serial Number S32XJ9AF345840
Firmware Version Number 2BA30001
LBA Size 48-bit LBA
Power On Count 1063 times
Power On Time 257.4 days
Speed 5400 RPM
Features S.M.A.R.T., APM, AAM, NCQ
Max. Transfer Mode SATA III 6.0Gb/s
Used Transfer Mode SATA III 6.0Gb/s
Interface SATA
Capacity 931 GB
Real size 1,000,204,886,016 bytes
RAID Type None
S.M.A.R.T
Status Good
Temperature 30 °C
Temperature Range OK (less than 50 °C)
S.M.A.R.T attributes
Partition 0
Partition ID Disk #0, Partition #0
File System NTFS
Volume Serial Number 34853FB1
Size 499 MB
Used Space 34.2 MB (6%)
Free Space 465 MB (94%)
Partition 1
Partition ID Disk #0, Partition #1
Disk Letter D:
File System NTFS
Volume Serial Number 2C260941
Size 931 GB
Used Space 129 GB (13%)
Free Space 801 GB (87%)

SanDisk SSD U100 24GB
Manufacturer SanDisk
Heads 16
Cylinders 2,919
Tracks 744,345
Sectors 46,893,735
SATA type SATA-III 6.0Gb/s
Device type Fixed
ATA Standard ACS2
Serial Number 131705403646
Firmware Version Number 10.56.02
LBA Size 48-bit LBA
Power On Count 1064 times
Power On Time 126.9 days
Speed Not used (SSD Drive)
Features S.M.A.R.T., APM, NCQ, TRIM, SSD
Max. Transfer Mode SATA III 6.0Gb/s
Used Transfer Mode SATA III 6.0Gb/s
Interface SATA
Capacity 22.4 GB
Real size 24,015,495,168 bytes
RAID Type None
S.M.A.R.T
Partition 0

You posted a lot of hardware information but nothing about the partitions on the disks. Elementary is an Ubuntu derivative so it probably uses the same installer. Are you windows partitions taking up all the drive space or do you have unallocated space? You should have a manual install option and with the Ubuntus it is usually referred to as "Something Else". That is the only option which will allow you to select drives/partitions. If you can boot the Elementary CD/flash drive, open a terminal and entery: sudo fdisk -l and/or sudo parted -l and post the output here. That's a Lower Case letter L in both commands.

If you have windows 10 installed using UEFI, you will need to do the same with Elementary.

Did you READ the install guide ?

Did you RESIZE the windows partition?
( it is BEST to have a windows install DVD in case something GOES WRONG!!! - and it might !)

and set aside a empty area on the drive to install Elementary ?

and it will NOT

it will set up a dual boot IF YOU set up a dual boot

so
READ THE INSTALL GUIDE

When testing the Win10 preview I had similar problems. If the (hard) disk was partitioned as gpt, the Win10 (preview) installer would simply reconfigure it as MBR and not erase the gpt header. Confused the hell out of all the Linux tools - easy to fix by zero-ing the gpt header.
Happened regardless of UEFI in native or legacy mode.

Don't know if it holds true for the released version of Win10 as I haven't "upgraded" any of my systems yet.

If you do the "sudo parted -l" mentioned above, we might get some idea.