Comments on: ROM Release…? …. Nah, I don’t think this counts. http://superfamicom.org/blog/2010/01/rom-release-nah-i-dont-think-this-counts/ A Satellaview research blog. Wed, 14 Jul 2010 17:12:34 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Kiddo http://superfamicom.org/blog/2010/01/rom-release-nah-i-dont-think-this-counts/comment-page-1/#comment-3635 Kiddo Fri, 29 Jan 2010 03:59:46 +0000 http://superfamicom.org/blog/2010/01/rom-release-nah-i-dont-think-this-counts/#comment-3635 "Memory Pack Error. Abnormalities in the Memory Pack have been discovered, erasing contents." http://superfamicom.org/blog/2009/01/i-am-error/ If you check back on this post, you can see all the errors I can trigger by myself. The initial batch are errors in a Derby Stallion 96 cart, so you could probably check that as well. I have never encountered errors 21, 22, 23, and 42, either. “Memory Pack Error.
Abnormalities in the Memory Pack have been discovered, erasing contents.”

http://superfamicom.org/blog/2009/01/i-am-error/

If you check back on this post, you can see all the errors I can trigger by myself. The initial batch are errors in a Derby Stallion 96 cart, so you could probably check that as well.
I have never encountered errors 21, 22, 23, and 42, either.

]]> By: Vehiek http://superfamicom.org/blog/2010/01/rom-release-nah-i-dont-think-this-counts/comment-page-1/#comment-3634 Vehiek Fri, 29 Jan 2010 03:37:50 +0000 http://superfamicom.org/blog/2010/01/rom-release-nah-i-dont-think-this-counts/#comment-3634 Try this: In a SNES debugger, set a write breakpoint on 0013C5 (the address of the error number) and trigger an error. After the error number has been written, change it to the number of the error you want to see and let the emulation resume. The only valid errors I can trigger through this are errors 8, 9, 11, 21, 22, 23, 41, and 42. Alternatively, I've dumped some of the BIOS text (it's stored in SHIFT-JIS encoding). メモリーパックエラーです。 メモリーパック内に異常が　 発見されたので、内容を全て 消去しています。 Try this:
In a SNES debugger, set a write breakpoint on 0013C5 (the address of the error number) and trigger an error. After the error number has been written, change it to the number of the error you want to see and let the emulation resume. The only valid errors I can trigger through this are errors 8, 9, 11, 21, 22, 23, 41, and 42.

Alternatively, I’ve dumped some of the BIOS text (it’s stored in SHIFT-JIS encoding).
メモリーパックエラーです。
メモリーパック内に異常が　
発見されたので、内容を全て
消去しています。

]]>