Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Mark Szkolnicki

Pages: 1 ... 18 19 [20] 21 22 ... 29
286
Games / Re: DOS VDM - USB and Game port Gamepad support
« on: December 08, 2021, 03:11:52 pm »
Hi Jochen

lsusb shows the joystick, but SDL2 doesn‘t. Since I don’t use hidapi directly, it have no error message.

Did you compile it yourself or use the one I compiled? Anyways here's the last version I compiled, used a different wcsdup() based on https://github.com/bitwiseworks/libc/issues/118 and hacked to not use iconv(). Test program and diff included.
Edit: fix typo
No, I used the version included in SDL2 with your wcsdup implementation. I'm now trying to compile the included hidapi, and test with that.

EDIT: I used hidtest from your version, but it says it cannot open the device.

BTW: Why do we have a lot wcs function,but not wcsdup?

Have you posted the updated hidapi? Didn't see it attached to any of the posts at the moment, and might want to see if it can see my joystick.

Haven't been following this much, as I've been busy at the moment fixing a sick printer - got a Printer Error 59.99 on my HP3500, which means tearing down the entire printer, to replace about 5 cents of worn padding on a solenoid. Takes about 12 hours ............ tedious work.

I recommend HP service manuals to anyone brave enough to undertake things like this _ very detailed.

Best!

M

287
Hardware / Re: Using a LaserJet 2100m on a Print Server
« on: December 02, 2021, 05:30:11 pm »
Heh Lars!

Why don't you use the SLPR port driver and specify the IP address of the print server (192.168.1.55) as "LPD Server" and "Printer" (without the quotes) as the "LPD Printer" ? That's at least what the DLink config page mandates (if you read through the help for "LPD Printer" you will see that it is the LPR Queue Name that you need to enter).
The use of USB should be completely transparent as long as the USB host implementation in the print server works according to standards.

EDIT: the reason why you don't see a "proper" name for your printer might indeed be related to the USB to parallel port adapter and/or also the printer itself. I suspect that you need bidirectional communication functionality to query a "decent" printer name from a printer. If the printer is very old, it might not support that or the USB to parallel port adapter might not support bidirectional communication. Nonetheless I would hope that at least you can print to that printer with the settings given above.

Tried the SLPR port suggestion and no difference - when ArcaOS sends a print job to the printer it times out with "Printer off-line, jammed or out of paper".

As the tower I'm experimenting on has multiple OS partitions I decided to load a Universal Printer driver on Windows 7 and try that way of printing to the printer. Setting to RAW and port address 9103 and then alternately, setting to LPR and queue "Printer", resulted in neither printing to the HP2100.

So it does seem, Lars, that while this printer can be seen as a device on the D-Link Print Server, it is not accepting any input when a print job is sent to it - I plan to try a couple of other things (different HP2100 compatible device drivers and moving to a different port address on the print server, just in case that port is faulty for some reason) but I suspect its a communication problem, possibly parallel to USB or lack of bidirectional communications as discussed.

After Doug Clark's post, I did look around on eBay and found a plethora of JetDirect 300x print servers for sale at reasonable prices, some still new in the box, so I may try the parallel direct to network possible solution just for interest - if it doesn't work at least it will be a cheap learning experience.

But thanks for the suggestions, Lars, and to Dariusz as well. I will report back if I purchase a JetDirect 300x, or if I find anything else interesting occurs.

But a fine day to all, gentlemen, and Best!

M


288
Hardware / Re: Using a LaserJet 2100m on a Print Server
« on: December 01, 2021, 08:03:32 pm »
Heh Lars!

By "old printer", I do not mean "bad printer". It's just that bidirectional communication with a printer was not standard when printers with parallel ports were first built.

Never took your comment in that way in the least, Lars - I think the 2100m may resemble that remark, related to lack of bi-directional communication.

Setting up SLPR as we speak, and Best!

Mark

289
Hardware / Re: Using a LaserJet 2100m on a Print Server
« on: December 01, 2021, 04:05:50 pm »
Hi Lars!

Why don't you use the SLPR port driver and specify the IP address of the print server (192.168.1.55) as "LPD Server" and "Printer" (without the quotes) as the "LPD Printer" ? That's at least what the DLink config page mandates (if you read through the help for "LPD Printer" you will see that it is the LPR Queue Name that you need to enter).
The use of USB should be completely transparent as long as the USB host implementation in the print server works according to standards.

EDIT: the reason why you don't see a "proper" name for your printer might indeed be related to the USB to parallel port adapter and/or also the printer itself. I suspect that you need bidirectional communication functionality to query a "decent" printer name from a printer. If the printer is very old, it might not support that or the USB to parallel port adapter might not support bidirectional communication. Nonetheless I would hope that at least you can print to that printer with the settings given above.

Thanks for the info!

A LaserJet 2100m is indeed an old printer, but still works perfectly at least in internal printout tests - have had it lying around for a number of years and as the 3500 requires 4 cartridges to print, and the 2100 only one, I thought it would be interesting to get it running if I only need Black and White output around the office. At the moment I'm exploring a lot of things, as you probably have seen from various posts.

As to the cable supporting bidirectional communication, I can't say, Lars - most parts of that nature don't have a lot of specs as to the nature of their functionality. I assumed that was the case when it was purchased, but we all know what "assume" means.

Will try the SLPR approach and see what happens.

BTW, thats a very interesting discussion your having on the DOS VDM topic line. Not being a programmer, but being interested in hardware tech for decades, that topic line is teaching me a lot about the nature of USB and the programming involved.

Have never tried your USB driver set implementation in the past, but am putting it on my "to do" list in future, for experimentation. Have noted what you were doing, but will have to read up on what you have done differently, in comparison to the ArcaOS standard USB.

Best and a fine day to you, Sir!

Mark


290
Hardware / Re: Using a LaserJet 2100m on a Print Server
« on: November 30, 2021, 07:35:06 pm »
Heh Dariusz!

Nice to hear from you today!

Quote
So what I'm thinking is that your D-Link Print Server should be exposing the attached printers through some kind of interface that differentiates the printers from each other. By the looks of it, that difference is the port# that the printer is going to respond on.

My Brother has a NIC with a print server built in, which means that my OS/2 setup is using a SLPR port driver to point to the printer's IP address (which would be your D-Link Printer Server IP address I believe) and a specific interface, which in the attached photo is the 'LPD printer' field, and for you that is probably going to be the printer's port number.

In my case I'm using the BINARY_P1 service of Brother's built-in print server.

Worst case, given that your D-Link Printer Server is at 192.168.1.55, you could point the SLPR port driver to 192.168.1.55:9103 and perhaps look to see what service names (if any) are exposed and can be used in the 'LPD printer' field.

In the case of the print server, you are correct Sir.

One static IP address for the print server which I set up on my wired network (192.168.1.55) with 4 port addresses, of which:

9100 - print address for the HP 3500
9101 - print address for an Epson 1280 Color Photo Stylus (was not on when the picture was taken - see my post to Doug)
9102 - I have a scanner connected but not in use, as I scan in other ways)
9103 - print address for the HP 2100

I'll have a look at your attachment with interest.

I suspect from the replies, that the problem is either:

1) The parallel to USB adapter not communicating with the print server, hence ArcaOS not being able to address the printer, no matter what driver I've set-up, or

2) Not using the correct Queue Name for the printer (a problem I had setting up the HP3500 originally)

I'm leaning towards 1) at the moment, and may try the JetDirect solution first, if I can get one at a reasonable price as it would only mean connecting another device to my router array.

But I will be interested in what you sent Dariusz, as it may twig something else in my laterally thinking brain and Best!

M

291
Hardware / Re: Using a LaserJet 2100m on a Print Server
« on: November 30, 2021, 07:14:23 pm »
Hi Doug!

Thanks for the reply

Quote

Your D-Link not recognizing the printer might be the usb to parallel adapter.


I actually was thinking that - I've has some successes with USB adapters and a lot of situations where items are not recognized under ArcaOS. I've been following Lars's current conversation on another topic thread about root and chained USB hubs with interest as well, to see if that might have some bearing on the problem, based on our implementation of USB support. A lot of food for thought at the moment.

As CUPS has a driver for an HP 2100m I've tried that, but haven't gone back to the drivers that originally came with OS/2. I suspect if the printer port is reporting the printer as "unknown" it also may not work, as it may be a communications problem as you pointed out. But never hurts to try.   

Quote

I don't know if your network is all wireless, or partly wired.  If it is wired, or you have an ethernet port close to where you want to put the printer, you could try an HP Jet Direct 300x print server.  I use that to connect an HP 4000 and HP 1320  laserjet to my network.  They are currently selling for $12 on ebay without an adapter and $45 with a power adapter.  (It accepts a 9 - 35 volt DC adapter)

The nice thing about the Jet Direct 300x is that it interfaces with HP Jet Admin - which installs a network port for talking to the print server.  Jet Admin can even show what is being displayed on the printer panel.  OS/2 comes with a printer driver for the HP 2100 driver, or you can use any PCL or PS driver (if the printer recognizes postscript) and then use the Jet Admin/Jet Direct port to talk to the printer.  Jet Admin can talk to HP printers through Jet Direct that it does not recognize - as shown in one of the attachments.


The D-Link has worked well for many years, and is a USB device - I actually switched to this one about ten years ago as when I got the 3500, it could only be USB connected - a previous D-Link Print Server I had actually was parallel port and the 2100 worked perfectly on it. I actually did not mention that I have a third printer on the current print server, which was not on when I snapped the picture - its an Epson 1280 Photo Stylus printer which also works perfectly but currently is down due to not using it for awhile, causing the printer head to clog.

My network is a combination of wired and wireless - towers and printers are connected via cat5 cables and routers and the set-up also includes one router which has a wireless function, so that our portables have a gateway to use the attached devices as well.

As to the Jet Direct Print server I might look into that - being up in Canada (don't know where your located, Doug - you may be up here too) I've found that most used equipment is being offered by sellers based in the states. And as a result buying on eBay can be rather interesting lately - something might be listed for $12.00 US, but then for some strange reason they may want to add $40-50 US in shipping charges to Canada, which is outrageous (you'd think we're on another planet).

But a couple of interesting suggestions I will examine, Sir! Thanks for the input and Best!

M






292
Games / Re: DOS VDM - USB and Game port Gamepad support
« on: November 25, 2021, 07:33:14 pm »
Hi Again Wim!

Quote
As the Thrustmaster Joystick I have really is defined by Mode 2 only, I would suggest that I will reset the adapter to a static Mode 2, and we should concentrate efforts on that mode only, as I do not have any other equipment which may meet the other definitions, for test purposes, and I am not sure anyway if DOSBOX would recognize Mode 1 and 4 configurations, as they were not defined in any of the legacy DOS games I am aware of.

Right you are. Which brings me to the question what efforts to concentrate on. I have enough information to process the input report data.

There are still 2 ways to support USB gamepads/joysticks (one  being thru GAMEVDD.SYS/ GAMEPDD.SYS and the other thru HIDAPI to DOSBox) and I think both should be working. I have enough information to try and modify GAMEPDD.SYS to work with your Thrustmaster Joystick. This will take some time and effort for me to accomplish. For starters I am thinking of an ioctl interface for gamepads/joysticks into GAMEPDD.SYS to be used by some program that uses USBECD.SYS to access your Thrustmaster Joystick. When I succeed then perhaps this could also be an alternative way for DOSBox to be used. Although for DOSBox it is better that someone gets HIDAPI to work well.

I had a look at your output analysis and it looked like you were playing a game of Tic-Tac-Toe <grin>

Personally I doodle thoughts when I'm doing a project - I've done some graphics design so many times I think in pictures.

Putting my project management hat on, I was suggesting a simple proof of concept to start, to see if we can get things talking.

If you think Dave's current port of HDIAPI would work perhaps the way to go would be that method, if we could also get it talking to DOSBox. Or being able to address a simple CMD style calibration program natively in ArcaOS (symbols or numbers appear when the joystick is manipulated, or button pressed)

Again being a programming expert (IOW you didn't duck fast enough when the job was suggested) in your opinion, would either of those types of suggestions be limited intensity in terms of effort?. Or can you suggest from your paths above a simple method to test whether we're getting the joystick recognized?

Looking at both methods you suggested, I will have to say that there are limited ways to test joysticks under ArcaOS natively at the moment, and most likely in future (Stardock used to retail a program called Trials of Battle which I do have but not loaded on my systems at the moment, which I could get running again)

As per discussion DOSBOX is supposed to recognize a joystick if the host operating system does and the device conforms to the specifications noted previously, which would be why the HIDAPI option may be attractive - I have at least 12 DOS flight and warfare games (eg. Mechwarrior) running through DOSBOX now, with Joystick capability, which may be candidates to see if that option may work.

Unless you think this will be fun and challenging, and yet another interesting test of USBECD capabilites, I'm not trying to fob a job off on you - would do it myself if I had the programming skills.

There's an old quote attributed to Pliny the Elder, Wim, which I have taped on the wall above my screen "Age takes on things that youth will not do, because they say it will take too long"

A fine day to you Sir and Best!

Mark


293
Games / Re: DOS VDM - USB and Game port Gamepad support
« on: November 25, 2021, 03:56:44 pm »
Hi Again Wim!

Quote
As the Thrustmaster Joystick I have really is defined by Mode 2 only, I would suggest that I will reset the adapter to a static Mode 2, and we should concentrate efforts on that mode only, as I do not have any other equipment which may meet the other definitions, for test purposes, and I am not sure anyway if DOSBOX would recognize Mode 1 and 4 configurations, as they were not defined in any of the legacy DOS games I am aware of.

Right you are. Which brings me to the question what efforts to concentrate on. I have enough information to process the input report data.

There are still 2 ways to support USB gamepads/joysticks (one  being thru GAMEVDD.SYS/ GAMEPDD.SYS and the other thru HIDAPI to DOSBox) and I think both should be working. I have enough information to try and modify GAMEPDD.SYS to work with your Thrustmaster Joystick. This will take some time and effort for me to accomplish. For starters I am thinking of an ioctl interface for gamepads/joysticks into GAMEPDD.SYS to be used by some program that uses USBECD.SYS to access your Thrustmaster Joystick. When I succeed then perhaps this could also be an alternative way for DOSBox to be used. Although for DOSBox it is better that someone gets HIDAPI to work well.

Currently, Dave Yeo could answer to this better than I, as he did the port, but I don't believe that he has a full implementation of HIDAPI up and running. His exact words were:

Quote
Meanwhile, I managed to compile hidapi but it seems there is something missing, possibly in my attempt at wcsdup(), the version I found on the net originally used strlenW() which we don't have, so I changed it to wcslen().

Here's the DLL and the test program in the lib directory, needs libusb100.dll, the libusb1 package, and the devel package to build. My patch against the github source also included, after patching run "sh bootstrap", "sh configure" then make.

I did try what he had ported so far, as mentioned previously, and running his test program was able to identify the joystick in Mode 3 on the adapter - I expect if I reset to Mode 2 as mentioned previously and keep it there, it would report that.

Will have a look at your input report data, Wim and see if any lateral thinking comes to any conclusion, one way or the other. Being a troubleshooter by professional, I can't provide technical specifics to you software programming types, but I can ask some really stupid questions - and occasionally that twigs flashes of brilliance in others ......... !

I was hoping that we weren't putting you to a lot of work, unless you find this fun and a challenge. As always, if I can test something for you, as with Dave or any others, I can at least provide feedback, and hopefully useful feedback.

Best!

M

294
Games / Re: DOS VDM - USB and Game port Gamepad support
« on: November 25, 2021, 03:30:54 pm »
Hi Wim!

Just starting my day - 0730 in Alberta.

M

295
Games / Re: DOS VDM - USB and Game port Gamepad support
« on: November 25, 2021, 06:00:43 am »
Hi Wim!

Quote

There is a 4 position switch on your device and it is my understanding that this switch corresponds to 4 different idProduct values.
Dependent upon the switch setting used (1, 2, 3, 4) I expect your device to report idProduct 2030, 2031, 2032, 2033 respectively.
This way oinput.cmd would work for all 4 switch settings and the actual hid input report obtained would vary accordingly.

Please obtain the lsusb report for each of the 4 switch settings of your input device.

Please try and run oinput.cmd for each of the 4 switch settings of your input device.


Completed my current tests successfully and have further to report.

After setting the USB2.0 to Gameport Adapter to each of Switch Modes 1-4 using the methodology I identified in my previous post, I have identified to use of each:

Mode 1: reports the device attached as a 2-axis, 4 button joystick w/view finder (hat), and rudder

Mode 2: reports the device attached as a 4-axis, 4 button joystick w/view finder (hat) (this is the configuration of the Thrustmaster Joystock I have)

Mode 3: reports the device attached as a 4-axis, 4 button joystick

Mode 4:  reports the device attached as a 2-axis, 8 button gamepad

I have attached the lsusb hardware reports of all four modes, as well as the associated oinput.cmd outputs.

As the Thrustmaster Joystick I have really is defined by Mode 2 only, I would suggest that I will reset the adapter to a static Mode 2, and we should concentrate efforts on that mode only, as I do not have any other equipment which may meet the other definitions, for test purposes, and I am not sure anyway if DOSBOX would recognize Mode 1 and 4 configurations, as they were not defined in any of the legacy DOS games I am aware of.

I have not had a look at the hex information presented for the various inputs which may be provided by the Joystick, as I have been doing other things in addition to the testing - will have a look tomorrow and may provide further comments.

In the meantime, best to you Wim and a fine day!

M

296
Games / Re: DOS VDM - USB and Game port Gamepad support
« on: November 25, 2021, 02:27:37 am »
Hi Mark,

Quote
Device= ?:\OS2\BOOT\USBECD.SYS /D:0583:203#:0110 /N:$THRUST$
.
I'm interested as to why that syntax was used, as I'm sure other people would be.
.
(I think we are all learning programming in this exercise)
There is a 4 position switch on your device and it is my understanding that this switch corresponds to 4 different idProduct values.
Dependent upon the switch setting used (1, 2, 3, 4) I expect your device to report idProduct 2030, 2031, 2032, 2033 respectively.
This way oinput.cmd would work for all 4 switch settings and the actual hid input report obtained would vary accordingly.

Code: [Select]
EC18000081030700 | 04000F4956FF6E | EE
EC18000081030700 | 04000F4A94FF6E | EE
EC18000081030700 | 04000F9250FF6E | EE
On each line, between the | characters, you see the actual hid input report data in hexadecimal.

Code: [Select]
04 | 00 | 0F | 49 | 56 | FF | 6E
B  | 00 | H  | X  | Y  | Z  | S
B=button, H=Hat, X=X-axis, Y=Y-axis, Z=Z-axis, S=Slider

Please obtain the lsusb report for each of the 4 switch settings of your input device.

Please try and run oinput.cmd for each of the 4 switch settings of your input device.

Wim

Hi Wim!

Have done some testing, and this is what I have found so far.

I ran lsusb using your statement in CONFIG.SYS
Device= D:\OS2\BOOT\USBECD.SYS /D:0583:203#:0110 /N:$THRUST$
(specific to my ArcaOS configuration)

And lsusb always came back, despite what mode was switched to as product ID 2032 (USB Nest Mode 3)

And your oinput.cmd essentially generated the same output.

I believe that there are only two types of thinkers generally, Wim - linear thinkers (just follow instructions to the inevitable conclusion) and lateral thinkers (the second ask things like "what do Babylon and Babe Ruth in an encyclopedia have to do with each other?) so I just didn't blindly follow the instructions - I went back to the beginning.

I modified CONFIG.SYS again to remove the /D and /N statements, rebooted, and four times ran your USBREAD.CMD after inserting the LogiLink adapter each time, with the switch setting changed from Mode 1 to 4, to generate the output.

(See the attached Logilink Mode X Test usbreadinsert.JPG files)

And you were correct - four different USB productID's were generated - however, despite the statement contained in the CONFIG.SYS and whatever switch configuration was tested, it would always default to the one that was plugged in last. (in the final case the Mode 3 switch setting and ProductID 2032 on the adapter).

To undertake the testing required, I will have to:

1) Remove the current CONFIG.SYS /D and /N switches from the driver statement and reboot.
2) Run USBREAD.CMD again, plugging in the adapter each time.
3) Put the /D and /N statements back, and
4) Run the tests for each mode again

I'm not concerned about the steps involved - will just require additional time - I expect that using this device (ie. the adapter) is an extraordinary case, given four modes involved.

In the past I have used Mode 2 (and that Mode switch setting) to use the Joystick, but will attempt to generate all four and Best!

M

297
Games / Re: DOS VDM - USB and Game port Gamepad support
« on: November 25, 2021, 12:11:42 am »
Hi Mark,

Quote
Device= ?:\OS2\BOOT\USBECD.SYS /D:0583:203#:0110 /N:$THRUST$
.
I'm interested as to why that syntax was used, as I'm sure other people would be.
.
(I think we are all learning programming in this exercise)
There is a 4 position switch on your device and it is my understanding that this switch corresponds to 4 different idProduct values.
Dependent upon the switch setting used (1, 2, 3, 4) I expect your device to report idProduct 2030, 2031, 2032, 2033 respectively.
This way oinput.cmd would work for all 4 switch settings and the actual hid input report obtained would vary accordingly.

Code: [Select]
EC18000081030700 | 04000F4956FF6E | EE
EC18000081030700 | 04000F4A94FF6E | EE
EC18000081030700 | 04000F9250FF6E | EE
On each line, between the | characters, you see the actual hid input report data in hexadecimal.

Code: [Select]
04 | 00 | 0F | 49 | 56 | FF | 6E
B  | 00 | H  | X  | Y  | Z  | S
B=button, H=Hat, X=X-axis, Y=Y-axis, Z=Z-axis, S=Slider

Please obtain the lsusb report for each of the 4 switch settings of your input device.

Please try and run oinput.cmd for each of the 4 switch settings of your input device.

Wim

Good Afternoon Wim!

I actually realized what you mentioned related to the mode switch in an inadvertent way.

Dave Yeo has been experimenting with the hidapi libraries, and installing his ported version of them and running his test file I got a product ID of 2032 back, not 2031. Running lsusb it gave a descriptor of the adapter as being USB Nest (mode 3) where previously it was USB Nest (mode 2).

I will attempt to run the tests you noted, with the various configuations, but probably will not be able to do all the configurations today or tonight,. so will try to feed you data as I complete each stage.

Best as always!

M

298
Games / Re: DOS VDM - USB and Game port Gamepad support
« on: November 24, 2021, 04:46:25 am »
Meanwhile, I managed to compile hidapi but it seems there is something missing, possibly in my attempt at wcsdup(), the version I found on the net originally used strlenW() which we don't have, so I changed it to wcslen().
Here's the DLL and the test program in the lib directory, needs libusb100.dll, the libusb1 package, and the devel package to build. My patch against the github source also included, after patching run "sh bootstrap", "sh configure" then make.
Tried my Sons XBox controller which wasn't detected. Then his Logitech Dual Action gamepad which was detected. First 2 entries are my unified keyboard/mouse controller, 3rd is his gamepad.
Code: [Select]
H:\tmp\hidapi\lib>hidtest.exe
hidapi test/example tool. Compiled with hidapi version 0.11.0, runtime version 0.11.0.
Compile-time version matches runtime version of hidapi.

Device Found
  type: 046d c534
  path:
  serial_number: (null)
  Manufacturer: (null)
  Product:      (null)
  Release:      2901
  Interface:    0
  Usage (page): 0x6 (0x1)

Device Found
  type: 046d c534
  path:
  serial_number: (null)
  Manufacturer: (null)
  Product:      (null)
  Release:      2901
  Interface:    1
  Usage (page): 0x6 (0x1)

Device Found
  type: 046d c216
  path:
  serial_number: (null)
  Manufacturer: (null)
  Product:      (null)
  Release:      300
  Interface:    0
  Usage (page): 0x4 (0x1)

unable to open device

I guess the serial number etc should be filled in? Perhaps the Usage (page) is good enough for SDL?

Yup, weird times indeed, Dave - was 9 C here yesterday and had an abnormal temperature trend here all day today - started at 2 C this morning - was -15 C at 16:00.

Just downloaded and tested your hidapi - attached a JPG of the output  - 0583:2032 is the Logilink USB2.0 to Gameport adapter with Thrustmaster Joystick attached - will have to run lsusb to see what the other device was that was detected.

Best!

M

299
Games / Re: DOS VDM - USB and Game port Gamepad support
« on: November 24, 2021, 04:24:29 am »
Hi Mark, you might be able to capture the output by redirecting stdout/stderr,
Code: [Select]
oinput.cmd 2>&1 | tee oinput.log

Thanks Dave!

Did get enough, I think to suit Wim's requests, I think with |more - will try that next time.

And how is things going near Abbotsford? Relatives of ours reported they are short of supplies (milk, food, fuel) near Chiiliwack. And we hear more storms are coming ............ !

Best!

M

300
Games / Re: DOS VDM - USB and Game port Gamepad support
« on: November 24, 2021, 03:15:45 am »
Hi Mark,

I understand your explanations. Thank you. We will take the step by step approach.
I have prepared oinput.cmd that hopefully obtains input from your LogiLink adapter.

Run oinput.cmd and operate your ThrustMaster for a few seconds.
When it works you will see something like below to appear.

Code: [Select]
EC100000810306000100000000FFEEEE
EC180000810306000100FEFFFF00EEEE
EC100000810306000100FFFFFF00EEEE
EC18000081030600010000000000EEEE
EC100000810306000100FFFFFF00EEEE

Please post your output with a description of your actions.

Have fun,

Wim

Hi Wim!

As to fun .............. playing with toys is always fun ........... sure beats cleaning up spills or evacuating people........

I downloaded your file, and undertook the following:

1) created a new /sys/gametest directory on one of my ArcaOS partitions, on the system where I had installed the Thrustmaster Joystick. Copied oinput.cmd into that directory.

Test 1

Ran oinput.cmd the first time from a command prompt and got:

required direct control driver
Device= ?:\OS2\BOOT\USBECD.SYS /D:0583:203#:0110 /N:$THRUST$
not defined in CONFIG.SYS file

(See attached oinput_test001.jpg)

I modified the CONFIG.SYS, to add the /N: descriptor and rebooted.

Test 2

Ran oinput.cmd again

This time the response was:

sys0031: A device attached to the system is not functioning
(See attached oinput_test002.jpg)

In this case I was testing to see whether you had had a typo, as the output that came back previously was:

Device= ?:\OS2\BOOT\USBECD.SYS /D:0583:203#:0110 /N:$THRUST$

As the device USB ID I had posted was 2031 and yours was 203#, I wanted to make sure that was indeed what you wanted in the CONFIG.SYS

I'm interested as to why that syntax was used, as I'm sure other people would be.
(I think we are all learning programming in this exercise)

I modified the CONFIG.SYS again and rebooted.

Test 3

After adding the octet (#) instead of (1) and running oinput.cmd again, the output was a static variation of what you described (see oinput_test003.jpg below):

Multiple rows of:

EC1800008103070000000F4956FF6EEE

I assumed you were attempting to address either the adapter or the Joystick, somewhat like a "ping" to see if your could contact the device. Did not adjust the joystick just left it in place so got that one data point which continued endlessly until I closed the prompt window.

Test 4

Ran oinput.cmd again, this time moving the joystick.

This test was a little harder to do, to capture the output, as the output moves so fast down the ArcaOS prompt window - used the |more command as I was moving the joystick. Output is as attached (oinput_test004.jpg).

This time there was changes to the output, as multiple data points were noted. I tried the same test as well with both the hat and the 4 buttons. but no data point changes were noted.

Hope this was what you were looking for, Wim.

I am usually checking messages until about 21:00 MST each day - if you would like any further information tonight my time, please contact me and Best!

M

Pages: 1 ... 18 19 [20] 21 22 ... 29