First post, by Kreshna Aryaguna Nurzaman
- Rank
- l33t
So, upon reading this thread, especially Cat's post...
Nevermind, I got my joystick to work. VPC emulates the joystick port, and uses whichever joystick is joystick ID #1 in Windows. As I have multiple game controllers, it was mapping the wrong one (my USB gamepad instead of my gameport joystick).
Cat
....then I decided to try it myself. I just happen to have an old copy of Connectix Virtual PC 5.2, and went through all the trouble. It wasn't easy. I had to struggle with the damn Windows 95 NDIS protection error, but that's another story.
Nonetheless, after finishing Windows 95 installation, I could not get gameport joystick to work with Virtual PC's Windows 95. The joystick section in Win95 control panel kept giving the "joystick not connected properly" error message. Then I checked the Windows 95's Device Manager. For some unknown reason, I had two gameport joystick connected, while one of them has yellow exclamation mark. My host-connected USB joystick, by the way, is Logitech Extreme 3D Pro USB, although it has nothing to do with the problem.
After doing trial-and-error for a while, turned out I needed to delete both gameport joysticks in Device Manager, and then the Virtual PC's Windows 95 detected the joystick properly during startup.
Windows 95 OSR 2 (running on Virtual PC 5.2) detected a gameport joystick during startup.
Then it shows properly during Joystick section in Control Panel.
Calibrating the gameport joystick on Windows 95 in Virtual PC, which is actually a host-connected USB joystick.
The gameport joystick is now detected properly.
So yes, I have a Windows 95 OSR 2 running on Virtual PC 5.2, with virtual gameport joystick which is mapped from my host-connected USB joystick.
There is some problems I note tough:
(1) the gameport joystick's axis is jumpy and spiky. I'm not sure why, perhaps because my host is not powerful enough to run Virtual PC, so that overall guest performance is spiky? Host is AMD Athlon(tm) II X2 250 3.00 GHz, with 1.5 GB of RAM. Yes, it's my office computer.
(2) Windows 95 protection error keeps coming quite often. At first, it was NDIS protection error. After I installed the necessary patch, it becomes OIS protection error. I found reducing the amount of RAM to 64 MB helps alleviating the problem.
(3) Novalogic F-22 Lightning II, which is actually a DOS game, runs unacceptable slow and non-responsive on the said Virtual PC's Windows 95. That's very disappointing, because the game is the very reason why went through all the effort of installing Virtual PC. I always wanted to see if Virtual PC could run the game faster than DOSBOX.
Any thoughts?
UPDATE: I need to reset the virtual machine "the rough way" (using virtual power button), because F-22 Lightning II runs very slow that I just cannot simply exit the game and shut down Windows. And since I did that, the Windows 95 virtual machine could never boot, because it is always plagued with IOS Protection Mode error at every boot attempt.
Never thought this thread would be that long, but now, for something different.....
Kreshna Aryaguna Nurzaman.
