wraggster
June 25th, 2008, 20:26
Uberjack posted this news:
The recent issue with fMSX 3.5.3 (fw 1.50 version) prompted me to rethink future support for 1.50/kxploit executables. One option was to regress to an earlier version of the library, dropping any of the adhoc functionality; another was to simply stop working on versions for 1.50.
I (grudgingly) decided to stop providing support for fw 1.50 - reasons for this being threefold - a) the ps2dev community recommends moving away from this firmware, as continuing support for it is getting more challenging (flash0 memory being one reason); b) running simple applications in kernel mode seems counter-intuitive, and c) it’s becoming exceedingly more difficult to cope with two distinct programming models.
The emulators that are currently up will probably be the last ones with support for firmware 1.50; all future emulators are likely to only run on firmware 2.00 and greater.
http://0xff.akop.org/2008/06/25/firmware-150/
The recent issue with fMSX 3.5.3 (fw 1.50 version) prompted me to rethink future support for 1.50/kxploit executables. One option was to regress to an earlier version of the library, dropping any of the adhoc functionality; another was to simply stop working on versions for 1.50.
I (grudgingly) decided to stop providing support for fw 1.50 - reasons for this being threefold - a) the ps2dev community recommends moving away from this firmware, as continuing support for it is getting more challenging (flash0 memory being one reason); b) running simple applications in kernel mode seems counter-intuitive, and c) it’s becoming exceedingly more difficult to cope with two distinct programming models.
The emulators that are currently up will probably be the last ones with support for firmware 1.50; all future emulators are likely to only run on firmware 2.00 and greater.
http://0xff.akop.org/2008/06/25/firmware-150/