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

Pages: [1]
1
You asked for an English translation of the page at https://ftpmirror.infania.net/sites/pccbbs/. Here's a translation of the introductory content:

Archive of the IBM PC Company BBS FTP Site

This is an archive of the IBM FTP server at ftp.pc.ibm.com/pub/pccbbs as it existed on December 13, 1999. Many thanks to Aron Eisenpress for making this available.

It has also been updated with contributions from RickE, curated by Kevin Bowling, including content from the mid-2000s.

This file archive is hosted by Infania Networks.

reagds

2
Hardware / Re: URGENT Need for OS/2 Compatible Inkjet Printer
« on: June 01, 2025, 12:58:37 am »
Look here

https://www.geocities.ws/os2_shutterbug/os2-printers.html



Compatible older HP inkjet printers for OS/2 Warp
HP DeskJet series (PCL 3):

HP DeskJet 500 / 510 / 520 / 540 / 550C / 560C / 600 / 610C / 630C / 660C / 690C / 693C / 695C / 697C / 810C / 840C / 850C / 870Cse / 895Cse
(Many of these even run on parallel port and USB; OMNI.DRV recommended.)

HP DeskWriter series (for Mac, but partly PCL):

HP DeskWriter 550C, 560C
(Only of limited relevance - mostly intended for Apple)

HP DeskJet Plus, HP DeskJet FAX

HP DeskJet Plus, HP DeskJet FAX
(same driver basis as above)

HP OfficeJet (older models, PCL 3):

HP OfficeJet 500 / 600 / 700 / 1170C / 1175C
(Attention: Newer OfficeJets usually no longer compatible!)

HP Photosmart (older models):

HP Photosmart P1000 / P1100
(Early models only - later models use proprietary languages.)


good luck ...

3
Hardware / Re: HP Deskjet 3635 need a workable driver
« on: April 14, 2025, 09:45:29 pm »
Good day Klipp,

With my printer – Brother MFC-9970CDW – I had to activate lprportd in the TCP/IP settings.

I used a printer driver from a Linux package and integrated it into the system via CUPS.
Without lprportd, the printer showed no interest at all.
Now it prints beautifully – in both colors and shapes!

Many thanks to everyone.
Wishing you all the best and much success!

4
Programming / Re: Brainstorm: OS/2 on a Different Kernel
« on: April 04, 2025, 10:23:18 pm »
Regarding your question about the communication between CPI (Config.sys Protected-mode Interface) and the OS2KRNL:

CPI provides an interface for the configuration system (config.sys) during boot time and passes information to the kernel before the actual session management (like PM, DOS boxes, etc.) starts. This communication follows a well-defined structure that is processed by the loader—typically involving memory areas, flags, and structured parameter blocks.

The interaction is mostly asymmetrical: CPI delivers startup parameters to the kernel (e.g., via the "init-table" or system objects), but the kernel does not actively call CPI in return. Some modules (such as drivers or IFS components) make use of the provided information via DevHelp or other internal OS/2 APIs, which may be indirectly influenced by CPI.


Relationship between Loader, CPI, and OS2KRNL:
The Loader (OS2LDR) is the first component activated during the boot process.
It loads the kernel (OS2KRNL) as well as other protected-mode modules such as CPI, BASEDEV, IFS, etc.

CPI (Config.sys Protected-mode Interface) is loaded and initialized by the loader.
CPI processes the CONFIG.SYS entries and creates structured information that is essential during system startup.

These pieces of information are passed from CPI to the kernel in the form of:

SysInitData structures Memory blocks / flags / initialization tables
Environment variables and startup parameters (e.g. PROTSHELL, RUN, DEVICE, etc.)

The kernel (OS2KRNL) uses this data to:
Continue system initialization
Properly load drivers and services
Launch the graphical or text-based user environment (e.g., Presentation Manager, DOS sessions)
The communication is one-way – CPI passes data to the kernel, but not the other way around.


References:

IBM Redbook: OS/2 Version 2.1 – Volume 1: Control Program, Chapter 3 – "System Initialization"
https://www.os2museum.com/wp/redbooks/gg243376.pdf

OS/2 Warp Kernel – Theory and Practice by Gary Urban (summary)
https://www.os2museum.com/wp/?p=1906

OS/2 Museum Blog – deep insights into CPI, boot process, kernel internals
https://www.os2museum.com/wp/

IBM OS/2 Warp 4 Device Driver Kit (DDK), includes SysInitData and DevHlp examples
Archived version: https://web.archive.org/...

Alternative approach (modern design principle):
Instead of keeping CPI permanently available, one could introduce a new modular architecture, where a kind of “boot service” or “initialization manager” takes over certain CPI-related functions — but operates in user space, for example under PROTSHELL.


Advantages of a Boot Service in User Space instead of Classic CPI:
Modularity & Extensibility A user-space boot service can be updated or extended more easily, without modifying the kernel or OS2LDR.
New features (such as network initialization or dynamic device management) could be added as loadable modules.

Runtime Intelligence
While CPI only operates during boot time, an initialization service could monitor, adjust, or log system states at runtime.

Improved Error Handling
Errors in CPI often lead to boot failure.
A user-space service can handle such issues more gracefully, write logs, or provide notifications without compromising system stability.

User Interface Capability
A modern initialization service could offer a graphical configuration interface, similar to tools like systemd-analyze on Linux.
This is especially useful for systems like ArcaOS or OS/2 still used in production.

Bidirectional Communication with the Kernel
Using defined APIs, shared memory, or message channels, the service could communicate with the kernel in a controlled way.
This would allow dynamic changes to system parameters or runtime analysis of kernel responses.

Security through Separation
The boot service does not run in kernel mode, which means that any faults or attacks have a lower risk of destabilizing the entire system compared to kernel-level CPI modifications.



I hope I understood the information correctly. I'm no technical genius.
Thanks everyone and for the additions.



5
General Discussion / Re: Brainstorm: What is Next with OS/2 ?
« on: March 31, 2025, 11:44:03 am »
Dear all,
How about an OS/2 or ARCOS without Windows and DOS? Wouldn't that be easier?

Thanks everyone

6
General Discussion / Re: Brainstorm: What is Next with OS/2 ?
« on: March 21, 2025, 10:13:54 pm »
What would need to be changed in ARCAOS to have a modern network?

**ChatGPT Response:**
To implement or improve a modern network in ArcaOS, several changes and enhancements would be necessary, as ArcaOS (a development of OS/2) has a more limited network architecture compared to modern operating systems like Windows or Linux. Here are some key changes that would need to be made:

1. **Updating the Network Stack Software**:
   - **TCP/IP Stack**: ArcaOS uses the "IBM TCP/IP for OS/2" stack, which has not been maintained for a long time. Updating or switching to a more modern network stack (e.g., `inetd` or an open-source project) could improve network performance and compatibility.
   - **IPv6 Support**: The current TCP/IP stack in ArcaOS only supports IPv4. To support modern networks, IPv6 would need to be implemented or at least complemented with a compatible IPv6 stack.

2. **Extending Network Protocols**:
   - **Modern Protocols**: Support for current protocols such as HTTP/2, HTTPS, FTP/FTPS, WebSocket, and other common network protocols should be added to ensure interoperability with modern web services.
   - **SMBv2 and SMBv3**: The current network file system protocol, SMB (Server Message Block), is outdated and uses SMBv1, which is increasingly blocked in modern networks. Implementing SMBv2 or SMBv3 would be necessary to remain compatible with modern Windows and Linux servers.

3. **Driver Updates**:
   - **Network Card Drivers**: Support for modern network cards (e.g., Gigabit or 10-Gigabit Ethernet) would need to be added, or existing drivers would need to be updated. Many modern network cards are not directly compatible with ArcaOS, so specific drivers would need to be developed or updated.
   - **Wi-Fi Support**: ArcaOS has limited support for Wi-Fi. The development and integration of modern Wi-Fi drivers for common chipsets (e.g., Broadcom, Intel, Realtek) and support for Wi-Fi 5 (802.11ac) or Wi-Fi 6 (802.11ax) could expand the network capabilities.

4. **Firewall and Security**:
   - **Firewall**: A modern firewall capable of monitoring and controlling traffic based on current security standards would need to be developed or integrated.
   - **Encryption**: Support for modern encryption protocols such as TLS 1.2 and 1.3 for web communication and VPN services (e.g., OpenVPN) should be enhanced to ensure secure communication.

5. **Integration of Modern Network Services**:
   - **DHCP and DNS**: Support for DHCP (Dynamic Host Configuration Protocol) for automatic IP address assignment and advanced DNS services would need to be integrated or improved.
   - **NAT and VPN**: Support for Network Address Translation (NAT) and VPN protocols like OpenVPN and WireGuard could enable ArcaOS to securely communicate in modern networks.

6. **Updating the User Interface**:
   - **Network Management**: A modernized user interface for network management (e.g., for configuring IP addresses, DNS, Wi-Fi, VPN) could improve the usability of ArcaOS and bring it on par with other operating systems.

7. **Software Compatibility**:
   - **Modern Applications**: Many modern applications and services rely on the latest network standards. Compatibility with these applications requires significant improvements in the network protocols and interfaces in ArcaOS.

**Summary**:
To equip ArcaOS with a modern network, extensive changes would be needed, both at the network stack software level and in terms of drivers and security protocols. While some of these changes could be addressed with new software solutions and drivers, it remains a long-term project, as ArcaOS was not originally designed for use in modern network environments.

**I don't know if all of this will be achieved, but I thank you.**

7
Virtualization / Re: print under virtual box
« on: March 07, 2025, 10:08:19 pm »
Good day everyone,

Thank you very much for your valuable responses.

I have set up the following configuration:

Used the driver from the Linux package:
mfc9970cdw.ppd

Installed it via CUPS
Connected it via LPD and made the necessary entries in the settings
It works great! I haven't managed to get the scanner working yet, but who knows—maybe I'll succeed in that as well.

Printing from Lotus Word, PDFs, and text files works flawlessly—and in color!

Thanks to everyone!

8
Virtualization / print under virtual box
« on: March 06, 2025, 08:27:00 pm »
Good day everyone,

I am writing here in this forum because I somehow cannot post on os2.org as I am unable to register.

https://www.os2.org/viewtopic.php?t=4218

The following was written in the forum:

ArcaOS 5.0: Printing from VirtualBox on Brother DCP-J140W
Post by 1967er » Fri, Dec 13, 2024, 17:09

Hello everyone,

I have tried all possible solutions.

System: ArcaOS (ver: The Operating System/2 Version is 4.50)
Printer: Brother DCPJ-140W (WLAN) with Linux PPD file
VirtualBox: 7.1.4
Network: Bridged mode
The printer can be pinged from the VM, and sometimes it is even automatically detected with a printer queue (!).
However, I always use lpd://192.168.178.37/BINARY_P1, which works well under Linux and Windows 11.

A print job is created, becomes visible, and then disappears as if it had been printed. However, nothing is actually printed.

Where should I start troubleshooting? PPD file? I can’t think of anything else.

Best regards & thanks,
Jürgen

I also needed a PPD file for my system to get my printer Brother MFC 9970 CDW working.
At first, I tried using FTP, but this resulted in only .txt files being printed.

In the help file of TCP (C:\TCPIP\HELP\lprpdrvr.hlp), it is stated:

"With LPD connections, printer icons on the desktop can be redirected to remote LPD printers.
Before submitting print jobs to an LPD connection, the program LPRPORTD must be activated.
Use the 'Configure Automatic Startup of Services' page in the 'TCP/IP Configuration' notebook to start LPRPORTD automatically.
The 'TCP/IP Configuration' notebook is located in the Internet folder (LAN)."

Set up LPRPORTD in the TCP/IP configuration and direct the printer object to the correct port.
Then, printing should work.

Thanks, everyone!



9
Hello everyone,

look, I also found something from IBM
I thank you

http://www.ibmfiles.com/index.htm

Pages: [1]