Recent Posts

Pages: [1] 2 3 ... 10
1
Virtualization / Re: Win-OS/2 - Open vbesvga.drv video driver
« Last post by Martin Iturbide on Today at 07:09:38 pm »
Hello

Currently my Win-OS2 full screen session (1920x1080) has a "slow-choppy" mouse and you can not move the mouse pointer down from the middle of the screen. (ArcaOS 5.1 BIOS running on a VirtualBox host. )

Hello again.

The author of "vbesvga.drv and vddvbe.386" wrote me back since he made some new releases of the driver, so I tried it all over again.

My issues of a Win-OS2 Full Screen session (1920x1080) with "slow-choppy mouse" and "middle screen limitation" are now gone. If someone on ArcaOS 5.1.1 (BIOS) (On VirtualBox host) experience that I would like you to try this driver and provide feedback.

The instruccions that I follow was:
- Download 0.6.0 versions of  "vbesvga.drv and vddvbe.386" - https://github.com/PluMGMK/vbesvga.drv/releases
- Follow the install instrucions:
Quote
The following changes are needed to your C:\WINDOWS\SYSTEM.INI file:

- In the [boot] section, change the display.drv= line to point to vbesvga.drv. You should specify the full path, or else copy the file to C:\WINDOWS\SYSTEM. (Note that if the path is too long, it can cause the CodeView debugger to crash on startup!)
- In the [386Enh] section, change the display= line to point to vddvbe.386. Again, you should specify the full path, or else copy the file to C:\WINDOWS\SYSTEM.

- Added the following on SYSTEM.INI
Quote
[VBESVGA.DRV]
Width=1920
Height=1080
Depth=24

Remember that on SYSTEM.INI the comments the semicolon ( ; ) in case you want to revert things.
Here it is my System.INI
Code: [Select]
[boot]
useos2shield=1
os2shield=winsheld.exe
shell=progman.exe
mouse.drv=mouse.drv
network.drv=
language.dll=langeng.dll
comm.drv=comm.drv
keyboard.drv=keyboard.drv
system.drv=atmsys.drv
;386grabber=vga.3gr
;286grabber=vgacolor.2gr
drivers=mmsystem.dll
WAVDMAPPS=
atm.system.drv=system.drv
;display.drv=ifgdi2vm.drv
display.drv=vbesvga.drv
sdisplay.drv=isgdi2vm.drv
fonts.fon=vgasys.fon
fixedfon.fon=vgafix.fon
oemfonts.fon=vgaoem.fon
os2user=user.exe
os2gdi.exe=GDI.EXE
os2user.exe=user.exe

[keyboard]
subtype=
type=4
keyboard.dll=kbdla.dll
oemansi.bin=
typeofswitch=2
secondkeyb.dll=kbdusx.dll

[boot.description]
keyboard.typ=Enhanced 101 or 102 key US and Non US keyboards
mouse.drv=Microsoft, or IBM PS/2
network.drv=No Network Installed
language.dll=English (American)
system.drv=MS-DOS System
codepage=437
woafont.fon=English (437)
aspect=100,96,96
display.drv=Full Screen GDI 2 VMAN
sdisplay.drv=Seamless GDI 2 VMAN

[386Enh]
mouse=*vmd
network=*dosnet,*vnetbios
ebios=*ebios
woafont=dosapp.fon
;display=*vddvga
display=vddvbe.386
EGA80WOA.FON=EGA80WOA.FON
EGA40WOA.FON=EGA40WOA.FON
CGA80WOA.FON=CGA80WOA.FON
CGA40WOA.FON=CGA40WOA.FON
keyboard=*vkd
device=vtdapi.386
device=*vpicd
device=*vtd
device=*reboot
device=*vdmad
device=*vsd
device=*v86mmgr
device=*pageswap
device=*dosmgr
device=*vmpoll
device=*wshell
device=*BLOCKDEV
device=*PAGEFILE
device=*vfd
device=*parity
device=*biosxlat
device=*vcd
device=*vmcpd
device=*combuff
device=*cdpscsi
local=CON
FileSysChange=off
PagingFile=D:\WIN386.SWP
MaxPagingFileSize=20480

[standard]

[NonWindowsApp]
localtsrs=dosedit,ced

[mci]
WaveAudio=mciwave.drv
Sequencer=mciseq.drv
CDAudio=mcicda.drv

[drivers]
timer=timer.drv
midimapper=midimap.drv


[Desktop]
IconSpacing=75

[VBESVGA.DRV]
Width=1920
Height=1080
Depth=24

Please let me know any issues or feedback.

Regards
2
Setup & Installation / Re: Cannot update python
« Last post by Dave Yeo on Today at 06:11:48 pm »
yum install python3 python2.7 2>&1 | tee yum.out
Code: [Select]
Setting up Install Process
Package python2.7-2.7.18-3.oc00.pentium4 already installed and latest version
Resolving Dependencies
--> Running transaction check
---> Package python3.pentium4 0:3.9.21-1.oc00 will be updated
--> Processing Dependency: python(abi) = 3.9 for package: python3-flit-core-3.12.0-1.oc00.noarch
--> Processing Dependency: python(abi) = 3.9 for package: python3-flit-core-3.12.0-1.oc00.noarch
--> Processing Dependency: python3 = 3.9.21-1.oc00 for package: python-unversioned-command-3.9.21-1.oc00.pentium4
---> Package python3.pentium4 0:3.13.2-1.oc00 will be an update
--> Processing Dependency: python3-libs = 3.13.2-1.oc00 for package: python3-3.13.2-1.oc00.pentium4
--> Processing Dependency: pytho313.dll for package: python3-3.13.2-1.oc00.pentium4
--> Running transaction check
---> Package python-unversioned-command.pentium4 0:3.9.21-1.oc00 will be updated
---> Package python-unversioned-command.pentium4 0:3.13.2-1.oc00 will be an update
---> Package python3-flit-core.noarch 0:3.12.0-1.oc00 will be updated
---> Package python3-flit-core.noarch 0:3.12.0-2.oc00 will be an update
---> Package python3-libs.pentium4 0:3.9.21-1.oc00 will be updated
--> Processing Dependency: python39.dll for package: python3-createrepo_c-1.2.1-1.oc00.pentium4
--> Processing Dependency: python39.dll for package: hplip-libs-3.19.12-1.oc00.pentium4
--> Processing Dependency: python39.dll for package: python3-rpm-4.15.1-3.oc00.pentium4
---> Package python3-libs.pentium4 0:3.13.2-1.oc00 will be an update
--> Processing Dependency: mpdec4.dll for package: python3-libs-3.13.2-1.oc00.pentium4
--> Running transaction check
---> Package hplip-libs.pentium4 0:3.19.12-1.oc00 will be updated
--> Processing Dependency: hplip-libs = 3.19.12-1.oc00 for package: hplip-3.19.12-1.oc00.pentium4
--> Processing Dependency: hplip-libs = 3.19.12-1.oc00 for package: libsane-hpaio-3.19.12-1.oc00.pentium4
---> Package hplip-libs.pentium4 0:3.19.12-2.oc00 will be an update
--> Processing Dependency: hplip-common = 3.19.12-2.oc00 for package: hplip-libs-3.19.12-2.oc00.pentium4
---> Package mpdecimal.pentium4 0:4.0.0-1.oc00 will be installed
---> Package python3-libs.pentium4 0:3.9.21-1.oc00 will be updated
--> Processing Dependency: python39.dll for package: python3-createrepo_c-1.2.1-1.oc00.pentium4
---> Package python3-rpm.pentium4 0:4.15.1-3.oc00 will be updated
---> Package python3-rpm.pentium4 0:4.15.1-4.oc00 will be an update
--> Processing Dependency: rpm-libs = 4.15.1-4.oc00 for package: python3-rpm-4.15.1-4.oc00.pentium4
--> Running transaction check
---> Package hplip.pentium4 0:3.19.12-1.oc00 will be updated
---> Package hplip.pentium4 0:3.19.12-2.oc00 will be an update
---> Package hplip-common.pentium4 0:3.19.12-1.oc00 will be updated
---> Package hplip-common.pentium4 0:3.19.12-2.oc00 will be an update
---> Package libsane-hpaio.pentium4 0:3.19.12-1.oc00 will be updated
---> Package libsane-hpaio.pentium4 0:3.19.12-2.oc00 will be an update
---> Package python3-libs.pentium4 0:3.9.21-1.oc00 will be updated
--> Processing Dependency: python39.dll for package: python3-createrepo_c-1.2.1-1.oc00.pentium4
---> Package rpm-libs.pentium4 0:4.15.1-3.oc00 will be updated
--> Processing Dependency: rpm-libs = 4.15.1-3.oc00 for package: python2-rpm-4.15.1-3.oc00.pentium4
--> Processing Dependency: rpm-libs = 4.15.1-3.oc00 for package: rpm-sign-libs-4.15.1-3.oc00.pentium4
--> Processing Dependency: rpm-libs = 4.15.1-3.oc00 for package: rpm-plugin-syslog-4.15.1-3.oc00.pentium4
--> Processing Dependency: rpm-libs = 4.15.1-3.oc00 for package: rpm-build-libs-4.15.1-3.oc00.pentium4
--> Processing Dependency: rpm-libs = 4.15.1-3.oc00 for package: rpm-devel-4.15.1-3.oc00.pentium4
---> Package rpm-libs.pentium4 0:4.15.1-4.oc00 will be an update
--> Processing Dependency: rpm = 4.15.1-4.oc00 for package: rpm-libs-4.15.1-4.oc00.pentium4
--> Running transaction check
---> Package python2-rpm.pentium4 0:4.15.1-3.oc00 will be updated
---> Package python2-rpm.pentium4 0:4.15.1-4.oc00 will be an update
---> Package python3-libs.pentium4 0:3.9.21-1.oc00 will be updated
--> Processing Dependency: python39.dll for package: python3-createrepo_c-1.2.1-1.oc00.pentium4
---> Package rpm.pentium4 0:4.15.1-3.oc00 will be updated
--> Processing Dependency: rpm = 4.15.1-3.oc00 for package: rpm-build-4.15.1-3.oc00.pentium4
---> Package rpm.pentium4 0:4.15.1-4.oc00 will be an update
---> Package rpm-build-libs.pentium4 0:4.15.1-3.oc00 will be updated
---> Package rpm-build-libs.pentium4 0:4.15.1-4.oc00 will be an update
---> Package rpm-devel.pentium4 0:4.15.1-3.oc00 will be updated
---> Package rpm-devel.pentium4 0:4.15.1-4.oc00 will be an update
---> Package rpm-plugin-syslog.pentium4 0:4.15.1-3.oc00 will be updated
---> Package rpm-plugin-syslog.pentium4 0:4.15.1-4.oc00 will be an update
---> Package rpm-sign-libs.pentium4 0:4.15.1-3.oc00 will be updated
--> Processing Dependency: rpm-sign-libs = 4.15.1-3.oc00 for package: rpm-sign-4.15.1-3.oc00.pentium4
---> Package rpm-sign-libs.pentium4 0:4.15.1-4.oc00 will be an update
--> Running transaction check
---> Package python3-libs.pentium4 0:3.9.21-1.oc00 will be updated
--> Processing Dependency: python39.dll for package: python3-createrepo_c-1.2.1-1.oc00.pentium4
---> Package rpm-build.pentium4 0:4.15.1-3.oc00 will be updated
---> Package rpm-build.pentium4 0:4.15.1-4.oc00 will be an update
---> Package rpm-sign.pentium4 0:4.15.1-3.oc00 will be updated
---> Package rpm-sign.pentium4 0:4.15.1-4.oc00 will be an update
--> Finished Dependency Resolution
Error: Package: python3-createrepo_c-1.2.1-1.oc00.pentium4 (installed)
           Requires: python39.dll
           Removing: python3-libs-3.9.21-1.oc00.pentium4 (installed)
               python39.dll
           Updated By: python3-libs-3.13.2-1.oc00.pentium4 (netlabs-exp)
               Not found
           Available: python3-libs-3.9.5-8.oc00.pentium4 (netlabs-rel)
               python39.dll
           Available: python3-libs-3.9.17-1.oc00.pentium4 (netlabs-rel)
               python39.dll
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest
3
Programming / Re: EDM/2 - The API Project - Undocumented
« Last post by Rich Walsh on Today at 05:53:28 pm »
- DosOpenMutexWaitSem

DosOpenMuxWaitSem
4
Applications / Re: warpin problem
« Last post by Pete on Today at 05:23:41 pm »
Hi andreas

Maybe the Warpin Install routine checks the existing C:\sys\install\WARPIN\DATBAS_C.INI file to see if Warpin is already installed (replace C with correct drive letter for your system). If that is the case deleting the Warpin entries from that file using Ini Editor from INI Tools, or any other ini file editor, should allow Warpin to be reinstalled.


Regards

Pete
5
Setup & Installation / Re: Cannot update python
« Last post by Alex Taylor on Today at 04:55:26 pm »
You need to install both the python2.7 and python3 packages at the same time.

yum install python3 python2.7

Or select both of these packages in ANPM and install them together.

https://www.arcanoae.com/wiki/anpm/known-issues-limitations/
6
Applications / Re: warpin problem
« Last post by Dave Yeo on Today at 07:36:47 am »
I think you're going to have to contact Alex about finding the lock, or examine the source code.
7
Programming / Re: EDM/2 - The API Project - Undocumented
« Last post by Dave Yeo on Today at 07:25:58 am »
Out of curiosity, I grepped x:\os2 for all 4 functions, nothing seems to use them. Or they're called by ordinal.
I also grepped \os2tk45. Found DosQueryPageUsage() only in os2386.lib, so a real function not prototyped. Also found DevHlp_OpenFile() in inc\devhlp.inc. Take a look at the inc for cardinal(?) and comment.
All but DevHlp_FileOpen are also in addendum.inf. I'd assume DevHlp_FileOpen is a typo with OpenFile reversed, a typo I could see making.
8
Programming / Re: EDM/2 - The API Project - Undocumented
« Last post by Martin Iturbide on Today at 04:15:20 am »
Hello

I was checking the "Programming Guide and Reference Addendum".

On "Device Helper (DevHlp) Services and Function Codes" there is this one that I can not find:
- DevHlp_FileOpen
The strange thing is that is list the same code, 7Fh, than "DevHlp_OpenFile" that is on the same page.  Does this "DevHlp_FileOpen" exists or it is a mistake?

On " APIs Supporting High Memory Objects" there are two functions I can not find:
- DosQueryPageUsage
- DosOpenMutexWaitSem
Are those mistakes or the documentation is available somewhere else ?

Thanks in advance for any tip or info.

Regards
9
Applications / Re: warpin problem
« Last post by andreas on May 15, 2025, 10:09:30 pm »
no, it's all wpi-files...

It seems to be impossible to reinstall warpin.

I deleted ini-entry, deleted the whole previous warpiin-folder.

There's definately no other warpin runnung, but the installation process claims there is and leaves me only the option to terminate ...

Is it maybe because ANPM is using warpin?

yes, it's newest AN. I lokked at TOP, but could not see any warpin there...    rebooted several times. problem resists
10
Storage / Re: How to discover the newly assigned USB drive letter?
« Last post by Jan-Erik Lärka on May 15, 2025, 10:04:40 pm »
No need to get fancy here...

SysDriveMap() before calling LVM.
SysDriveMap() after calling LVM.
What changed?

something like:

Code: [Select]
/* Comment */
...
before = SysDriveMap()
'@LVM.EXE /RediscoverPRM'
after = SysDriveMap()
DO i = 1 TO WORDS( after )
  IF 0 = POS( SUBWORD( after, i, 1 ), before )  THEN
    SAY SUBWORD( after, i, 1 ) "must be the drive we're looking for!"
END

Nice!
Pages: [1] 2 3 ... 10