What it's trying to do is obtain the machine's unique BIOS ID, which is the preferred method of identifying clients in GSS2 (before that it used the network adapter MAC address), but accessing this BIOS data from Windows is a little tricky up until Windows 2003 which added an API for it.
In fact, there are two standards which define this ID, and two methods for getting it; one is defined by the System Management BIOS specification, and one is defined by the PXE specification. The code is in the middle of trying to decode the PXE one, but it seems to have hit a problem decoding the PXE bios data.
The first thing to look at is how your machine's BIOS formats this block of BIOS data. I generally find the simplest way to do this is with the good old DOS debug command. Open a command window on the client, and enter this:
C:\> debugYou can get out of the debugger back to the command line using the command "q". In the debugger, enter this search command:
-s f000:0 ffff "_SYSID_"That command asks the debugged to seach the BIOS data segment for the string _SYSID_ which is one of the "eye-catchers" that marks the presence of this block. For instance, in this notebook I'm using this spits out
F000:7550If it doesn't print anything, then the string wasn't found so it might be in an alternative area which you can seach using
-s e000:0 ffff "_SYSID_"Next, I take that number that it printed and ask it to print the memory at that location
-d f000:7550
F000:7550 5F 53 59 53 49 44 5F BF-11 00 61 75 0F 00 01 00 _SYSID_...au....
F000:7560 00 5F 55 55 49 44 5F C4-19 00 44 45 4C 4C 51 00 ._UUID_...DELLQ.
F000:7570 10 4C 80 37 CA C0 4F 4C-31 53 00 00 00 00 00 00 .L.7..OL1S......
F000:7580 5F 53 4D 5F 80 1F 02 04-FD 00 00 00 00 00 00 00 _SM_............
F000:7590 5F 44 4D 49 5F 10 CC 09-A0 75 0F 00 3B 00 24 90 _DMI_....u..;.$.
F000:75A0 DA FB 00 DA B2 00 0D 5F-0F 37 40 7D 00 00 00 00 ......._.7@}....
F000:75B0 00 7E 00 02 00 00 00 40-00 04 00 01 00 41 00 04 .~.....@.....A..
F000:75C0 00 00 00 90 00 05 00 00-00 91 00 05 00 01 00 92 ................That block of data contains a string "_UUID_" which is the eye-catcher for the PXE UUID. In my system, this is fine and the code has no trouble with it - your system appears to have this data block formatted unusually, and I have to figure out how to tweak the code to cope with it.
At this point, if you can cut-and-paste this data out of the command window and into a text file (command windows have a system menu which allows you to mark an area of the text window - like any normal Windows window, alt-space is a keyboard shortcut which opens the system menu) and either post it here or e-mail it to me at nigel dot bree at gmail dot com to analyse.