Drupal 4.65 Module causing header submission error - PHP, MySQL

Based on information on the Drupal website detailing their experiences, it seems that my particular situation was caused by what is common to all the explained situations - there are characters in the PHP file (extra spaces) cause PHP to emit that error. Below is detail of my experience in relation to this.

As detailed in the document 'Drupal /mySQL crash - 'Warning: Cannot modify header information - headers already sent' Drupal 4.65 has an incident that causes it to generate the above error message and if the administrator has not set errors to only appear in the log and not on screen (admin -> settings), this error message can cause the application to become unusable and if the error message appears to a web visitor or a search engine crawler, the incident could hurt your online business or sheet popularity and page ranking.

In the above-mentioned document, the hypothesis is that the error message and subsequent breakdown on the DB and application are caused by changing the Charset of the DB. In my new installation on Windows,Apache,mySQL and PHP, I have begun seeting the error message and it's related to Flexinode-1. I have not observed the same log message in my Linux installation. Also, another root of this problem could be the fact that after my previous Windows setup collapsed, I exported the node table from my database as SQL and re-imported it intot he new setup to avoid having to copy and paste the already created page.

This action generated a conflict with subsequent Flexinode pages and I had to go into the database and in the 'event table', I removed references to nodes that were not events (they were appearing on the block list for upcoming events). This solved the problem. To be exact, during the publishing process of the Flexinode (webcast - event type), the system kept telling me that there was already content assigned to NID 1,2,3 ... and after refreshing for every error message (there was one for as many pages as I had manually imported into the database), it created the new page and assigned the already existing pages as events - hance the reason why I had to clean them up manually fromt he 'events' table as explained above.

At this moment, I am trying to do research on the Flexinode module to see if that error has been attributed to it, or if this was caused by my importing of nodes into the database (including the ever-sensitive mode-1 cause I chose to replace where existing during my import). So far, I have not see any reports on the Drupal website support to this effect.