VOGONS


First post, by Hans Tork

User metadata
Rank Member
Rank
Member

After taking ages, my Win 95 build is sort of complete. As of writing this post,I am still having issues with the motherboard and/or the PS/2 keyboard. However, I think I have gotten some decent time with the OS to document my experience.

First off, my hardware list:

Asus CUV4X Socket 370 motherboard(having issues so will probably need a replacement I reduced the speed im BIOS to 366 Mhz and now the issues are sorta gone)
Intel Pentium 3 Coppermine
Riva TNT2 64M Vanta(I had the better RIVA TNT2 but the motherboard refuses to display anything. Fortunately I also got the vanta as it was quite cheap)
SB AWE 64 CT4520
128 MB RAM
128 GB SSD(used qemu to make it bootable)

Probably the most valuable thing I learnt is how to use qemu to install Win 95 without a floppy or even a CD/DVD ROM!!!! I used qemu to make the 128 GB SSD bootable on my real PC using a Win 95 image and then transferred the SSD over to the retro one. Apparently you have to keep the SSD unallocated(ie do not make any partitions there), use FDISK(ideally a patched FDISK) on it from the qemu Win 95 boot disk to create a primary DOS partition and then format the boot partition to make it bootable. It took me a lot of time to figure out that making partitions before using the boot disk messes things up.

For the Win 95 OSR version, I went with the modified OSR 2.1 version(following the guide created by Leonardo). After a lot of trial and error I did manage to get a stable system running and even played pinball, Diablo 1&2 and Age of Empires 2 on the system. I did have a lot of crashes/BSODs before I figured out the bare minimum things to install to keep the system stable.

It seems disabling every port or resource not needed by the BIOS, getting the RLOEW patches, installing only the XUSB update and the VIA 4in1 drivers, the unofficial updates and installer(nothing else on the list), then Dx 7.0 and finally the gpu/sound drivers is the way to go. Win 95 gave me a BSOD everytime I installed Dx 8 and Plus! Themes. I also had to avoid setting up a network and the additional stuff on the unofficial updates pack as those installations also gave me issues. I cannot say if OSR 2.1 was a better choice than OSR 2.5 since I only installed OSR 2.5 once and it seemed okay till it kept on asking me to restart due to registry errors. I feel OSR 2.1 had less of those issues but I did not test the 2 versions comprehensively. Also it seems getting 7zip and Clone Drive is enough to run and test the games I want to play on the OS.

The attachment IMG_2718.jpg is no longer available
The attachment IMG_2713.jpg is no longer available
The attachment IMG_2712.jpg is no longer available

The above pictures were taken when I had Themes installed. I would not recommend installing as it later caused crashes for me.

All in all, I am quite satisfied with what I saw. The OS itself was pretty snappy and I did get to experience the authentic feeling of playing Diablo 1, Age of Empires 2(it was Win 98se but somewhat applicable) on Win 95. I would like to thank the forum members for chiming in with some sound advice in my initial post about the build.

Presently, due to the motherboard issue I am unable to use a keyboard or give an input when my system logs in to the Win 95 OS or even POSTs. I do plan to get a RIVA TNT2 in the future and also change the motherboard. Right now, I do not know if the motherboard is having problems or it is a PSU thing. It might even be something to do with the mouse/KB. I keep on getting a wheezing sound from the motherboard speaker and it seems some users with this motherboard previously had similar issues with their PS/2 ports. I hope to change the motherboard soon and update the post once everything is stable.

Fingers crossed but resetting the bios and rebooting a few times with only KB and then the mouse worked and the system can boot into Win 95. I still do not know what causes the issue but I can only pray that the system does not give me that annoying KB/mouse issue.

So the system is right now working with BIOS CPU speed set to 366 Mhz.

Ok after a lot of messing around and trying to fix the issue, I think I would ditch the motherboard. I even tried this fix as suggested in another thread, however the problem only worsened. I think a new motherboard has to be procured for my socket 370 build.

Keyboard not working

Last edited by Hans Tork on 2025-09-19, 19:38. Edited 6 times in total.

i7/Titan X/X-Fi- XP
P4/X800/Audigy 2 ZS- W98
P3/Voodoo 3 3000/AWE 64 - W95

Reply 1 of 6, by jakethompson1

User metadata
Rank l33t
Rank
l33t

Windows 95 isn't particularly stable, but it shouldn't be as bad as your experiences. Aside from the motherboard, I wonder if you have some subtle file system corruption going on through the SATA-IDE. That registry error message on a new installation can be indicative in particular.

Reply 2 of 6, by Hans Tork

User metadata
Rank Member
Rank
Member
jakethompson1 wrote on 2025-09-18, 00:58:

Windows 95 isn't particularly stable, but it shouldn't be as bad as your experiences. Aside from the motherboard, I wonder if you have some subtle file system corruption going on through the SATA-IDE. That registry error message on a new installation can be indicative in particular.

Actually I did not have issues with the registry once I made a minimal OSR 2.1 build(ie by putting the bare minimum drivers and software/fixes). However I started having the keyboard/mouse issue and the motherboard wheezing sound today. I am unable to pinpoint what causes the sound. It is most likely due to the bad PS/2 ports which some user documented here on vogons. However, I can sometimes boot into the OS but I find that none of my keystrokes register.

Last edited by Hans Tork on 2025-09-18, 03:14. Edited 1 time in total.

i7/Titan X/X-Fi- XP
P4/X800/Audigy 2 ZS- W98
P3/Voodoo 3 3000/AWE 64 - W95

Reply 3 of 6, by Hans Tork

User metadata
Rank Member
Rank
Member

Ok a small update I can again boot back to my OS with only a keyboard and all it took was resetting the BIOS. I still do not know if this solution/hack would hold. However I am yet to get the mouse working. I am still getting the wheezing sound when a mouse is attached.

Edit: The KB and mouse now work and I no longer get the sound. Dunno if resetting the BIOS did the trick or if it was a bad connection.

Edit2: It is back to not working again. I have even installed a driver for the mouse (a WYSE PS/2 mouse). Now I do not get any wheezing sound from the motherboard but the mouse simply remains undetected. What is weird is the driver sees the mouse as a serial mouse.

Details

BIOS screen and driver

The attachment mouse1.jpeg is no longer available
The attachment mouse2.jpeg is no longer available

Mouse

The attachment mouse3.jpg is no longer available
The attachment mouse4.jpg is no longer available

Does anyone with this motherboard know what settings are to be kept in the BIOS?

i7/Titan X/X-Fi- XP
P4/X800/Audigy 2 ZS- W98
P3/Voodoo 3 3000/AWE 64 - W95

Reply 4 of 6, by dionb

User metadata
Rank l33t++
Rank
l33t++

This sounds like PnP issues resulting in resource conflicts. If PS/2 and sound are conflicting, it's probably on the ISA end of things.

- is PnP OS enabled or disabled? Try the other...
- do you have any resources reserved for legacy/non-PnP in BIOS? If a lot is reserved, it could lead to your PnP devices being squeezed onto the same resources.

Tbh I'm sort of suspicious of your install on different (emulated) hardware too. Win9x really doesn't like being moved from one system to another and that might be a factor in this.

Reply 5 of 6, by Hans Tork

User metadata
Rank Member
Rank
Member
dionb wrote on 2025-09-18, 06:13:
This sounds like PnP issues resulting in resource conflicts. If PS/2 and sound are conflicting, it's probably on the ISA end of […]
Show full quote

This sounds like PnP issues resulting in resource conflicts. If PS/2 and sound are conflicting, it's probably on the ISA end of things.

- is PnP OS enabled or disabled? Try the other...
- do you have any resources reserved for legacy/non-PnP in BIOS? If a lot is reserved, it could lead to your PnP devices being squeezed onto the same resources.

Tbh I'm sort of suspicious of your install on different (emulated) hardware too. Win9x really doesn't like being moved from one system to another and that might be a factor in this.

I have it enabled but I also disabled it once and it did not make any change.

I have tried to disable as many resources as possible in the BIOS like the USB/COM ports. I am even thinking of disabling the PCI IDE.

Here are some more details of the BIOS

Details
The attachment p4.jpg is no longer available
The attachment p3.jpg is no longer available
The attachment p2.jpg is no longer available
The attachment p1.jpg is no longer available

I have also installed the Intellipoint 2.2 driver and that seems have to worked somewhat well in detecting the mouse. The thing is that the system works fine on initial boot. After half an hour or so I get the wheezing sound. It seems once it starts it does not matter if I reboot my machine or keep it as it is. I have to once again wait for an hour before it gets back to normal.

I went through a lot of vogon posts where members have detailed problems with the board like not being able to boot. It seems I am able to boot but get intermittent KB/mouse errors.

Actually I am having issues some what similar to this thread on page 2, except I do not have a processor speed issue but a KB/mouse one.

FB Marketplace Gateway Rebuild - Beginner Build Log!

Also this one.

CUV4X - Powerleap Tualatin Build

The thread below has a post where the exact problem I am facing is detailed. I wonder if I was sold the same board.

BIOS does not detect input devices in ASUS CUV4X board

Sadly, reading the above threads makes me think it is a motherboard issue and since I do not know how to recap motherboards or make hardware adjustments, I will try to get another one.

Update: I have gotten a sort of stable system now(no crashes or KB/mouse errors) by setting the CPU speed all the way down to 366 Mhz. I have kept the system turned on for more than an hour and so far I am no longer getting that annoying sound.

i7/Titan X/X-Fi- XP
P4/X800/Audigy 2 ZS- W98
P3/Voodoo 3 3000/AWE 64 - W95

Reply 6 of 6, by Hans Tork

User metadata
Rank Member
Rank
Member

I think I have to replace the motherboard. The noise(seems to be coming from the motherboard speaker) is back. I wanted to know what would be a good replacement for my motherboard considering the processor I have(P3 coppemine SL3XY with 133 MHz FSB). I have browsed through a few possible replacements like an Abit Vl6 motherboard, a Soyo SY-7VCA-E and a few others. Would they work with this processor? Thanks.

i7/Titan X/X-Fi- XP
P4/X800/Audigy 2 ZS- W98
P3/Voodoo 3 3000/AWE 64 - W95