Thanks for replying Bob! It might be more appropriate for me to start a new thread given a change in circumstance regarding my PC hardware. After you read this let me know if you think I should probably do that. BTW - I'm quite surprised you still have your GedStar wineprefix!
So, some detail that may help:
My old laptop which I was using during all the previous replies on this post died. I bought a Dell XPS 17 running Windows 10 so of course GedStarPro still runs on it.
I was gifted a new Acer Chromebook for Christmas. I used MrChromebook's firmware utility to add boot legacy and boot usb support to the firmware. Running a live linux Mint 19.3 64-bit live media I installed Linux Mint 19.3 64-bit to a microSD card. So, I am running a full-blown linux Mint 19.3 installation but booted on a Chromebook instead of ChromeOS.
Over the weekend I went to winehq and followed the instructions for installing it for ubuntuMint. While still there I installed winetricks
I created my WINE-PREFIXES directory and created a LEGACY9 directory in it and installed Legacy 9 to that prefix and it runs fine as per before.
I created a GEDSTAR directory in WINE-PREFIXES as a 32-bit Windows XP prefix. I then loaded the database support as per your instruction previously in this thread:
Code: Select all
winetricks -q mdac28
winetricks -q jet40
I then instatlled GedStarPro to that prefix.
Started GedStarPro and selected the sample database. Clicked on convert data base and got the error from the program about unable to open the database and gave detail as a .cpp module.
So, I thought maybe I installed the windows C runtime environment in the previous prefix using winetricks, so I tried that now but there are no selections now for the c runtime packages.
That's where I'm at now - I hope that helps. I was thinking maybe I should start a new thread titled "GedStarPro, Chromebook running linux Mint 19.3 from microSD" but didn't know if I should do that or not. If you think that would be a good idea considering the Chromebook and booting linux Mint on it from a microSD card is quite different from the prior configuation.