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 - Ibrahim Hakeem

Pages: [1] 2 3
1
Applications / Re: OS/4 (technical details only)
« on: June 14, 2020, 03:48:47 am »
From what I've read, ACPI.PSD 3.23.01 should work with OS4 but before I make the effort of actually trying to retrieve a copy of it.

Yes, as far as I know, 3.23.01 is the latest ACPI.PSD which work with OS/4. It is very likely that you will get the battery widget and ACPI shutdown (I have neither notebook, nor a 3.23.01 to check this).

Duly noted, I currently plan on seeing how I do with ACPI4.BPD but if it ends up being more trouble than it's worth I'll need to hunt down 3.23.01.

I got around to giving it a shot (Many thanks to Lars Erdmann for sending me a copy!), it behaves like it's successfully installed but doesn't actually work.
The battery widget icon doesn't show the E4 error code, but doesn't give any data on the battery's remaining power and states that it failed to load if you double-click on it.
When shutting down, it stalls on a black screen rather than automatically turn off once the shutdown process is complete.

2
Applications / Re: OS/4 (technical details only)
« on: June 04, 2020, 04:35:00 am »
From what I've read, ACPI.PSD 3.23.01 should work with OS4 but before I make the effort of actually trying to retrieve a copy of it.

Yes, as far as I know, 3.23.01 is the latest ACPI.PSD which work with OS/4. It is very likely that you will get the battery widget and ACPI shutdown (I have neither notebook, nor a 3.23.01 to check this).

Duly noted, I currently plan on seeing how I do with ACPI4.BPD but if it ends up being more trouble than it's worth I'll need to hunt down 3.23.01.

3
Applications / Re: OS/4 (technical details only)
« on: May 31, 2020, 01:20:28 am »
I've been using OS/4 for the sake of being able to use Virtualbox + getting a bit more overall out of my T450S. I've absolutely loved how much more useful it's made my environment but my current grievance is the lack of a mostly functional ACPI driver (battery widget, ACPI shutdown, etc).

From what I've read, ACPI.PSD 3.23.01 should work with OS4 but before I make the effort of actually trying to retrieve a copy of it, I was hoping to see if anyone has any input on how well it performs and if I'd be running into any issues due to it being nearly 4 years out.

4
Marketplace / Re: ebay Stuff
« on: May 30, 2020, 03:22:35 am »
Congratulations if anyone here won the item! I had my back turned to my computer on the last minute to tweak with something on my workbench and before I knew it I missed my chance to bid  ;D

5
Applications / Re: Dos window
« on: May 01, 2020, 10:06:37 am »
Hi Rick

Try the .wpi found in this page, it's resolved all my issues with WINOS/2 and DOS on my T450S and other Thinkpads so far.

https://mantis.arcanoae.com/view.php?id=1193

If I'm not mistaken, there's also a commonly used config.sys entry that's helped for others, I can't exactly remember what it is however.

6
I have prepared Yoga12-20200422.zip containing two rexx scripts for you to try out:

1. Run ofinger.cmd in a command window to obtain and show raw finger events. Touch the screen with your finger to see if that works.

2. Run ostylus.cmd in a command window to obtain and show raw stylus events. Touch the screen with your stylus to see if that works.

Thank you for the cmd files

Running ofinger.cmd resulted in the following output:
Code: [Select]
Set Configuration Failed!
The output of ostylus.cmd was:
Code: [Select]
Set protocol failed!

Unfortunately I wasn't able to get any further than this despite following Lars' advice on installing his driver kit and doing my best to make sure config.sys was up to date. I'm currently backing up my system and once that is complete I may do a fresh reinstall and try following the steps on a clean slate - I'm sincerely hoping that may yield better results than what we've been facing so far.

I have also once again attached a copy of my config file for anyone who is interested.

7
Quote
The program is retrying because usbecd.sys reports an i/o error. Please report which USB driver set you are using. Try and use the Lars Erdmann USB driver set.

I am currently using the latest Lars Erdmann driver set (10.234) however seeing this error is still occurring makes me doubt that I have installed it correctly. My procedure was to uninstall all Arca Noae USB drivers using the Warpin installer, then to copy in the files from the Erdmann driver set.

With hindsight, I'm pretty sure this was quite incorrect and I would greatly appreciate having the method of installing these drivers explained to me.

8
Quote
Nice. However, I really would like you to attach UVCVIEW.RAW created from the procedure outlined above (using uvcview without parameter) for me to inspect.

I apologize for not attaching this beforehand, I've uploaded it with this post. From inspecting the file myself I see it is putting out a picture, the UVCVIEW program itself just doesn't display it.



Quote
Strange. Seems to me that in config.sys the $FINGER$ device driver statement is missing or still not correct. Please check again.


I had REM'd the line referring to $FINGER$ before I ran YOGA12.EXE /v. With that corrected the output opens with this:

Code: [Select]
started.
 opening finger
 opening stylus
 opening tablet
 finger configuration

And then loops on this:
Code: [Select]
stylus configuration
 stylus configuration
[0000001D]

9
Hi Ibrahim.

Is the TouchScreen and Pen now working? Can you please share the config.sys so I can update the wiki page?

Regards

Hi Martin. Sorry but neither are still working at this point... I'll update my previous post to clarify that too

10
Quote
Rem out the "RUN=C:\OS2\BOOT\YOGA12.EXE" line in config.sys and reboot. In a command window use "C:\OS2\BOOT\YOGA12.EXE /v" to get debug ouput on stdout. Try and use your pen to see if it is working. Post your results.

The results are as follows:
Code: [Select]
opening finger
[00000003]
stopped.

Still no functionality I'm afraid.

Quote
Perhaps the mjpg decoding in uvcview.exe is not good enough. Click on "Testshot" to capture raw input data. Captured input data is written to the UVCVIEW.RAW file for later inspection. This could be of help in situations where the WebCam Viewer is working but the displayed picture stays black. Post your results. Try uvcview /u to watch yuyv video.
yuyv appears to fix the camera issue entirely, I'm happy to say the camera is now working perfectly. It's a shame I didn't try the /u flag beforehand as it's clearly there in the documentation

11
Quote
As Lars wrote earlier the proper lines for pen and touch are:

Code: [Select]
DEVICE=C:\OS2\BOOT\USBECD.SYS /D:04F3:0254:1112 /N:$FINGER$ /S /V
DEVICE=C:\OS2\BOOT\USBECD.SYS /D:056A:00EC:0131 /N:$STYLUS$ /S /V

With these lines I expect the pen to work. I expect touch not to work because the program expects a different device.

No such luck I'm afraid. I'm still not getting any response from the pen or from normal touch (I even ran an Ubuntu live disk to verify it's not a hardware issue, it's definitely operational).


Quote
The webcam program works with usbcalls.dll and usbresmg.sys and usbecd.sys should not be used for this device.

I'm glad to say I'm no longer getting any error messages, the webcam appears to function with the recording light turning on but I am still met with no video.


12
Hi again.

I haven't tried this, so I don't have much experience, but I see this on your config.sys

Quote
DEVICE=C:\OS2\BOOT\XSMOUSE.SYS
DEVICE=C:\sys\apps\AMOUSE\AMOUSE.SYS STYPE=XSMOUSE$
DEVICE=C:\OS2\BOOT\USBECD.SYS /D:06CB:7244:0005 /N:$FINGER$ /S /V
DEVICE=C:\OS2\BOOT\USBECD.SYS /D:056A:00EC:0135 /N:$STYLUS$ /S /V
RUN=C:\OS2\BOOT\YOGA12.EXE

On the hardware report I don't see the "06CB:7244" device. But on the report I see a "ELAN capacitive 10-point multitouch touchscreen / 04f3:0254".

Do you think you may have to change that on config.sys ??

Regards

I tried editing config.sys to reflect the inaccuracy but unfortunately, still no luck. Thank you for the wiki page but unfortunately the digitizer pen is just as problematic as the finger touch at the moment, neither are currently working.

13
Hi Ibrahim

I always like to document the tests of hardware on ArcaOS and OS/2.
Can you please provide me the Model number of your Thinkpad and the PCI.exe and lsusb report (I got this article explaining how to do that).

My plan is to document your machine also on the OS2World wiki for reference.

Regards

No worries at all Martin, my Thinkpad is a type 20CD and I've got the requested output TXTs attached. Please tell me if there's anything else I can do to help.


Quote
It seems to me that you added amouse.sys to your config.sys whereas you needed to modify the existing amouse.sys device driver statement.

I misread a vital step in your guide and after following it correctly I was able to boot without any errors with the drivers appearing to load correctly... unfortunately touch is still not working. I've also attached a copy of my config.sys because I feel I may be making a trivial mistake without even realizing it. I am also thinking that there might even be a hardware compatibility issue due to this being an older version of the device for which the driver was originally written for...

14
I've decided to give Arca OS a shot on a Yoga S1 which I was recently given and while most of it's been a breeze so far, I've inevitably ran into a few issues which I can't quite get past... In order to avoid going into a ramble I'll list them out as plainly as I can.

>Whilst trying to get the touch screen to function, I've been getting an error during boot stating that amouse.sys is not installed and therefore the line in CONFIG.SYS has been ignored. I am currently using the latest version of the Arca Noae driver. The hardware manager also tells me the driver has been installed however and appears to refer to amouse.sys for AUX_0 PS/2 and MOUSE_0 IBM

>When trying to run UVCVIEW, I am getting the 0000FF14 Obtain Thread error. The webcam light turns on but I receive no picture.

>Audio is working which is a relief, but it seem be playing both through the 3.5mm jack and the speakers. I've used the /A:1 switch as the wiki recommends but the recommended startup.cmd script simply errors out and doesn't seem to do anything useful.

As always, thank you all kindly for your advice.

I'm also currently searching for any solutions that might already exist and will update as I go if I find anything in order to help future users who may run into the same problems.

15
Once again, Neil was correct. I had made the blatant error of not running the zip command from a separate disk. I was able to make a proper backup and restore by using a separate installation

Pages: [1] 2 3