Author Topic: DOS VDM - USB and Game port Gamepad support  (Read 32734 times)

Wim Brul

  • Sr. Member
  • ****
  • Posts: 279
  • Karma: +23/-0
    • View Profile
    • Wim's home page
Re: DOS VDM - USB and Game port Gamepad support
« Reply #300 on: June 15, 2022, 10:11:37 am »
Hi Martin and Mark,

I am a little bit disappointed. What you are doing is not the way to go. The "PlayStation 3 controller (USB Connected)" and the "Genius MaxFighter F-31U Vibration" are controllers not yet tested at all. Remember the method we used in the past. You need to follow the step by step approach as outlined in the "testing.txt" files that are part of the package. For the huskee device that procedure starts as follows:

Code: [Select]
Installation Instructions - Part A
==================================

A1. Ensure that USBECD.SYS has been installed.

A2. Put the following line in your CONFIG.SYS file:
(Use the proper drive and directory for your system).

DEVICE=H:\OS2\BOOT\USBECD.SYS /D:0C12:0005:0001 /N:$HUSKEE$ /V

A3. Reboot your system.

A4. Run OINPUT.CMD and watch gamepad events in hexadecimal format.
Use Ctrl+C to end this procedure.

Once this is working I would like you to do the following:
---------------------------------------------------------

A5. Run OINPUT.CMD > BUTTON.LOG and press available buttons
(one at a time, after each other, and tell me which ones)
Use Ctrl+C to end this procedure.

A6. Run OINPUT>CMD > STICK.LOG and press stick to different positions
(one at a time, after each other, and tell me what positions)
Use Ctrl+C to end this procedure.

Send me files BUTTON.LOG and STICK.LOG for me to inspect.
--------------------------------------------------------

Since you are preparing oinput.cmd yourself for these new devices, you have to prepare the corresponding testing.text accordingly. It is waste of time and effort to skip these steps.

I am currently investigating what needs to be done to provoke the "PlayStation 3 controller (USB Connected)" to send event records so step A4. can be completed succesfully.

I understand that for the "Genius MaxFighter F-31U Vibration" step A4. has been completed successfully. Why not append some of that output for me to inspect?

Best regards, Wim.

Martin Iturbide

  • OS2World NewsMaster
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 3644
  • Karma: +34/-0
  • Your Friend Wil Declares...
    • View Profile
    • Martin's Personal Blog
Re: DOS VDM - USB and Game port Gamepad support
« Reply #301 on: June 15, 2022, 02:15:08 pm »
Hi Wim

Thanks for posting the instructions again and keep us on the right track. I will follow that procedure for the "Genius MaxFighter F-31U Vibration" and post back.

Regards
Martin Iturbide
OS2World NewsMaster
... just share the dream.

Mark Szkolnicki

  • Sr. Member
  • ****
  • Posts: 286
  • Karma: +15/-0
    • View Profile
Re: DOS VDM - USB and Game port Gamepad support
« Reply #302 on: June 15, 2022, 05:53:15 pm »
Hi Wim!

Hope you are having a fine day!

Hi Martin and Mark,

I am a little bit disappointed. What you are doing is not the way to go. The "PlayStation 3 controller (USB Connected)" and the "Genius MaxFighter F-31U Vibration" are controllers not yet tested at all. Remember the method we used in the past. You need to follow the step by step approach as outlined in the "testing.txt" files that are part of the package. For the huskee device that procedure starts as follows:

Code: [Select]
Installation Instructions - Part A
==================================

A1. Ensure that USBECD.SYS has been installed.

A2. Put the following line in your CONFIG.SYS file:
(Use the proper drive and directory for your system).

DEVICE=H:\OS2\BOOT\USBECD.SYS /D:0C12:0005:0001 /N:$HUSKEE$ /V

A3. Reboot your system.

A4. Run OINPUT.CMD and watch gamepad events in hexadecimal format.
Use Ctrl+C to end this procedure.

Once this is working I would like you to do the following:
---------------------------------------------------------

A5. Run OINPUT.CMD > BUTTON.LOG and press available buttons
(one at a time, after each other, and tell me which ones)
Use Ctrl+C to end this procedure.

A6. Run OINPUT>CMD > STICK.LOG and press stick to different positions
(one at a time, after each other, and tell me what positions)
Use Ctrl+C to end this procedure.

Send me files BUTTON.LOG and STICK.LOG for me to inspect.
--------------------------------------------------------

Since you are preparing oinput.cmd yourself for these new devices, you have to prepare the corresponding testing.text accordingly. It is waste of time and effort to skip these steps.

I am currently investigating what needs to be done to provoke the "PlayStation 3 controller (USB Connected)" to send event records so step A4. can be completed succesfully.

I understand that for the "Genius MaxFighter F-31U Vibration" step A4. has been completed successfully. Why not append some of that output for me to inspect?

Best regards, Wim.

I deeply apologize as well if you feel we are jumping the gun, Wim as I consider you a friend and as that was not my intention. I am probably more to blame than Martin in this.

However, here is a perspective for consideration - as this testing is being done in a public forum, there is a lot of interest being generated, and a lot of people are watching what is happening. Since publishing the Testing Guide I have received private e-mails from others wondering if they can participate, as they feel we are actually carrying on a private conversation between ourselves, in public, and they are simply watching.

As we are also releasing the gamepad-xxxxxxxx,zip files in public, they are wanting to try these drivers for themselves and are looking for a path to do so. IOW there are a lot of potential testers out there that can help - but we need to enable them to do so.

Since the original gamepad package was released, the additional packages have not contained the original sub folders, for the equipment we started with (ie. Marttins and mine), which were actually the items that contained the testing instructions. If we want to keep this more structured, and possibly generate more data from others and their game controllers, I would propose the following:

1) Can we create a new gamepad package, with the most current drivers, and two folders - simply gamepad, and joystick, if the instructions need to be different for the two, and Include the necessary files in each to stay to the structure you specified. They should simply contain the files necessary to test the device, and generate the necessary information for you, to be posted here.

2) I will modify the Testing Guide to stay strictly to the program you specify there in testing.txt, plus the additional information that will allow them to test game controller function once an xevents file is created, that either we or they can test. I would also suggest adding some information on generating lsusb reports, and how to do that to the guide as well.

I will send the draft version of the guide to you privately first, so you can approve the testing info in it, so we can run these tests properly.

The only problem I foresee with that, Wim, is that you may be literally inundated with data from all sides, and it may overwhelm in that sense. You have already done a lot for this project, and being overwhelmed is the last thing we want, because, strangely you also have a life.

Best as always, Sir

M

« Last Edit: June 15, 2022, 07:03:41 pm by Mark Szkolnicki »
Vincit Que Se Vincit - "He Who Conquers Self Succeeds"

Mark Szkolnicki

  • Sr. Member
  • ****
  • Posts: 286
  • Karma: +15/-0
    • View Profile
Re: DOS VDM - USB and Game port Gamepad support
« Reply #303 on: June 15, 2022, 07:48:47 pm »
Heh Dave!

110 mm of rain so far in the last two days - more to come

Hi Mark, when I first started using OS/2, Warp v3, it was on a 4MB 386/33. At first just as a drop in replacement for DOS, then slowly migrating to OS/2 programs like WebExplorer. Had to be very careful in tuning and not use the WPS for it to be usable. That readme would have been very pertinent at the time. Even when I upgraded to 8MBs and swapped the CPU for a 486DLC.
Now here we are, so much memory that most is used as a ramdisk and still worried about the browser using all the memory :)

My first computer was the third IBM PC in Winnipeg (the original PC, not PC-XT).

It was an 8088 CPU, no 8087 co-processor installed, came with two full height 5.25" 360K floppy drives  (the full height brick size hard drive was too expensive for my meager budget of the time - and its full capacity, if I bought one was a whopping 10 Mb).

I think on-board memory was either 64K or 128 K, with a Hercules monochrome graphics card and screen, no sound other than the built-in PC speaker.

Strangely you were still able to do a lot on it command line wise - I learned DOS, and my first word processor was Volkswriter, which did not have bells and whistles but still worked well. Learned Windows starting with v3, as I learned I could add new components to the box and upgrade it (remember AST memory cards, and the absolutely state of the art 10 Mb Hardcard hard drive, which plugged into the motherboard bus, like other add on cards?).

Still have that box, but most items in a disassembled state - got rid of the full height floppys, but wish I had kept them - was hoping to reassemble that box someday, but probably will just get rid of it to make space ............

I jumped up to a 386/66 next, where I installed OS/2 for the first time - v2.0 (missed v1.3), then v2.11, Warp 3, Warp 4 (added all the fixpacks, which came on the new 1.44 Mb 3.5" disks - sometimes 16 or so of them), then on to eCS and now ArcaOS,

Along the way I learned how to build computers from components, setup and run a network, connect first with a 28 K modem, then 56 K (remember Compuserve and Golden Compass for OS/2?) then on to ADSL, Satellite and where we are today.

So about 25 or so Desktops, Towers and portables later here I am - still a hardware geek, but one that has covered the entire history of the PC line, IBM or otherwise.

So yes, its amazing that we marvel at 94 Mb being small, given where we've come from ............

M

Vincit Que Se Vincit - "He Who Conquers Self Succeeds"

Wim Brul

  • Sr. Member
  • ****
  • Posts: 279
  • Karma: +23/-0
    • View Profile
    • Wim's home page
Re: DOS VDM - USB and Game port Gamepad support
« Reply #304 on: June 16, 2022, 05:26:06 pm »
Hi Mark,

Quote
The only problem I foresee with that, Wim, is that you may be literally inundated with data from all sides, and it may overwhelm in that sense. You have already done a lot for this project, and being overwhelmed is the last thing we want, because, strangely you also have a life.

Thank you Mark, for your compassion. Right now I am already grinding to a standstill. This is all too much for me to handle. In light of my health I have to let go.

Will send you an email soon.

Best regards, Wim.

Mark Szkolnicki

  • Sr. Member
  • ****
  • Posts: 286
  • Karma: +15/-0
    • View Profile
Re: DOS VDM - USB and Game port Gamepad support
« Reply #305 on: June 17, 2022, 04:02:07 am »
Thanks Wim, for your contribution to this.

Hi Mark,

Quote
The only problem I foresee with that, Wim, is that you may be literally inundated with data from all sides, and it may overwhelm in that sense. You have already done a lot for this project, and being overwhelmed is the last thing we want, because, strangely you also have a life.

Thank you Mark, for your compassion. Right now I am already grinding to a standstill. This is all too much for me to handle. In light of my health I have to let go.

Will send you an email soon.

Best regards, Wim.

You've been nothing other than gracious, in both your time, and interest in this small little project, as well as the advances you have contributed to in all areas, including this, based on your technical knowledge.

The least we can all do is say - Thank-you!

We will muddle on, as always, Sir, like the rest of humanity,

Rest, Warrior and Best, as always - will email soon as well!

M
Vincit Que Se Vincit - "He Who Conquers Self Succeeds"