Repository navigation
DiscWright 0.11.0
The question this release answers is the one that has no good answer anywhere else: what do you do with a game that is bigger than the discs you own?
A game across several discs
Press BUILD with a payload too big for the blank you picked and DiscWright offers a set, rather than refusing and leaving you to work out the arithmetic. It splits one game across as many discs as it takes.
It does not assemble compilations. Which games belong together on a disc is a decision for the person making it, and a tool that packs them in whatever order the rows happened to sit in is making that decision badly.
Every disc of a set carries Disc set.txt, which lists every file on every disc, not just its own. Any single disc can tell you what the whole set should be, what is on the one in your hand, and what is still missing.
A file bigger than any disc you have
A set places whole files. That is the right rule until one file is larger than a disc, which on a CD is nearly every game made this century.
Ticked, DiscWright cuts that file across discs and puts it back together on the hard drive before anything is installed. The pieces are plain .dwpartNN files, and the disc tells you how to rejoin them with no DiscWright present:
copy /b "game.exe.dwpart01"+"game.exe.dwpart02" "game.exe"
cat 'game.exe.dwpart01' 'game.exe.dwpart02' > 'game.exe'
The set hashes the whole original file as well as each piece, so the rejoined copy can be checked against the file that existed before it was ever cut. The parts being right does not prove the join was.
One menu, through the swaps
Put disc 1 in and the menu copies it, then says "Please put disc 2 in the drive. This carries on by itself once it is there." It notices the new disc, copies it, joins anything that was cut, checks the result, and only then offers to install.
Nothing is written down between discs. Each disc works out the same destination folder from the game's name and the drive with the most room, so disc 2 inserted cold on a machine that has never seen disc 1 arrives at the same folder and finds disc 1's files already there.
Play appears only once the game is really on the machine, rather than pointing at a disc.
Watching a burn happen
The burn engine has reported its progress all along and nothing was listening, because it reports from a thread with no runspace in it. The write now runs in a runspace of its own and the window shows a real bar, the phase the drive says it is in, and what it has left.
A drive that will not say how far along it is reads as not saying, which is a different fact from nought per cent and is not drawn the same way.
Burning, without leaving
DiscWright burns a set itself, one disc at a time, checking every file on each disc before asking for the next blank. It goes first in the list of ways to burn, ahead of handing the ISO to another program, because a set is exactly the case that needs a verified write: disc 2 is no use at all if disc 1 came out wrong.
| Two writers | it asks which one, with the media and free space of each, rather than taking whichever answered first |
| A disc in the way | it offers to erase a rewritable, and refuses to choose when two of them could be erased, because a wrong guess there is somebody's disc |
| Burn with... | hands the ISO to Windows' own burner, or whatever else you have, read out of the registry rather than hardcoded |
Artwork goes on the disc, and printing goes away
DiscWright used to lay out a case wrap and a disc face for a printer. That is the printer software's job, and it knows the case, the paper and the tray. What makes a disc last is the disc carrying its own artwork, so the cover and disc face you choose now go into ARTWORK on every disc exactly as you gave them, beside a READ ME.txt.
The print module, its dialog, its case sizes and its opinions about picture shape are gone.
Fixed
Copying a file off a real disc could not work at all. The menu reported a freshly burned disc as damaged, every time, for anybody who ever used it.
robocopy "D:\" "F:\restore" "game.bin" /R:1 /W:1
A disc is always a drive root, so the source always ends in a separator, and a separator immediately before a closing quote escapes that quote. robocopy read the rest of the line as one argument, settled on a destination inside System32, and the menu told the person their twenty minute old disc was scratched. 875 tests, three recorded films and a published demonstration all missed it, because every one of them copied from a staging folder, and a folder path never ends in a separator.
A half-copied file is exactly the right size. robocopy sets the destination to its full length before writing a byte, so a copy that stops halfway leaves a file that passes a size check and fails a hash. The menu reads robocopy's own exit code now.
Burn to disc could only ever write the last disc of a set, and a second writer in the machine broke the burn outright.
Smaller things
| Checksums | on by default now. A set carries hashes either way; the tick is what gives a single disc the same |
| A disc can check itself | a tick beside the mute in the menu verifies every file against the list on the disc |
| Title on the menu | the field formerly called Title on artwork, which set text on the menu and pointed at the wrong half of the form |
| Project files | schema 14, for the disc set tick and the cut. Older projects open and build exactly as before |
Thanks
To xniwo on GitHub, whose issue #98 is still the only report here from somebody who came to this application without having built it.
Five of the changes above are his: the disc set itself, which was item 1 on his list; cutting a file so it fits, which he asked for twice; handing the ISO to whatever else can burn it; the one click checksum verification in the menu; and three labels that said something other than what they set.
He also worked out the risk before anybody else did, asking whether a split could be reversed without "a database of some sort to remember a game's original state". It does need one, and Disc set.txt already was it. Thank you.
Checksums
| artifact | sha256 |
|---|---|
DiscWright-0.11.0.zip |
14413fce78ddd08c1e76348729d93f4d9edc55752659c0b2c23d69c249c4e6ca |
DiscWright-0.11.0-setup.exe |
c330bcbd8868f6ccd21680662ef4d4ebeac761f818898fb237d475e94eed9a43 |
What was tested, and where
1,327 logic tests and 145 window tests, all passing on the machine this release was cut on, plus a parse check over all 35 scripts under Windows PowerShell 5.1 and PSScriptAnalyzer with no errors. The same tree reports 1,303 logic tests on the Windows 11 test VM, which has one of the four GOG downloads this machine has; the window suite passes on both.
The downloaded installer was installed, started and uninstalled on a Windows 11 that had never seen DiscWright, all seventeen checks passing, and the zip was unpacked and started there, where its window title read DiscWright 0.11.0. Both artifacts were hashed after download and match what the tag build produced. That install check ran on the test VM rather than in Windows Sandbox, because the sandbox came up with Smart App Control on and would not start an unsigned installer at all.
And it was done with real discs, which is new for this release and is the only way any of the above could be believed. A 1.16 GB GOG installer was cut across two 700 MB CD-RWs, burned to both a DVD writer and a USB Blu-ray writer, read back file by file off each disc, and rejoined by the instructions printed on the disc. The rejoined file is byte for byte the file that was cut, da05d18b3b573cf00135639b7950a731d5c0807be66c630232d4671b721fb8e4, and the game it installed is 1,799 files and 4.91 GB of working Hollow Knight. The menu was driven for real: it copied disc 1, asked for disc 2, noticed the swap five seconds after the tray shut, joined, verified and launched the installer on its own.