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 ... 71 72 [73] 74 75 ... 96
1081
Multimedia / Re: SYBA USB Stereo Sound Adapter: Good or bad?
« on: May 24, 2019, 08:18:40 am »
Unfortunately the USBRes output is broken (the tool is broken).

My guess is that it is an USB audio standard 2.0 device in which case you will need the USB audio drivers from my USB package. There is a USBAUD2.SYS driver that will serve those devices.

1082
Web applications / Re: Firefox and youtube
« on: April 15, 2019, 09:25:11 am »
Hi André, it is actually the symbol in the icon that is trademarked. The rules are here, https://www.mozilla.org/en-US/foundation/trademarks/distribution-policy/ which clearly states that we can't distribute the Firefox branded web browser.

Hi Dariusz, yes the icon is compiled into firefox.exe as a resource and can't be easily changed.

Normally you should be able to use resmgr (comes with eCS and also AN) and pull the resources from the exe.
Then, you can replace the icon and use "rc.exe" to readd the resources to the exe (the whole resources segment will be overwritten/replaced by rc.exe). But you might need to use LXLITE /X to uncompress the exe before pulling out the resources and after readding you need to use LXLITE to recompress the exe.

1083
Applications / Re: Converting .BOO to PDF ?
« on: April 08, 2019, 09:55:42 am »
Hallo Martin,
Just to lessen your expectations:

the IBM library reader does NOT allow to print the whole document (via a converter to PDF, for example).
For copyright reasons the reader will only print MARKED text. I don't think that is what you want ...

1084
Applications / Re: OS/4 (technical details only)
« on: April 08, 2019, 09:40:14 am »
You should have read the OS/4 kernel readme. It clearly states that in order to use OS4APIC.PSD with the /APIC switch you have to also use ACPI4.BPD. The only alternative to this set up is a patched ACPI.PSD as a replacement for OS4APIC.PSD+ACPI4.BPD (which will never happen as the OS/4 guys need to patch each and every new version of ACPI.PSD in order to make it work with the OS/4 kernel).

In short: if you don't have ACPI4.BPD then you cannot specify the /APIC switch. But if you have working MPS 1.4 tables then you also do not necessarily need ACPI support. One drawback will be that you cannot power off via ACPI (obviously) if you don't have ACPI support.

1085
Programming / Re: OW, JNI (GCC built java 1.6) and parameters
« on: April 07, 2019, 08:46:44 pm »
class LoadLib {
...

public:
    EXCEPTIONREGISTRATIONRECORD *pex;
...
    LoadLib( EXCEPTIONREGISTRATIONRECORD *prec, PSZ pszLibrName = "", PSZ pszLibrPath = ".", bool fpe = true) {
    pex = prec;
    memset(pex,0,sizeof(*pex));
    ...
    pex->ExceptionHandler = ( ERR )fpeHandler;
    DosSetExceptionHandler( pex);
    ...

    ~LoadLib() {
         if (pex->ExceptionHandler)
              DosUnsetExceptionHandler(pex);
     ....


call:

JNIEnv* create_vm(EXCEPTIONREGISTRATIONRECORD *pex) {
    javm = new LoadLib( pex,"client\\jvm" );//, ".", false ); //when used with sqlite3 and cairo
    ...


int main( int argc, char **argv ) {
    EXCEPTIONREGISTRATIONRECORD ex;
    JNIEnv* env = create_vm(&ex);
    ...
    delete javm; <---- your forgot this one ...
    return 0;
}


Just one thing to note: be aware that an exception handler can only be registered for the CURRENT stack frame (and everything called directly or indirectly from this point).
That is, you need to do "delete javm" BEFORE you return from the function where you called "new LoadLibrary". That also means you cannot pass around the LoadLibrary object and then return from the function registering it.

Also be aware that you need to set exception handlers PER THREAD. You cannot do a "new LoadLibrary" and then expect the exception handler to work from another thread (but see above, it's forbidden to pass around the object anyways).



       

1086
Applications / Re: Converting .BOO to PDF ?
« on: April 06, 2019, 02:42:05 pm »
The link I gave contains everything: the DOS version, the Windows version and the OS/2 version.
The files you need (for english) are ios2pen1.exe and ios2pen2.exe.

1087
Applications / Re: OS/4 (technical details only)
« on: April 06, 2019, 02:06:09 pm »
That still does not answer the question why ACPI4.BPD is not bundled with the OS4 kernel package. The kernel package only contains OS4APIC.PSD but not the BPD.
And by now, ACPI4.BPD cannot be found on the OS4 web page any more.
I do have ACPI4.BPD but I don't even remember where I got it from ...

1089
Ok, after having had a private exchange I take it for granted that this problem is fixed in the OS/4 kernel but not in the IBM or AN kernels.

1090
Applications / Re: OS/4 (technical details only)
« on: April 04, 2019, 11:58:17 am »
For what it is worth:
if you ask the OS/4 guys, they are going to provide you with an ACPI4.BPD driver plus the OS4APIC.PSD driver that goes along with it. This combination is a full replacement for ACPI.PSD as provided by AN.
The "BPD" driver variant is an OS4 extension to the driver model (they are special, will load without being listed in CONFIG.SYS and load early in the boot process).

However, the ACPI4.BPD driver is beta.

1091
But what's more: this mismatch between the filename and the internal module name will eventually massively confuse/screw up the module loader (if done repeatedly) until the whole system reboots without showing any trap screen or the like.

Quote
I could easily create a test case that would blow your whole system just by creating (and loading a DLL) that has a mismatch in filename and internal module name.

What if  you prepare some test so I can run it om my computer and have this reboot?

Ok, just give me some time. Where can I send that ?

1092
Programming / Re: OW, JNI (GCC built java 1.6) and parameters
« on: April 01, 2019, 06:06:28 pm »
I think the problem he tries to catch is that some DLLs keep resetting the FPU control word to what they think is correct. So if you call a routine in those DLLs, the FPU control word will be modified when the call returns (which of course is bad,bad,bad).
Jan-Erik does set the FPU control word to what he wants (namely, to disable all FPU exceptions).
But then he wants to register an exception handler so that if something resets the FPU control word and subsequently an FPU exception occurs he can reset the FPU control word to what he wants (namely, to disable all FPU exceptions)

1093
MMRES_DE.DLL  installed with eCS 2.2 beta. Back at the time, I chose the installation in german.
Maybe you need to look into the CWMM install package to find it (but I don't know where you find that on the DVD, eCS or ArcaOS).
If you want to experience the "sudden system reboot", what you can do is to back up mmres_en.dll, lxlite /x the DLL, use a hex editor to change the internal module name from MMRES_EN to say MMRES_DE and save back.
For once that will prevent the DLL from loading. But if you try often enough (by invoking volume.exe multiple times, say 10 times) it will eventually take down your whole system.

1094
Applications / Re: nguest2.exe (netop) fails to start
« on: March 31, 2019, 09:36:02 pm »
Hi Dave

If I unlock and delete helpmgr.dll then during the necessary following reboot I see this message:-

The system cannot find the file HELPMGR specified
in the PROTSHELL statement on line 105 of the CONFIG.SYS file.
Line 105 is ignored.
The system is stopped.  Correct the preceding error and
restart the system.


Line 105 is
   PROTSHELL=M:\OS2\PMSHELL.EXE

Ummm...  not sure how to get around that apart from putting helpmgr.dll back in place.


I have installed the latest NewView, 2.19.5, to eCS2.2b2 and, following a reboot, I can report that the helpmgr.dll file included with the latest NewView causes exactly the same problem - no netop applications will start, all deliver SYS3175.

Replacing helpmgr.dll with the earlier release resolves that problem.


Regards

Pete

Can you do a "exehdr /V helpmgr.dll" on the failing helpmgr.dll and post the results ?

1095
I updated both Resource DLLs (the english as well as the german one) but yes that's the version I am talking about:

[d:\mmos2\mmclass\bin]bldlevel mmres_en.dll
Build Level Display Facility Version 6.12.675 Sep 25 2001
(C) Copyright IBM Corporation 1993-2001
Signature:       @#(c) Chris Wohlgemuth :0.2 (13.03.02) (mmres_en.DLL)#@##1## 13
.03.2002 18:17:00      My ;-)  ::::1::@@Resource-DLL
Vendor:          (c) Chris Wohlgemuth
Revision:        0.02
Date/Time:       13.03.2002 18:17:00
Build Machine:   My ;-)
File Version:    0.2.1
Description:     Resource-DLL

But the problem is the GERMAN Resource: DLL mmres_de.dll.
And the real universal problem is that the OS module loader will barf on the mismatch between file name and internal module name. This is true for ANY DLL loaded. I could easily create a test case that would blow your whole system just by creating (and loading a DLL) that has a mismatch in filename and internal module name.

Pages: 1 ... 71 72 [73] 74 75 ... 96