classicdosgames.com

Crossword Weaver is a Windows-only crossword puzzle maker that supports two distinct puzzle styles: free-form puzzles built from only your own words, and themed symmetrical newspaper-style grids. It offers a demo so you can test it before buying. Choose it if you need both styles in one tool and work on Windows; look at alternatives if you need cross-platform support, a browser-based workflow, or a free tool with no purchase step.

The core difference: two puzzle styles in one tool

Most crossword makers specialize in one output style. Crossword Weaver's distinguishing feature is that it handles both:

If you only ever need one style, a simpler or cheaper tool may cover you. If you switch between casual word-list puzzles and publication-style grids, having both in one program avoids juggling two tools.

Windows compatibility and trying before buying

Crossword Weaver is Windows only. That is a hard constraint, not a preference:

• Windows users: you can run it natively.
• Mac, Linux, or Chromebook users: you would need a Windows environment, or you should choose a cross-platform or web-based alternative instead.
• Before purchasing: the site provides a demo. Use it to confirm the puzzle styles, grid behavior, and output match your needs. The demo is the intended evaluation path, so treat it as your compatibility and feature check rather than assuming the paid version behaves the same in every detail.

The site references purchasing, so plan for a paid product rather than assuming it is free. Pricing details are not specified in the available information, so check the site directly for current terms.

Output: printable and playable puzzles

Crossword Weaver is described as producing printable and playable puzzles. When comparing tools, check these output dimensions on the same basis:

• Print: does the tool export a clean grid plus clues suitable for paper handouts?
• Play: can the puzzle be solved on screen, or is it print-only?
• Format control: can you adjust grid size, clue layout, and numbering?

A tool that prints well but has no on-screen play mode suits classroom handouts. A tool with playable output suits digital assignments or casual solving. Decide which of these you actually need before comparing, because it narrows the field quickly.

Ease of use and automation

Crossword Weaver emphasizes automatic generation: you supply words and clues, and it builds the grid. The practical questions to ask of any maker:

1. How much manual grid adjustment is required after auto-generation?
2. Does it handle word placement conflicts for you, or do you fix them by hand?
3. How long does a typical puzzle take from word list to finished output?

For hobby use, a rougher auto-generated grid is fine. For publishing or repeated classroom use, the amount of manual cleanup matters more than the feature list.

Which tool fits your use case

• Hobby and personal puzzles: a free or low-cost maker is often enough. Crossword Weaver's demo lets you judge whether the two-style support is worth paying for.
• Classroom use: prioritize printable output, fast generation from vocabulary lists, and Windows availability if your school machines run Windows.
• Publishing or newspaper-style grids: the symmetrical themed style is the relevant feature. Compare how each tool handles symmetry and grid polish, since that is where output quality diverges most.
• Cross-platform or browser-based work: Crossword Weaver is not the fit. Choose a web-based maker instead.

How to decide

1. Confirm you are on Windows. If not, stop here and look at cross-platform tools.
2. Decide whether you need both free-form and symmetrical styles, or just one.
3. Download the demo and build one real puzzle you would actually use.
4. Check the output: print it, and try solving it on screen if playable output matters to you.
5. Compare the result against one alternative on the same puzzle, then decide whether the purchase is justified.

The fastest way to choose is to run the same puzzle through Crossword Weaver's demo and one competing tool, then compare grid quality, output options, and time spent.

Freeware is software you can download and use at no cost, but the developer keeps the copyright — you don't get the source code or the right to modify and redistribute it. That single fact separates it from open-source software, and it's also why "free" tells you nothing about how the program is funded. Some freeware is genuinely free with no strings; some bundles adware, toolbars, or upsells. The practical skill is telling those apart before you install. XnView, a photo viewer and batch converter for Windows, macOS, and Linux, is a useful example of freeware done cleanly — its own site describes it as free for private (non-commercial) use, with no adware.

Freeware vs. the other "free" labels

These terms get used interchangeably, but they describe different licensing and business models. Knowing which one you're looking at tells you what to expect after install.

The key distinction for freeware: the price is zero, but the license usually restricts how you can use it. XnView's own wording — "free for private (non-commercial) use" — is a common freeware pattern. If you plan to use a tool at work or in a product you sell, check the license terms rather than assuming "free" means "free for anything."

How freeware gets funded (and where the risk lives)

A zero price doesn't mean zero cost to produce, so the money comes from somewhere. The common sources:

• Donations — the developer asks, you decide. XnView's site includes a Donate link, which is a request, not a requirement.
• A paid tier or companion product — the free version drives interest in something paid.
• Ads or bundled software — the installer offers extra programs, toolbars, or changes your browser settings. This is the main safety concern with freeware.
• Commercial licensing — free for individuals, paid for business use.

The risk isn't freeware itself; it's where you download it from. Third-party download portals often wrap a legitimate installer in their own downloader that adds bundled offers. The developer's own site is the reliable source.

Verifying a download before you install

Run these checks in order. Each one is quick, and together they catch most problems.

1. Start at the official site. Search for the product name and confirm the domain matches the developer. For XnView, that's xnview.com — not a mirror or aggregator.
2. Read the license line. Look for wording like "free for private use" or "free for personal and non-commercial use." That tells you whether your intended use is covered.
3. Check the version and platform. The official page lists current versions and which operating systems they support, so you can confirm you're getting a build that matches your machine.
4. Watch the installer, not just the download. Decline any pre-checked boxes offering extra software. A clean freeware installer won't require them.
5. Note the uninstall behavior. Before committing, know how you'd remove it — a normal entry in your system's app list is the baseline.

If a download page pushes a "download manager" instead of the file itself, or the file name doesn't match the product, stop and go back to the official source.

What XnView shows about a well-run freeware product

XnView is a concrete case of freeware that fits the clean pattern. According to its site, it's a free image viewer for Windows, macOS, and Linux that opens a wide range of formats — JPEG, TIFF, PNG, GIF, WEBP, JPEG-XL, AVIF, HEIC, PSD, JPEG2000, OpenEXR, camera RAW, PDF, DNG, and CR2 among them. Beyond viewing, it handles color adjustment, resizing, cropping, screen capture, and metadata editing (IPTC, XMP), plus batch rename, batch conversion, duplicate finding, and image comparison.

The product line is split by task, which is worth knowing before you pick one:

• XnView MP — the current cross-platform viewer and organizer (version 1.11.7 at the time of the source page).
• XnView Classic — the Windows-focused viewer (version 2.52.7).
• XnConvert — a batch image converter for Windows, macOS, and Linux (version 1.116.0), for converting, resizing, watermarking, adding text, and filtering in bulk.
• XnResize — a batch resizer.
• NConvert — a command-line tool for developers who need format support in their own applications.

The site describes these as "professional free applications" and states XnView and XnConvert are free for private (non-commercial) use. It also advertises "no adware." Note what the source does not say: it doesn't claim the software is open source, and it doesn't state pricing for commercial use. If you need it for business, treat the commercial terms as something to confirm with the developer rather than assume.

A practical checklist before installing any freeware

• [ ] Downloaded from the developer's official domain, not a portal
• [ ] License terms read, and your use (personal vs. commercial) is covered
• [ ] Version and platform match your system
• [ ] Installer's optional extras declined
• [ ] You know how to uninstall it
• [ ] For batch or automated work, you've confirmed the tool does what you need before relying on it

Freeware is a legitimate and often excellent way to get capable software at no cost — XnView's format support and batch tools are a good example. The deciding factor is rarely the price tag; it's whether the license fits your use and whether the download came from the source that controls it.

Retro game source code is the original human-readable program text behind a released game, and it survives in three very different forms: officially published code, leaked internal code, and decompilation projects that reconstruct source from a shipped binary. Which form you are dealing with determines what you can legally do with it and how much you can trust it. RetroReversing (retroreversing.com) is an archive built around exactly this material — its tag index lists 26 entries under "Source Code," alongside 60 SDK, 51 Leak, and 45 Hardware entries — so it is a practical starting point if you want to study how games were actually built.

The three kinds of "source code" you will encounter

These get lumped together in conversation but behave very differently.

A decompilation is not the same object as the original source. It is a reconstruction produced by reading disassembly and rewriting it into compilable code, and projects often track a "matching" percentage because large parts may still be approximations. RetroReversing's own feed includes a "How Decompilers Work" tutorial, which is worth reading before you assume a decompiled file is byte-identical to what the developers wrote.

How to locate source code in an archive like RetroReversing

The site organizes material by platform and by tag rather than by a single search box, so the fastest route is tag-driven.

1. Start from the tag index. Tags are ranked by volume: Introduction (60), SDK (51), Leak (45), Hardware (37), Nintendo 64 (30), Source Code (26), Super Nintendo (25), and so on. The "Source Code" tag is the direct entry point.
2. Narrow by platform. If you care about a specific system, combine tags — for example Source Code plus Game Boy, or Source Code plus SNES. The index shows Game Boy at 20 entries, SNES at 25, and Nintendo 64 at 30, so platform tags usually have more material than the generic source tag alone.
3. Check the "Leak" tag separately. Leaked material is often filed under Leak rather than Source Code. The Gigaleak-related posts (for instance the Yoshi's Island source code and the NEWS_11 workstation restore) sit in this space, and they include things beyond code — art workspaces, file formats, and development hardware notes.
4. Read the post, not just the title. Entries like "Mr Do! Source Code (Game Boy)" or "MAME Source Code" describe what the archive actually holds. MAME is an open-source emulator project, so its code is a normal public repository — a useful contrast to leaked console code.

Expect the archive to be a mix of complete source trees, partial snapshots, and supporting artifacts (SDKs, dev kit hardware documentation, file format notes). That mix is the point: source code alone rarely explains a game, but source plus toolchain plus file formats usually does.

What you can actually learn from it

Studying retro source is most useful when you treat it as evidence about process, not as a ready-made project to rebuild.

• Toolchains and SDKs. The SDK tag (51 entries) and the "Console & PC Software Development Kits" section document what developers compiled with. Reading source alongside its SDK shows why certain code patterns exist.
• File formats. Source often reveals the structure of asset and data formats that shipped in the final game — useful if you are writing a viewer or converter.
• Game logic. Physics, AI, and rendering routines are readable in source in a way they never are in a disassembly listing.
• Development history. Leaked snapshots and art workspaces show intermediate states, cut content, and how a game changed before release.

If your goal is to understand a specific mechanic, source code is usually the highest-value artifact available — higher than a disassembly, because variable names and comments (where present) carry intent.

Legal and ethical constraints you should not skip

Leaked source code is copyrighted material that was not published by its owner. Possessing or redistributing it can expose you to legal risk depending on your jurisdiction, and archives that host it often do so in a legally gray area. Practical guidance:

• Do not redistribute leaked code, and do not incorporate it into a project you release.
• Treat decompilation projects differently — many are developed with clean-room practices specifically to reduce legal exposure, but the legal status of decompiled code still varies and is not settled everywhere.
• Official and open-source releases (like MAME) are the safest to study, modify, and cite.
• If you are unsure whether something is leaked or officially released, assume it is leaked until the archive or the rights holder says otherwise.

This is general information, not legal advice; if you plan to publish anything derived from this material, get jurisdiction-specific guidance.

A reasonable first workflow

If you are new to this, a sequence that avoids dead ends:

1. Pick one platform you already know well (Game Boy, SNES, or N64 have the most material here).
2. Read the platform's reverse engineering overview post before touching any code — it gives you the hardware and format context the source assumes.
3. Open a decompilation or source entry and identify the build toolchain it expects; without the right SDK or assembler, the code will not compile and you will not learn much.
4. Cross-reference the file format tags for that platform so you can interpret the asset data the code loads.
5. Keep leaked material read-only in your own notes; do your experiments on open-source or officially released code.

The archive's value is that it collects source, SDKs, hardware documentation, and file formats in one place, so you can move from "what does this routine do" to "what did the developer compile it with and what data did it consume" without leaving the site.

DOS (Disk Operating System) was the command-line operating system that most IBM-compatible PCs ran before Windows became the dominant environment, and it's the platform nearly every classic PC game from the 1980s and early-to-mid 1990s was built for. Because modern 64-bit Windows, macOS, and Linux can't run those games natively, you play them through an emulator such as DOSBox, or through a site that packages the emulator and game together so it launches with a click. This article explains what DOS actually was, why emulation is necessary, and how to get a DOS game running — including the sound, speed, and fullscreen problems that trip most people up.

What DOS actually was

DOS is not a single product but a family of operating systems. The version that mattered for gaming was MS-DOS (Microsoft) and its close relative PC DOS (IBM), with compatible clones like DR-DOS and FreeDOS filling out the field. Key traits:

• Command-line interface. You typed commands at a prompt (C:\>) rather than clicking icons. Games typically launched by typing an executable name, e.g. PRINCE or DOOM.
• Real-mode memory model. Early DOS gave programs direct access to hardware and to a limited pool of conventional memory (640 KB), which is why so many games shipped with memory-configuration instructions for CONFIG.SYS and AUTOEXEC.BAT.
• Direct hardware access. Games talked straight to the sound card, graphics adapter, and input devices. That's what made them fast on period hardware — and what makes them fragile on modern machines, where the operating system mediates all hardware access.
• No multitasking. One program ran at a time. Later versions added limited memory management, but the model stayed fundamentally single-tasking.

Windows 3.1 and Windows 95 could run on top of DOS, and many games of that era shipped as DOS executables launched from within Windows. That's why a preservation project like Zomb's Lair lists DOS alongside Windows 3.1 and Amiga as separate platforms — they're genuinely different targets requiring different handling.

Why you need an emulator on a modern PC

A DOS game expects to own the machine: it writes directly to video memory, programs the sound chip, and reads the keyboard hardware. A modern OS forbids all of that. Three practical consequences:

1. 64-bit Windows cannot run DOS programs at all. The NTVDM (NT Virtual DOS Machine) that provided DOS support was dropped from 64-bit builds. On 32-bit Windows it still exists, but it's unreliable for games.
2. Timing breaks. DOS games often tied game speed to CPU clock speed. On a multi-gigahertz processor, a game designed for a 33 MHz 486 may run absurdly fast or refuse to start.
3. Sound hardware is gone. The Sound Blaster, AdLib, and Gravis Ultrasound cards these games target don't exist in modern machines, and the games don't know how to use what replaced them.

DOSBox solves all three by emulating a complete DOS PC — CPU, video, sound card, and all — inside a window. It's the standard tool, it's free and open source, and it runs on Windows, macOS, and Linux.

Where to get DOS games

You have two broad routes, and they differ mainly in how much setup you do yourself.

Preservation and curation projects occupy the second category. Zomb's Lair, for example, describes itself as "a passion project dedicated to bringing old classics to a modern audience, while eliminating all of the hurdles that that normally entails," and organizes its catalog by platform (DOS, Amiga, Windows 3.1) and by genre (Adventure, RPG). The value of that kind of packaging is precisely the configuration work — memory settings, sound setup, and speed calibration — done for you.

A note on the legal side, since it affects which route you choose: much of this material is abandonware — old commercial software whose publisher has stopped selling or supporting it. Abandonware is a community norm, not a legal category, and rights holders can and do re-release games commercially. Where a game is currently sold (on GOG, Steam, or elsewhere), buying it is both the safer and usually the easier path, since those storefronts ship pre-configured DOSBox builds too.

Running a DOS game: the basic steps

If you're configuring DOSBox yourself, the workflow is the same for almost every game.

1. Install DOSBox for your platform and note where you put your game folder. Keep paths short and free of spaces — C:\DOS\GAMES\GAMENAME rather than a deep folder with spaces in the name. DOS itself had no concept of long filenames.
2. Mount a drive. At the DOSBox prompt, MOUNT C points an emulated drive letter at a real folder. The expected result is a confirmation message; if you get an error, the path is wrong.
3. Switch to that drive and change into the game directory.
4. Run the game's setup utility first if it has one (commonly SETUP.EXE, INSTALL.EXE, or SOUNDSET.EXE). This is where you tell the game which sound card to use — pick Sound Blaster or Sound Blaster 16 with the default port and IRQ values, which is what DOSBox emulates.
5. Launch the game by typing its executable name.
6. Adjust speed if needed. DOSBox's cycle count controls how fast the emulated CPU runs; raising it speeds a sluggish game up, lowering it slows a too-fast one down.

If you're using a pre-packaged release, steps 1–4 are already done. You launch a shortcut and the emulator starts with the right drive, sound, and speed settings.

Troubleshooting the usual problems

No sound, or sound only in some places. The game's own setup utility is almost always the culprit — it's still configured for a card DOSBox doesn't emulate. Re-run setup and select Sound Blaster. If the game predates sound-card setup utilities, it may only support PC speaker audio, which DOSBox emulates but which sounds thin by design.

Game runs too fast or too slow. This is the cycle setting. Games from the late 80s and early 90s are the most sensitive. Some front-ends let you bind hotkeys to raise and lower cycles while the game runs, which is the fastest way to find a stable value.

Fullscreen looks stretched or has black bars. DOS games ran at fixed resolutions like 320×200, which don't match a modern monitor's aspect ratio. Stretching fills the screen but distorts the image; leaving it unstretched preserves the original proportions. There's no correct answer — pick based on whether you prefer accuracy or a filled screen.

The game can't find enough memory. Classic DOS memory errors come from the 640 KB conventional-memory limit. DOSBox handles most of this automatically, but games with unusual requirements may need specific memory settings in the emulator's configuration file.

Keyboard or mouse doesn't respond correctly. DOSBox captures input when the game window is focused; releasing the capture (usually with a hotkey) returns control to your desktop. If a game needs a joystick, it has to be configured both in DOSBox and in the game's own setup.

What to take away

DOS was the command-line, single-tasking, hardware-direct operating system that defined PC gaming for roughly a decade, and its design is exactly why those games don't run on a modern machine without help. DOSBox emulates the whole environment; packaging projects remove the configuration burden on top of that. If you want to play rather than configure, start with a pre-packaged release and treat the game's own setup utility as the first thing to check whenever sound or speed misbehaves.

Shareware is software distributed for free so you can try it before paying. In the DOS era, that usually meant you got a complete, playable game — often the first episode of a trilogy or a version with some features locked — and could send the developer a registration payment to unlock the rest or receive later episodes. It is not the same as freeware (free to use with no payment expected), a playable demo (a limited slice of a commercial game), or public domain software (rights waived entirely). DOS Games Archive is a working example of a site that hosts shareware, freeware, demos, and public-domain releases legally, with 1,663 DOS games available to download or play in a browser.

Shareware vs. freeware vs. demos vs. public domain

These four labels get used loosely, but they describe different things. The distinction matters because it tells you whether you are expected to pay, what you are getting, and whether the copy is authorized.

A single archive can carry all four. DOS Games Archive describes its catalog as "shareware, freeware, playable demos or full versions which are released as freeware or into the public domain" — so the license label on each game page is what tells you which model applies.

The try-before-you-buy model

Shareware worked because distribution was cheap. Developers uploaded a game to bulletin boards and shareware disks, players copied it freely, and anyone who liked it sent a check or called a registration line. The "upgrade" from the free shareware build to the registered version was the whole business model. That is why a shareware game often feels complete rather than crippled: the point was to convince you, not to frustrate you.

Common distribution forms

• Episode one of a trilogy — the first chapter is free, later chapters require registration.
• Limited feature set — the full engine with some levels, weapons, or options disabled.
• Time- or nag-limited — the game runs but reminds you to register.
• Full game released as shareware later — some titles were eventually given away entirely, which is why a game can appear as both shareware and freeware depending on the version.

How to legally download and play shareware DOS games

The practical steps are the same whether you want shareware, freeware, or a demo.

1. Pick a source that states its legal basis. DOS Games Archive says all games on the site can be downloaded legally and that it is "not a so-called abandonware website." That statement is the signal to look for.
2. Check the license label on the game page. Each entry lists a category — Shareware, Freeware, Playable demo, or Full version — plus developer, publisher, and year.
3. Download the game files, or use the Play online option if the page offers it.
4. Run it. Two routes work on modern PCs:
   • Browser emulation — the "Play online" button runs the game in your browser, no setup needed.
   • DOSBox — download the files and run them in DOSBox, the standard DOS emulator. Game pages on the archive list DOSBox alongside the download and play options.
5. Verify it runs. If the game launches to a title screen and accepts input, you are set. If it exits immediately or shows a blank window, see the troubleshooting notes below.

Why the source matters

Abandonware sites host copies whose legal status is unclear — the original rights holder never authorized the distribution. A site that explicitly separates shareware, freeware, demos, and public-domain releases, and states that downloads are checked for adware, malware, and viruses, is doing the work that tells you the copy is legitimate. DOS Games Archive makes both claims: legal downloads and virus/adware/malware checks on all downloads.

Troubleshooting shareware games on modern PCs

Deciding what you actually need

• You want to play a classic game for free, legally → filter for Freeware or Public domain entries.
• You want to try a game before buying the full version → Shareware or Playable demo entries are the right category.
• You want the complete commercial game → a demo won't give it to you; look for a full version released as freeware, or buy it where still sold.
• You care about safety → prefer archives that state their legal basis and scan downloads, and avoid sites that don't.

The license label on each game page is the single most useful piece of information — it tells you what you are getting, whether payment is expected, and whether the distribution is authorized.