Toshiba debug code on iHDSim

I have a debug script that allows me to abstract my debug logging.

Its worked all week on the Toshiba (it originated from example code for it) and on iHDSim (which I use for getting some clue as to where my 00C errors are!).

But suddenly, today the iHDSim is giving me an HDDVD_E_ARGUMENT script error.

var _appDebug;

* Call this just once from the one-off Initialiser.

**/

function initialiseDebugger( diagTrace, diagListeners, Index, dout )

_appDebug = new Object();

..........

* Basic debug string output

**/

function debugOut( msg, part, lvl )

If I comment out the above 2 highlighted lines, iHDSim is okay again.

Of course the first question is why is iHDSim failing (the Tosh is fine)

This debug file has not changed for days, whereas other scripts have been added and modified which I would have liked to have blamed.

The second question is, how might I write code that can determine what player its running on, and perhaps avoid calling incompatible debug methods...

The same as me: I stumped as to how unchanged code started throwing an error!! It was reporting an error on line 83 in 'unknown file' so after playing with all the line 83's in my project, debug.js was the last file I tried and... here I am!

I have Visual Studio installed, and I think because its the Express edition I can't get the debugger working (I'm launching with HDiSim -debug -jit -p "<path>").

So trying to download the 90 day trial of the full VS 2005, it gets as far as downloading 2.5k of a 2.6GB 'iso' file. And stops. I tried it in Opera before IE, and it reported a 'stopped' status instead of a 'finished' status so I'm guessing a web server problem somewhere (or could it be my proxy ).

I'll try again later, but unless there is a way to use another script debugger or Express, I'm stuck...!

However, you mentioned HDiSim does support the same debug interface as the Toshiba: Could you tell me where to find the debug output

thx,

Nathan.

Thanks for your help so far, it looks like the 'writeLine' method I'm using doesn't like the DOM Elements returned by HDiSim.

Using code like...

var mmElement = document.getElementById( "menu_main" );

myDiagnosticsListenersItem.writeLine( mmElement, "main_menu", 0 );

...was my problem. Even though the typeof mmElement is 'object', there doesnt seem to be a toString() method on it, and I'm guessing thats the real problem here.

But I still haven't found the diagnostics.txt anywhere on my harddrive...!

I was given the following code to get hold of a debug text file handle...

var listenerCollection = Diagnostics.listeners;

var Index = listenerCollection.add("debugger");

var myDiagnosticsListenersItem = listenerCollection.item(Index);

Would this affect what and where the file is I've searched my entire hard drive for 'diagnostics.txt' and 'debugger' and can't find it!

thnx

Thanks Peter, but I'm not sure what you mean by 'host objects' or why it would exist on some and not all. As far as I'm concerned the purposed of .toString() has always been as an aid to logging and debugging, and as such is why it is part of Object.prototype and therefore part of all other objects (so not to need to write extra debug code).

On the Toshiba it worked fine, it was only the HDiSim that it wasnt working with

However, I'm completely failing to find the diagnostic.txt file. Any help there would really ...help!

thnx,

Nathan.

Thanks Peter. I guessed this is the situation, but I was trying to point out the Toshiba implementation had the foresight to give these host objects (that claim to be type of javascript 'object' on both HDiSim and Toshiba player) at least the .toString() method.

You advise these objects don't have to follow the JS Object spec, but lets face it, theres no reason why they shouldn't!

So would you be for or against a move advising other implementors to implement the base 'object' methods, and perhaps 'fix' the MS implementation

Thanks,

Nathan.