mirh

But.. uh, can you load that XP installation without quibble (of course, through the use of of whatever appropriate hacks)? Because it's not like you can blame the bootloader for...

I can report that with 0.13 this still doesn't work with a normal .srt file and android 9.

Still nothing. With the even more odd mystery that between 0.10.18 and 0.10.20 I couldn't notice any particular change over the built architectures.

https://github.com/opencv/opencv/issues/7013?

I was also seeing the same error, already in the file import step, with Just Cause (JustCause.exe)

Meanwhile, almost literally the same minute https://community.amd.com/t5/ai/new-amd-rocm-6-1-software-for-radeon-release-offers-more-choices/ba-p/688840 (and yes that [should](https://www.anandtech.com/show/21421/amd-slims-down-with-radeon-pro-w7900-dual-slot) include miopen too)

Ok, so, like.. Every single windows issue is closed by now. And I can just presume it should work if built from source? But the biggest blocker for an official...

Not sure how that has anything to do with anything. As I said, this is probably already possible if you can put up with compiling stuff from source.

[Oh, I see](https://github.com/ROCm/MIOpen/discussions/2703). https://github.com/ROCm/MIOpen/pull/3263 https://github.com/ROCm/ROCm/issues/3571 So, anyway, as for getting an official WSL2 release as I had guessed it's waiting on the mainlining of overall rocm support (which does [seem](https://github.com/search?q=org%3AROCm+windows+is%3Aopen+NOT+dependabot&type=pullrequests&s=updated&o=desc)...

Native windows can even wait eventually.. But I think **a lot** of people were grasping at straws to know the requirements for WSL2. Because even in the original announcement it...