The course I have developed has been published in CD format.

On some machines (3 XP machines) it is running fine.

On two of the machines (one running XP professional and other Windows 7), while loading module it gives a message "loading..." and hangs, does not proceed further.

Could anyone please tell how do I solve this problem?

Raj from what you are saying you have no problems on some windows PCs and not others.
So the module and its support needs remain the same, that is what is on the CD can be considered constant.
What has changed is the PC so this is related to the PC or PCs and not Courselab.
I would start by checking the hardware, are the CD/DVD drives OK.
Are the default autoplay settings the same.
What is the user role that is invoking the start up file.
What are the UAC settings on Win7.
I can think of a huge list of problems windows might be causing and is it at windows you need to be looking.

Thanks Nick for your response.

When it enters "start.html" file after clicking any module from course page, it stops working.

The behavior is:
* The displayed course page remains same
* the message "loading..." appears
and
* then no further progress

I even tried by create a sample module with only 1 slide (and no complicated scripts, images etc)

This is the behavior even on one of XP machines (XP + Service pack 3).

My question is:

* When it runs on other couple of XP machines after simply copying the generated run time folder, what must be causing this problem on this machine?

* Is there any settings of browser or any other external environment related setting? I did NOT do any special setting on the XP machines where it is working well.
By the way, I am using windows media player on all the slides.

[:confused:]

Media player ... could be that the PCs have either:
Different versions of media player,
Different defaults set in media player,
Different security setting applied to media player.
You might want to try this.... Go to the drop down menus and select from MODULE the RUNTIME SETTINGS. On the checks tab select Media player and click enable.
What should happen is as soon as you open the module it checks to see if the software is available. If not you'll see a pop up error message. I think (not sure though) that this might flag up errors too.

I tried all what you had mentioned for the Windows XP machines that are giving problems while loading the module i.e. showing the message "loading..." and then hanging, but, no luck.

IMP:- An additional information is (strange), on these problematic machines, if I run the entire runtime generated package (autorun.html and then start.html) from USB drive, then it works !

Could you please tell the problem? May be this information may be a hint to the core problem.. I hope so [:confused:]

See Neils comments above on DOM and XML Raj. You may find these help

Another thing to look at will be codecs. Any media object can be encoded in a large number of ways, many of these can be considered industry standard and will be available on standard installations of most players on most operating systems.
However if you have used one that the target system doesn't have then it might cause it to hang.
Courselab asks media player to open an object, media player doesn't know the codec and fails but as it is being displayed within another program doesn't report the error it leaves it to the host application. So the whole thing stalls.

This error is very similar to what Darren Cheney mentioned before. I work with Darren and we are still trying to diagnose/figure out the oddness in his scorm package.

The modules work perfectly the first time, everytime. Randomly when retrying a module it will exhibit the exact behaviour described by the OP. Once it does that once, that module will no longer work for that user (on that pc). I've tried resetting LMS settings to correct it, it won't fix it. We've tried clearing all browsing data, still nothing. Oddly, this only occurs in IE. We've reproduced the error on IE7, 8, and 9. This rules out the flash suggestion.

We are really at a loss here. I am hoping 2.7 fixes whatever is causing this issue. We'd purchase courselab in a heartbeat if compatibility was better.

2.7 looks to be quite happy on chrome, webkit and mozilla.
Kinda hard to tell quite what will happen omce you throw in interactions with an LMS though but it should remain pretty solid.
I'll have to run up a few VMs to host some LMS's and see what happens.

BTW which LMS is this happening on? I assume that it's just the one LMS and one or more PCs.
It could be the XML caching problem in IE which could be almost anything!! Usual culprit will be an IE add-on or active-x component, either working or just a failed installation.
I'd strip out any add-ons one by one and see if it works then

We tracked down the issue. Its the XML DOM 6.0 and XML HTTP 6.0 plugins in IE. When we disabled these in IE, it reverts to using 3.0 automatically. Problems instantly go away.

Thanks for the tip, it saved us a ton of grief.

Unfortunately IE can be superbly flakey to start with and especially if you add any anything! It is suprisingly easy to code a page to make IE6 onwards go into a real hissy fit!
I see NSWIOP has a moodle instance so how is this problem affecting users out in the wild??
I don't think that there is a friendly way to remotely switch off or replace plugins on the users PCs that won't have AV or UAC screaming at the user. Well you could but silent background installs are generally a bad thing to do.
Possibly a page that lists required dependancies then checks the users PC where they have problems might be the way to go.

We do have multiple moodle instances. Strangely enough we havent encountered this issue in the past, its only been encountered while developing a new, fairly large module for an external party.

Fortunately most area health services are quite far behind in browser updates. This isn't a problem that affects most people, but it is common enough that we needed to identify the cause and solution.

Our solution is to roll it out, and deal with it on a case by case basis. We can communicate directly with the user, or the areas IT department.

Fortunately now that its identified its a very easy solution. Thanks for your assistance in the matter.