Add support for detecting XCP2 as itself instead of as XCP #14

Closed
opened 2026-01-29 21:04:57 +00:00 by claunia · 5 comments
Owner

Originally created by @TheRogueArchivist on GitHub (Oct 27, 2020).

Originally assigned to: @mnadareski on GitHub.

For at least XCP2 (the only example I have), BOS detects XCP but doesn't recognize the VERSION.DAT file in the root directory, and so doesn't recognize it as XCP2 specifically, only XCP. It also doesn't give a version number, in this case Version 1.5.

Contents of VERSION.DAT:
[XCP]
VERSION=XCP2, Version 1.5

[PLAYER]
VERSION=2.7

Originally created by @TheRogueArchivist on GitHub (Oct 27, 2020). Originally assigned to: @mnadareski on GitHub. For at least XCP2 (the only example I have), BOS detects XCP but doesn't recognize the VERSION.DAT file in the root directory, and so doesn't recognize it as XCP2 specifically, only XCP. It also doesn't give a version number, in this case Version 1.5. Contents of VERSION.DAT: [XCP] VERSION=XCP2, Version 1.5 [PLAYER] VERSION=2.7
claunia added the enhancement label 2026-01-29 21:04:57 +00:00
Author
Owner

@mnadareski commented on GitHub (Oct 27, 2020):

It is likely finding one of the other files common to XCP since the original BurnOut code checked for XCP.DAT, ECDPlayerControl.ocx, and go.exe. This is good info, though, since I can add a check for this different DAT name and then read the contents as an INI. Do you happen to have an XCP1 disc as well to check?

@mnadareski commented on GitHub (Oct 27, 2020): It is likely finding one of the other files common to XCP since the original BurnOut code checked for `XCP.DAT`, `ECDPlayerControl.ocx`, and `go.exe`. This is good info, though, since I can add a check for this different DAT name and then read the contents as an INI. Do you happen to have an XCP1 disc as well to check?
Author
Owner

@TheRogueArchivist commented on GitHub (Oct 27, 2020):

I don't unfortunately, but I can tell you all the detected files on here if you'd like, as well as zip them along to you to see if those files themselves might have some version information.

@TheRogueArchivist commented on GitHub (Oct 27, 2020): I don't unfortunately, but I can tell you all the detected files on here if you'd like, as well as zip them along to you to see if those files themselves might have some version information.
Author
Owner

@mnadareski commented on GitHub (Oct 27, 2020):

XCP2 detection enhanced given the information above: 43cbafc0f5

Leaving this open for XCP1, if we can get more info.

@mnadareski commented on GitHub (Oct 27, 2020): XCP2 detection enhanced given the information above: https://github.com/mnadareski/BurnOutSharp/commit/43cbafc0f5ff3a3e20d6a27f0abde86b8439cbcf Leaving this open for XCP1, if we can get more info.
Author
Owner

@mnadareski commented on GitHub (Oct 27, 2020):

Fixed the mixup with XCP.DAT, added content checks based on GO.EXE: 095de1441d

@mnadareski commented on GitHub (Oct 27, 2020): Fixed the mixup with `XCP.DAT`, added content checks based on `GO.EXE`: https://github.com/mnadareski/BurnOutSharp/commit/095de1441d1daafc288a5f18b874acb042756c11
Author
Owner

@mnadareski commented on GitHub (Oct 23, 2024):

This is long since been fixed.

@mnadareski commented on GitHub (Oct 23, 2024): This is long since been fixed.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SabreTools/BinaryObjectScanner#14