next »

[Xyphos]

While developing my XML plugin for my XRDB4 tool,
I copied the general schema from jayde's xml plugin
in an attempt to keep things compatible between other existing tools
such as aodboffline and aodbc (aodbc seems to crash no matter what file you feed it, jayde's or mine)

I've managed to produce the same xml output as jayde's tool does
but for some odd reason that I am unable to figure out on my own,
aodboffline freezes when parsing my xml output.

attached to this post is a zip file containing aodboffline, jaydes' working xml and my crashing xml
perhaps someone can tell me why aodboffline chokes. or at least find any difference between
the two xml files, as I can't find anything out-of-place.

[Etheryal]

Speaking of XRDB4, I'm having trouble getting it to work "out-of-box."  It detects my DB just fine, as well as the DB version, but I get this error/exception:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.BadImageFormatException: An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B)
   at XRDB4.CTrees.InitializeCtree(Int16 buffers, Int16 Files, Int16 sectors)
   at XRDB4.CTrees..ctor(ProgressBar pbMarqee)
   at XRDB4.frmXRDB4.btnExtract_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

[Neo-Vortex]

Perchance are you on a 64-bit version of windows...?

[Etheryal]

yep

[Neo-Vortex]

Yup, that'd do it. Xyphos, as you are using the ctree dll, which is 32 bit only, force your app to run in 32 bit mode only and not 64 bit, else you'll get the issue Etheryal is describing.

For the meantime, theres a hack you can do to force a .NET Application to run in 32 bit mode on a 64 bit version of windows, do a bit of googling and I'm sure you'll find it...

[Xyphos]

I changed the config setting in my project; but the change is currently unreleased
as I'm still working on a few changes to the tool.

I'm hoping someone can help me with the XML output tho
it's really bothering me

[pzycho]

Found it with a few simple steps...

1. Cut your dataset into halfs to narrow the error down to a single item.
2. Pretty print working and freezing version to get a readable diff.
3. Look for the usual problems or corner cases like special characters, empty strings etc.

This brings us to an empty value in item 136672:

Code:

<Attribute Name="Can" Value="" />

Put something into the value and you'r good to go.

Code:

<Attribute Name="Can" Value="0" />

PS: Happens 2 times in your 'freezing' file.

[Xyphos]

Awsomesauce.

+1 Reetness and many thanks

[Etheryal]

ok the fix for ctree allowed me to do an extract just fine, but the PARSE is where it froze.  To be specific it froze on the "initializing plugin..." step.  Didn't get any actual debug error like last time.  Just a windows "this program has stopped responding" error.  Does the plugin have any issue with 64-bit windows?

[Xyphos]

ok the fix for ctree allowed me to do an extract just fine, but the PARSE is where it froze.  To be specific it froze on the "initializing plugin..." step.  Didn't get any actual debug error like last time.  Just a windows "this program has stopped responding" error.  Does the plugin have any issue with 64-bit windows?

XRDB4 and all of it's dependencies were converted to x86 code (32-bit)
which allowed you to run it on 64-bit sytem without it crashing.

however, as an experiment, I've compiled another build of it to where the application itself is x86 and it's dependencies are "Any Platform"

you can download this experimental build here:
http://www.xyphos.com/files/XRDB4401.zip

please let me know if this solves your problem.

[Etheryal]

that experimental build brought back my 64bit problem (during the extract process):

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.BadImageFormatException: An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B)
   at XRDB4.CTrees.InitializeCtree(Int16 buffers, Int16 Files, Int16 sectors)
   at XRDB4.CTrees..ctor(ProgressBar pbMarqee)
   at XRDB4.frmXRDB4.btnExtract_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


---------------
I think the other (parse related problem) I'm having might be if you didn't choose a plugin in the beginning (ie. by default its on the null plugin)?  If so, you get a file called:
XRDB4_Plugins-NULL_18-02-02-00

The fact that it was null may be crashing the tool during parse?

[Xyphos]

that experimental build brought back my 64bit problem (during the extract process):

{snip}

I think the other (parse related problem) I'm having might be if you didn't choose a plugin in the beginning (ie. by default its on the null plugin)?  If so, you get a file called:
XRDB4_Plugins-NULL_18-02-02-00

The fact that it was null may be crashing the tool during parse?

ok, then that's a good indication that he app and all of it's dependencies need to be in x86 mode

"XRDB4_Plugins-NULL_18-02-02-00"  doesn't tell me WHAT kind of file it's creating.
you probably don't have "show extensions" enabled on your PC.
looking at the NULL plugin, I don't see any code written that would generate an output file
so I'm going to assume that the created file has ".XRDB4" written on the end
which is perfectly fine because that's the datafile containing the extracted data from which XRDB4
reads from during it's parsing process.

also NULL plugin isn't directly useful in any way since it doesn't generate output but rather, it's
useful for debugging/determining problems reading from datafiles.

so, back to where we started; another experimental build:
http://www.xyphos.com/files/XRDB4402.zip

let me know if this one crashes also.

[Suicidal]

Why are you still using ctree lib anyway? that thing is slow and bugged 

[Xyphos]

Why are you still using ctree lib anyway? that thing is slow and bugged  

you got a better method?
cuz my former ctree-less  (XRDB3) took forever to extract
and was highly errornous

if you have an alternative lib that works perfectly, I could use that.

[Suicidal]

I don't have specific lib or anything, but in AODB resource tool for example I removed the code that used ctree lib and do the index reading without that lib. As long as you don't need to edit RDB (Why would you want to edit it anyway), reading index file is all you need to find needed data in RDB.