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 - Doug Clark

Pages: 1 2 [3] 4 5 ... 17
Setup & Installation / Win-OS/2 installed on non-boot drive
« on: May 29, 2021, 05:40:52 pm »
If I remember correctly you can install Win-OS/2 on a drive other than the boot drive.   I also seem to remember that when you do this some environment variable is set to indicate which drive holds the Win-OS/2 system.

So my questions are:

1) does this environment variable, or some other means, exist to determine which drive Win-OS/2 is installed on?

2) What is the directory structure when installed on a different drive?   (Normally it is C:\OS2\MDOS\WINOS2)

I think you might be able to make a modified program object which would copy the file name used when opening  a program to a central "recently opened" list.  The fully qualified file name should be sufficient since the file type would link it to the application. It would probably work with files dropped on the program object, specified as a argument on the Program page, or when double clicking on a file in a folder.  That wouldn't be that difficult to do.  The problem is it would only work when using the WPS to open an app - meaning it would not pick up files opened from the File menu inside the app.  It probably would also not pick up files dropped on an already open application window (as opposed to files dropped on the Program object).

I did a little of this as a way of making long file names work with Win-OS2 apps.  You can make it work when going through the WPS but not when going through the app itself unless you have a way of hooking into the File open feature of an application.  You MIGHT be able to do that if you provided a modified File Open dialog (such as FOC) that would copy the file(s) specified to the central list.

After thinking a minute more - instead of copying the file name to a "central list" what should happen is a shadow is created of the file in a ROD folder.  That way if the file is renamed or moved the "list" would still be accurate due to the magic of the WPS and shadows.

Listing the recently opened docs would then be simply opening the folder containing the shadows - and double clicking on the shadow would start the app.

I don't know if you can make shadows of file system objects stored on media that doesn't support EAs.  If the shadow is stored in OS2.INI then you probably can.

Okay - it appears my problem is the open class library is stripping off mp2 for command messages.  Mp2 is where the EPM "command" is stored when it sends an EPM_EDIT_COMMAND message to itself (rather to the E-MLE window)

I think this because 1) mp2 in a EPM_EDIT_COMMAND message is, essentially, blank by the time it arrives as the E-MLE window procedure.  And 2) because of what I read in the book "Power Gui Programming with VisualAge for C++"

Quoting from the book
"An Open Class LIbrary library application is a presentation system application. Open Class Library itself provides a single window procedure that operates for most window represented by IWindow objects.  Every time you create an object derived from IWindow [which you must do to integrate a non-OCL routine with the OCL application - my addition] the object registers this window procedure as a subclass window procedure.   As a result, Open Class Library's window procedure gets the first chance to process all messages that the presentation system sends to a window."

Quoting again later in the book
"Open Class Library treats the field that identifies the source of the command (the high word of IEventParameter1 in the Windows operating system or the low word of the IEventParameter2 value in the OS/2 operating system) as if it contains only that value instead of data that you choose."  It goes on to say that as it passes that event (window procedure message) it alters the value in mp2.

Has anybody written an open class library handler to capture application messages before they get routed through the open class library ICommandHandler?

My current solution is to pull off the value that should be in mp2, store it somewhere in memory, subclass the E-MLE window procedure and for each type of EPM_EDIT_COMMAND message translate into an EtkExecuteCommand() function call.  Which is crude and I will have to do that for each ETK message that needs to transfer something in mp2.

Could you post the  6.03b version of the ETK here please?

Has anyone successfully used the EPM Etoolkit  to create an EPM based MLE in a VisualAge C++ v 3.0 IOC application?

Sample 2 from the etoolkit shows an E-MLE inside of an EFrame inside of an application window.  The E-MLE is the actual editor guts; the EFrame adds scroll bars, message line, title bar etc.  I lightly modified sample 2 from the etoolkit SDK, compiled with VAC 3.0 and it works - attached as

But when I convert that into a "custom control" as a C++ class, to integrate with the user interface part of the IOC library, part of the E-MLE stops working.  It appears to be the part that sends messages, or receives messages related to editor commands.  What I THINK is happening is the dispatcher that the IOC uses to intercept and route window messages is somehow not sending the messages to the E-MLE window procedure.  Or rather some of the messages, because other messages clearly are getting through.

So has anyone converted a customized PM window/control into a IOC user interface object that can be inserted into various other IOC UI objects? is the lightly modified Sample 2 from the eToolkit sdk. contains my class EpmMle (descended from IControl) which is my attempt to integrate an EFrame/E-MLE into a custom control that can be used in IOC.  Run testmain.exe from and try issuing a command from the menu;  Command - Command Dlg and then type some EPM command, such as SAYERROR 'Hello'   You will need the VAC 3.0 runtime libraries to run testmain.exe

That sounds like a pretty good compromise - considering the US is the land of the lawsuit.  It is almost like the right to sue is in the Bill of Rights.

Even if there was not one dedicated site for all these "additional" applications, just a list of apps and links of where to download (almost the same thing) would be great.  I saw a number of apps in this thread that I had never heard of before.

As for media players, I haven't used Mplayer or PMplayer but I do use VLC and it is VERY impressive.  Kudos and thanks to the VLC team and especially
KO Myung-Hun for porting to OS/2.

I would suggest VLC.  Don't know what the issue is with software patents v SMPlayer/MPlayer

General Discussion / Re: Revolutionary PC Technology
« on: January 14, 2021, 09:20:07 pm »
The other question here is how did the PC revolutionize the software industry.

Mainframe and minicomputer software cost tens of thousands to hundreds of thousands of dollars.  And all required support agreements that cost tens of thousands of dollars a year, which kept the sofware companies in business.

With PCs in the $3,000 to $5,000 price range no one was going to pay $20,000 for software so the software had to be cheaper.  I remember when FrameMaker ported FrameMaker v 3 to the PC and sold it for $500 a copy (I bought a copy) - which did the same thing the $2,500 a copy version did on workstations and minicomputers.

The difference of course was volume, but once you have sold your software to everyone that owns a computer, how do you stay in business?  The answer is, you don't.  You can come out with upgrades and new versions for awhile, but at some point there are no more new features to add.

So OS/2 biggest liability is also its greatest asset - that it doesn't change much. We can still run software purchased/released in 1993, and can run it on new hardware.  Software that is valuable, but is no longer available or has never been ported to the ever newer Windows versions, and/or the manufacturer is out of business.

So the revolution of the PC is that it drove down the cost of software but it made it almost impossible for a software company to stay in business for more than a decade.

General Discussion / Re: Revolutionary PC Technology
« on: January 14, 2021, 08:50:46 pm »
I think the reason why OS/2 "failed" in the market place is the same reason all other PC operating systems "failed" - you can't compete with an operating system that is free and comes already installed. i.e. Windows.  Microsoft was smart enough to know that it needed to dominate marketing - and did so with its  agreements with PC manufactures.

Do you all remember how hard it was to install OS/2 2.0?  Now imagine your parents doing that.

IBM certainly started out not understanding the consumer market place.  When I bought OS/2 v1.3 the only place to buy it was at an IBM retail store and those stores closed at 5:00PM and weren't open on the weekend.
But by the time version 2 came around I think IBM was much smarter about marketing to consumers and OS/2 became available in software and computer stores.

But you couldn't buy very many new computers with OS/2 preinstalled - a few manufactures gave you the choice, but for those that did OS/2 always cost most than Windows when preinstalled.

As long as the govt allowed these sales agreements between Microsoft and PC makers where the PC maker paid Microsoft for every PC shipped, regardless of whether Windows was installed or not,  no other operating system really had a chance.

IBM certainly did pursue third party application makers, even going to far as to pay some companies to port their software to OS/2.  But the preinstall strangle-hold MS had on PC makers always meant that OS/2 would never beat Windows.

Events / Re: Preparing for Warpstock Virtual 2020 ...
« on: November 07, 2020, 09:30:11 pm »
Nice presentation Sigurd.  I  enjoyed all the presentations.  Thanks to the presenters and all the others that made Warpstock come together.

Setup & Installation / Re: Problem with SNAP resulution
« on: October 17, 2020, 11:17:56 pm »
AN bought the driver, but they have done absolutely NOTHING with it, other than change the branding to Arca Noae

As Dariusz points out AN did "something" to it because the AOS version of SNAP runs on a multicore machine with all CPUs enabled without hangs where the SciTech version does not.  For me it was not only the startup of the WPS but I would also experience hangs during operation, sometimes an hour or two after booting up.  AOS version does not have those problems.

Martin - it seems strange that you are missing the check boxes for wide screen and 4x3 resolution.  I am running AOS and SNAP and those check boxes appear on the second of the SNAP pages in the Screen object on my system.   That would seem to indicate there is something messed up with the install.

Dariusz also pointed out he limits his memory usage for SNAP to 24 MB "for other hardware."  While I don't think this is affecting your screen resolution issue, once you get that working you probably should limit the memory SNAP uses.  Apparently SNAP allocates main memory based on how much is on your card, and that eats up virtual memory that might otherwise be available for vBox and other applications that are very memory hungry.  So you probably want to limit the amount of memory SNAP uses. There is a discussion about this on another thread - try searching for memory and SNAP

Hardware / Re: Someone tried OS/2 with 3840x2160 Display?
« on: October 16, 2020, 07:17:46 pm »

Could you please hook up the Samsung S32D850T and see what resolutions the ATI X850 XT will drive though SNAP?

I am currently running two 1920x1080 monitors as a dual-head setup and am looking for more vertical resolution - say 1920x1440.
So if SNAP and the ATI x850 XT would drive the samsung at 1920x1440 that would be perfect for me.

Applications / Re: SAMBA Network access denied
« on: October 02, 2020, 08:59:52 pm »
Thank you all for your responses - especially you Neil for you excellent documentation.  I finally got it to work and I conclude my problems where mostly stupid user errors on my part plus some mysterious issues I don't understand.

And thanks Paul for explaining the relationship between klibc user management and samba users/groups/

For anyone else that may have similar problems.

I was accidently installing samba-1-3-0-122.wpi instead of samba-1-1-4-804.wpi Stupid mistake on my part.  What is labeled samba-1-1-4-804.wpi actually installs samba server version 3.3.16  What is labeled samba-1-3-0-1022 installs a later version of Samba server.  I was finally able to get past the root user login in order to create Samba users with the later version (perhaps because I changed to a password to at least 8 characters long?) and get the server running, but I could not see the server from ArcaMapper or connect from WInNT.

Suggest to the Samba gurus - could you please make the version number of the install packages match the version number of the server that is being installed?

When I uninstalled the later version and installed Samba version 3.3.16 I could see everything from ArcaMapper and from WinNT in vbox and make connections.  So all is good.

I am probably a bad person for using the earlier version, but it works.  And I can connect from Macs, various windows versions and ecs/AOS.

Thanks again for all the responses.  The discussion on the later versions of Samba has been interesting.

Applications / Re: SAMBA Network access denied
« on: October 01, 2020, 03:24:55 pm »
I am sorry - I should have given more information.

The system is AOS 5.01

I installed the Net drive plugin for Dropbox which requires kLIBC, and if memory serves me, also kLIBC user manager, which I seem to remember was required for authentication at Dropbox.  That was months ago.

I installed Samba server 3.3.16 on the machine using the WPI package - in order to exchange files with Windows NT on vbox, since vbox doesn't implement shared folders for Windows NT.  I believe the install process prompted me for a password for root, which I entered.

Now when I try to add the Samba Users or Groups I am prompted for a password for root, and no password I enter works - they all come back with network access is denied.

I  deleted  pwd.db, master.passwd, spwd.db and because I was brave and desperate, master.passwd.bak and spwd.db.bak  all in unixroot\etc, and ran the Samba reload configuration which went through part of the setup, including prompting me for a password for root, but I have the same issue.

When I start kLIBC user management I now get a dialog that says "Samba user management found. Continue?"  The title of the dialog says: WarpIN:\Samba\SmbUsers\1\0\1\804

I have no idea why WarpIN would be involved at this point, it is not running.  I cannot find any documentation on kLIBC user management.  kLIBC user management has a button for edit user, but clicking that on root brings up a dialog that doesn't allow any changes to root.  kLIBC user management, when in debug mode, shows a password for root but that password still does not work when trying to add or modify users in Samba.

I know this Samba version and install package (*WPI) works because I have it installed on my server (eComStation machine) and I used that same package to install on AOS which is where I am having problems.

So do I need to delete everything in UNIXROOT (and the Samba tentacles elsewhere) and start re-installing or is there a less nuclear option?

Applications / SAMBA Network access denied
« on: September 30, 2020, 11:21:30 pm »
I am trying to set up samba 3.3.16 and when attempting to execute Samba Users and Groups I get the message

Sys0065: Network access is denied.

For some reason I also have KLIBC User Management - I think it was for the Drop Box plugin
Any thoughts on how to fix this.

Pages: 1 2 [3] 4 5 ... 17