OS/2, eCS & ArcaOS - Technical > Applications

OS/4 (technical details only)

(1/60) > >>

OS4User:
Patched DIVE.DLL can increase video speed on OS/4 system.

At the same time the patched DIVE.DLL is not compatible with original OS/2 -  to avoid missboot do the following:

1) Create C:\OS4 dir
2) Put the patched DIVE.DLL into C:\OS4
3) Insert C:\OS4; exactly after LIBPATH=  into your CONFIG.OS4 so you will have LIBPATH=C:\OS4;.;.......

This way the patched DIVE.DLL will be loaded instead of original DIVE.DLL and  original DIVE.DLL will remain for booting with CONFIG.SYS (for ex. original kernel).

http://gus.biysk.ru/os4/test/patched_dll/patched_dive.zip

Martin Iturbide:
Hi OS4User

Can it be possible for the author to explain a little bit what was patched on this DIVE.DLL ? like which functions of the OS4 kernel is now using to increase the video speed?

Regards

OS4User:

--- Quote from: Martin Iturbide on April 17, 2018, 01:12:02 am ---Can it be possible for the author to explain a little bit what was patched on this DIVE.DLL ?

--- End quote ---

Hi Martin

some details is here https://www.os2world.com/wiki/index.php/Phoenix_OS/4#Video_bus_bandwidth_.28VBB.29

Dariusz Piatkowski:
OK, OS4User, time for me to get off of my butt and get the debug info to troubleshoot the hard trap right after PMSHELL comes up. With FreeRDP making progress and VBox supporting extra features of the OS4KRNL I have no reason to delay further.

I re-read the Wiki you posted above and will get the debug kernel setup and ready to go. Beyond this though, is there anything specific I need to do in order to capture the "moment" the system traps?

My assumption is that maybe through the debug kernel I have some way to communicate with the OS/2 box, but even if that is the case, once the trap occurs, how do I know what additional information to log? Can you provide any 'working instructions' for this? Even high-level stuff might help...

Thanks!

OS4User:

--- Quote from: Dariusz Piatkowski on April 17, 2018, 05:10:44 pm ---I re-read the Wiki you posted above and will get the debug kernel setup and ready to go. Beyond this though, is there anything specific I need to do in order to capture the "moment" the system traps?

My assumption is that maybe through the debug kernel I have some way to communicate with the OS/2 box, but even if that is the case, once the trap occurs, how do I know what additional information to log? Can you provide any 'working instructions' for this? Even high-level stuff might help...

--- End quote ---

Welcome on board :)

You do not need anything specific, you will see trap info in your comport log.
Additional info always depends on trap info, working instruction is quite big,  it is called
"The OS/2 Debugging Handbook"  for ex. https://openlibrary.org/works/OL8414318W/The_OS_2_Debugging_Handbook

Navigation

[0] Message Index

[#] Next page

Go to full version