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 - Dariusz Piatkowski

Pages: 1 [2] 3 4 ... 78
Multimedia / Re: Updated Uniaud32 build
« on: September 19, 2022, 06:02:28 pm »
Hi Paul,

...This is VERY helpful! I dug out an old drive with an older copy of my eCS-udrive.vdi and found the source folders for:

A diff of the changes is at

Unfortunately, this is a large-ish diff - I'll have a look for anything obvious when I get a moment - hopefully it will be something obvious...

Edit: 1st attempt - hda_intel.c from 3.9.11 backlevelled to the 3.8.13 version -

Not sure if what I'm seeing here may be in some way related to what Mark is reporting. However, the drop results in a HARD trap while doing MPLAYER playback. So basically while watching any video and attempting to move back or forward causes the sync-up function to eventually freeze and the whole system is non-responsive.

I've attached my current test-matrix, bottom line: I always go back to the 3.16.85 release which has been rock-solid here (this is what's prompting me to ask whether this is similar situation to what Mark is seeing).

I will try this test version next. Thanks, as always!

You already gave the answer: the device is correctly detected at 3:1 but you are forcing to 1:1.
With unpredictable consequences.

Indeed, that was the problem!

I rely on a home-cooked scan REXX script that allows me to pass a whole slew of different option parameters to it, and these are all selected through different SCAN program icons/objects. So in the end it's an easy drop-down/select from the WPS folder.

I suspect in my testing I discovered that I needed that SET statement and eventually just moved it to CONFIG.SYS instead of having it done at the script level.

If there is a comment I'd make, it is the following: SCANIMAGE should fail more gracefully...LOL, yeah, it can't quite stop me from shooting myself in the foot like I did...but something better than a TRP would go a long way to troubleshooing the root cause.

Anyways...FALSE ALARM everyone, my appologies.

Thank you for the talking points b/c that's ultimatley what made me pick up that CONFIG.SYS statement.

Hi Lars!

No the bus number change is intentional.
It used to be hard coded to 1, now it is taking the host controller number (which effectively is the bus number).
The second number is the device number. That should be > 1 though (I am not sure,I forgot). in any case, that is purely cosmetic and not the problem. If someone could send me an exceptq report, that could help to fix the problem...

Hmm...very good, well, at least it's reassuring to know this isn't some kind of un-known that I've ran into.

So here is the output of 'usbtree':

Code: [Select]
USB driver version = 12.13
----- USB device tree ---------
DS 0808=7814

Controller 0: USBEHCD$
Root Hub 0 (5 ports) 1002:4396
Cannot find hub

Controller 0: USBEHCD$
Root Hub 1 (0 ports) 1002:4396

Controller 0: USBEHCD$
Root Hub 2 (0 ports) 1002:4396

Controller 0: USBEHCD$
Root Hub 3 (0 ports) 1002:4396

Controller 0: USBEHCD$
Root Hub 4 (0 ports) 1002:4396

Controller 0: USBEHCD$
Root Hub 5 (0 ports) 1002:4396

Controller 0: USBEHCD$
Root Hub 6 (0 ports) 1002:4396

Controller 0: USBEHCD$
Root Hub 7 (0 ports) 1002:4396

Controller 0: USBEHCD$
Root Hub 8 (0 ports) 1002:4396

...and I've attached a quick screenshot of the Hadware Manager window showing the HP Scanner and the remaining USB ports.

...The other thing that you could do is to do a "SET LIBUSB_DEBUG=255" and pipe stderr to a file. That'll give detailed info of what Libusb is doing.

I've attached the sane LOG files I was attempting to u/l to the GitHub ticket. The TRP file is in there as well.

Now, here is an interesting part that I had ran into, found the following lines in my CONFIG.SYS:

Code: [Select]
SET SANE_CONFIG_DIR=g:\etc\sane.d
SET SANE_DEFAULT_DEVICE=hp:libusb:001:001


...and now I suspect that the "SET SANE_DEFAULT_DEVICE=hp:libusb:001:001" is the actual PROBLEM here!!!

There is a reason why I had set this up...I did this at the time that I moved to RPM based SANE setup, previously I had a separate ZIP based install.

Soooo....let me take a shot at this by figuring out why I would have used that SET statement and then re-running with the latest USBLIB1 1.0.24 drop to see if that's perhaps what has caused the problem.

Damn...nice...thank you for asking the questions...normally I look through CONFIG.SYS to rule out any of such customizations, but clearly in this case I missed that step.


Good job I changed all my scanners to be network based ones after scanimage stopped working on my usb based unit.  The big advantage with this is the fact I can get PDFs direct from the scanner as well as pictures.

LOL, you know, when that failure took place I went to my "Plan-B", which is the little WiFi HP Envy printer/scanner (that does JPG & PDF formatted scans), but I do prefer my dedicated HP scanner otherwise.

By the looks of it the new libusb1 DLL is misidentifying the USB "bus" that device is connected on: '003:001' vs '001:001' (which worked before). So maybe it's an easy fix? We'll see...

Hey Tom!
I went ahead and opened a NEW Issue, but great GitHub functionality prevents you for actually uploading any LOG files...LOL!!!

You could try uploading that logfile as a textfile with the .txt extension.

Actully did try that already, initially I was attempting to u/l them individually (to make it easier to look through), but when that failed I tried the ZIP way.

Anyways...I think this is that whole GitHub "totally unfriendly to anything but Chrome" issue.


Just a quick FYI, I'm seeing a trap in SCANIMAGE.EXE following the deployment of libusb1 1.0.24 RPM package.

My scanner is USB attached, latest AOS drivers and was previously successfully using 1.0.21-2 release.

I went ahead and opened a NEW Issue, but great GitHub functionality prevents you for actually uploading any LOG files...LOL!!!

Anyways, if you're seeing strange results/traps be aware.

Multimedia / Re: Updated Uniaud32 build
« on: August 07, 2022, 05:21:16 pm »
Paul, everyone...

Paul thank you everything except VLC works here too, which may be a problem with VLC

The 'b' version boots up fine, regular sounds plays fine, but I did run into a HARD trap during mplayer playback. Specifically, take a look please at the attached mplayer log, looks like some kind of an error in the 'uninit_ao' module, and since I'm using AO: kai:dart config here (as opposed to uniaudio - which plays no sound at all) I'm not quite sure if this points to an actual uniaud driver problem or not.

I re-tested by going back to the earlier 5.15 drop, that works fine, or at least I was NOT able to reproduce the same TRAP with the same video file.


Hardware / Re: Displayport?
« on: August 06, 2022, 02:58:00 pm »
Hi ivan,

I can't help wondering why people keep on using something designed to prevent phosphor burn in on CRT monitors when it doesn't work on modern LCD panels.  I gave up using a screen saver back in 1990 when I pensioned off my CRT monitor for a 28" LCD unit....

Well, there is still that power use part of the LOL ;) If you want to be either ECO friendly, or wallet friendly, the real DPMS option allows the display to go into power-saving mode...and for my Dell units that's a difference of 30W (operating) vs 0.5W (active-off).

Hardware / Re: Displayport?
« on: August 05, 2022, 04:26:21 pm »
Hi Dave,

I'm afraid I cannot add much in terms of a "fix", but I will say this is interesting because having set up my dual display config here (Dell DU2412M) and being fed by my old trusty ATI X850XT PE, I am dealing with 1 of the units being hooked up through DVI and the 2nd one through VGA.

This is primarily a limitation of the current SNAP drivers, which do not support the ATI card's dual DVI ports to drive matching DVI ports on the display units.

The end result is that the VGA connected 2nd display is a little fuzzier (barely there, but my eyes pick this stuff up, so I can see it) and it does get slightly impacted by the VGA port's 'Pixel Clock' and 'Phase' settings. This sometimes results in that tell-tale noise when you display some dithered colour & texture combinations on the screen. Again, no biggie...but heck, with modern day hardware why suffer like this??? LOL

So point being, I have been meaning to try the monitor's DisplayPort as well, would need to use a DVI to DP connector, etc, but I'm curious how that might pan out?

Multimedia / Re: Updated Uniaud32 build
« on: August 05, 2022, 04:01:57 pm »
Hi Paul,

Updated to 5.15.59 -

Similar to David's experience, I am not getting no SOUND with the 5.15.59 release...HOWEVER, the 5.15 kernel update does work quite fine and unless it's my ears playing tricks on me, the sound seems to have higher quality??? ugh...???

Seriously...fired up PM123 and went through some of my music (eg Phil Collins' "In the Air Tonight", 251 kb/s VBR, 44.1 kHz, Joint-Stereo) and it literally kicks ass!!!

Thank you!

Applications / Re: New builds of Thunderbird and SeaMonkey
« on: July 12, 2022, 03:11:11 pm »
Might be worth trying the GCC10 build from

I think the intent is there, but the latest TB release ( reports itself as:

Code: [Select]
Compiler Version Compiler flags
gcc.exe 9.4.0 -Wall -Wempty-body -Wpointer-to-int-cast -Wsign-compare -Wtype-limits -Wno-unused -Wcast-align -Zomf -std=gnu99 -fgnu89-inline -fno-strict-aliasing -Zomf -fno-math-errno -pthread
c++ 9.4.0 -idirafter K:/usr/include/os2tk45 -Wall -Wempty-body -Woverloaded-virtual -Wsign-compare -Wwrite-strings -Wno-invalid-offsetof -Wcast-align -Zomf -fno-exceptions -fno-strict-aliasing -Zomf -flifetime-dse=1 -fno-delete-null-pointer-checks -Wclass-memaccess -fno-rtti -fno-exceptions -fno-math-errno -std=gnu++0x -pthread -DNDEBUG -DTRIMMED -g -march=pentium4 -mtune=generic -O2 -flifetime-dse=1 -fno-delete-null-pointer-checks -Wclass-memaccess -msse2 -fomit-frame-pointer

So at least my impression here is that this is a GCC9.4.0 build.

Regardless, it appears to be more stable than the previous GCC9.2.0 build ( that would cause some weird hangs in FF.

Not sure why, but for what it's worth, I tried running both ways:

1) leave all the prepackaged DLLs in place
2) remove all the intree NSPR4 and NSS DLLs and use the system-wide stuff that's deployed in \usr\lib instead

In both cases the GCC9.2.0 drop was iffy, but GCC9.4.0 is markedly better.

Applications / Re: Hardware Explorer
« on: July 02, 2022, 11:11:16 pm »
Fixed. A new version:

Thank you S9 is recognized successfully with no impact on the WPS. Appreciate the work!

Maybe I'm getting slow in my old age but I wonder why you are doing a two step operation to get a PDF file - why not go directly to the PDF?

I think Martin is saying that on one of the two systems he has BOTH generating a PS as well as PDF file results in much larger file sizes.

Try what Tom suggest, but you could get there in a slightly easier way:

1) run 'yum history'
2) pick the transaction ID that's closest to the time you think when the problem started
3) run 'yum history info ID', where ID= what you found above

...that will show you the details of what package was updated.

Off Topic discussions / Re: Lying low for a few days
« on: June 22, 2022, 05:14:31 am »
Hi Paul,
Sorry to hear of a good friend leaving!

Have one of my own here, we are pretty close, enough so that my family calls me "favourite human" whenver he's around.

Take care,

Pages: 1 [2] 3 4 ... 78