cfg file and put the port in there manually. With Crusader, for ex, I had to edit the game's. Some games won't let you choose the port it uses, for their native Soundscape option. It is PnP and uses a wave port address that's not in the usual Soundscape range. There are some catches to that card though. I was using it for a bit because it is a lot shorter than the Elite and S-2000 which didn't fit in one of my cases.
One of the chips on the card says "OPUS" right on it. I am attaching two screenshots, one of the blue screen and the other one of the device manager after installation of the driver.The Opus card is shorter than the big Soundscape cards, but longer than the VIVO. I also tried the other two drivers but the results were exactly the same. The sound card was now recognised as "Creative Sound Blaster PCI128" but had an exclamation mark on its icon and didn't work - no sound was available. However, what happened was that I got a blue screen complaining about the ctpci9x(05) vxd. I then installed the most recent one and hoped that it would also take care of the other unknown device. I found three different drivers there for use of the device with Windows 98. As recommended, I went to the Creative web site and searched for "PCI 128". I didn't expect to see another unknown device there, though, this one called "PCI System Peripheral". I didn't worry because I knew Windows 98 had no driver for the sound card Workstation provides. I then went to the device manager and, as expected, the sound card was driverless and listed under "other devices", with a question mark and named "PCI Multimedia Audio Device". The OS installed normally, with no errors, and I then proceeded to install the VMware tools. I am having trouble setting up a Windows 98 virtual machine working under WMware Workstation 7.0.1, in a Windows 7 64 bit host.
0 kommentar(er)
