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 ... 21
31
Thanks for the reply Peter.

I have read them both, and they are for slightly different situations than my issue. The solution turned out to be:

1) Switch BIOS to UEFI only

1) Boot to AOS -

2) Open the Logical Volume Manager - Simple

3) On the menu go to System - Boot Menu - Install/update

4) Select  Air Boot on the drop down for "Boot menu program"

5) Click on Install and reboot

6) Set BIOS to Legacy Only

7) Select Windows 7 on the Air Boot menu.

It boots to Windows.  To boot to AOS

1) switch BIOS to UEFI Only

2) Select AOS from the AN Launcher

Kudos to the AOS team - excellent job. 

See ya at Warpstock






Martin's post ws

32
I have a laptop (thinkpad 530) which had AOS 5.0x and Windows 7 installed with Air Boot for switching between the two.  They are both installed on a MBR drive and using legacy bios.  The problem was Win-OS/2 programs did not run in AOS on this machine.

So I "upgraded" to v AOS 5.1. My BIOS has a setting for: UEFI, Legacy, or Both.  I first tried switching the BIOS to both, and installing AOS v 5.1 as an upgrade to my existing system.  That did not fix the Win-OS/2 issue.  So I switched the bios to UEFI only, and performed a new install of AOS 5.1 on top of my existing C: partition - which contained the old AOS 5.0x.  The install program wants a EFI partition and complained about not enough primary partitions - I already had 3: one for the AOS v 5.0x, one I assume for Win 7, and a third for who knows what.  So I deleted the smallest partition (300mb), created an EFI partition and the installation was able to continue.  I did not change the drive from MBR.

And Win-OS/2 now works.  Yeah.

I would like to now be able to boot into my already existing Win7 partition/system.  I am assuming it is the 93MB primary partition that shows up in Simple LVM.

Anybody have any ideas?



33
Communication / Re: COM Port Setup
« on: November 29, 2023, 10:41:30 pm »
Chris,

If you are just running USB to Serial adapter you do not need COM.SYS in your config.sys.   If you are using a serial port on your motherboard (which you mentioned) you probably do need the COM.SYS - and VCOM.SYS for Dos programs - unless your device supplies its own device driver.

The device driver you need for a USB to serial adapter depends on the adapter - meaning the chipset in the adapter.  It also depends on which version of the USB stack you are using on your machine.  There are also parameters you can supply to the DEVICE=  line in your CONFIG.SYS  for USB to serial adapters that may affect the operation of the adapter.  I would suggest you check the USB section of the wiki on Arcanoae.com.  It will potentially save you time and effort.  I speak from experience.

34
Setup & Installation / Re: ArcaOS Sluggishness
« on: October 31, 2023, 05:28:57 am »
Roderick,

I have a serial port on the motherboard  - but I am running AOS 5.0x, i.e. MBR and legacy BIOS so I don't know if I can be any help.

35
Setup & Installation / Re: ArcaOS Sluggishness
« on: October 14, 2023, 07:31:00 am »
Chris,

I am not sure of your situation.  It is a upgrade of an existing system to AOS  ver 5.1 and has become slow after the upgrade to v 5.1?  Or have you been running AOS 5.1 for awhile and it has become slower and slower?

As for filesystems, drives, and speed: my experience is JFS is much faster in chkdsk than HPFS.  SSDs are MUCH faster than spinning  drives on chkdsk and any kind of directory access - like opening a folder - even if both the spinning drive and SSD have the same sustained transfer rate.  Spinning drives also have the obvious problem of fragmentation over time.

If you have upgraded AOS and are accessing network drives, and the slow down occurred after the upgrade, could the NIC driver have changed?  I have had speed issues using the  multimac driver for the network adapter built into my motherboard, which I solved by installing a Intel pro 1000 NIC and using the Intel driver.  Don't know if it was multimac, my particular network adapter/motherboard combo or something else in my system.  But opening a file dialog box (FOC) was painful because of the slow access to networked drives.

My recommendation: boot drive/partition on an SSD,  swap file and firefox profile and TEMP directory on a spinning drive because of SSD wear and potential slow down.  Or if you have enough RAM, use a RAM disk for the TEMP directory.   If you are using the AOS RAM disk, format the RAM drive HPFS (unless that has been fixed.)
Use/add an SSD even if you are running SATA 2 or slower bus on your motherboard.

36
Programming / Re: WPS dragged object handle
« on: October 01, 2023, 12:18:19 am »
Thanks Lars for the tips.

WPS programming is actually pretty interesting.  The difficult part is finding all the "special" tricks or knowledge you need to do some stuff.

For anyone else starting out, I found the book "OS/2 Workplace Shell API" by Mindy Pollack to be very helpful because it lists a lot of those special things that are helpful or necessary to know.  Although the book doesn't go much in the SOM aspect - it stays pretty much in the WPS, so it doesn't have Lars' tips.

37
Programming / Re: WPS dragged object handle
« on: September 30, 2023, 07:05:39 am »
Thanks Rich for the help and info.

There are portions of the app that run in the WPS process and portions that run outside the WPS process.  I was planning on using RWS for the outside-of-WPS-process parts. (BTW thanks for building and releasing that)  I did not know that it was bundled with all AOS versions - that will help with building the install process.

For anyone else that might follow this topic, the code section looks something like this
----------------------------------------------
if( DrgVerifyRMF( DrgQueryDragitemPtr( pdrgInfo, ulCount),"DRM_OBJECT", NULL))
{
     WPObject * pObject;
     PDRAGITEM   pDragItem;     
     
     pDragItem =  DrgQueryDragitemPtr( pdrgInfo, ulCount);
     pObject = OBJECT_FROM_PREC(pDragItem->ulItemID);     
     if (_debug) PmPrintfPtr("wpDragOver   DRM_OBJECT name: %s",_somGetClassName(pObject));

   ...
----------------------------------------------------------------------
after you know that ulItemID contains pointer to the container record (thanks Rich)  for the object, the magic sauce is the WPS macro OBJECT_FROM_PREC(), which extracts a pointer to WObject  from ulItemID

-- editor to remove late night operator error --

38
Programming / WPS dragged object handle
« on: September 29, 2023, 12:18:52 am »
When you drag a WPS object (or anything actually) a _DRAGITEM is created to store data about the item being dragged, the structure of DRAGITEM shown below
-------------------------------
typedef struct _DRAGITEM {
  HWND       hwndItem;           /*  Window handle of the source of the drag operation. */
  ULONG      ulItemID;           /*  Information used by the source to identify the object being dragged. */
  HSTR       hstrType;           /*  String handle of the object type. */
  HSTR       hstrRMF;            /*  String handle of the rendering mechanism and format. */
  HSTR       hstrContainerName;  /*  String handle of the name of the container holding the source object. */
  HSTR       hstrSourceName;     /*  String handle of the name of the source object. */
  HSTR       hstrTargetName;     /*  String handle of the suggested name of the object at the target. */
  SHORT      cxOffset;           /*  X-offset from the pointer hot spot to the origin of the image that represents this object. */
  SHORT      cyOffset;           /*  Y-offset from the pointer hot spot to the origin of the image that represents this object. */
  USHORT     fsControl;          /*  Source-object control flags. */
  USHORT     fsSupportedOps;     /*  Direct manipulation operations supported by the source object. */
} DRAGITEM;
--------------------------------

I am trying to identify the object that is being dragged over my window - either the class of the object or the specific object itself.  Is there someway of translating the hwndItem  or ulItemID  value into a WPS object handle?  I am hoping to avoid searching the source container for the source name in order to find the object being dragged.

There is a value in ulItemID, put there either by the WPS or xWorkplaceShell when a WPProgram type object is being dragged.  Anyone know what that value is?

I only want to accept dragged WPObjects of a certain type being dropped, and disallow everything else.

Thanks in advance

39
Applications / Re: [LOOKING] OS/2 1.x, Word/Excel for OS/2 related stuff
« on: September 21, 2023, 06:21:01 pm »
Dave,

Thanks for the WLO info.  I had forgotten about that.  My guess is the DLLS (GIDI.DLL, KERNEL.DLL, KEYBOARD.DLL, PMMETA.DLL, PMWLO.DLL, SOUND.DLL, SYSTEM.DLL, USER.DLL and WIN87EM.DLL on Corel's  WLO diskette) are needed for running the Corel "utilities" (Mosaic, Trace, Font conversion) in OS/2 v 1.x, but are not needed in OS/2 v 2.x and above.  CorelDrw.exe itself appears to be a full fledged 16 bit OS/2 v 1.x PM program and doesn't need the DLLs from the WLO disk.

After looking at it this morning, the reason why the utilities don't start from a WPS Program Object is the Program Object is assigning the wrong program type to the executable.  When you enter a name in the Program field of Program Object it reads the executable to determine what type the executable it is, and sets that type into one of the fields in a structure called ProgDetails.    It uses this value itself in order to disable or enable portions of the Sessions tab/page in the settings notebook.  ProgDetails is queried by the system when it starting a program - either by association or by double-clicking on the Program Object itself. 

After reading the read.me you posted my GUESS on why this is happening is an executable that has been created by linking to the WLO library changes something in the executable that confuses the WPS Program Object.  It is reporting this in ProgDetails as a program type 3, which is a PM program.  If you change the program type in the ProgDetails to something that is windows, like type 15 for instance (standard seamless VDM) the program will run from a WPS Program Object.

FWIW the WPS Program Object, and OS/2 itself, also cannot distinguish between a true Win32 executable and a Win32s executable.  Which makes it a little difficult to execute an ODIN program directly from a WPS Program Object.

To complicate the matters more for the Corel utilities, it appears the utilities were converted to full PM programs in some later version but used the same executable name(s).  The database (DATABASE.TXT/DATABASE.DAT) that OS/2 uses for migration and for automatically populating values in a WPS Program Object based on the executable file name, shows MOSAIC.EXE as an OS/2 program.  Ivan, who has version 2.5 of CorelDraw, could confirm if the utilities in that version are full OS/2 apps or still WLOed Windows apps.

40
Applications / Re: [LOOKING] OS/2 1.x, Word/Excel for OS/2 related stuff
« on: September 21, 2023, 07:49:31 am »
What I have is Corel version 2.0.  Turns out it does run - mostly - on AOS.  I had saved a zip of a previous installation and tried to get that to run - no luck.  But when I installed off of the original floppies it did install, and run.  However it demands to be installed from drive a:  It is amazing to me that 30 year old floppies still work, but most of them do.

I have attached a zip file with pics of most of the docs.

The date on the files is 07/24/1991.  CorelDrw.exe is  an OS/2 v 1.3 program.  CorelTrc, Mosaic, and Wfnboss are windows programs. And, interestingly enough, the windows programs will not start from their program objects in the folder - they do start if you click on the executable in the directory.

The manual is for the DOS and Windows versions.  There is no mention of OS/2.  There are no install instructions for OS/2 - at least that I have left and/or could find.  The install program doesn't touch any of the 4 diskettes with clip art.  It also doesn't install a mysterious disk labeled WLO, which contains a number of DLLS and a command line program that copies them to C:\OS2\DLL

Since CorelDrw is a OS/2 v 1.3 program it expects a control panel - there is an option for it in the File menu.  And it doesn't go through the normal printer setup. Plus it thinks my postcript printer is a non-postscript printer - which is probably why the trumpet printed in black and white.

Anything else you need to know about CorelDraw 2.0?

41
Applications / Re: [LOOKING] OS/2 1.x, Word/Excel for OS/2 related stuff
« on: September 20, 2023, 10:29:15 pm »
Sorry I can't help with CorelDRAW 2.0 for OS/2 but I do have a working copy of CorelDRAW 2.5 for OS/2 for OS/2 v 2.0

I purchased a copy of CorelDraw 2.0 for OS/2 when I first came out.  Actually it may be v 2.01.  I have the manual, font list, plastic template for measuring font sizes, reference card, two character reference cards and the typeface3 reference chart.   I may even have the original floppy disks in the basement (shudder).  It was a nice package.  I don't know if it runs on AOS, but it certainly ran on OS/2 2.0  Let me know what you want pics of.

42
Programming / Re: Using AI to Code for OS/2
« on: September 20, 2023, 05:34:31 pm »
Are you SURE the baptists aren't working on building open source OS/2?

Their motto, after all,  is  hope, truth, and community.

43
Applications / Re: Installing VisualAge C++ 3.0 on ArcaOS 5.1.0
« on: September 10, 2023, 02:56:07 am »
Robert,

One last warning about VAC 4 Visual Builder.  If adapter 0 for TCP/IP is not active the Visual Builder part will not start.  For desktops this is usually not an issue, because most people only have one adapter specified in TCP/IP for a desktop machine.  But if you are using a laptop, and are switching between wireless and wired networking, then you probably have two adapters specified: adapter 0 and adapter 1: one is used for wireless connections and the other is used for wired. When you switch between wireless and wired one of those adapters is made inactive and the other is made active.

I am doing this from memory so I might be mis-stating  something.  But I believe if you are using a wireless card in your laptop you can choose whether adapter 0 is used for the wireless or the wired connection.  Whichever you choose, that will be the only type of connection you can use with version 4 Visual Builder.  This is not an issue for version 3.

And one warning for Visual Builder version 3.  I sometimes get a bunch of really strange error messages when I compile a project.  It appears the compiler gets confused.  Usually rerunning the compiler fixes that issue - the error messages.  I sometimes have had to rerun it 3 times, and once it took 4 times.  So if you are faced with a bunch of strange error messages when compiling, run the compiler again, a couple of times, before you spend time investigating the messages.

And sometimes you have to delete all the object files (*.obj) and recompile.  So if something that was working suddenly stops working, delete the object files and recompile.

44
Applications / Re: Installing VisualAge C++ 3.0 on ArcaOS 5.1.0
« on: September 08, 2023, 12:46:48 am »
Robert,

Do you have fixpack 1 installed for VAC 4?  That fixes instability problems.  If you click on the Help - About VisualAge C++ menu item that dialog will say if the fixpack is installed - see attached.  Unfortunately the fixpack breaks the links from the help "panels" to sample code.  The samples are still there, you just have to navigate to them manually.  I haven't had a crash with VAC 4 for years.  But I do have to Clean (under Program Workbook menu item) occasionally. 

You probably already have this book, but if not I highly recommend "Power GUI Programming with VisualAge for C++" by Tsuji, Love, Law and Olson.  It covers IOC version 3, but most of the concepts and specifics also apply to IOC v 4.  And it comes with LOTS of code samples. Very good code samples.  For example it was from one of the code samples that I got the idea for how to get color tabs in "classic" notebook controls - see attached. (I like the classic style notebooks better than the Warp 4 style notebooks that have the tabs along the top.

For Visual Builder I recommend  "VisualAge for C++ Visual Programmer's Handbook" by Nilsson and Jakab, and "Object-Oriented Application Development with VisualAge C++ for OS/2" by Carrel-Billiard, Jakab, Mauny and Vetter.  Those both are written for VAC 3, but the concepts for how Visual Builder works and how to construct parts, make connections, etc. all carry over from version 3.  A note of caution though - VB was rewritten from v 3 to v 4 and a project built in version 3 Visual Builder will not migrate to version 4.   

45
Applications / Re: Installing VisualAge C++ 3.0 on ArcaOS 5.1.0
« on: September 07, 2023, 06:27:28 am »
vac++ V 3.0x does have both multithread and single thread versions of IBM's libraries.  Plus
there is an "update" out there that adds multi-thread capability and ODBC support to Visual Builder applications for version 3.0x.

For me the library and the tools that are bundled with a compiler are usually more important than specific attributes of the compiler like compile time and executable size, etc.   And the quality of the error messages that tell me what stupid thing I have done in my code.

Versions 3.0x/3.5, 3.65 and 4 all include extensive libraries for C++, including a very powerful library for building user interfaces. Versions 3.0x/3.5 use version 3 of the IBM open class library (IOC),  Versions 3.65/4 compilers are bundled with IOC version 4. Parts of the IOC were rewritten between versions 3 and 4.  The v 3 of the IOC seems more optimized (for performance) on OS/2 than v 4- at least the user interface parts of the library.

Version 4 of the compiler bundles a version the C++ standard stl - earlier versions do not.

I like using the visual builder tool in 3.0x better - it is easier to get to the "parts" that you are building than going through the IDE in version 4. I also like the user interface in the v 3.0x Visual Builder better - notebooks for setting values instead of the Delphi like properties list that is used in version 4.  On the other hand if you are not programming with the Visual Builder  the version 4 IDE is very nice.  It is nice to have all the functions in the project listed in a window and be able to jump directly to that function while coding.  And you  can write pure C code in version 4 - just change the file extensions  from .C to .cpp and don't write/use any C++ features and you get almost all the advantages of the IDE.

In my experience the programming editor (LxPM) bundled with version 3.0x does not work on AOS (and may not work with eCS).  However you can substitute EPM in the WorkFrame (the "ide" for version 3.0x) settings and that does work.  The version of LxPM that is bundled with version 4 does work with AOS.  While LxPM is integrated into the version 4 IDE you can execute LxPM as a standalone editor.



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