If it was heavy, you knew there was an impressive manual inside, and if they took the time to make and print a manual, they probably took the time to develop the software well.
Here's Lotus 1-2-3: https://www.ebay.com/itm/283699892988
SimCity 3000 was perhaps the last game with a big printed manual: https://www.ebay.com/itm/354226256399
There were exceptions in both directions of course (for example, shareware-distributed Doom; random clip-art compilations with a crappy "editor" that came with a printed book showing each one), but if you were browsing a shelf it wasn't a bad rule of thumb.
Shortly after that everything went to small box with a CD/DVD in it (and a manual in PDF form, if any) and then even those mostly disappeared and now everything is online help.
It spawned the whole Missing Manual series, and there's something lost that interactive help can never replace - the manuals had a journey and a theme and you'd often find things you never even knew you wanted by reading them.
I still sometimes pick up old manuals at thrift stores just to read.
Lately I have been learning Moho, an animation program that's been around since 1999. It's got two PDF manuals - one that's specifically ~300p of tutorials, one that's ~600p of reference - and they are both fabulous. Gorgeously laid out, lucidly written. I'm in heaven. Fuck context-sensitive help, fuck video tutorials, here's everything I need to know to get started with this power tool. From the rawest beginner concepts to "here is how a .moho file is structured in case you need to read/write one as part of some convoluted multi-app workflow".
Sadly if you buy a physical copy you just get a DVD. I think I need to take these two PDFs down to Office Depot and get them printed out, sharing the computer screen with the program or putting it on a tablet just isn't cutting it.
In addition to the manuals, I remember Ultima also came with a map and a shiny coin. It was worth buy some games back then just for the physical toys.
Other than the bugs/extreme performance regressions they turned up in our product, the most interesting takeaways from these exercises were that: 1. most consumer software is really, really bad; 2. good package design is really, really hard.
It may be hard to imagine now, but unboxing software used to be quite exciting. How many manuals? How good? Early software releases had pretty good documentation: I still fondly remember the first editions of Microsoft's developer tools as well as their Office suite, which came with a full set of printed decent-quality manuals. That practice went out of the window for good shortly after, though, and online documentation has IMHO never reached the same quality. But that may just be the nostalgia speaking...