....just my general observation, something else is awry... there's too long a literary of different things not working properly, and for mine (apart from win98) the only thing they have in common is PSU ~ have you checked the voltage rails are on spec?
The other thing I have to say, is that I'm ... errm .. 'amused' at this talk of reinstalling windows ~ life is too short =) What I do...
....on the retro hardware, install windows (whatever release, my choice is win95 OSR2), and go through the countless reboots necessary to get all the hardware drivers you need installed, and a clean bill of health in the device mangler. I just did this recently with the target HDD being the noisy platter motor whined Seagate ST32132A IDE drive (2.1Gb iirc) ~ V66M mobo, Matrox G200 AGP, 3com NIC, SBLive!, Voodoo2 ...once all this is peachy keen, shutdown windows ... remove IDE (PATA) harddrive... this is the source drive now...
....grab a pair of 8Gb or bigger USB drives ~ make one of them bootable by flashing the Clonezilla image to it (balenaEtcher or rufus) -- the other flashdrive is for saving the image to...
....for sake of speed, it's handy to have a more modern mainboard that still has IDE/Floppy ports (I use a N68-S3)....plug the IDE source drive onto the PATA port, plug the 2 USB flashdrives into mobo ports, turn on a grab boot selector to boot from the Clonezilla drive..two beeps, and you can load into ram at 800x600 and follow the prompts, mounting the blank USB drive as /home/partimg, select a disk-to-image operation, select the IDE source disk, don't check it (if windows shutdown cleanly that's enough), and create the drive image...be a dummy, use all the default choices, and do it --- you will end up with an image of the HDD on the once blank USB drive....
..what you do with that image, may vary... so I'll just describe my mad-house... I use CF for boot(+system)/storage 'drives'. The sound of the ST32132A spinning-up and win95 doing it's best to thrash the heads to death, is a thing to behold, 'aural history' if you like, thus I tend to 'retire' them while they're still operational ....so in this case I'm imaging that drive, to replace it with a CF 'clone' (same geometry/mbr/partition mapping) ~ for this, remove IDE cable from header socket, plugin CF<->IDE adapter with 4Gb CF card inserted, boot & run Clonezilla again, this time a restore disk image operation, choosing the CF card as the target drive, don't change any geometry/params, and good to go...operation completes in <5mins....pull CF card out of adapter, walk to other end of house and plug CF card into slot of rear I/O mounted CF/IDE adapter, power up retro hardware. boots win95 in next to no time, all good ~ this confirms Clonezilla's backup/restore path has a greenflag finish.
So now if ninetyfivebee ever really gets it's nickers in a knot, I can return to this staging (restore) point, of good to go, ready for software. One might choose to do this, after installing a particular set of games/software, to return to that staging point instead.... but regardless, this is much, much cleaner and simple, than having to reinstall windows...again ; instead you redeploy the image. I could've used a different (quieter) spinning drive, but CF is no slouch. Wrt the elephant in the room....2.1Gb HDD imaged to 4Gb CF equals ~1.9Gb of unused space.... I very much don't care ~ at best, it gives the wear-leveling algo in the controller a vast unused field of cells to flip out, and at worst it keeps the restore process time to a minimum. Odd thing is, I've had zer0 problems with CF boot/system drives, and no need to blow away a mess and restore ... yet ...
The other thing this process gives you, is a bit perfect map of the hardware that imaged software was running on....ie; if you restore this image on the same hardware makeup and discover it's still not running as it should ; it's the hardware, not windows =)