Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DQ crash in XP #37

Closed
larsiusprime opened this issue Jun 12, 2014 · 9 comments
Closed

DQ crash in XP #37

larsiusprime opened this issue Jun 12, 2014 · 9 comments
Assignees

Comments

@larsiusprime
Copy link
Owner

Running TDPRG 0,0,2 + DQ2 0,0,2, it crashes as soon as it starts up in Windows XP mode. Does not crash in Windows 7.

@larsiusprime larsiusprime self-assigned this Jun 12, 2014
@larsiusprime
Copy link
Owner Author

The crash occurs even when the crashdumper BAT files are disabled. I notice my XP virtual machine runs in 16 bit color, perhaps this is an issue too. Using this hack to enable 24 bit color.

@larsiusprime
Copy link
Owner Author

Okay, with 24 bit color enabled it no longer crashes, using a build with disabled crashdumper BAT files. I'm going to re-run with a build that enables crashdumper BAT files to verify these are in fact the problem.

@larsiusprime
Copy link
Owner Author

Alrighty, it looks like wmic is indeed the culprit on windows XP. The "ver" command is not hanging, but is also not producing the right output in crash dumps, this is the fault of my own parsing code, not the command itself.

@larsiusprime
Copy link
Owner Author

Alrighty, "ver" now works correctly and it can properly detect Windows XP!

Now to figure out what's up with wmic.

@larsiusprime
Copy link
Owner Author

BAM!

windowsxpdump

According to some random forum, if you have this problem you can put " <nul" at the end of a wmic command and it mysteriously works.

Strange.

@larsiusprime
Copy link
Owner Author

Build is up.

@Nathan-P-B
Copy link

DQ1 0.0.2 / TDRPG 0.0.3 on "real" Windows XP 32-bit

I wasn't having crashes previously, but I had to kill each of the three batch files using wmic before continuing. With this version, the batch files close successfully.

Oddly, I captured the output from wmic three ways into a file: with no input, with < nul and with < nul: (colon at the end). All three had the exact same output (same byte length and bytes). But removing the < nul from a batch file makes the DQ program hang on that batch file. Quite strange, but as long as the work-around is fine for others, it looks like you can get the debug information.

update: this is using "real" 32-bit Windows XP

@larsiusprime
Copy link
Owner Author

Cool! Glad to hear it.

Are you using a "real" Windows XP install, or a virtual one like I'm using?

@larsiusprime
Copy link
Owner Author

I'm closing this for now. If someone notices this is still broken, please re-open this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants