开云体育

Bill Lewis wrote: [...] [...] Wow! You appear to be more on top of modern Visual Studio issues than I am, Bill! I still use the older and simpler VS2008 and have only dabbled with VS2017 and VS2019

Laddie, You can import the following configuration using Visual Studio Installer, to get the required workloads and individual components required for VS2022. Once Visual Studio Installer is running,

Read the instructions on Fish’es page?linked below.? Laddie Hanus

I'm at a loss now other than XP really you need that O/S ? Best of luck but you could send a msg in the MS community forum area may be some one will know there. Vince

I installed all the SDK’s including the on for XP Laddie Sent from whatever device I am using.

As a weak guess you might? need to install the Windows SDK that matches 2022. Vince

I get VS 2022 installed today and I could not find anywhere in the VS directories the following files From http://www.softdevlabs.com/hercules-vs2015-build.htmlThe two Property Sheets that we need to

Laddie, Changes for VS2022 support have been pushed to the SDL-Hercules-390 GitHub. Works on Windows 11 as well. Be sure to tell Windows Defender to avoid the Hercules directory or the additional time

I would like the changes but I won’t be able to do much until the weekend. Thanks? Laddie Hanus

Yes, I have tried VS2022.? It works on Windows 10.? On Windows 11 I'm still working out why some of the tests fail. But you'll need to modify a couple of the files to build with it as the repo isn't

Been rebuilding my pc after getting rid of windows 11. I am doing a clean install. Went to install visual studio express and found that the new version is visual studio community 2022. I was able to

I understand your concern, but I don't seriously think that a module *name* is going to be a legal issue with anyone if it shares the name of a licensed product. IBM is at this point well WELL aware

Ooops - I meant NOW!

Now or Not? Dave Sent: 23 November 2021 15:50 To: [email protected] Subject: Re: [h390-vm] EXECIO problem Just to say that all is no OK!

Just to say that all is no OK!

Dave, Do not give up!! Worst case scenario is to delete your copy of vm370ce and download a fresh copy. That means reapplying anything that has changed. I have done that myself more than once :-) One

Things have gone from bad to worse, much worse! CMS will no longer IPL. Looking at the Hercules log (luckily I redirected it to a file), the 6A1 disk has lots of errors: 17:39:02 HHCCU601W 06A1

Hi Dave, You have to IPL CMS in the CMSUSER machine to see the copy on the updated 190 disk. I just did this: L MAINT ENTER PASSWORD: DASD 19D LINKED R/W; R/O BY 002 USERS DASD 19E LINKED R/W; R/O BY

I followed the github steps successfully until the last bit - the COPYFILE. MAINT doesn't seem to have a 593. The rebuilt EXECIO MODULE is on MAINT's S disk - CMSDISK 190 (readonly). There's also a

Hi Olaf, That technique will not work when called from the original EXEC language. The calls to ASMAHL in GCC expect it to be a MODULE. Bob Bolch