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 ... 86
1021
Storage / Re: Chkdsk log formatter
« on: October 27, 2018, 11:49:14 pm »
It might be possible that it will still start. But you will no longer be able to run chkdsk to clear up any potential errors because chkdsk.exe will abort operation if it finds something wrong with the transaction log.
That's really unfortunate (I think it would be better if chkdsk completely wiped the transaction log if it gets corrupted).
But now you might have some lurking errors. I had the very same, including these unexpected system restart. I never realized there was something wrong with my JFS partition (because the transaction log was fine) until I finally ran chkdsk /F:3 from another partition.  A whole bunch of errors turned up and I had about 400 MB of crosslinked files (fortunately, that was basically a source file tree that I had cloned from a GITHUB repo which I could just reget).
But after that, the JFS partition was in an errorfree state.

The only thing I can suggest is that you save the files to another partition/media and reformat the JFS partition.

1022
Storage / Re: Chkdsk log formatter
« on: October 27, 2018, 05:38:49 am »

1023
Applications / Re: VirtualBox version 176 compiling/testing
« on: October 27, 2018, 05:08:27 am »
I am pretty sure that C/C++ does not allow the hyphen in symbol or macro names or defines. Only underscore allowed.
At least I have never ever used a hyphen.

1024
Storage / Re: Chkdsk log formatter
« on: October 25, 2018, 11:59:20 am »
The chkdsk log ("Unrecoverable error writing M to d:. CHKDSK CANNOT CONTINUE.") means that your JFS transaction log is broken which is really bad news because I think that is non-recoverable.

The "M" should really spell "Metadata" but this is some problem either with the tool or with the JFS transaction log.
There had been a bug report for this in either the AN or the eCS bugtracker.

1025
Hardware / Re: acpistat tells me that I need apm.add
« on: October 18, 2018, 01:03:07 pm »
The acpistat output is meant to be read this way:
1) Hopefully all (relevant) drivers have ACPI suspend/resume support. In that case, you would not need to load APM.ADD.
2) If one or more drivers neither support ACPI nor APM suspend/resume support, the acpistat tool will tell you "This system will not support suspend/resume as configured." if you have properly loaded APM.ADD.
3) If you do not load APM.ADD you will instead get the "Failed to communicate with APM.ADD. Results may not be accurate." message. Of course, in that case, the APM suspend/resume support will definitely not work even if the drivers report that they would support the APM suspend/resume method. APM.ADD is a mandatory component to support APM suspend/resume.

So, if you get ""This system will not support suspend/resume as configured." that will tell you that you have set up everything correctly but unfortunately, there is at least 1 driver that does not support suspend/resume at all (neither ACPI nor APM). Don't ask me what drivers acpistat picks to examine suspend/resume support, obviously it does not query each and every driver but only drivers that it claims to be vital to support suspend/resume.

You can now go ahead and still try to suspend/resume but as others have pointed out it is likely to fail. On my system, I can drive it into suspend but it will never wake up again, no matter what I try.

1026
Applications / Re: A button to set window to ideal size
« on: October 13, 2018, 12:50:28 pm »
So what is the criteria to again set a new "ideal" size and position ? Do you want the user to select a specific menu item ? Do you want him to press a key combination ?

As Neil said, the API already exists (WinStoreWindowPos, WinRestoreWindowPos, storing to and restoring from OS2.INI).
The only problem is on what occasion you would invoke these functions.

1027
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.

1028
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.

1029
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 ...

1030
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.

1031
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 ...

1032
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.


1033
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.

1034
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 ?

1035
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.

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