Theoretically a PostScript printer should be compatible all the way back to the 80s when desktop publishing took off.
The printer comes with a PPD file to tell the PostScript generator the names of its paper trays, whether it supports duplexing, etc. If you can't find it elsewhere, it's probably included with the Windows driver or buried in one of the .CAB files inside.
I have had mixed results with trying to load the PPD file into ancient (eg Windows 3.1 PostScript driver) software. Sometimes it's better just to pick a period, preloaded color PostScript printer and just make the printer deal with it.
The simplest way to print to these is your computer connects to TCP port 9100 of the printer, sends PostScript, breaks the connection, and the printer prints. I've heard there is a JetDirect driver from HP you can install on Win9x to add support for that (2000/XP had it out of the box). There's also an Axis Print System you can try to do port 9100 or LPR printing. And finally you can go down the path of trying to get the printer to act as an SMB 1.x server, or have an intermediate SMB 1.x machine on your network (I'm using this to allow Win3.x to send PostScript that then gets fed into CUPS and goes to a modern color inkjet).
Be aware that there is a rebellion going on against all of this, starting from the mobile device community, called driverless printing. Many of its advocates don't seem to get that the whole idea was to keep it as PostScript all the way until it gets sent to the printer, so it's been "driverless" all along. The new driverless uses some restricted variant of PDF I believe, among other formats, but wants you to use Bonjour/Zeroconf and IPP (HTTP/HTTPS) to connect to the printer rather than the port 9100 trick. They consider PostScript and PPD files especially (because their only exposure to them is these pseudo-PPDs that CUPS produces for printers that are not actually PostScript printers) very deprecated.