OS2World.com Forum is back !!!
Remember to visit OS2World at:
http://www.os2world.com
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.
Thanks, yes it does. But on reflection I think the ball is gliding more than turning. Even though it’s brand new it’s a Microsoft ball mouse (new old stock) and I have a funny feeling it’s just not rotating properly. And that would of course cause exactly the problem I’m experiencing.For Warp 3 systems it's more useful to use the IBM ScrollPoint mouse driver (https://public.dhe.ibm.com/ps/products/os2/os2ddpak_cur/scrollms.exe).
So I’ve reverted to my Logitech PS/2 optical mouse and will take advantage of AMouse to see if I can get the wheel working for scrolling.
Thanks!
Richard.
What about fiber channel, is there any FC adapter known to work with OS/2?Yes, of course. The Compaq StorageWorks around 1999/2000 supported OS/2 Warp Server (http://h10032.www1.hp.com/ctg/Manual/c00688043.pdf).
I installed some Win16 networking application, and I realized that it won't work without some kind of WinSock support.There is no reason for adding the support. It should be available from IBM TCP/IP for OS/2 by default (VDOSTCP.SYS). Only configuration for \TCPIP\dos\etc\RESOLV should be done.
https://mochasoft.dk/win311x.htm
Apparently I've forgotten how to add WinSock support. Anyone remember this one?
I have these questions:Please give us a FRU and I can check.
1) Which are the "Support Element" software versions that runs on OS/2 ?
2) Some Mainframes came with a Thinkpad with OS/2 preloaded, how it is connected physically to the mainframe? Serial/Parallel/PCMCIA/Network?It's not connected physically. Usually a console controller was used.
3) Some other mainframes came with a PC with OS/2 (I think it is called HMC - Hardware Management Console ). how it is connected physically to the mainframe?Please give at least a part number - there were dozens of devices which run internally OS/2 for different tasks.
4) I don't think I can find a list of which mainframe models used to be compatible with OS/2's HMC, but I will like to build one. I only have the Multiprise 3000 and the IBM z890 on my list, if someone remember some other model that has OS/2's HMC or know where to get this information, please let me know.What's the question here? Do you want to operate 15 to 20 years old systems and need replacement parts today? It would be cheaper to use emulation or a zPDT.
1) There was a PCI card (also some older ISA) called P/390 that used to be "a mainframe in a card" that you plugged into a PC so you can do development and testing for mainframe applications.In fact there were different PCI adapters. And there was never an equivalent ISA solution. It's not helpful to mix here different architectures. Neither a PCI nor an ISA adapter would fit into a PC. The S/370 solution for the XT consisted of 3 boards and for the AT of 2 boards. Non of those adapters is required for "development and testing" of "mainframe applications". You can simply use the usual development environment via 3270-sessions or one of the GUI solutions.
Perhaps I can add a list of these programs and then a conventional VIO window gets started, or I define a command /VIO where the user can start a VIO window in a command.This may only work for programs that don't use the following calls:
but apparently not as straightforward as calling single API methods like win32's CreateMenu, AppendMenu, SetMenu, etc.At least the mentioned functions will behave the same as their Win32 counterparts.
IIRC, attachments have to be base64-encoded,[QuoteNot true, even for old-school SMTP.Quotebut I don't know how they are appended to the message text.Please take a look at MIME.
RXHELO which utilises RXSOCK is a good starting point, but nowadays authentication features should be considered unless you're running an MTA for in-house operations.
At the picture there's FAT, but on later installation I changed type to HPFS. My VM hard drive is only 20 MB.That's to small, please use a proper partition size (200 - 400 MB). When using VirtualBox the host adapter support should be changed to the BusLogic SCSI adapter. LADDR support on the installation disks needs to be updated by including BOOTBID.BID. Using ESDI-506.BID for emulated IDE drives can cause more problems including the symptoms shown on the mentioned pictures. Furthermore the serial ports for communication should be setup properly in VM configuration.
