If I install Moodle 1.8 Windows complete package, let the database install and complete first setup, then rename the moodle folder to moodle-1.7 and extract the latest moodle-1.8 generic build in its place, then go to the /admin/ page and authenticate as administrator to apply the database table changes, then create a new course in the Miscellaneous group, then automatically get prompted to Add an AICC/SCORM package, then choose to upload the package as uploaded to http://www.peterchamberlin.dsl.pipex.com/M2775101-2004.zip, then provide a title and description for it and then click the Save Changes button then...

I get the following JavaScript error to begin with:

Line: 189
Char: 3
Error: 'parentNode' is null or not an object
Code: 0
URL: http://ws806/course/modedit.php?add=scorm&type=&course=2&section=0&return=0

This is caused by:
function validate_mod_scorm_mod_form_reference(element) {
var frm = element.parentNode; // This line

Which is called by:
ret = validate_mod_scorm_mod_form_reference(frm.elements['reference']) && ret

Which fails because there's no such element "reference"

Getting past this error then results in a pause while the package is extracted and made ready to be added to the course and then I receive an empty HTML page and no error message. If I wipe down the filename and go to the /course/ folder then I see that the package has not been added and it goes through the auto-add process again. I see that the package files have been extracted to course folder "2" but in the \moodledata\2\moddata\scorm\KdkWOQVF\ folder I see some of the extracted files and the package .zip file - but in checking what's been extracting I see that the operation stopped before file \M2775101\help\help\measureDCVoltage_images\MeasureDCVoltage_04.jpg was in place. On repeating this entire process in Firefox I note that the extraction stops around the same place, but not on the exact file. Firefox also raises a JavaScript error and receives an empty page in response to the Save Changes form submission.

This seems like a pretty major fault to have in a 1.8 version that's being "polished". It seems to be package specific as most of my generated content files, and some from other vendors, goes wrong in a similar manor. Others work fine. Our package is SCORM 2004 3rd Edition conformant.