Jump to content

jumper

Member
  • Posts

    1,943
  • Joined

  • Last visited

  • Days Won

    7
  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by jumper

  1. The Athlon is a great processor to use FineSSE with. It is fast and has full MMX and (I believe) CMOV support, so only FCOMI and FUCOMI instructions would need emulation. The easiest way to test FineSSE is to put finesse.exe (or a link to it) in your SendTo folder. The next time an app crashes with an Illegal Instruction error, note the executable's name and location. Then Explore to that location, right-click on the executable, and SendTo finesse.exe. The app will launch normally. Do whatever you did before; this time there should be no crash. You can also put finesse.exe (or a link to it) on your desktop and drag an executable onto it there.
  2. There have been some reports that Flash 10 still has problems with some content. Hopefully Adobe now has those fixed for all MMX cpus. FineSSE uses 386-compatible code for most of the patches and emulation, but some MMX instructions are used. Because programs that use SSE instructions will also likely use MMX instructions, I've set MMX support as the minimum processor level. Any processor that supports the full, original MMX instruction set should benefit from FineSSE. (Actually any 32-bit processor should benefit--FineSSE only trys to help if there is already a fatal error!) CMOV and Prefetch instructions are not SSE instructions, but FineSSE handles them simply because on many MMX-capable cpus they need to be handled and can be handled. I have no problem with (attempting) to add support for any Illegal Instruction issues that users report. If anyone finds an Illegal Instruction error in any app while using FineSSE, please report it to this thread. The error details will be on the clipboard for easy pasting! After some discussion here of how best to patch or emulate the problem, I'll update FineSSE to handle it.
  3. Hello everyone, I have a 735MHz VIA C3 Ezra running Win98se. Flash 9 r47 just wasn't enough anymore, so I've been working on a Just-In-Time debugger to handle the various Illegal Instruction exceptions I've been encountering with more recent builds of Flash 9 and other apps. Since the goal of this debugger is to put an end to SSE issues on older cpus, I've optimistically named it FineSSE: finesse.exe finesse27a.exe (04Jun2011, least unstable) finesse29.exe (12.5K) (16Jul2011, usage) FineSSE will patch or emulate all illegal instructions mentioned in this thread or its references: PSHUFW is patched according to the Adobe Flash references MOVNT instructions are patched to become standard MOV's FENCE and Prefetch instructions are NOP'd CMOV, FCOMI, and FUCOMI instructions are emulated FineSSE can be launched by dropping the app to be debugged onto it (or on the command line). This method of testing does not require a restart after download. FineSSE is installed as a Just-in-time Debugger by adding these lines to WIN.INI (or the equivalent to the registry), followed by a restart: [AeDebug] Auto=1 Debugger=C:\Program Files\finesse.exe -p %u -e %u If you already have a debugger installed, rename it to "Debugger2" and in the near future FineSSE will pass on exceptions it can't handle: Debugger2=C:\Program Files\DevStudio\SharedIDE\BIN\msdev.exe -p %ld -e %ld FineSSE is a Win32 app and a work in-progress. It should work on Win95-WinXP, but I've only tested it on Win98se thus far. The patches and emulation code are designed to be PentiumMMX-compatible, but testing has been limited to my VIA C3. Testing feedback for other CPU/OS combos would be great. Hopefully FineSSE will fix the problems jds was having with JPEG2YUV and MPEGENC in mjpeg tools. Apps tested on my C3: Flash 9 r289 works, so content requiring r115 now works! Over a dozen problem builds of FFmpeg now work great. no more illegal instructions [edit]rarely[/edit] seen in anything.
×
×
  • Create New...