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 - Lars

Pages: 1 ... 67 68 [69] 70 71 ... 85
1021
Technically yes. I am not sure if there are legal problems. I also wonder if eComStation 1.1 does not also come with the SMP kernel (you would need to search the installation CD).
But just exchanging the kernel is not enough, there are other things like HARDERR.EXE and DOSCALL1.DLL (to name a few) that are specific to the used kernel.
Then there are several fixes to several components to make them work properly with SMP /multiple cores for example TCPIP32.DLL and SOCKETSK.SYS which, in this case, come with the ACPI driver that AN offers.

To be honest, I don't think it makes much sense to use eComStation 1.1 unless you decide to stick to support for only one core in which case the 14.093_W4 and the existing components are sufficient.

1022
Hardware / Re: 122-Key keyboard
« on: October 10, 2018, 07:25:36 am »
That's not how it works. The only thing that USBKBD.SYS does it to transform a USB keycode (that's just a number for a key on the keyboard) to the corresponding "make" and "break" scancodes as defined by some Microsoft table and then send this sequence of scancodes to the legacy mouse driver (AMOUSE.SYS, MOUSE.SYS) which in turn send that to IBMKBD.SYS (I think, I would need to check the code).

It is the job of upper layers to map these scancodes to a keycode (for example by using the KEYBOARD.DCP table).

And that might also be the problem. It is possible that the legacy mouse driver and/or IBMKBD.SYS do not know what to do with the scancodes or the KEYBOARD.DCP table contains no entry for these scancodes.

Fortunately, for PM virtual keys VK_F13 to VK_F24 are defined which gives me some hope that the OS/2 keyboard subsystem at least knows that these keys exist on some keyboards.

1023
Hardware / Re: 122-Key keyboard
« on: October 09, 2018, 11:44:57 pm »
Thanks Lars,

Would the output from LSUSB of the various keyboards be helpful?

That won't be necessary yet (you did already attach lsusb Output for one of your PS/2 to USB Adapters, that's a starting point). The LSUSB Output only Shows the report descriptor which is the structural description of the received data packet(s) but not more.
First I need to find out if the keypresses reach USBKBD.SYS (that is, USBKBD.SYS receives a report with the USB keycode of the key on the keyboard). Then I need to find out if the mapping from USB keycode to PS/2 scancode(s) is done correctly. What happens underneath is that USBKBD.SYS calls the legacy mouse driver (amouse.sys, mouse.sys) with the PS/2 scancodes for "make" (key press) and "break" (key release) for the key. Not all USB keycodes have a defined mapping to PS/2 scancode so let's see where this Ends up ...

1024
Hardware / Re: 122-Key keyboard
« on: October 09, 2018, 01:31:29 pm »
Hi Lars,

Any chance you could send me the modified USBKBD.SYS so I can test it with my USB keyboards with extra keys?

ivan10 at free dot fr

Thanks
If I can get anything to work at all, I am also going to send it to you.

1025
Hardware / Re: 122-Key keyboard
« on: October 08, 2018, 03:40:20 pm »
I found the piece of information I was looking for. I am going to update USBKBD.SYS and send it to you.
Let's hope for the best ...

1026
Hardware / Re: 122-Key keyboard
« on: October 08, 2018, 08:03:04 am »
Hi Neil,

1) how do you query the received scan codes (how did you get the results in the AN ticket) ? If you have written a REXX util, can you post it here ? Do I understand correctly that you get scancodes for the F13-F24 keys only if you directly attach the 122 key keyboard to a PS/2 port ?

2) <quote>SysReq gives no keyboard output on my standard USB keyboard</quote>. So that means, that disregarding the 122 key keyboard you also don't get a scancode for this key on a "normal" keyboard ? Maybe that gives me a chance to find a common cause.


1027
Hardware / Re: 122-Key keyboard
« on: October 07, 2018, 07:05:48 pm »
Neil: Never mind, found your email address. I have sent the updated driver to you.

1028
Hardware / Re: 122-Key keyboard
« on: October 07, 2018, 06:54:48 pm »
Neil: I have a vague idea of what needs to be done. I have now modified USBKBD.SYS to hopefully support the F13-F24 keys. Where do you want me to send you an updated USBKBD.SYS ?

By the way: when you hit Shift-F1 on this keyboard, is this equivalent to hitting SysReq on an ordinary AT keyboard ?

1029
Hardware / Re: 122-Key keyboard
« on: October 07, 2018, 03:49:28 pm »
If I ever find the time, I'll try and read the USB HID specification (https://usb.org/sites/default/files/documents/hid1_11.pdf) plus the HID usage tables doc (https://usb.org/sites/default/files/documents/hut1_12v2.pdf).
These are horrible documents to read but they should give a clue what scancode range the adapter supports.

1030
Hardware / Re: 122-Key keyboard
« on: October 05, 2018, 07:48:15 am »
Maybe I should have read your posts more thoroughly:
Quote
The PS/2 to USB adapter does work for supported operating systems

If that means that say under Windows all keys of this keyboard did work with the PS/2 to USB adapter then my assumption was wrong and it should be possible to support all keys with the USBKBD.SYS driver.

As to what exactly the PS/2 to USB adapter reports to the USB host (computer): maybe you can plug in just the adapter and then run a tool like "lsusb.exe" with the "-v" switch and see what you get back as HID info. I would expect that the OS sees a combination of a keyboard and mouse (plus a generic HID device maybe) even if no such device is plugged into the adapter.

1031
Hardware / Re: 122-Key keyboard
« on: October 04, 2018, 10:42:32 am »
As far as PS/2 to USB conversion goes I wonder if there can be a generic solution. The PS/2 to USB adapter acts as a USB device from the computer's point of view. That said, it should provide all the descriptor info (standard USB device and config descriptors as well as HID device specific HID descriptor) to present itself as a USB keyboard and/or mouse.

But of course, that HID info cannot possibly cover each and every keyboard on planet earth. I would expect that most of these adapters will limit themselves to a MF102 keyboard. And USBKBD.SYS (and USBMOUSE.SYS) can only serve what the USB device reports as being supported.

1032
Article Discussions / Re: Translating ArcaOS to local languages
« on: October 02, 2018, 12:26:27 pm »
Look at "WinSetHook" function.

1033
Applications / Re: VirtualBox v5.0.51 Testing
« on: September 27, 2018, 09:29:32 am »
OK, I'll try to update the wiki. I thought it is evident thing that hardware virtualization is unsupported on IBM's kernels. As it never worked on them and it lacks the "CPU rendez-vous" feature which alows to run code on all CPU cores in parallel. This is essential for enabling AMD-V/VT-x. So, it is experimental feature with OS/4 kernels. Of course, VBox enables it if it finds that it is enabled in BIOS and it is supported by your prosessor. But it cannot check which kernel you have installed.

Hi Valery: I have written a device driver that would do "CPU rendez-vous" to set up "SYSENTER" entry point on all cores, see:
http://hobbes.nmsu.edu/download/pub/os2/system/drivers/misc/syscall.wpi
It comes with full source. It basically issues an IPI to all cores and the cores will then run an interrupt routine, in this case, to set up the necessary MSRs on all cores to being able to use the "SYSENTER"/"SYSEXIT" instructions. This driver works with the standard OS/2 kernel.

I think that you could do about the same to set up virtualization on all cores.

1034
Setup & Installation / Re: network: MMRE driver
« on: September 07, 2018, 08:36:19 pm »
Hi Remy,

no it does not. There is no corresponding setting in the NIF file and therefore switching between these 2 receive modes is not supported.

Lars

1035
General Discussion / Re: Problems booting ArcaOS
« on: August 15, 2018, 04:05:06 pm »
I doubt it has Something to do with broken Harddisk. I am seeing the same Problem Here but it Happens only occasionally. I suspect IT IS yet another SMP issue as I never See this Problem with only one core (which you could try as a Test).

Pages: 1 ... 67 68 [69] 70 71 ... 85