MattRocks wrote on 2025-11-26, 22:45:Crysis is after my time, but my understanding is that Crysis is a bit of a resource pig - and Windows XP doesn't know what an SS […]
Show full quote
luckybob wrote on 2025-11-26, 18:52: if you look at this video: https://www.youtube.com/watch?v=3HWBmbb0YNY (specifically @ the 13min mark) Brand new drive, brand new adapter, didn't work right.
Crysis is after my time, but my understanding is that Crysis is a bit of a resource pig - and Windows XP doesn't know what an SSD is.
So, like a fish on dry land, that Kingston SSD performed as badly as I think it should have. You see neither Windows XP nor the IDE controller support SSD TRIM commands. My view is that TRIM is critical to new consumer SSDs because the TRIM command tells the SSD which blocks have been deleted. Without the TRIM command, the SSD is preserving blocks the OS thinks have been deleted and the SSD thinks have not been deleted. That setup is going to create one big mess, and very quickly if the OS is using virtual memory for a resource pig like Crysis. My view is that Crysis should hit a 0.0 FPS brick wall when the OS thinks there is new space for virtual memory and the SSD thinks there is no space left.
What Jayz could have done with his Crysis rig is use the SSD for read-only tasks (there are a lot disc assets in games) with OS temp files and OS swap file on a HDD. Or, stick to games that fit in RAM and need no swap file.
But to your other point, you implied that new Kingston SSDs power Crysis on PCI adapters with WinXP? I'd be interested in seeing that because I don't think they should.
I have been using Windows 98SE and Windows XP test benches with solid state drives for several years and they always run fine. I have a 16GB mini-SATA SSD (from a Chromebook) running through multiple adapters hooked up to a 440BX board in my 98SE test rig and it has something like 20 Windows folders on it (I boot to DOS and rename the Windows folder I want for testing a certain piece of hardware... saves a huge amount of time dealing with drivers), and has been operating nearly full for 4-5 years with no noticeable performance problems.
My XP test system is an nForce 2 with SATA using an old 64GB Crucial C300 from ~2010, and it has tons of games and demos on it, is constantly being loaded up with various GPU driver packages and having things reinstalled... it works flawlessly, and the drive has been in the system for at least 5 years.
For retro systems, TRIM is nowhere near the big deal that people make it out to be and it probably isn't going to be an issue unless you are daily driving the system for an extended period of time and expecting it to handle thousands of writes\deletes from cache\temp files, application reinstalls, etc. without any performance impact. To be fair, though... I have never seen SSD performance degrade noticeably over time on a retro system or a modern one.
These SSDs I've been using are relatively old, but newer ones should be even better at handling a lack of TRIM because they have more sophisticated internal garbage collection... at least that's what I've read online. I'm not going to claim to be an expert on the subject. Personally, I've never had an issue with any SSD.
Regarding the video... I'm not sure exactly what we're supposed to be looking for there. The system was acting weird with the 1TB SATA drive on the adapter, but he was able to format it through Disk Management... and honestly, he could have deleted and remade the partition and left that part out. He then successfully installed an 18GB game to it, seemingly without issues. The game was running HORRIBLE because he was running with a below spec CPU from 2001, with minimum spec RAM with the OS installed on a positively ANCIENT 20GB IDE hard drive. Due to the lack of RAM the game would have been constantly swapping to virtual memory using an IDE hard drive from probably ~2001... it doesn't matter that the game was on the SSD.
If he would have just installed the OS and everything else to the SSD, assuming the adapter wasn't garbage, the system likely would have worked far better. The game would still run like trash, but I'd bet that it would have been playable with virtual memory swapping to an SSD. Trying to play through the whole game like that would probably not go well, but it'd be better than waiting for the hard drive to swap at a few dozen MB\sec with ton of latency.
Sadly, this isn't real surprising from JayZTwoCents though. I had to stop watching his videos a couple years ago because he frequently makes factual errors, leaves out important details and then when problems are encountered a lot of times his explanations\assumptions about the cause are inaccurate. A big part of it is probably just being too busy with other things to worry about accuracy in a one-off video, and another part is probably an effort to dumb down the video to be more accessible. He and LTT both do this at times, especially when referring to old hardware. GamersNexus doesn't do this, and I appreciate how accurate their comments are about old hardware when it does come up... I just wish they could make a video these days without it being laced with expletives.
EDIT: Also, this is getting waaay OT for the thread. Sorry for dragging it on...