I never looked into this in detail, but in what experience I do have looking at it (still having a number of "restore CDs" for systems that are long gone)... I had the impression that the OEM systems each have a custom BIOS which has a "special" string in it somewhere which is read by the installer to verify that the system is "legit". It may also involve looking for a bit of hardware that's not expected to change with future editions of the machine (manufacturers don't want to spend money arranging new Winblows CDs due to a small hardware update).
This can vary a fair bit - I've got some restore CDs which won't proceed on anything but the EXACT system they were made for, not even differing ones by the same manufacturer.
On the other hand I have a few Dell OEM Win7 CDs (I did some work for a company that ran Linux on "new" Dells and often found the unused Winblows install CDs in the garbage) - I've since gotten at least 5 Dell machines and these installs always work (and the machines are quite different from each other = I7, I5, I3, Pentium, different on-board peripherals, full and small form factor (so very different mainboards) etc. - there's even at least one the CD doesn't have all the drivers for and I have to install drivers after ... but the OS still installs even though it was obviously not made for this exact system)
My advise: Just use a "standard" Win98 retail/general install CD and scrounge up any extra drivers you might need.
I would think that trying to "bypass" vendor system verification is not going to be easy - obviously Microsoft would have wanted the OEMs to have fairly robust protection in place to prevent exactly this kind of thing!
https://dunfield.themindfactory.com ; "Daves Old Computers" ; SW dev addict best known:
ImageDisk: rd/wr ANY floppy PChw can ; Micro-C: compiler for DOS+ManySmallCPU ; DDLINK: simple/small filecopy(w/o netSW)via Lan/Lpt/Com