I get warned about being not compatible in regards to my internal SSD everytime I start my prime 4+. But after about a minute the drive is seen and I can access my tracks as normal.
I can also update from Engine DJ software to the SSD when connected to the prime 4+ via USB, when in computer mode.
My PC sees it perfectly, engine DJ software writes to it, and as I said it eventually sees it in Prime 4+ but only after clicking through the screen warning me it is incompatible. So strange.
Hi bro, I have the same SSD in my prime 4, I had this a few times before, I lost those screws that hold the SSD in place so my card was slightly loose, I placed some sticky back tape to the SSD and made sure the connection was in place again. It worked for me. Never had it again. Hope it’s something this simple as a connection for you.
is the drive in FAT32 or exFAT? I noticed that some time during the Engine 3.x revs that my decks started to not like exFAT. The problem that you will then run into that MS has limited FAT32 partitions to a max of 32Gb forever. They recently changed this though, but not sure with what patch update. The GUI tool will not do it and you will need to do it from the command line. I think the command is ( format G: /q /fs:fat32 ) Change the G: with whatever your drive letter is. There was 3rd party tools that can do the formatting for you as well in windows. I would try that and see how it goes.
Hi everyone. Firstly thanks for the replies…I appreciate it.
OK so I tried a second SSD, brand new, formatted exfat MBR. Same issue. After I get the warning that the SSD is incompatible, about 60 seconds later all my tracks show up, all cues are present, and I can use the deck for hours no issue. So this is something quirky with 4.0.0.
The new SSD I used is an Ediloca SSD SATA III 6Gbps 3D NAND.
Basically exactly the same specs as my other Samsung SSD.
If that screenshot works then you can see it is only a 2TB drive. My PC is latest fully up to date W11 Pro.
In reply to: Thatswhatyourmumsaid I have my SSD screwed in so this is not a loose connection issue.
I Talked to the store I purchased from, the manager Ian wonders if this is a OS issue where the OS does not wait long enough for the SSD to ‘handshake’? This is an interesting thought. It is possible that there needs to be a little bit longer wait by the OS before it decides to announce the drive is ‘INCOMPATIBLE’ Which clearly is not the case here.