DiscWright 0.7.2

A bug-fix release. Nothing needs migrating: project files are unchanged, the disc layout is unchanged, and a 0.7.1 project opens and rebuilds exactly as it did.

Readable on Windows XP and older now says no when the answer is no

0.7.0 added a box that writes ISO9660 and Joliet filesystems beside the UDF one, so a disc can be read on Windows XP, 2000, ME, 98 and 95. The box greyed itself when a file was too big for those filesystems, using ISO9660's own limit of 4 GiB minus a byte.

That limit is wrong. IMAPI, the Windows image writer that builds every disc DiscWright produces, stops at 2 GiB exactly. So a disc could pass the check and still fail, and it failed late, after staging the whole payload:

Adding ISO9660 and Joliet beside UDF, so the disc reads on Windows XP and older.
ERROR: Data file is too large for 'ISO9660/Joliet' file system.

Found on a 7.79 GB game whose largest part is 4,294,040,574 bytes, a byte under 4 GiB and nearly twice what the writer accepts. The ceiling is now the measured number, and tools\Measure-IsoFileCeiling.ps1 measures it again on any machine: it takes a file of exactly 2,147,483,648 bytes and refuses one byte more, with or without Joliet, and Joliet cannot be requested on its own.

What this costs you. GOG splits its installers into parts just under 4 GiB, to stay under the identical FAT32 ceiling. That is twice this limit, so a game that arrives in parts cannot have the older filesystems at all. Those discs stay UDF only, which needs Windows Vista or newer. A game that arrives as a single installer under 2 GiB can still have it, and so can a disc of manuals, patches and extras.

The box greys itself and names the file that is the problem, rather than letting you find out several minutes into a build.

If you built a disc with that box ticked and it worked, nothing about it changes. If you built one and the build died, this is why.

Thanks again to u/kelphelpOG on Reddit, whose Windows XP and 98 testing prompted the feature in the first place. This narrows it, and it is better to know the shape of it than to have a box that sometimes throws a build away.

Also in this release

The window tests can walk a folder dialog. The test harness has always taken arguments for stepping through a folder tree, and they had never moved anything: Browse For Folder opens with the keyboard focus on its OK button, so every arrow key went to a button and OK returned the folder it started on. Nothing caught it because every test so far picked the folder the app had already seeded.

The demonstrations in the README were re-recorded. Both still showed 0.4.0, three releases back. The new ones show the compatibility row, including the XP box greying itself for a game that came in parts, and the one-game demonstration still ends on a real build of a real 7.79 GB disc.

A skill that records them, by driving the window rather than filming it, so the next time they go stale it costs ten minutes and nobody has to touch the machine.

Checksums

DiscWright-0.7.2-setup.exe  E15AC76905D62A84A7914248CA9CBA584DE0756389CC8042A8269BD0025665C1
DiscWright-0.7.2.zip        09441179982CB95809EA355737623D1B6EDEDBF921746EC66A92D3A62D8DF359

Tests: 415 logic, 78 window.