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 - ChrisGWarp

Pages: [1] 2
1
Applications / Re: yum failure on WSeB 4.52
« on: June 03, 2025, 12:28:17 pm »
I no don't get the above error. Yey!

But I am getting this:

Code: [Select]
[C:\]yum install pango hunspell libicu libjpeg libkai libvpx

...

================================================================================
Installing:
 hunspell             pentium4    1.7.0-2.oc00             netlabs-rel    276 k
 libjpeg-turbo        pentium4    3.0.1-1.oc00             netlabs-rel    291 k
 libkai               pentium4    2.1.0-1.oc00             netlabs-rel     32 k
 libvpx               pentium4    1.8.2-1.oc00             netlabs-rel    1.4 M
 pango                pentium4    1.28.4-2.oc00            netlabs-rel    529 k
Installing for dependencies:
 cairo                pentium4    1.12.18-4.oc00           netlabs-rel    627 k
 fontconfig           pentium4    2.13.1-4.oc00            netlabs-rel    245 k
 fontconfig-legacy    pentium4    2.11.94-1.oc00           netlabs-rel     74 k
 freetype             pentium4    2.10.0-2.oc00            netlabs-rel    361 k
 hunspell-en-US       noarch      0.20140811.1-1.oc00      netlabs-rel    196 k
 libpng               pentium4    1.6.40-1.oc00            netlabs-rel    117 k
 pixman               pentium4    0.32.8-4.oc00            netlabs-rel    302 k

Transaction Summary
================================================================================
Install      12 Packages

Total download size: 4.4 M
Installed size: 4.6 M
Is this ok [y/N]: y
Downloading Packages:
(1/12): cairo-1.12.1 | 627 kB  00:08     ====-]  67 kB/s | 615 kB  00:00 ETA
(2/12): fontconfig-2 | 245 kB  00:02     ==-  ]  56 kB/s | 203 kB  00:00 ETA
(3/12): fontconfig-l |  74 kB  00:00          ]  0.0 B/s |  50 kB  --:-- ETA
(4/12): freetype-2.1 | 361 kB  00:03     ====-]  76 kB/s | 358 kB  00:00 ETA
(5/12): hunspell-1.7 | 276 kB  00:02     ==== ]  82 kB/s | 263 kB  00:00 ETA
(6/12): hunspell-en- | 196 kB  00:01     ==== ]  71 kB/s | 187 kB  00:00 ETA
(7/12): libjpeg-turb | 291 kB  00:02     =====]  80 kB/s | 291 kB  00:00 ETA
(8/12): libkai-2.1.0 |  32 kB  00:00
(9/12): libpng-1.6.4 | 117 kB  00:00          ]  0.0 B/s |  75 kB  --:-- ETA
(10/12): libvpx-1.8. | 1.4 MB  00:22     ====-]  63 kB/s | 1.4 MB  00:00 ETA
(11/12): pango-1.28. | 529 kB  00:05     ====-]  79 kB/s | 526 kB  00:00 ETA
(12/12): pixman-0.32 | 302 kB  00:02     ===  ]  70 kB/s | 264 kB  00:00 ETA
--------------------------------------------------------------------------------
Total                                            80 kB/s | 4.4 MB     00:56
Running Transaction Check
Running Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing : libpng-1.6.40-1.oc00.pentium4                               1/12
  Installing : freetype-2.10.0-2.oc00.pentium4                             2/12
  Installing : fontconfig-legacy-2.11.94-1.oc00.pentium4                   3/12
  Installing : fontconfig-2.13.1-4.oc00.pentium4                           4/12
  Installing : hunspell-en-US-0.20140811.1-1.oc00.noarch                   5/12
  Installing : hunspell-1.7.0-2.oc00.pentium4                              6/12
  Installing : pixman-0.32.8-4.oc00.pentium4                               7/12
  Installing : cairo-1.12.18-4.oc00.pentium4                               8/12
  Installing : pango-1.28.4-2.oc00.pentium4                                9/12
  Installing : libjpeg-turbo-3.0.1-1.oc00.pentium4                        10/12
  Installing : libvpx-1.8.2-1.oc00.pentium4                               11/12
  Installing : libkai-2.1.0-1.oc00.pentium4                               12/12


Rpmdb checksum is invalid: dCDPT(pkg checksums): libkai.pentium4 0:2.1.0-1.oc00 - u

[C:\]

Things seem to have been installed, but the persistent rpmdb error is worrysome. Is this normal/expected?
Cheers
-Chris/2

2
Applications / Re: yum failure on WSeB 4.52
« on: June 03, 2025, 12:18:23 pm »
Switching to the Pentium4 version as opposed to i686 (which is obviously broken) worked.
Thanks everyone!
-Chris

3
Applications / Re: yum failure on WSeB 4.52
« on: June 03, 2025, 07:46:04 am »
I did a base install of WarpIn 1.0.26 (warpin-1-0-26.zip)
I added in the other pre-reqs (klibccfg_1_0_2_1.exe and anpm_1_1_0_2.exe)
Which is where I basically am now.
I'll remove things and try again. This time with the P4 and not i686 (I must have been spending too much time in Linux land...)

As for how config.sys was not modified? I have a dir with useful things \OS2Stuff, where lots of tools utils etc live. One of which was cube.exe. That clashed with the ANPM update process. And explains why things were not modified as expected (but not always). But hey. Shrug.

4
Applications / yum failure on WSeB 4.52
« on: June 02, 2025, 01:57:09 pm »
Hi everyone,

I'm attempting to get ANPM/yum working on WSeB 4.52 (or 4.50 - I forget).

After manually updating config.sys and removing a DIFFERENT cube.exe from the path, (just what is cube.exe used for??? [My cube.exe was from 1998 and was a rubiks cube PM app...]) I managed to get path the stage of being prompted to 'fix' config.sys each and every time. yey!

So I attempt to perform a simple, first off yum update, to which:

Code: [Select]
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package ncurses-base.i686 0:5.9-1.oc00 will be updated
--> Processing Dependency: ncurses-base = 5.9-1.oc00 for package: ncurses-libs-5.9-1.oc00.i686
---> Package ncurses-base.noarch 0:6.4-1.oc00 will be an update
---> Package os2-rpm.noarch 0:1-10.oc00 will be updated
---> Package os2-rpm.noarch 0:1-11.oc00 will be an update
--> Finished Dependency Resolution
Error: Package: ncurses-libs-5.9-1.oc00.i686 (installed)
           Requires: ncurses-base = 5.9-1.oc00
           Removing: ncurses-base-5.9-1.oc00.i686 (installed)
               ncurses-base = 5.9-1.oc00
           Updated By: ncurses-base-6.4-1.oc00.noarch (netlabs-rel)
               ncurses-base = 6.4-1.oc00
           Available: ncurses-base-5.7-4.oc00.i386 (netlabs-rel)
               ncurses-base = 5.7-4.oc00
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

Ugh. Any suggestions?

5
The 'kLIBC Pathwriters' that I installed (klibccfg_1_0_2_1.exe) did not added TEMP, TMPDIR, LOGFILES on the config.sys.

I add those manually and the D: drive issues are gone.
Strange. I've just checked the installation .wis script. It contains:
Code: [Select]
      REGISTERCLASS="kLIBCConfig|$(1)\klibccfg.dll"
      CREATEOBJECT="REPLACE kLIBCConfig|kLIBC Pathrewriters|<WP_CONFIG>|OBJECTID=<WP_KLIBCPRW>"
      CONFIGSYS="SET LIBC_HOOK_DLLS=$(1)\klibccfg.dll@_kLIBCInitPath!pathrewrite"
      WRITEPROFILE="$(ETC)\klibcfg.ini\REWRITE\/etc|%ETC%"
      WRITEPROFILE="$(ETC)\klibcfg.ini\REWRITE\/var/log|%LOGFILES%"
      WRITEPROFILE="$(ETC)\klibcfg.ini\REWRITE\/tmp|%TMP%"

That looks as if it should have added the CONFIG.SYS entry and created %ETC%\KLIBCFG.INI.

Apologies for restarting this thread, I have essentially the same problem. But with slightly differing results. I have a very full popuplog.os2 file with lots of ANPM.EXE and REXXAPI.DLL errors... :)

ANPM is on C:, but I've setup and wanting UNIXROOT to be on D:.

I'm not even being asked if I want config.sys fixed but it does inform me that it's modified config.sys (it hasn't).

Which makes me wonder if there is an implicit assumption here that all of the packages are on the one singular drive (ie no reference to UNIXROOT)?

Thoughts?

6
Networking / Re: Sharing WSeB Server drives to Win 10/11 Clients
« on: April 10, 2025, 03:32:56 pm »
Well. I'm back on this old chestnut. :)

I have a Win 7 Ultimate RC1 (of all things) VM! And that WORKS. I can mount an OS/2 share and DIR works.
I have a Win 7 SP1 VM and that's broken too. I've played with all of the SecPol.msc and RegEdit settings I can find, but although I can mount an OS/2 share, the DIR shows incorrect function calls.

To be clear, has anyone managed to get any Win 7 SP1 versions talking to an NT or OS/2 share?

Or, failing that, does someone have some setup instruction for SAMBA for WSeB (4.50 and 4.52)?

Cheers,
-Chris


Hey Chris,

later versions of windows have deprecated SMB1 and the legacy NTLM authentication. https://winsides.com/enable-smb-1-0-cifs-file-sharing-support-windows-11/ might help....

I tried that for years after Windows 7 and higher SMB 1 support is complete broken is my experience. I tested with a lot of LAN MAN settings in the registry but gave up.
SMB 1 support from Windows 10/11 seems to be to much broken. Maybe some magic registry setting can get it to work. But I spent long nights on this.

Roderick

7
Networking / Re: Sharing WSeB Server drives to Win 10/11 Clients
« on: December 15, 2024, 04:09:46 am »
As if to rub salt into the wound, I just successfully mounted an OS/2 Server drive from an XP VM. And a DIR worked.

So, yes, it looks like the removal of NTLM is what's causing the issues.

And all I wanted to do was to run an A/V scan using a modern tool against the old VM's - god knows what I'd find.

Thanks all for your help everyone! :)

-Chris

8
Networking / Re: Sharing WSeB Server drives to Win 10/11 Clients
« on: December 15, 2024, 04:05:08 am »
Well, that sums it up:

NTLMv1 is removed starting in Windows 11, version 24H2

And I'd only upgraded to W11 24H2 last week. This was one of the final tests that I wanted to perform.

Can I roll back a Windows 11 upgrade back to Windows 10? The command prompt still reports at Windows V10 ????

-Chris

9
Networking / Re: Sharing WSeB Server drives to Win 10/11 Clients
« on: December 12, 2024, 10:08:54 am »
Hey Guys,
Yes, it looks like they have broken things badly.
I can't tell if it's a function call or an auth error that is causing the issues (or an auth error caused by newer functionality).
Given the age of the systems, they probably removed any explicit support for them.
The SMB/CIFS stuff has been added and enabled.
Cheers,
-Chris

10
Networking / Sharing WSeB Server drives to Win 10/11 Clients
« on: December 12, 2024, 04:05:50 am »
Hi Everyone,
I've virtualized my WSeB development box (from waaaaaay back) and my Windows NT 4.0 Server as well.
I can map (net use ... from windows) that works successfully, and I can even do a properties on the drive, but, a DIR fails. Mapping a drive and using a specified user, gives a different result entirely.

This is from a windows 11 client (Windows 10 was the same):


C:\Users\Chris>net use m: \\DEVELSMP\SMP-C
The command completed successfully.


C:\Users\Chris>dir m:
 Volume in drive M is OS2
 Volume Serial Number is 2D6E-F814

 Directory of M:\

File Not Found

C:\Users\Chris>net use m: /del
m: was deleted successfully.


C:\Users\Chris>net use m: \\DEVELSMP\SMP-C /user:Chris
Enter the password for 'Chris' to connect to 'DEVELSMP':
System error 5 has occurred.

Access is denied.


C:\Users\Chris>


However, things like viewing the shares of the OS2 host works:

C:\Users\Chris>net view \\DEVELSMP
Shared resources at \\DEVELSMP

SMP Development Machine

Share name  Type  Used as  Comment

-------------------------------------------------------------------------------
NETLOGON    Disk           Domain controller share
SMP-C       Disk           SMP Drive C:
SMP-D       Disk           SMP Drive D:
SMP-E       Disk           SMP Drive E:
SMP-F       Disk           SMP Drive F:
SMP-G       Disk           SMP Drive G:
SMP-H       Disk           SMP Drive H:
SMP-I       Disk           SMP Drive I: (CD-ROM)
The command completed successfully.


I'm guessing that there might be some SMB functions being called that the OS2 host does not recognise and is choking on.

Has anyone successfully mounted some OS2 Server drives (and Windows NT 4.0 for that matter too) from a modern Windows 10/11 client?

Ideally, I'd prefer to avoid Samba and stick with the base functionality, but (if I absolutely must, then I'll consider it).

Cheers,

-Chris

11
General Discussion / Re: It's a sad day...
« on: July 21, 2022, 12:22:13 pm »
Actually it didn't. So back to the gif.  ::)

12
General Discussion / Re: It's a sad day...
« on: July 21, 2022, 08:26:45 am »
I got bored. ;)
Dropping the colour depth from 24 bit to 8 allowed the file to be loaded.
Could be a size thing. :)

13
General Discussion / Re: It's a sad day...
« on: July 21, 2022, 08:14:18 am »
Well. That's about right!
It could handle some other BMP's. I had a whole host of StarTrek Voyager ones. They worked.
Not any of that image, irrespective of whether I saved them as OS/2 1.x or OS/2 2.x (with or without RLE encoding). It just choked.
As did that image as a JPG. I didn't try a number of options here.
Could it be the colour depth? If I get bored I'll try.
However, saving it as a GIF did allow it to work.
The underlying error was that the exception handler ran out of stack space. The BMP's were 2+ Mb. I wonder if someone was doing something stupid and putting it on the stack rather than allocate mem?
Shrug
-Chris

14
General Discussion / Re: It's a sad day...
« on: July 21, 2022, 01:39:31 am »
I had some issues with the INI file. The load WPS classes checks hung. Thankfully (thanks martin!) the source to checkini was in GitHub, so I looked at it, and wrote a quick check progress to help diagnose which class was killing that test. As it turns out, it was one of the Fastback classes, so an uninstall/reinstall fixed that aspect of it.

As for the bitmap/background issue, I noticed in startup that I was renaming OS2OOOC.DLL just fort he PMShell startup. I wondered why I'd done this, so I stopped doing it and bam, no PMShell. :( Doing a cross check, it appears that it's referenced in a few EXE's, notably some of the MMPM ones... Fits.

I have lots of these in my popuplog.os2 file ;)


07-20-2022  20:45:31  SYS3171  PID 0027  TID 0001  Slot 0044
C:\OS2\PMSHELL.EXE
c0000005
1e5566e1
P1=00000002  P2=0003ffe8  P3=XXXXXXXX  P4=XXXXXXXX 
EAX=00914370  EBX=00914370  ECX=18a14944  EDX=00000000
ESI=010955b4  EDI=00914370 
DS=0053  DSACC=f0f3  DSLIM=ffffffff 
ES=0053  ESACC=f0f3  ESLIM=ffffffff 
FS=150b  FSACC=00f3  FSLIM=00000030
GS=0000  GSACC=****  GSLIM=********
CS:EIP=005b:1e5566e1  CSACC=f0df  CSLIM=ffffffff
SS:ESP=0053:0003ffec  SSACC=f0f3  SSLIM=ffffffff
EBP=0004002c  FLG=00010212

OS2OOOC.DLL 0001:000666e1


As described here: http://www.44342.com/os2-f520-t705-p1.htm. I do not get the intermittent hangs though.

I'm actually on the base WSeB (XR04500).

Suggestions would be welcome ;)


15
General Discussion / Re: It's a sad day...
« on: July 20, 2022, 04:34:22 am »
Hi Chris

Your IBM black keyboard remind me the "IBM SK-8809 Multimedia USB Keyboard" that I used to have long time ago. Your seems to be a newer one with the "IBM Access" key.

Nice memories.

Regards

I might have some of those floating around too! :)

Pages: [1] 2