OSReportFlush

Syntax

#include <revolution/os/OSLog.h>

s32 OSReportFlush( void );

Arguments

None.

Return Values

Returns 0 if successful or one of the following codes if unsuccessful.

NAND_RESULT_ACCESS NAND_RESULT_ALLOC_FAILED NAND_RESULT_BUSY NAND_RESULT_CORRUPT NAND_RESULT_EXISTS NAND_RESULT_INVALID NAND_RESULT_MAXFD NAND_RESULT_NOEXISTS NAND_RESULT_UNKNOWN NAND_RESULT_FATAL_ERROR

Description

If you call OS(V)Report with the output destination set to Wii console NAND memory, the string is not written directly to the NAND memory. Instead, it is temporarily stored in a buffer in the console's main memory.
OSReportFlush must be called to write this string correctly to Wii console NAND memory.

Note:
When you use OSReportFlush, the oslog library becomes linked, and you need to use OSReportViewer to allocate a region for writing in NAND.
Before you use OSReportFlush, we recommend that you take a look at OSLog Overview first.

Revision History

2010/08/20 Replaced NAND_RESULT_MAXFILES with NAND_RESULT_MAXFD, and revised the return values to be correct.
2009/10/19 Made revisions to correspond with OSVReport.
2008/11/19 Initial version.